Community
Participate
Working Groups
discussed with angel vera... opening issue here http://download.eclipse.org/jetty/updates/jetty-wtp That is the url of the jetty wtp plugin. It is a composite p2 repo so we can make releases behind the scenes and not influence the url... we also have the CI publishing to http://download.eclipse.org/jetty/updates/jetty-wtp/development but I suspect that is not something that you would want to expose to the wst discovery...unless you have some cutting edge version of things that people were used to using, then we could tie into that. I am working on getting the docs into the wiki now before we officially release the plugin but I figured I would get you the url now.
Created attachment 184732 [details] exception from 1st URL Jesse, I try adding: http://download.eclipse.org/jetty/updates/jetty-wtp but nothing showed up in the additional servers, so I then tried your URL using the 'Help' -> 'Install New Software' and it didn't work either. For that I got the following attached exception.
odd, it installed correctly into eclipse I'll dig into it a bit more
Can you give it another whirl? I just deployed a new release of the plugin and updated the composite repository xml files... It installed fine into a clean eclipse instance for me as well. cheers, jesse
changes committed to HEAD (3.3)
Jesse, I have committed the changes to 3.3 but I am still not seeing the server under the download additional adapters section, adding the URL doesn't hurt the framework, thus I have added. But your server still doesn't show. We can continue the investigation of it by email, I would suggest creating a bug on your side to track down the problem.
* Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. Without this change the server adapter won't be available through the "download additional adapter" ui * Is there a work-around? If so, why do you believe the work-around is insufficient? Yes, but is a bit convoluted for the user. * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? I tested that eventhough the URL is not working, it doesn't affect any other function and the product is still usable, once the URL becomes active the server should be available and downloadable as any of the other servers. * Give a brief technical overview. Who has reviewed this fix? The change is just adding a URL to a xml file * What is the risk associated with this fix? The worst it can happen is that the XML is no in the right format, but I have checked that the URL is proper format and the loading of the xml still works and all the other URLs (for the other server adapters) are still working
I'm assuming the URL and changes on our end are correct, and expect teams to work together to make sure it displays correctly. Thanks!
Changes committed to 32M
Changes released to 32M
