You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Herve Boutemy (JIRA)" <ji...@codehaus.org> on 2007/05/29 16:44:59 UTC

[jira] Updated: (MANTTASKS-29) more powerful filesetId

     [ http://jira.codehaus.org/browse/MANTTASKS-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Herve Boutemy updated MANTTASKS-29:
-----------------------------------

    Attachment: MANTTASKS-29_site.diff
                MANTTASKS-29.diff

Here is a new patch for a VersionMapper, with corresponding documentation.

Here si the typical use case (taken from the documentation):

{code:xml}
<artifact:dependencies filesetId="dependency.fileset"
        sourcesFilesetId="sources.dependency.fileset" versionsId="dependency.versions">
...
</artifact:dependencies>
<copy todir="lib">
  <fileset refid="dependency.fileset" />
  <mapper classpathref="maven-ant-tasks.classpath" classname="org.apache.maven.artifact.ant.VersionMapper"
          from="${dependency.versions}" to="flatten" />
</copy>
<copy todir="lib/src">
  <fileset refid="sources.dependency.fileset" />
  <mapper classpathref="maven-ant-tasks.classpath" classname="org.apache.maven.artifact.ant.VersionMapper"
          from="${dependency.versions}" to="flatten" />
</copy>
{code}

> more powerful filesetId
> -----------------------
>
>                 Key: MANTTASKS-29
>                 URL: http://jira.codehaus.org/browse/MANTTASKS-29
>             Project: Maven 2.x Ant Tasks
>          Issue Type: New Feature
>            Reporter: Dave Brondsema
>            Priority: Minor
>         Attachments: MANTTASKS-29.diff, MANTTASKS-29_site.diff, maven-ant-tasks_mapper-2.patch, maven-ant-tasks_mapper.patch
>
>
> I would like to copy all dependencies into a 'lib' directory without version numbers in the filename. I don't think I can safely determine which part of the filename is the artifact and which part is the version number.  Only maven knows that, so I think the m2 ant tasks need something more flexible than the current filesetId.
> Brett Porter suggests:
> Basically, filesetId references the local repository directory, so it
> will need to be something that:
> 1) produces a reference to all the artifacts downloaded for use later
> 2) can be used as a mapper in association with the filesetId produced

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