Awhile back, I sent out an email asking for use cases where backward
compatibility was broken from 2.1. This is obviously one of those...can we
log a jira for this, so we can incorporate a test case or three to keep it
from happening again?
I've found several issues with backward compatibility si
I am running 2.2-SNAPSHOT and will try the HEAD later today.
Cheers,
Stéphane
On 11/6/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
I had the same issue (the second one you mentioned), and I think I fixed it in
revision 466968.
Are you running with HEAD? (2.2 is still at SNAPSHOT).
Let's
I had the same issue (the second one you mentioned), and I think I fixed it in
revision 466968.
Are you running with HEAD? (2.2 is still at SNAPSHOT).
Let's try to find where it broke: can you svn up -r466968 the assembly plugin
and check if that version works?
If so, it must have been broken
Hi,
I don't know if this is made on purpose but I'm really having a hard
time configuring my assembly descriptor with the latest snapshot
version of the assembly plugin (2.2).
The way dependencies are handled has really changed and I am stuck on
a simple use case.
Project A is a simple resource
