Brett Porter wrote:
Trygve mentioned the repo code wasn't needed in the appassembler plugin
any more. I've isolated and deprecated the repository generation code
rather than removing it at this point, though.
Also, I'm wondering about the different types of repositories.
The Maven assembly plugin supports generating a flat directory with this:
<dependencySets>
<dependencySet>
<outputDirectory>lib</outputDirectory>
</dependencySet>
</dependencySets>
and a Maven2 repository with this:
<repositories>
<repository>
<outputDirectory>repo</outputDirectory>
</repository>
</repositories>
But the latter does not support generating a Maven1 repository.
Is there a use case for needing this in the appassembler plugin, or is
it a future need (in which case we should probably file an issue in the
assembly plugin)?
To me the only useful layouts are the Maven 2 layout and the lib/
layout. The appassembler plugin came in existence long after Maven 2 was
released and no one us using it with Maven 1 projects. There are tools
and libraries to work with Maven 2 repositories, but hardly any for
Maven 1 libraries.
Kill the Maven 1 goop and if requested we can add it back in both the
appassembler and the assembly plugins.
--
Trygve
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
