[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[buckminster-dev] Problems with creating JNLP build of eclipse RCP product
|
Hello all,
while investigating in creating a Java Web Start package from an Eclipse
RCP product with Buckminster, we found that the generated JNLP file for
the wrapper feature references the JNLP files for the dependent features
with a wrong href-location.
The structure generated by Buckminster looks like this:
- features
o feature1.jar
o feature2.jar
o …
- plugins
o plugin1.jar
o plugin2.jar
o …
- wrapper.jnlp
- feature1.jnlp
- feature2.jnlp
Whereas in the wrapper.jnlp file the feature1.jnlp and feature2.jnlp
files are referenced as
<extension … href=”features/feature1.jnlp” />
<extension … href=”features/feature2.jnlp” />
There was a short discussion on this topic a while ago via the list
buckminster-dev where the same problem has occurred. Please let me know
if someone can tell me about the current state of the JNLP generation in
Buckminster. We are about to create an EAR of our Java EE application
with an Eclipse RCP client that we would also like to build via
Buckminster. We can already build the RCP product with Buckminster on
Hudson and have now almost succeeded in build ing a Web Start version.
So we are almost there but this seems to be a show stopper…
Btw, we are using the latest 3.6 version (pulled in automatically via
Buckminster/Hudson integration).
Thanks,
Martin Klinke
PS: For your reference, the original messages on the list are
http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg00950.html,
http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg00988.html and
http://dev.eclipse.org/mhonarc/lists/buckminster-dev/msg00989.html.
PPS: I have also sent this to the mailing list, sorry for bothering you
if this is not the right place to ask.
