| RE: [higgins-dev] command line build |
|
Hi Jim,
Yeah, for example in
org.eclipse.higgins.idas.cp.jndi
if i do "ant jar" I
get
Buildfile:
build.xml
BUILD
FAILED
D:\aDev\higgins\org.eclipse.higgins.idas.cp.jndi\build.xml:15: The following err or occurred while executing this line: D:\aDev\higgins\org.eclipse.higgins.idas.cp.jndi\buildaux.xml:18: The following error occurred while executing this line: D:\aDev\higgins\org.eclipse.higgins.idas.cp.jndi\build.xml:16: The file or path you specified (..\..\..\..\DEV\eclipse\plugins\org.eclipse.core.resources_3.2.1. R32x_v20060914.jar) is invalid relative to D:\aDev\higgins\org.eclipse.higgins.i das.cp.jndi Total time: 0
seconds
George From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim Sent: Tuesday, March 06, 2007 5:27 PM To: Higgins (Trust Framework) Project developer discussions Subject: RE: [higgins-dev] command line build George,
Are you experiencing problems with all of the build targets, or do some
(like "ant jar") work? I ask because I seem to be experiencing problems
where it complains about path issues for targets that don't even use those
aspects of the classpath. This used to work (IIRC). The goal was to
have all targets except the one that builds the eclipse plugin able to run
without eclipse even being installed.
Jim
>>> "George Stanchev" <Gstanchev@xxxxxxxxxx> 3/6/07 1:03 PM >>> I just checked the latest
eclipse2ant plugin source code and it always uses the value of the
ECLIPSE_HOME variable to
hardcode it in the ECLIPSE_HOME property value in the
generated
build.xml
I guess we're out of luck
there and we're stuck with the -D option
to get around that hardcoding...
Thanks!
From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim Sent: Monday, March 05, 2007 5:12 PM To: Higgins (Trust Framework) Project developer discussions Subject: RE: [higgins-dev] command line build >>> "George Stanchev" <Gstanchev@xxxxxxxxxx> 3/5/07 3:55 PM >>> I see. Thanks Jim, that
would fix my build problem.
However still it might be
more convinient to have
<property
environment="env" />
<property
name="ECLIPSE_HOME" value="${env.ECLIPSE_HOME}"/>
This way, it can
use the environment variable for ECLIPSE_HOME, which
always points to the
correct eclipse home, instead
of relying on the user to
supply it on the command line in the form of
-D parameter, which tend
to be tidious to type each time you run a build.
Best
Regards,
George
From: higgins-dev-bounces@xxxxxxxxxxx [mailto:higgins-dev-bounces@xxxxxxxxxxx] On Behalf Of Jim Sermersheim Sent: Monday, March 05, 2007 3:05 PM To: Higgins (Trust Framework) Project developer discussions Subject: Re: [higgins-dev] command line build George,
I assume you're running the build from the command line with no target
(like war or jar). Doing so not only requires you to have eclipse
installed, but also to run it like this:
ant -DECLIPSE_HOME=<path to eclipse installation>
The problem is that the build.xml file is generated from eclipse and it
uses the path to the eclipse install from whatever machine was used to generate
it.
Jim
>>> "George Stanchev" <Gstanchev@xxxxxxxxxx> 3/5/07 12:42 PM >>> Hi, Right now, if one updates from CVS and tries the command line build.xml for some of the higgins projects, the build fails. This is due the fact that it looks for eclipse in a hardcoded location: <property name="ECLIPSE_HOME" value="../../../../eclipse"/> Can I suggest the eclipse's home is defined using an environment variable may be - ECLIPSE_HOME which is used to specify the location for eclipse. This way I don't have to update the build.xml each time I do a full sync. I see that environment variable is declared, <property environment="env"/> it is just not used. George ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. _______________________________________________ higgins-dev mailing list higgins-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/higgins-dev |