Berin Loritsch wrote:
Well, I checked it out using IDEA. The advantage of the new Maven integration is this:
1) IDEA can use the GUMP build scripts directly as long as you check the "Include Project ClassPath" checkbox in the ANT properties. This allows us to verify the GUMP integration build without GUMP!
depending on the content of your project classpath, of course. You'd have to cvsco and cvsup all of the required libraries, compile them, and add the results to your classpath. Otherwise there's no latest-of-everythin integration ;)
2) Even the Pre/Post goals that are in your project's "maven.xml" file will be respected. Excellent!
ehm, no? At least my IntelliJ won't read nor parse maven.xml files...
The symlink solution is still a question in my mind. I am not crazy about it, but I am also not crazy about copying source files from one Maven repo (i.e. Fortress/Container) to another's src/java directory. I tried to do it in the target/src directory, but Maven doesn't respect that.
why do you need to copy source files? Do the tools/ need access to container/ sourcefiles at runtime?
I think all that's needed to fix last night's gump failures is changing of
<depend property="excalibur-fortress-tools.jar" project="avalon-fortress-tools"/>
to
<depend property="excalibur-fortress-tools.jar" project="avalon-fortress-tools" inherit="all"/>
things are not making sense to me......
- LSD
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
