You are viewing a plain text version of this content. The canonical link for it is here.
Posted to m2-dev@maven.apache.org by ji...@codehaus.org on 2005/02/08 13:15:21 UTC

[jira] Created: (MNG-140) refactor ArtifactResolver and ArtifactRepository

Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-140
    Summary: refactor ArtifactResolver and ArtifactRepository
       Type: Improvement

     Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
 Components: 
             design

   Assignee: Brett Porter
   Reporter: Brett Porter

    Created: Tue, 8 Feb 2005 7:13 AM
    Updated: Tue, 8 Feb 2005 7:13 AM

Description:
currently, there are a few inconsistencies in the way the artifact resolution is implemented.

ArtifactRepository objects are created from the project builder. It makes more sense that the artifact resolver actually factory these on behalf of the builder - currently setting any additional parameters on them requires it be in the project, or that the project builder has knowledge of wagon.

It is also uncertain if the wagon manager is required at all and may be able to be folded into the artifact resolver.


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

[jira] Updated: (MNG-140) refactor maven-artifact

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-140?page=history ]

Brett Porter updated MNG-140:
-----------------------------

    Fix Version: 1.0-alpha-2
    Environment: 
    Description: 
currently, there are a few inconsistencies in the way the artifact resolution is implemented.

ArtifactRepository objects are created from the project builder. It makes more sense that the artifact resolver actually factory these on behalf of the builder - currently setting any additional parameters on them requires it be in the project, or that the project builder has knowledge of wagon.

It is also uncertain if the wagon manager is required at all and may be able to be folded into the artifact resolver.

  was:
currently, there are a few inconsistencies in the way the artifact resolution is implemented.

ArtifactRepository objects are created from the project builder. It makes more sense that the artifact resolver actually factory these on behalf of the builder - currently setting any additional parameters on them requires it be in the project, or that the project builder has knowledge of wagon.

It is also uncertain if the wagon manager is required at all and may be able to be folded into the artifact resolver.

        Summary: refactor maven-artifact  (was: refactor ArtifactResolver and ArtifactRepository)

there are plenty of places to clean up in maven-artifact before it can be a public API.
- scope handlers
- improve use of type handlers vs artifact factory
- any artifact stuff in maven-core should be called MavenArtifactFoo instead of DefaultArtifactFoo
- ArtifactMetadataSource vs ArtifactMetadata
- treatment of POMs as artifacts vs metadata

> refactor maven-artifact
> -----------------------
>
>          Key: MNG-140
>          URL: http://jira.codehaus.org/browse/MNG-140
>      Project: m2
>         Type: Improvement
>   Components: design
>     Reporter: Brett Porter
>     Assignee: Brett Porter
>     Priority: Minor
>      Fix For: 1.0-alpha-2

>
>
> currently, there are a few inconsistencies in the way the artifact resolution is implemented.
> ArtifactRepository objects are created from the project builder. It makes more sense that the artifact resolver actually factory these on behalf of the builder - currently setting any additional parameters on them requires it be in the project, or that the project builder has knowledge of wagon.
> It is also uncertain if the wagon manager is required at all and may be able to be folded into the artifact resolver.

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