Michael Baessler wrote:
Marshall Schor wrote:
Michael Baessler wrote:
...
The XML statement below only works if there is just one jar but not if
there is more than one.
<!-- get path to equinox jar inside ${eclipse.home} folder
(copy/rename actual jar) -->
<copy
tofile="${eclipse.home}/eclipse/plugins/org.eclipse.equinox.launcher.jar">
<fileset dir="${eclipse.home}/eclipse/plugins"
includes="**/org.eclipse.equinox.launcher_*.jar"/>
</copy>
Is it common that there is only one jar, or should we change the code
above that it also works with more than one?
If have
org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
org.eclipse.equinox.launcher_1.0.0.v20070606.jar
Yes, you are right - this "trick" is to get a common name for the
launcher; it depends on there only being one launcher jar. Any idea how
there came to be two launcher jars in your configuration?
Is there a way in Ant to specify copying just 1 of the potentially
multiple launcher jars, when you don't know the name (beyond the leading
part)?
-Marshall
Sorry I don't know much about these two jars. But it seems they come
with the eclipse update to version 3.3.1.1. Not sure if both are
required or not.
Does anyone else see those two jars?
-- Michael
I have several Eclipse 3.3 installations, and I always have either the
one jar, or the other. However, maybe you get a newer one when you do
an update via Eclipse itself?
--Thilo
