You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Shane Isbell (JIRA)" <ji...@codehaus.org> on 2007/12/15 07:48:58 UTC
[jira] Closed: (NMAVEN-19) Dependency resolution and Maven
integration (site, deploy)
[ http://jira.codehaus.org/browse/NMAVEN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shane Isbell closed NMAVEN-19.
------------------------------
Resolution: Fixed
> Dependency resolution and Maven integration (site, deploy)
> ----------------------------------------------------------
>
> Key: NMAVEN-19
> URL: http://jira.codehaus.org/browse/NMAVEN-19
> Project: NMaven
> Issue Type: Wish
> Reporter: Alexandre Garcia
> Attachments: components.patch
>
>
> First of all Shane, we really appreciate your effort.
> We tried to complement your packaging lifecycles in order to test site and deploy
> The Maven plugins site and deploy use the standard Maven artefact layout: ArtefactId-Version.dll
> We were able to use mvn site after renaming accordingly installed artefacts in the local repo ($reports is not expanded though).
> We rebuilt NMaven after altering NMaven\plugins\maven-compile-plugin\src\main\resources\META-INF\plexus\components.xml to include the deploy phase in the packaging lifecycles.
> The deploy phase is successful but is once again maven style.
> Unfortunately, the deployed artefacts cannot be downloaded because NMaven dependency resolution doesnot include the version suffix and hence doesnot find the artefact on the remote repo.
> More generally, i wish NMaven could adopt default Maven style artefact layout or a mixed mode for GAC dependencies.
> We attach the modified components.xml
--
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