[
http://jira.codehaus.org/browse/NMAVEN-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116451
]
Shane Isbell commented on NMAVEN-95:
------------------------------------
I took a look at the check in. I think that it will get things working but we
shouldn't be using the dotnet version of the maven-deploy plugin anymore. I
checked around and their is another bug in the components.xml file under the
library lifecycle mapping. It's coded to use the dotnet one, rather than the
standard Maven one. This needs to be changed
<deploy>
org.apache.maven.dotnet.plugins:maven-repository-plugin:convert-artifact,
org.apache.maven.dotnet.plugins:maven-deploy-plugin:deploy
</deploy>
to
<deploy>
org.apache.maven.dotnet.plugins:maven-repository-plugin:convert-artifact,
org.apache.maven.plugins:maven-deploy-plugin:deploy
</deploy>
and then NMaven.Model.Pom and NMaven.Model.Pom should use the standard deploy
plugin.
> artifacts in the GAC should be deployed to the repository with their public
> token key id
> ----------------------------------------------------------------------------------------
>
> Key: NMAVEN-95
> URL: http://jira.codehaus.org/browse/NMAVEN-95
> Project: NMaven
> Issue Type: Bug
> Affects Versions: 0.14
> Reporter: Brett Porter
> Assignee: Brett Porter
> Fix For: 0.14
>
>
> NMaven.Model.Pom and NMaven.Plugin both require their key in the remote
> repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
