I found we can fix this with a new feature of Ant 1.7.0 - the <first ...
> element (part of a new thing called Resource Collections).
That would make ant 1.7 a prereq, though.
-Marshall
Michael Baessler wrote:
I tried to do a clean build, but it doesn't work. The error is
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: The following error occurred while executing this line:
D:\code\eclipse330\apache\uimaj-eclipse-update-site\build.xml:65:
Cannot concate
nate multiple files into a single file.
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
-- Michael
Marshall Schor wrote:
The changes I'm checking into our SVN include as part of the
"assembly" step, running your Eclipse to optimize and package the
eclipse update site (this optimization is significant both in terms
of size and space - for instance, the uima-core jar file (one of our
bigger ones) shrinks to about 1/3 it's former size).
In order to run this, the update-site build script (an ant task run
via the maven ant-run task) needs to know where there is an Eclipse
installed it can use.
It finds this out by looking for a maven property. You need to set
this maven property in a "settings" file. This is a file in your
".m2" directory (in windows, under documents&settings/<userid>/.m2).
Here's my settings file to use as a prototype, if you don't have one
already; the property is set to the path where Eclipse is installed.
You can add other things to the settings file - useful if you do
"deploys" to remote maven repositories. For more on settings, see
http://maven.apache.org/settings.html
<settings xmlns="http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
<profiles>
<profile>
<id>local-build-configuration</id>
<activation>
<activeByDefault>true</activeByDefault>
</activation>
<properties>
<uima-maven-build-eclipse-home>c:/p/eclipse/3.3Apache</uima-maven-build-eclipse-home>
</properties>
</profile>
</profiles>
<activeProfiles>
<activeProfile>local-build-configuration</activeProfile>
</activeProfiles>
</settings> -Marshall
