History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: MPANT-21
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Arnaud Heritier
Reporter: Chuck Daniels
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1.x Ant Plugin

get-deps target should download to local maven repo

Created: 01/Dec/04 11:44 AM   Updated: 26/Feb/05 06:45 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 1.9

Time Tracking:
Not Specified

Environment: All


 Description  « Hide
The get-deps target downloads dependencies to target/lib. This is problematic since it forces downloads to occur after a 'clean' is performed. I suggest downloading to the local maven repository, regardless of whether or not maven has been installed. This avoids unnecessary downloads after a 'clean' and also makes migration to maven easier. Once a user migrates to maven, dependencies will already exist in the local repo.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Arnaud Heritier - 01/Dec/04 05:57 PM
It seems to be a good idea. I'll investigate it.

David Eric Pugh - 02/Dec/04 05:58 AM
I thought about doing this, but I don't believe that the get-deps does all the stuff that the maven version does in terms of detecting resources? Also, how do you figure out what the maven local repo is if they aren't using Maven? I guess you could do something conditional.

Chuck Daniels - 02/Dec/04 06:51 AM
What do you mean by "detecting resources"? As far as I know, maven doesn't do anything with respect to resources when it is dealing with dependencies.

As far as the location of the local maven repository goes, maven doesn't have to be installed in order to determine where a local repository would be. Just use the default, which is ${user.home}/.maven/repository. I would be surprised if the majority of maven users use something other than this. You could even add a property (say maven.ant.local.repo) to the maven ant plugin that would allow you to override this default value.

Even if a user of the generated ant script were to migrate to maven and use a different location for their local maven repository, at least while they use the ant script they would avoid re-downloading all dependencies after doing a 'clean' (which deletes target/lib).

I don't see any harm in using ${user.home}/.maven/repository instead of target/lib, and users of the ant script avoid the annoyance of re-downloading dependencies after a 'clean'.


Arnaud Heritier - 26/Feb/05 06:45 PM
Fixed.