On Sun, 2006-02-12 at 04:36, Adrian Brock wrote: > I still don't know how to make this compile within Eclipse? > i.e. > Without a standard location for thirdparty how do we share the > Eclipse project descriptors? > Although, I believe Maven has a task to generate them locally > rather than sharing them, I don't currently know how to do this.
This is relatively trivial, you just use mvn eclipse:eclipse to generate the files, as long as you have a compiler property set M2_REPO=~/.m2/repository But the project structure is broken for this. e.g. the pom.xml says the common project is called "jboss-common" so it cannot find. It is a directory called just plain "common". I have no idea why eclipse:eclipse requires a full build? i.e. download and compile. The information it needs is in the pom.xml I can see this being tortous, especially when people like the webservices project change their project structure/dependencies at a rate of 600 MHz. :-) On the Maven/Eclipse plugins from Codehaus. * The main ide plugins only seem to support Maven 1.x * I have no idea what the new plugin does, the one referenced from the Maven site. The only docs are in flash demos! The only option that seems to do anything is the "update sources" which just has the affect of munging your .classpath :-) -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
