2009/12/3 Lee Thompson <[email protected]>:
>
> Dan wrote:
>> <[email protected]> wrote:
>>> I think a "codehaus-parent" would be a good idea.
>>>
>>> But remember that the "codehaus-parent" would have to enforce the
>>> noRepositories rule too (or else codehaus would have to stop pushing
>>> repository.codehaus.org to repo1.maven.org
>>
>> the enforcement of noRepositories is how the debate started. and
>> there fore no point for seperation
>
> To Dan's point, "plugin-parent" would essentially be "codehaus-parent"
> without the addition of the noRepositories rule
if it hasn't got the noRepositories rule, then IMHO, mojo-parent
should not inherit from it
>
> Stephen wrote:
>> But remember that the "codehaus-parent" would have to enforce the
>> noRepositories rule too (or else codehaus would have to stop pushing
>> repository.codehaus.org to repo1.maven.org
>
> Isn't this the mojo community supporting the maven community and an example
> of supporting a wider audience than just the mojo community?
And an example of best practice for projects syncing to repo1 is that
they have an enforcer rule to ensure they do not have any repository
definitions in their pom.xml files
> What would be the negative effect of discontinuing the push to
> repo1.maven.org?
Without the push to repo1, you would be unable to use _any_ of the
mojo plugins without adding a repository definition to your
settings.xml.
If codehaus decides to move it's repository, you have to keep things
up to date...
your build would now be slower as you have an additional repository to
search for artifacts from...
it would basically reduce the useage of the mojo plugins... and on a
wider level, it would reduce the uptake of all the codehaus hosted
projects from maven (as they would no-longer be available on repo1 -
which is the only repo that everyone has configured by default)
>
> Thanks for your thoughts in advance.
>
> Lee
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
