Can we have a filesetid attribute, to create a fileset for the downloaded files?

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0
  • Component/s: None
  • Labels:
    None
  • Environment:
    ant1.7alpha

Description

The artifact tasks create path, which feeds in to things like <javac> and <java>. But not into <copy>, <zip>, etc, etc. If the task could take a fileset ID and create a fileset on demand, that would simplify integration with the rest of the ant system.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Brett Porter added a comment -

is a filelist sufficient?

If you want a fileset, can you recommend how these are usually constructed?

I've implemented it like so:

fileSet.setDir( localRepository.getLocation() );
// for each dependency
fileSet.createInclude().setName( filename );

ie, not flattened. If you'd prefer a filelist or something different, please reopen.

Show
Brett Porter added a comment - is a filelist sufficient? If you want a fileset, can you recommend how these are usually constructed? I've implemented it like so: fileSet.setDir( localRepository.getLocation() ); // for each dependency fileSet.createInclude().setName( filename ); ie, not flattened. If you'd prefer a filelist or something different, please reopen.
Hide
Permalink
Anders Harrisson added a comment -

Very nice feature!
I was hoping the fileset would be (or optionally be) flattened though. That would really simplify the use of the dependencies when creating a lib-contract for a war-task - allowing direct use of the dependency-reference there. I can see the use of having the complete directory-tree of the artifact-groups at some level, but I am having a real hassle flattening the filesets. Is this issue functioning as designed, or will it be developed further?

Show
Anders Harrisson added a comment - Very nice feature! I was hoping the fileset would be (or optionally be) flattened though. That would really simplify the use of the dependencies when creating a lib-contract for a war-task - allowing direct use of the dependency-reference there. I can see the use of having the complete directory-tree of the artifact-groups at some level, but I am having a real hassle flattening the filesets. Is this issue functioning as designed, or will it be developed further?

People

  • Assignee:
    Brett Porter
    Reporter:
    Steve Loughran
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: