maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (MNG-127) finalise plugin download/handling
Date Wed, 02 Mar 2005 04:43:16 GMT
The following comment has been added to this issue:

     Author: Brett Porter
    Created: Tue, 1 Mar 2005 11:42 PM
paraphrasing Jason:

* it can be specified, if not we have a store (file, or little jdbm database) that can be
updated from the repository with the most current version which would be used if one wasn't
specified (or use a latest identifier)

* should then get written into the POM though to prevent it from breaking across plugin updates

* a specification of the version is probably better. less magic.

from me:
* maybe for alpha-1 we'll just require the version specification
* concern is that it might be a pain for some things where you want to update across the board,
but we have similar pains with dependencies, so we can use similar solutions, like <pluginManagement>

also, what about transparent plugin downloading using goal names? This probably requires the
use of latest/repository database.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: MNG-127
    Summary: finalise plugin download/handling
       Type: Task

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: m2
   Fix Fors:

   Reporter: Brett Porter

    Created: Mon, 7 Feb 2005 3:16 AM
    Updated: Tue, 1 Mar 2005 11:42 PM

currently, 1.0-SNAPSHOT is downloaded and used.

The details about how this should work in practice need to be finalised, including any ability
to have specific plugin dependencies and per-user profiles.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message