maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@codehaus.org
Subject [jira] Commented: (MNG-47) Reorganize maven-artifact code splitting it up between maven-project and wagon proper
Date Thu, 22 Jul 2004 18:52:11 GMT
The following comment has been added to this issue:

     Author: Jason van Zyl
    Created: Thu, 22 Jul 2004 2:52 PM
       Body:
Another reason for doing is the control from the client code how things like offline mode
might work or any other notions that might be created in client code.
---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MNG-47?page=comments#action_22108

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-47

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-47
    Summary: Reorganize maven-artifact code splitting it up between maven-project and wagon
proper
       Type: Task

     Status: Unassigned

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:
             1.0-alpha-1

   Assignee: 
   Reporter: Jason van Zyl

    Created: Thu, 22 Jul 2004 2:16 PM
    Updated: Thu, 22 Jul 2004 2:52 PM

Description:
What maven 2.x needs specifically in terms of artifact handling is relatively small so the
small parts of maven-artifact that are pertinent to maven should be moved into maven-project.
But there are some notions that are currently in maven-artifact that are of general use in
Wagon.

For example we have an artifact downloader and artifact resolver which are tools that would
be relevent to projects like Plexus where we want to pull down the dependencices for a particular
component. Plexus could either use things like the artifact downloader and resolver directly
or be passed a live instance in order to integrate with client code. So Maven would already
have configured a downloading mechanism based on Wagon and this we would like to pass to Plexus
for use because we want the same policies being used when downloading dependencies for a project
as downloading the dependencies of a component.

So I think what we would end up is having something like the artifact resolver which uses
a downloader and executes various policies as desired: in our case we have special behavior
for snapshots and JAR overrides. We should be able to easily decorate the standard behaviour
of the download mechanism for Maven's purposes and to make adding addition behaviour easier
for users.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message