You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2005/11/22 09:33:11 UTC
[jira] Updated: (MNG-1544) Attached artefacts not handled
[ http://jira.codehaus.org/browse/MNG-1544?page=all ]
Brett Porter updated MNG-1544:
------------------------------
Fix Version: 2.1
> Attached artefacts not handled
> ------------------------------
>
> Key: MNG-1544
> URL: http://jira.codehaus.org/browse/MNG-1544
> Project: Maven 2
> Type: Bug
> Components: maven-artifact-ant
> Versions: 2.0
> Reporter: Tomislav Bodor
> Fix For: 2.1
>
>
> The install and deploy tasks don't seem to be able to handle attached artefacts. There appear to be two sides to the problem: first, there seems to be no way to attach anything, and second, even if it were attached, the install and deploy tasks don't do anything with attachments.
> The latter could be solved by adding to the install (and similar to the deploy) task something along the lines of (similar to the InstallMojo in the install plugin):
> List attachedArtifacts = pom.getMavenProject().getAttachedArtifacts();
> for (Iterator i = attachedArtifacts.iterator(); i.hasNext(); ) {
> Artifact attached = (Artifact) i.next();
> installer.install(attached.getFile(), attached, localRepo);
> }
> For the former (how to attach anything), a new task could be added (say, 'attach', taking a type, classifier and file).
> This functionality is needed to handle source archives and EJB client jars.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org