Hi Kenney,
On 14/09/2007, at 9:15 PM, Kenney Westerhof wrote:
Hi,
I sent a mail a few days ago but it didn't make it to the list.
One very important feature would be the separation of build artifacts
(maven plugins and their dependencies), and project artifacts.
The separation isn't clear in maven itself - repo's get mixed up,
wrong repo's consulted; build artifacts interfering with plugin
artifacts.
Having a separate directory containing information on what build
artifacts
are used makes it easy to freeze a maven environment, and see what
was used runtime.
Also see [1], which you, Brett, weren't in favour of back then.
Perhaps
now this can be taken into consideration with this proposal.
[1] http://jira.codehaus.org/browse/MNG-724
I definitely like the idea of separating the different contexts of
the build (plugin/extension) dependencies from the project
dependencies. I think this is most important for the metadata and
snapshots - I don't think we need duplicate copies of plexus
container releases, etc floating around in the local repository.
This will help to some extent by already separating some things out
(in particular the ability to have a different place for locally
built plugins) - but plugins that come from the same place as other
artifacts will still be grouped together.
How would you like to see that worked out in practice -
pluginRepositories and build extensions stored separately? Or do you
think that with the other plugin lockdown/enforcer uses enough can be
achieved already?
Cheers,
Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
