The following issue has been updated:
Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
Date: Mon, 30 Jun 2003 10:03 AM
Comment:
What is the status on that? Do we have a POM updater now? In any case, I've changed
this issue to be a "minor" "improvement".
Changes:
type changed from Task to Improvement
description changed from The "maven:verify-project" was used to auto-update
the POM from a remote
location. Maven B5 doesn't have it.
It would be nice to be able to update the POM automatically.
The remote repo could be a valid choice for the remote location.
Maybe a "pom:update" goal could do that ?
(There is already a "pom:deploy" goal.) to The "maven:verify-project" was used to
auto-update the POM from a remote
location. Maven B5 doesn't have it.
It would be nice to be able to update the POM automatically.
The remote repo could be a valid choice for the remote location.
Maybe a "pom:update" goal could do that ?
(There is already a "pom:deploy" goal.)
environment changed from to
priority changed from Major to Minor
timeestimate changed from to 0 minutes
Version changed from 1.0-beta-7 to
Fix Version changed from 1.0-beta-7 to
---------------------------------------------------------------------
For a full history of the issue, see:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-73&page=history
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-73
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-73
Summary: Maven lost the "verify-project" target in the move to B5.
Type: Improvement
Status: Unassigned
Priority: Minor
Time Spent: Unknown
Estimate: 0 minutes
Project: maven
Components:
core
Assignee:
Reporter: Stéphane MOR
Created: Thu, 15 Aug 2002 1:23 AM
Updated: Mon, 30 Jun 2003 10:03 AM
Description:
The "maven:verify-project" was used to auto-update the POM from a remote
location. Maven B5 doesn't have it.
It would be nice to be able to update the POM automatically.
The remote repo could be a valid choice for the remote location.
Maybe a "pom:update" goal could do that ?
(There is already a "pom:deploy" goal.)
---------------------------------------------------------------------
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/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
