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
