while investigating in creating a Java Web Start package from an Eclipse RC=
P product with Buckminster, we found that the generated JNLP file for the w=
rapper 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

There was a short discussion on this topic a while ago via this list where =
the same problem has occurred. Please let me know if someone can tell me ab=
out the current state of the JNLP generation in Buckminster. We are about t=
o 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 p=
roduct with Buckminster on Hudson and have now almost succeeded in build in=
g a Web Start version. So we are almost there but this seems to be a show s=
topper...

Btw, we are using the latest 3.6 version (pulled in automatically via Buckm=
inster/Hudson integration).

<p class=3DMsoNormal><span lang=3DEN-US>while investigating in creating a J=
ava Web
Start package from an Eclipse RCP product with Buckminster, we found that t=
he
generated JNLP file for the wrapper feature references the JNLP files for t=
he
dependent features with a wrong href-location.<o:p></o:p></span></p>

<p class=3DMsoNormal><span lang=3DEN-US>There was a short discussion on thi=
s topic
a while ago via this list where the same problem has occurred. Please let m=
e
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 almos=
t succeeded
in build ing a Web Start version. So we are almost there but this seems to =
be a
show stopper&#8230; <o:p></o:p></span></p>