Stephen Connolly <[email protected]> wrote:
> If it is an example of best practice and it is ending up on repo1, it should
> enforce the best practices of repo1,
> i.e. it should help people comply with the rule for repo1
> (http://maven.apache.org/guides/mini/guide-central-repository-upload.html)
>
* > I have other repositories or pluginRepositories listed in my POM,
is that a problem?
>>
>> Yes,
>the central repository must be self contained, which means that all
>your dependencies must already be in the
>> central repository. You need
>to remove the repositories and pluginRepositories entries and make sure
>> your project still builds when your local repository cache is empty.
>>Thanks for that, I'm starting to get clear on this now. I think a
>>"plugin-project" archetype separate from mojo-parent is the way to go at this
>>point. The "plugin" archetype which already exists would be minimal project
>>infrastructure and "plugin-project" would be almost the same but include
>>similar plugins/reports/lifecycle as mojo.
