I realize I'm bumping a VERY old thread at this point, but I'm
completely unsuccessful in tracking down the error here (even with -x
and -e on).

I'm also seeing the ejbs rebuilding every time (recompiling the source
with each pass).

How are people making ear files with maven two?  Is there some sort of
textual layout I could look at?  I'm totally losing it.

I've read and re-read (and we followed their example very closely) the
better builds with maven pdf. 

-----Original Message-----
From: Wayne Fay [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, February 07, 2007 4:02 PM
To: Maven Users List
Subject: Re: compile tries to bundle up the ear - should it?

Unfortunately, you've completely exhausted my knowledge of Maven, and
I have no response to your queries at this point.

Perhaps try debugging Maven while it is executing your EAR compile and
you'll find out... You might even uncover a bug.

Wayne

On 2/7/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> Ok, my final attempt - why would there be code inside maven that sees
an
> "packaging" type of ear and decide there's something to do during the
> compile lifecycle goal.
>
> What purpose could this serve?
>
> -----Original Message-----
> From: Wayne Fay [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, February 07, 2007 2:49 PM
> To: Maven Users List
> Subject: Re: compile tries to bundle up the ear - should it?
>
> I also spend a bit of time working at the top most level...
>
> I just ran my test again (jars etc named to jarx in local repo) and
> had no problems running "mvn clean compile" from my parent directory.
> Everything ran straight thru and I got a BUILD SUCCESSFUL at the end.
>
> One possible thought is that you are basically dirtying your project
> files etc with the p4 sync, so Maven thinks it has to recompile all
> the files etc in all the modules instead of just the EAR (?). I don't
> use SCM with Maven so I don't know much about that, just a thought.
>
> Wayne
>
> On 2/7/07, EJ Ciramella <[EMAIL PROTECTED]> wrote:
> > No, my question is still unanswered.
> >
> > I guess what I'm looking for is for those working at the top most
> level,
> > is it expected that if you want to compile, you must build an ear?
> >
> > So for anyone who does an install, p4 sync, compile - they can
expect
> to
> > see errors unless they do an additional install?
> >
> > -----Original Message-----
> > From: Wayne Fay [mailto:[EMAIL PROTECTED]
> > Sent: Wednesday, February 07, 2007 2:14 PM
> > To: Maven Users List
> > Subject: Re: compile tries to bundle up the ear - should it?
> >
> > 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]
> >
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to