EJ, based on this response, does this mean that your issue can be considered "fully resolved" or are there other issues?
As for the install question -- yes, I have previously executed "mvn install" to copy these artifacts to my local repo. The way I work, I am generally only working inside one module at a time, so I can run "mvn install" to copy all the other artifacts into my repo, then go into the specific module to do my edits etc and run "mvn compile" in that artifact alone, which will use the other unedited dependent artifacts out of my repo if needed. As for "why does Maven EAR plugin require all artifacts be available during compile" -- I'm pretty sure this just happens automatically during validate phase, which happens before compile, so when those artifacts are not available to validate, you never get to the compile phase. Wayne On 2/7/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
Well I figured out why the ejbs continue to recompile - their package name doesn't reflect their location in main/java. -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 07, 2007 1:38 PM To: Maven Users List Subject: RE: compile tries to bundle up the ear - should it? Wayne - did you do an "install" to get them into your local repository? My problem is compile tries to build an ear. In all my years of release engineering, compile has meant "turn source code into byte code". Nothing more, nothing less. To have compile build an ear (which needs a war and ejbs) seems backward to me. Add to this that a standard compile took 58 seconds. Due to the other things that have to get run (namely the atg assembler), in order to get everything built and installed into our local repository, we need to run "mvn install" from the top level. This takes 13 - 15 minutes. That just isn't going to work.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
