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 2004/10/11 19:35:24 UTC

[jira] Created: (MNG-91) Migrate all m2 builds to use new plexus 0.18-SNAPSHOT and separated container api artifact

Message:

  A new issue has been created in JIRA.

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-91
    Summary: Migrate all m2 builds to use new plexus 0.18-SNAPSHOT and separated container api artifact
       Type: Improvement

     Status: Open
   Priority: Major

 Original Estimate: 2 hours
 Time Spent: Unknown
  Remaining: 2 hours

    Project: m2
   Fix Fors:
             1.0-alpha-1
   Versions:
             1.0-alpha-1

   Assignee: John Casey
   Reporter: John Casey

    Created: Mon, 11 Oct 2004 1:34 PM
    Updated: Mon, 11 Oct 2004 1:34 PM
Environment: all

Description:
The plexus container artifact (plexus-0.17-SNAPSHOT) has been separated into three pieces: plexus-container-api is the artifact which contains the container API defined by the plexus system; plexus-utils is the artifact which contains common utilities in plexus; and plexus is still the standard container implementation.

All of the new artifacts outlined above have the version 0.18-SNAPSHOT to distinguish them from the 0.17-* integrated lineage.

To maintain compatibility with the new definition of plexus containers (separated API and utilities), we need to migrate all maven2 builds to use these three artifacts rather than just plexus-0.17-SNAPSHOT.

* This will require migrating all plexus-0.17-SNAPSHOT dependency declarations to plexus-container-api-0.18-SNAPSHOT.

* Depending on the particular build, it MAY also involve re-addition of the standard container: plexus-0.18-SNAPSHOT (for standard container-specific APIs).

* Depending on the particular build, it MAY also involve addition of the utilities artifact: plexus-utils-0.18-SNAPSHOT (to accommodate usage of the DAG for instance).

We need to make adjustments as necessary, and verify that all builds function in the plx-0.18-snapshot environment.

This issue is related to PLX-83 and PLX-84.


---------------------------------------------------------------------
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] Closed: (MNG-91) Migrate all m2 builds to use new plexus 0.18-SNAPSHOT and separated container api artifact

Posted by ji...@codehaus.org.
Message:

   The following issue has been closed.

   Resolver: Jason van Zyl
       Date: Fri, 24 Dec 2004 12:54 PM

o we're using a single JAR now
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MNG-91

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MNG-91
    Summary: Migrate all m2 builds to use new plexus 0.18-SNAPSHOT and separated container api artifact
       Type: Improvement

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: 2 hours
 Time Spent: Unknown
  Remaining: 2 hours

    Project: m2
   Fix Fors:
             1.0-alpha-1
   Versions:
             1.0-alpha-1

   Assignee: John Casey
   Reporter: John Casey

    Created: Mon, 11 Oct 2004 1:34 PM
    Updated: Fri, 24 Dec 2004 12:54 PM
Environment: all

Description:
The plexus container artifact (plexus-0.17-SNAPSHOT) has been separated into three pieces: plexus-container-api is the artifact which contains the container API defined by the plexus system; plexus-utils is the artifact which contains common utilities in plexus; and plexus is still the standard container implementation.

All of the new artifacts outlined above have the version 0.18-SNAPSHOT to distinguish them from the 0.17-* integrated lineage.

To maintain compatibility with the new definition of plexus containers (separated API and utilities), we need to migrate all maven2 builds to use these three artifacts rather than just plexus-0.17-SNAPSHOT.

* This will require migrating all plexus-0.17-SNAPSHOT dependency declarations to plexus-container-api-0.18-SNAPSHOT.

* Depending on the particular build, it MAY also involve re-addition of the standard container: plexus-0.18-SNAPSHOT (for standard container-specific APIs).

* Depending on the particular build, it MAY also involve addition of the utilities artifact: plexus-utils-0.18-SNAPSHOT (to accommodate usage of the DAG for instance).

We need to make adjustments as necessary, and verify that all builds function in the plx-0.18-snapshot environment.

This issue is related to PLX-83 and PLX-84.


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