The build files have hard coded paths in them which makes it kind of hard to work
with. Here is some modifications to get rid of the hard coded files.
In the top of the file add:
<path id="eclipse.plugins.libs">
| <fileset dir="${eclipse.home}/plugins" includes="**/*.jar"/>
| </path>
Also... why is does it not fail on javac error? That seems like it is dangerous and
can cause confusion.
I then broke out the classpath for the javac task:
<javac destdir="/org-jboss-ide-eclipse-core.jar.bin" failonerror=""
verbose="" debug="" includeAntRuntime="no" bootclasspath="">
| <src path="src/"/>
| <classpath>
| <path refid="eclipse.plugins.libs"/>
| <pathelement
path="../org.apache.xalan/bin;../org.apache.xalan/xalan.jar;../org.apache.xalan/xercesImpl.jar;../org.apache.xalan/xml-apis.jar"/>
| </classpath>
| </javac>
with a path refid for the plugin libs, and then a pathelement for any other jars that
are required.
This should work in most any environment--just make sure the eclipse.home property is
set. If you're inside eclipse, this should be done for you.
You have to make the above changes to the build.xml files in all projects except
feature.
There is more that could be done in the build files (remove all the duplication) but
this should help to get rid of the hard coded paths so anyone can build.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3830410#3830410
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3830410
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
JBoss-Development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
