I'm ok with it as long as we're documented it as a removal of
functionality along with the fixing of bugs.
On Thu, 8 Jul 2004 07:53:42 +0200, Arnaud Heritier [EMAIL PROTECTED] wrote:
Ok Brett, if everybody is agree with the remove of sourceModifications usage. Dion?
If it's ok, I'll do it
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 07, 2004 1:10 PM
To: Maven Developers List
Subject: [vote] plugin releases
Doesn't seem so long since I was last doing this :)
I would like to release the following plugins as they've had
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPANNOUNCEMENT-9
Here is an overview of the issue:
-
vmassol 2004/07/08 01:20:58
Modified:abbot.cvsignore
Log:
one more more file to ignore
Revision ChangesPath
1.2 +1 -0 maven-plugins/abbot/.cvsignore
Index: .cvsignore
===
RCS file:
vmassol 2004/07/08 01:29:02
Modified:xdocs/reference/developers Tag: MAVEN-1_0-BRANCH
releasing-plugins.xml
Log:
Added the JIRA step to the release process
Revision ChangesPath
No revision
No revision
evenisse2004/07/08 01:36:52
Modified:changelog project.xml
changelog/src/main/org/apache/maven/changelog ChangeLog.java
ChangeLogParser.java
changelog/src/main/org/apache/maven/clearcaselib
vmassol 2004/07/08 01:37:34
Modified:abbot/xdocs changes.xml
Log:
fix version
Revision ChangesPath
1.2 +1 -1 maven-plugins/abbot/xdocs/changes.xml
Index: changes.xml
===
RCS file:
Hi,
I got the following errors/problems while trying to deploy the maven web
site:
C:\dev\maven-branch-1.0maven site
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-final-SNAPSHOT
[snip]
pdf:init:
[mkdir] Created dir:
Excellent. I was just creating this step in xdocs.
Emmanuel
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 10:29 AM
Subject: cvs commit: maven/xdocs/reference/developers releasing-plugins.xml
vmassol 2004/07/08 01:29:02
It's ready to release.
I'll do it when brett will fix access rights to maven/poms in
java-repository.
Emmanuel
- Original Message -
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 10:36 AM
Subject: cvs commit:
Hi guys,
I'm trying (for the first time) to use the scm project to release a plugin,
following the instructions at
http://maven.apache.org/reference/developers/releasing-plugins.html
However, I just got a problem (see below). Any idea why I get those question
marks from the ant:cvs task?
I have the same problem. Arnaud?
Emmanuel
- Original Message -
From: Vincent Massol [EMAIL PROTECTED]
To: 'Maven Developers List' [EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 10:38 AM
Subject: Pb while executing maven site:deploy for Maven project
Hi,
I got the following
Check your connection:
On Thu, 8 Jul 2004 11:08:10 +0200, Vincent Massol [EMAIL PROTECTED] wrote:
Hi guys,
scm:parse-connection:
[echo] Using connection:
scm:cvs:pserver:[EMAIL PROTECTED]:/home/cvspublic:maven-plugins/abbot/
Using SCM method: cvs
Using CVSROOT: :pserver:[EMAIL
It seems the problem is with:
cvs [server aborted]: tag requires write access to the repository
And as the cvs command is executed anonymously it's failing.
I'll have a look at the plugin code to see how it works
Thanks
-Vincent
-Original Message-
From: Vincent Massol [mailto:[EMAIL
It's necessary to have a developerConnection tag in pom.
Emmanuel
- Original Message -
From: Vincent Massol [EMAIL PROTECTED]
To: 'Maven Developers List' [EMAIL PROTECTED]
Sent: Thursday, July 08, 2004 11:13 AM
Subject: RE: Pb with maven scm:prepare-release
It seems the problem is
vmassol 2004/07/08 02:32:58
Modified:abbotproject.xml
Log:
Adding developerConnection tag which seems to be required by the scm plugin
Revision ChangesPath
1.7 +1 -0 maven-plugins/abbot/project.xml
Index: project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-16
Here is an overview of the issue:
-
Key:
Or at least warn you...
On Thu, 8 Jul 2004 11:34:10 +0200, Vincent Massol [EMAIL PROTECTED] wrote:
Thanks. It's working now.
I guess the plugin should be improved to check for this and not default to
using the connection tag.
-Vincent
-Original Message-
From: Emmanuel
I think we can now remove the deploy namespace from:
artifact
dist
jar
release
True?
--
http://www.multitask.com.au/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
I believe warning is not enough as it will always fail because it needs
write access to create a tag
-Vincent
-Original Message-
From: Dion Gillard [mailto:[EMAIL PROTECTED]
Sent: jeudi 8 juillet 2004 11:41
To: Maven Developers List
Subject: Re: Pb with maven scm:prepare-release
vmassol 2004/07/08 02:50:45
Modified:abbotproject.xml
Log:
manually remove the HEAD version tag that was not removed by the scm plugin (see
http://jira.codehaus.org/browse/MPSCM-17)
Revision ChangesPath
1.9 +0 -5 maven-plugins/abbot/project.xml
Hello guys,
For the PDF problem you must remove from the navigation-pdf.xml the line 43 :
item name=Plugins href=/reference/plugins/index.html/
This file isn't generated with maven site.
Arnaud
-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoy :
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-17
Here is an overview of the issue:
-
Key:
I'm not sure that we specify that connection MUST be read only anywhere
On Thu, 8 Jul 2004 11:44:48 +0200, Vincent Massol [EMAIL PROTECTED] wrote:
I believe warning is not enough as it will always fail because it needs
write access to create a tag
-Vincent
-Original
I found a proposal on Jira which can help to reintroduce the use of
sourceModifications but without using a fileset for javadoc.
The idea is to use the filter (sourceModifications) to copy in a working directory all
sources needed by the javadoc.
Because I think it will be a little time
vmassol 2004/07/08 02:59:44
Modified:xdocsTag: MAVEN-1_0-BRANCH navigation-pdf.xml
Log:
As suggested by Arnaud, remove generation of PDF for the plugins site .
Revision ChangesPath
No revision
No revision
1.1.2.6 +0 -1
Hi (Brett),
When trying to release a plugin I got the following problem:
C:\dev\maven-plugins\abbotmaven scm:perform-release
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-final-SNAPSHOT
build:start:
carlos 2004/07/08 03:29:19
Modified:aspectj/xdocs changes.xml
Log:
Fixed version
Revision ChangesPath
1.22 +1 -1 maven-plugins/aspectj/xdocs/changes.xml
Index: changes.xml
===
RCS file:
Can you tell me where is defined the jelly tag assert:assertFileExists ?
I would like to know if assert:assertFileNotExists is defined ?
_
Arnaud HERITIER
Axway - Sopra Group
Axway France Services
Tél. : +33 (0)1 47 17 22 79
Email : [EMAIL PROTECTED] / [EMAIL PROTECTED]
_
Yesterday I modified the template used to access to issues on Jira on
CodeHaus.
I defined in the parent-plugin :
maven.changes.issue.template = %URL%/%ISSUE%
Instead of the default one : %URL%/ViewIssue.jspa?key=%ISSUE%
I don't know if we must replace the default template defined in the
plugin
-Original Message-
From: Heritier Arnaud [mailto:[EMAIL PROTECTED]
Sent: jeudi 8 juillet 2004 12:54
To: [EMAIL PROTECTED]
Subject: [maven-changes-plugin] Issues template for Jira
Yesterday I modified the template used to access to issues on Jira on
CodeHaus.
I defined in the
It's in the plugin plugin
-Vincent
-Original Message-
From: Heritier Arnaud [mailto:[EMAIL PROTECTED]
Sent: jeudi 8 juillet 2004 12:43
To: Maven Developers List
Subject: Where is defined assert:assertFileExists ?
Can you tell me where is defined the jelly tag
It's assertFileNotFound
On Thu, 8 Jul 2004 12:43:29 +0200, Heritier Arnaud [EMAIL PROTECTED] wrote:
Can you tell me where is defined the jelly tag assert:assertFileExists ?
I would like to know if assert:assertFileNotExists is defined ?
_
Arnaud HERITIER
Axway - Sopra Group
Ok, thanks
It's not assertFileNotExists but assertFileNotFound.
Arnaud
-Message d'origine-
De : Vincent Massol [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 8 juillet 2004 13:02
À : 'Maven Developers List'
Objet : RE: Where is defined assert:assertFileExists ?
It's in the plugin
carlos 2004/07/08 04:27:58
Modified:aspectj/src/plugin-test/src/aspect/org/apache/maven/aspectj
Sample.aj
aspectj/src/plugin-test/src/test/org/apache/maven/aspectj
AspectTest.java
aspectj/src/plugin-test
The following comment has been added to this issue:
Author: Brett Porter
Created: Thu, 8 Jul 2004 7:38 AM
Body:
fixed.
-
View this comment:
http://jira.codehaus.org/browse/MPPLUGIN-22?page=comments#action_21510
Just a clarification: its not necessary to have a developer connection, but its
necessary that the connection used is not anonymous for tagging.
I don't know how you can check on this: the anonymous user is not specifically
anonymous, but rather a published, low permission user. On some
Quoting Dion Gillard [EMAIL PROTECTED]:
I think we can now remove the deploy namespace from:
artifact
no, it contains the old deploy tag library
dist
jar
its only there as a sanity check - sure
release
I think it uses deploy:copy-deps, so that would need to be changed first?
- Brett
brett 2004/07/08 04:48:19
Modified:plugin-parent project.properties
Log:
force artifact plugin deployment so we get md5 files
Revision ChangesPath
1.3 +3 -0 maven-plugins/plugin-parent/project.properties
Index: project.properties
fixed sorry all.
Quoting Vincent Massol [EMAIL PROTECTED]:
Hi (Brett),
When trying to release a plugin I got the following problem:
C:\dev\maven-plugins\abbotmaven scm:perform-release
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_|
brett 2004/07/08 04:56:06
Modified:xdocsTag: MAVEN-1_0-BRANCH development-process.xml
navigation-pdf.xml navigation.xml
xdocs/ant-guide Tag: MAVEN-1_0-BRANCH practical.xml
terminology.xml where.xml
On Thu, 8 Jul 2004 21:47:58 +1000, Brett Porter [EMAIL PROTECTED] wrote:
Quoting Dion Gillard [EMAIL PROTECTED]:
I think we can now remove the deploy namespace from:
artifact
no, it contains the old deploy tag library
Woops.
dist
jar
its only there as a sanity check - sure.
its only there as a sanity check - sure.
I'd much prefer we keep things clean, otherwise we end up with cruft everywhere.
Yeah, but it makes for a less confusing experience when someone installs
RC4/1.0 over the top of something older.
I think we can ditch it in 1.0 though - a fleeting
On Thu, 08 Jul 2004 22:05:45 +1000, Brett Porter [EMAIL PROTECTED] wrote:
I think we can ditch it in 1.0 though - a fleeting message in RC4 was
enough :)
Jason was going to relegate release to the sandbox as incomplete last
year, but we kept it around because some of the java code is being
At this stage of the game, might be best left alone, and just indicate
in the docs that the plugin is only intended for reuse by other plugins
and is deprecated otherwise.
Dion Gillard wrote:
On Thu, 08 Jul 2004 22:05:45 +1000, Brett Porter [EMAIL PROTECTED] wrote:
I think we can ditch it
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-32
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Thu, 8 Jul 2004 8:31 AM
All done.. The only caveat is the property
maven.gen.src=${maven.build.dir}/generated-sources
is defined by the eclipse plugin for now, and therefore you will proebably need to
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Thu, 8 Jul 2004 8:34 AM
At this time (1.8-dev) there isn't a problem. You do get an annoying message, but
that I think will be resolved in the 1.0 version of Maven. We don't want to add more
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 8 Jul 2004 8:40 AM
Body:
Can you supply a patch? At least with my Eclipse (3.0 RC3) it does that automatically.
Eric
-
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Thu, 8 Jul 2004 8:42 AM
I think this is beyond the scope of what most people need. If you can come up with a
patch that would be great. One of the core tenets of Maven is that the classpath
isn't
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1366
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Thu, 8 Jul 2004 8:49 AM
Body:
That's right.
I don't why nobody find this problem before.
It was introduced in the 1.44 two weeks ago.
I will correct it tonight or tomorrow
The following comment has been added to this issue:
Author: Boris Boehlen
Created: Thu, 8 Jul 2004 8:55 AM
Body:
I just noticed, that the version control files disappear as soon as you share the
project. Thus, I think that its not that important.
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-30
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Thu, 8 Jul 2004 8:58 AM
A) you place your own xdocs in the xdocs directory. Is that what you are trying to do?
I'm not sure I understood the question - please pose it at [EMAIL PROTECTED] after
subscribing
brett 2004/07/08 06:04:03
Modified:.Tag: MAVEN-1_0-BRANCH project.properties
Log:
PR: MAVEN-1364
remove werkz api docs - they aren't online there anyway
Revision ChangesPath
No revision
No revision
1.51.2.30 +1 -1
epugh 2004/07/08 06:06:11
maven-plugins/cruisecontrol/src/plugin-test/cvs-scm - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
epugh 2004/07/08 06:06:11
maven-plugins/cruisecontrol/src/plugin-test/svn-scm - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
epugh 2004/07/08 06:06:15
Added: cruisecontrol/src/plugin-test/cvs-scm project.xml maven.xml
cruisecontrol/src/plugin-test/svn-scm project.xml maven.xml
.cvsignore
cruisecontrol/src/plugin-test project.xml project.properties
epugh 2004/07/08 06:08:13
Modified:cruisecontrol plugin.jelly
Log:
better syntax
Revision ChangesPath
1.8 +1 -1 maven-plugins/cruisecontrol/plugin.jelly
Index: plugin.jelly
===
RCS
epugh 2004/07/08 06:08:38
Modified:cruisecontrol/xdocs changes.xml
cruisecontrol/src/plugin-test/cvs-scm maven.xml
cruisecontrol/src/plugin-resources cruisecontrol.jsl
Log:
Show unit tests results in results tab of cc
Revision ChangesPath
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Thu, 8 Jul 2004 9:08 AM
maven:installer builds one now
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1346
Here is an overview
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Thu, 8 Jul 2004 9:10 AM
Committed! Can you verify the fix?
-
View the issue:
http://jira.codehaus.org/browse/MPCRUISECONTROL-6
Here
The following comment has been added to this issue:
Author: Paul Spencer
Created: Thu, 8 Jul 2004 9:10 AM
Body:
I suggest a printing a warning message, i.e.
Warning - The respositories time is in the past. This may cause
the wrong SNAPSHOT to be used. It is suggest
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1160
Here is an overview of the issue:
-
epugh 2004/07/08 06:17:12
Modified:cruisecontrol/xdocs changes.xml
Log:
Fix misapplied changes
Revision ChangesPath
1.11 +4 -1 maven-plugins/cruisecontrol/xdocs/changes.xml
Index: changes.xml
epugh 2004/07/08 06:17:27
Modified:cruisecontrol project.xml
Log:
bump version to 1.4-dev!
Revision ChangesPath
1.25 +1 -1 maven-plugins/cruisecontrol/project.xml
Index: project.xml
===
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Thu, 8 Jul 2004 9:17 AM
I have a feeling this was fixed with the changes in RC4 - ask for it to be reopened if
still broken in the same way
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1268
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Thu, 8 Jul 2004 9:18 AM
Fixed!
-
View the issue:
http://jira.codehaus.org/browse/MPCRUISECONTROL-5
Here is an overview of the
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1268
Here is an overview of the issue:
-
The following comment has been added to this issue:
Author: Brett Porter
Created: Thu, 8 Jul 2004 9:21 AM
Body:
I'm not sure what is causing this... do you have a small sample project that exhibits
the behaviour?
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1268
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1090
Here is an overview of the issue:
-
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-435
Here is an overview of the issue:
-
Key:
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1082
Here is an overview of the issue:
-
Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Thu, 8 Jul 2004 9:32 AM
implemented... although it doesn't run before dep resolution.
-
View the issue:
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-221
Here is an overview of the issue:
-
Key:
bump to 1.4-SNAPSHOT please.
Cheers,
Brett
[EMAIL PROTECTED] wrote:
epugh 2004/07/08 06:17:27
Modified:cruisecontrol project.xml
Log:
bump version to 1.4-dev!
Revision ChangesPath
1.25 +1 -1 maven-plugins/cruisecontrol/project.xml
Index: project.xml
evenisse2004/07/08 06:47:53
Modified:jalopy project.xml
jalopy/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.3
Revision ChangesPath
1.37 +6 -1 maven-plugins/jalopy/project.xml
Index: project.xml
dion2004/07/08 07:12:16
Modified:plugin/xdocs changes.xml
plugin project.xml
Log:
Use 1.5.1 instead of 1.6
Revision ChangesPath
1.27 +1 -1 maven-plugins/plugin/xdocs/changes.xml
Index: changes.xml
The following comment has been added to this issue:
Author: Rickard Lundin
Created: Thu, 8 Jul 2004 10:16 AM
Body:
I cant't get maven Rc4 it to work with NTLM , on my Win2000 machine.
Tried1: jdk1.4.1_05 + ant 1.5.1
Tried2: jdk1.4.2+ ant 1.6.2beta1
Maven simply says:
dion2004/07/08 07:20:27
Modified:plugin/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.5.1
Revision ChangesPath
1.28 +2 -4 maven-plugins/plugin/xdocs/changes.xml
Index: changes.xml
Hi dIon,
Just a question: when you do some changes like this, are you also making the
equivalent change in JIRA?
I've found that lots of people make change to versions in project.xml but
JIRA is often neglected. Like for example when a plugin is released.
Thanks
-Vincent
-Original
vmassol 2004/07/08 07:27:57
Modified:announcement project.xml
announcement/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.2
Revision ChangesPath
1.23 +6 -1 maven-plugins/announcement/project.xml
Index: project.xml
vmassol 2004/07/08 07:29:02
Modified:announcement project.xml
Log:
manually remove the HEAD version tag that was not removed by the scm plugin (see
http://jira.codehaus.org/browse/MPSCM-17)
Revision ChangesPath
1.24 +0 -5 maven-plugins/announcement/project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPPLUGIN-24
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-18
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 8 Jul 2004 10:35 AM
Body:
it works fine on jdk 1.4.
This is with:
maven.repo.list=apache
maven.repo.apache=scp://www.apache.org
This is really a documentation issue. The artifact plugin has
dion2004/07/08 07:38:57
Modified:plugin project.xml
Log:
scm:prepare-release fails again
Revision ChangesPath
1.43 +6 -1 maven-plugins/plugin/project.xml
Index: project.xml
===
RCS
evenisse2004/07/08 07:47:50
Modified:jcoverage project.xml
jcoverage/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.0.6
Revision ChangesPath
1.27 +6 -1 maven-plugins/jcoverage/project.xml
Index: project.xml
The Maven team is pleased to announce the Maven Plugin Plugin 1.5.1 release!
http://maven.apache.org/reference/plugins/plugin/
Maven Plugin management plugin. Requires Maven 1.0 RC4.
Changes in this version include:
New Features:
o Prompt for artifactId, groupId and version if missing.
evenisse2004/07/08 08:34:54
Modified:changelog project.xml
changelog/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.7
Revision ChangesPath
1.46 +6 -1 maven-plugins/changelog/project.xml
Index: project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCHANGELOG-44
Here is an overview of the issue:
-
vmassol 2004/07/08 08:45:09
Modified:xdoc/src/plugin-resources/templates downloads.jelly
Log:
Generate announcement files only once
Revision ChangesPath
1.4 +7 -2
maven-plugins/xdoc/src/plugin-resources/templates/downloads.jelly
Index: downloads.jelly
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 8 Jul 2004 11:48 AM
Body:
Arh! Starteam is a bad tool.
Can you post a sample stcmd output?
-
View this comment:
vmassol 2004/07/08 08:49:03
Modified:changes project.xml
changes/xdocs changes.xml
Log:
[maven-scm-plugin] prepare release 1.5
Revision ChangesPath
1.32 +6 -1 maven-plugins/changes/project.xml
Index: project.xml
vmassol 2004/07/08 08:50:06
Modified:changes project.xml
Log:
manually remove the HEAD version tag that was not removed by the scm plugin (see
http://jira.codehaus.org/browse/MPSCM-17)
Revision ChangesPath
1.33 +0 -5 maven-plugins/changes/project.xml
The maven team is pleased to announce the Maven Changes Plugin 1.5 release!
http://maven.apache.org/reference/plugins/changes/
Changes in this version include:
New Features:
o Add generation of RSS feed for current version changes
To automatically install the plugin, type the following
The following comment has been added to this issue:
Author: Pierre-Yves Chauveau
Created: Thu, 8 Jul 2004 12:26 PM
Body:
Example :
Historique pour : build.properties
Description : Initial Check In
VerrouillÚ par :
Etat : Manquant
RÚvision : 1 Vue : PIM
1 - 100 of 115 matches
Mail list logo
