Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-ide-wg] Minutes of May 3rd Eclipse IDE WG Steering Committee Meeting

Christoph,

A reply that starts with "but" sounds like a contradiction is coming right up. :-P  But I think you are just agreeing that the primary use case is in a target platform.

That being said, I'm not sure what exactly this "user/developer" would do with such an update site:

https://www.eclipse.org/forums/index.php?t=msg&th=1110394

Likely he wants to include these additional things not provided/used by Eclipse in his own update site.


On 19.05.2022 09:51, Christoph Läubrich wrote:
Hi Ed,

but for what purpose? If I install the jetty bundles in my eclipse simply nothing would happen ... I still would require additional plugin to do something useful, configure the jetty-osgi and so on.

So most of the time I would have a project and that includes the jetty bundles in their target, add some bundles, and features and publish that as an update-site I could use to install some new cool feature into my IDE.

And that's what this update-site is meant for. It enables consumers of the jetty-bundles in the p2 eco-system to include them in their builds/targets so it is not really an end-user thing I would send over to a random user who asks for web-server support in eclipse IDE :-)


Am 19.05.22 um 09:41 schrieb Ed Merks:
Christoph,

Yes, I doubt many folks would install directly from such a site, but many folks would use it in their target platform.  After all, what is the intended consumer of this Jetty p2 site if it's neither of these?

There is often a tradeoff between the production side of things where "no one really was interested in making such efforts" versus the consumption side where the absence of such "saved" efforts  is disruptive and creates additional work for many people (and then in total, there is more work).  If only the many more people actually contributed just one little iota towards the commons...

On 19.05.2022 09:24, Christoph Läubrich wrote:
Hi Ed,

the jar URL is really not meant to be used here. For the mvn protocol to work, m2e currently needs to be activated once, I'm working hard to get away this limitation and thanks to the recent changes in resources-plugin this hopefully will be fixed with the next release.

For now, if you not try to add this page via "Update Sites" (I assume no one really likes to install jetty *inside* eclipse) this activation should happen as soon as you open the target editor and hit the "Add" button (or earlier if you already has maven items in your target).

I found the "eclipse forum" a really bad place to ask questions, most of the time one don't get any response and I don't look at it myself, so mailinglist and hopefully soon github discussions are maybe more profitable to redirect users on the long term for such questions.

Beside the jetty documentation, I think the best is to just open a ticket at the jetty repo and then they can add a note.

As mentioned, there was an issue with PGP in a previous release so pgp signing is disabled, but as this is fixed now the next release will contain signatures again I already opened a ticket [1] and encourage everyone to help testing so we can get this part working without any additional effort in the future.

Her again, I think no one will install jetty "as-is" into a running eclipse, so there is still the opportunity to sign the used items in the site of the project as Mickael has described.

Sure one might want to create a mirror or similar, but jetty has stopped publishing a site in the past because no one really was interested in making such efforts, so I think the most future-proof is to get this feature "smooth" (hint: test it / use it / report problems) so we do no longer need to care about.

[1] https://github.com/eclipse/jetty.project/issues/8021


Am 19.05.22 um 08:51 schrieb Ed Merks:
Christoph,

Previously I'd tried this approach:

jar:https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-p2/11.0.9/jetty-p2-11.0.9-p2site.zip!/

That loads the content such that one can select it, but then fails because of this

java.net.MalformedURLException: unknown protocol: mvn
     at java.base/java.net.URL.<init>(URL.java:652)
     at java.base/java.net.URL.fromURI(URL.java:719)
     at java.base/java.net.URI.toURL(URI.java:1116)
     at org.eclipse.ecf.provider.filetransfer.identity.FileTransferID.getURL(FileTransferID.java:80)
     at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:879)
     at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:148)
     at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:456)
     at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:386)
     at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:107)
     at org.eclipse.oomph.p2.internal.core.CachingTransport.download(CachingTransport.java:136)
     at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:748)
     at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:672)
     at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:804)
     at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:329)
     at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:299)
     at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:232)
     at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:162)
     at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:787)
     at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:64)
     at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)

The mvn:org.eclipse.jetty:jetty-p2:11.0.9:zip:p2site URL fails the same way although before loading.  When I debugged I found that the mvn protocol is only registered if the right bundle is started, but that doesn't happen automatically; visiting the Maven preferences helps.

In older versions I tested in the past, the PGP signatures were rejected, but it seems this version doesn't have such signatures:

When a  user asked about this on the newcomers forum, nobody had an answer for them and when I went hunting, this site was not helpful in discovering such an answer when I looked:

https://www.eclipse.org/jetty/download.php

It would be trivially easy to create a mirror that doesn't rely on additional things being installed (and being activated in some way)...

On 19.05.2022 07:33, Christoph Läubrich wrote:
Just noticed the part about "a proper p2 repo for Jetty would be nice"

There actually is already a p2 repository from jetty, you can add the following URL to your target (requires m2e installed) as an Update-Site:

Jetty 10:
 mvn:org.eclipse.jetty:jetty-p2:10.0.9:zip:p2site

Jetty 11:
 mvn:org.eclipse.jetty:jetty-p2:11.0.9:zip:p2site

See here for available versions:
https://mvnrepository.com/artifact/org.eclipse.jetty/jetty-p2

This includes all jetty bundles and you can select the ones you like. Next release of jetty will also contain PGP signatures again (there was a bug in the previous Tycho release that is fixed now).


Am 18.05.22 um 19:56 schrieb Pradeep Balachandran:
The minutes of the Steering Committee meeting held on May 3^rd was unanimously approved in this week’s meeting and the same has been attached.

Thanks,

Pradeep


_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg

_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg
_______________________________________________
eclipse-ide-wg mailing list
eclipse-ide-wg@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/eclipse-ide-wg

Back to the top