> > With XMvn this kind of change doesn't require changes
> > packages,
> > just approving by Java SIG and implementing this in XMvn itself.
> > That's one of great advantages of not installing files manually
> > but letting a specialized tool care about file installation.
> Note that we need to handle Ant builds too.
My 2 cents - I suffer enough from maven central containing random
stuff under random groupId:artifactId so if upstream doesn't ship
pom.xml to define the groupId:artifactId, putting jars in maven repo
like structure can only make things worse for cases where upstream
hasn't thought about that at all.
I think we are talking about packages that already have POMs. Maven
unaware packages can still install stuff in %_javadir.