Issue Subscription
Filter: Design & Best Practices (28 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
Can you avoid cross posting? I went to reply to this on d...@mojo and
it had the reply-to of this list as gmail merges the messages.
If you aren't getting the answers you're seeking on d...@mojo you can
post here to point people at it, but cross posting in general is kinda
evil :)
Thanks,
I don't think that's really practical if you are tightly integrated with a
project that has a non-maven build. We have some projects with Ant builds that
regularly need to be integrated and tested with Maven built projects. So it
might mean deploying a release version once a day in some cases.
OK, here is the problem set:
For animal-sniffer, we need to have signatures of each of the java runtime
libraries (i.e. the animal smells/scents)
That way animal-sniffer can detect whether you are compatible with a
specific java runtime library.
Initially I was going to have these signatures as
>From my point of view you can't have SNAPSHOTs of things not built
with Maven. Just give them a release version, anything without
SNAPSHOT and go with it. I would typically use the svn rev if i
grabbed code, or some other id like a date.
On Wed, Sep 16, 2009 at 11:01 AM, Paul Gier wrote:
> Anoth
