On 05/12/2012, at 11:24 AM, Daz DeBoer <[email protected]> wrote:
> G'day
> I'm adding 'mvn install' type support to the new 'maven-publish' plugin. Just
> wanted to confirm some behaviour:
> Should we _always_ try to install to maven local repo when publishing to a
> remote maven repository.
We are already doing this, and have no choice. You can't make the maven ant
tasks not do this. We have a JIRA for this with some comments.
> So 'publish' with the 'maven-publish' plugin will combine the current
> 'deploy' and 'install' of the 'maven' plugin. I think this makes sense, as it
> matches the behaviour of 'mvn deploy'. An alternative would be a separate
> lifecycle task for 'maven-install'.
> What should happen if the 'maven-publish' plugin is used without a local
> maven installation? I assume that we should just skip the 'install' step in
> this case.
Because it's out of our control, not sure what we can do.
> What should happen if there is a problem parsing the local maven
> settings.xml? I suggest we emit a warning and continue.
