Bugzilla – Full Text Bug Listing
| Summary: | Provide JNLP (Java WebStart) support for Eclipse Features | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Kai Toedter <kai.toedter> |
| Component: | Tycho | Assignee: | Project Inbox <tycho-inbox> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | anthony.dahanne, bugs.eclipse.org, dmeibusch, dzonekl, estrnod, gregory.amerson, hoffmann.frank.germany, igor, jason, lukasz.koniecki, nyssen, olivier.prouvost, simon.goodall, strider80, zimmermann.k |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | hasPatch | ||
|
Description
Kai Toedter
As I commented on the original request, JNLP support does not belong to the main tycho source tree. tycho-extras is more appropriate. .product file better describes webstart applications, so it makes more sense to generate JNLP descriptor from .product file as opposed to feature.xml. And as a reminded, all code contributions to tycho must come as attachments to bugzilla (see [1] for more details) [1] http://www.eclipse.org/legal/EclipseLegalProcessPoster.pdf Igor,
tycho-extras would be ok.
>.product file better describes webstart applications, so it makes more sense
>to generate JNLP descriptor from .product file as opposed to feature.xml.
Most info in the .product is not needed for JNLP. But others that are not part of the .product are. So I still would prefer a feature...
IIRC, Igor said that he had something for this implemented, but it doesn't have the quality yet to go into Tycho. Maybe a "Tycho Incubator" sub-project could be a way for Igor to contribute his POC so that others can bring it to production quality. @Igor: If we set up an Incubator sub-project, would you go through the contribution process for your POC? The code I have is of production quality (has adequate test coverage and is actually used) but it has not been updated for recent Tycho versions and, obviously, will need ongoing maintanence. So the plugin is of no real use unless somebody volunteers to update the plugin to work with Tycho 0.13 and maintain it afterwards. I have opened up the source repository which contains the JNLP related code. If anyone is interested in updating this for the most recent version of Tycho they can find the code here: https://github.com/sonatype/tycho-jnlp-plugin Thanks Jason, as soon as I have a bit time, I try it. @Kai I think some changes will be required because we have not worked with this code for a while so it's using Tycho version 0.9.0. I doubt this will work with the most recent version of Tycho. We might spend on some on this in the future but we won't be doing anything for at least a couple months. But the code does work and is production quality. I've created a fork on github with a version that works against Tycho 0.13.0. https://github.com/drsgoodall/tycho-jnlp-plugin Is this something that can be merged in? For the record, tycho-jnlp-plugin is currently at github and we use Sonatype IP process to manage patches. I also merge the only pull request we had so far, so there are no outstanding patches as far as I know. (In reply to comment #9) > For the record, tycho-jnlp-plugin is currently at github and we use Sonatype IP > process to manage patches. I also merge the only pull request we had so far, so > there are no outstanding patches as far as I know. This is good - this leaves the option to move the code to Eclipse. I don't know the code: is this something we want to have in Tycho or Tycho Extras? (In reply to comment #10) > (In reply to comment #9) > > For the record, tycho-jnlp-plugin is currently at github and we use Sonatype IP > > process to manage patches. I also merge the only pull request we had so far, so > > there are no outstanding patches as far as I know. > This is good - this leaves the option to move the code to Eclipse. I don't know > the code: is this something we want to have in Tycho or Tycho Extras? Certainly not in Tycho. We may move it to Tycho Extras eventually, but I'd like to see strong user interest first before spending any time on this code. I'm very interested in this feature :) The code is there and you are welcome to use it, but, quite frankly, I do not see strong enough interest in this functionality to justify effort required to move the code to eclipse.org (or make any other changes to the code, for that matter) I am interested also, for the record. Thanks! Please avoid "+1 me too" posts but use Bugzilla's vote functionality instead. It would be very nice if an RCP + Webstart application can be built with Maven Tycho. Note that recent Java 7 updates require adding extra security entries to the manifest. See bug 421294 I misunderstood this bug report to mean that tycho-jnlp-plugin does not work at all. In fact I got it working in a toy example based on Goodall's blog at http://codeiseasy.wordpress.com/tag/jnlp/ Indeed the plugin uses only one template jnlp instead generating a separate extension jnlp like done with the PDE export wizard. For the time being I used a separate ant task to update the manifests with the new required security entries before signing the jars. It looks like someone recently created a recent pull request that does exactly this, perhaps it can be integrated? https://github.com/sonatype/tycho-jnlp-plugin/pull/2 (In reply to comment #17) > It looks like someone recently created a recent pull request that does exactly > this, perhaps it can be integrated? The tycho-jnlp-plugin is not part of the Tycho project, so this is (currently) not the right channel for such a request. This bug is for requesting JNLP-support from the Tycho project (e.g. by incorporating the Github project into Tycho), but there are no concrete plans to do this yet. Vote for this issue if you want this to be done.
> This bug is for requesting JNLP-support from the Tycho project (e.g. by
> incorporating the Github project into Tycho), but there are no concrete
> plans to do this yet. Vote for this issue if you want this to be done.
There are 11 votes, how many would you need?
JNLP/java web start is dead now AFAICT. |