You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Tomislav Bodor (JIRA)" <ji...@codehaus.org> on 2005/11/13 17:52:06 UTC

[jira] Created: (MNG-1544) Attached artefacts not handled

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


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


[jira] Updated: (MNG-1544) Attached artefacts not handled

Posted by "Tomislav Stojcevich (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1544?page=all ]

Tomislav Stojcevich updated MNG-1544:
-------------------------------------

    Attachment: MNG-1544-maven-artifact-ant.patch
                MNG-1544-site.patch

> Attached artefacts not handled
> ------------------------------
>
>          Key: MNG-1544
>          URL: http://jira.codehaus.org/browse/MNG-1544
>      Project: Maven 2
>         Type: Bug

>   Components: Ant tasks
>     Versions: 2.0
>     Reporter: Tomislav Bodor
>      Fix For: 2.1
>  Attachments: MNG-1544-maven-artifact-ant.patch, MNG-1544-site.patch
>
>
> 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


[jira] Commented: (MNG-1544) Attached artefacts not handled

Posted by "Tomislav Bodor (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1544?page=comments#action_50810 ] 

Tomislav Bodor commented on MNG-1544:
-------------------------------------

Alternatively, a nested fileset could be added to install and deploy tasks... Then the attachments would not be handled the 'maven way', but more the 'ant way'. Since maven plugins cannot be executed in this mode anyway, perhaps there is no need to support the proper attachments.

> 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

>
>
> 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


[jira] Updated: (MNG-1544) Attached artefacts not handled

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ 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