dion2003/09/28 23:09:54
Modified:src/plugins-build/dist/xdocs changes.xml
src/plugins-build/checkstyle/xdocs/current changes.xml
src/plugins-build/clover/xdocs changes.xml
src/plugins-build/ant/xdocs changes.xml
Missed something here...
[EMAIL PROTECTED] wrote on 29/09/2003 03:12:08 PM:
[snip]
version
idb11/id
- name1.0-beta-11/name
+ name1.0-rc1/name
tagHEAD/tag
/version
/versions
The id is still b11.
--
dIon Gillard, Multitask Consulting
Blog:
dion2003/09/28 23:12:03
Modified:src/plugins-build/hibernate project.xml
Log:
Fix typo
Revision ChangesPath
1.16 +1 -1 maven/src/plugins-build/hibernate/project.xml
Index: project.xml
On Mon, 2003-09-29 at 02:14, [EMAIL PROTECTED] wrote:
Missed something here...
[EMAIL PROTECTED] wrote on 29/09/2003 03:12:08 PM:
[snip]
version
idb11/id
- name1.0-beta-11/name
+ name1.0-rc1/name
tagHEAD/tag
/version
/versions
I would anticipate that Maven should permit inheritance of the three files
below (project.xml, project.properties, maven.xml), and in this case there
is true inheritance...all properties defined by the child override the
parent definition.
But I would suggest it is the aggregete of the
dion2003/09/28 23:28:38
Modified:.project.xml
Log:
Fix typo
Revision ChangesPath
1.309 +1 -1 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.xml,v
dion2003/09/28 23:29:09
Modified:.project.xml
Log:
Move name to SNAPSHOT
Revision ChangesPath
1.310 +1 -1 maven/project.xml
Index: project.xml
===
RCS file:
dion2003/09/28 23:33:48
Modified:xdocs/start download.xml
Log:
Fix URL again
Revision ChangesPath
1.16 +2 -2 maven/xdocs/start/download.xml
Index: download.xml
===
RCS file:
dIon,
I did this on purpose so that we don't have to change it every time.
Also the text does not say that we are pointing to the latest version
but to the release archive... I think it is best to point to the
archives instead of a specific version.
-Vincent
-Original Message-
From:
AFAIK, yes.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 29/09/2003 04:24:03 PM:
Has RC1 been tagged and can we commit again?
Thanks
-Vincent
Thanks for the response Brett, I thought at first when nobody
responded that my request was not well received. :)
Gotta wait for us to get in the right timezone :D
I was browsing through the bugs and there are some that I can
definitely help with. Is the procedure just to attach the
dion2003/09/28 23:40:42
Modified:xdocs/start download.xml
Log:
Back to vincents version
Revision ChangesPath
1.17 +1 -1 maven/xdocs/start/download.xml
Index: download.xml
===
RCS file:
Ok, I agree, makes more sense that way.
Reverted.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Vincent Massol [EMAIL PROTECTED] wrote on 29/09/2003 04:36:20 PM:
dIon,
I did this on purpose so that we don't have to change it every time.
Also the
vmassol 2003/09/28 23:42:41
Modified:xdocsstatus.xml
Log:
points to list of bugs fixed.
Revision ChangesPath
1.16 +4 -3 maven/xdocs/status.xml
Index: status.xml
===
RCS file:
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 29 Sep 2003 2:07 AM
Body:
This really isn't an issue for 1.0.
What do we do? Close it? Set up a separate jira project for the plugin?
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 2:08 AM
Changes:
Fix Version changed to maven-new-unreleased
Fix Version changed from 1.0-final
Shouldn't we keep using 1.1 as the next milestone? We should merge
maven-new-unreleased and 1.1 and rename it appropriately whenever we decide
if it is 1.1 or 2.0 or whatever.
My understanding was 1.1 was the paretial plexus version, and 2.0 was the
full plexus version. I think these sorts of
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 29 Sep 2003 2:19 AM
Body:
Got a patch?
AFAICT, the problem is, around line 124, someone decided to pass the variables of the
context in to the class, and they are not completely resolved yet.
The Maven team is pleased to announce Release Candidate 1!
http://maven.apache.org/
Maven is a Java project management and project comprehension tool. Maven
is based on the concept of a project object model (POM) in that all the
artifacts produced by Maven are a result of consulting a well
Congratulations, Apache Maven Team!
http://jakarta.apache.org/site/elsewhere.html#20030929.1
Also,
http://nagoya.apache.org/wiki/apachewiki.cgi?ApacheNewsletterDrafts/Issue2
Please feel free to modify it and create a nice newsletter Issue #2.
Sincerely,
-- Tetsuya. ([EMAIL PROTECTED])
On
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-863
Here is an overview of the issue:
The following issue has been updated:
Updater: Mauro Talevi (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 3:17 AM
Comment:
Attached POM
Changes:
Attachment changed to dna.pom
-
For a full
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 3:20 AM
Changes:
Fix Version changed to 1.1
Fix Version changed from maven-new-unreleased
I've downloaded the zip and tried it out.
Do we bother fixing this?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Works for me.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Porter [EMAIL PROTECTED] wrote on 29/09/2003 04:54:28 PM:
Shouldn't we keep using 1.1 as the next milestone? We should merge
maven-new-unreleased and 1.1 and rename it appropriately
I've made a small rmic plugin for my own usage (with some help from
within here)
what it does is that it searches all compiled classes from your project,
and locates every class that implements the java.rmi.Remote interface,
the class cannot be an interface or abstract) it then calls rmic for
Christian Andersson wrote:
I've made a small rmic plugin for my own usage (with some help from
within here)
what it does is that it searches all compiled classes from your project,
and locates every class that implements the java.rmi.Remote interface,
the class cannot be an interface or
Rafal Krzewski wrote:
Christian Andersson wrote:
I've made a small rmic plugin for my own usage (with some help from
within here)
what it does is that it searches all compiled classes from your project,
and locates every class that implements the java.rmi.Remote interface,
the class cannot be an
Hmm - sounds a little like overkill to me.
How much time does it add to each build compared
to one where the list of classes to generate stubs
for are predefined?
And how well does it scale to large codebases?
From: Christian Andersson [mailto:[EMAIL PROTECTED]
I've made a small rmic plugin
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-864
Here is an overview of the issue:
perheps a bit overkill, but for me, it was the ease of useage that was
the most important stuff..., I mean it is very easy to just forget to
add anything to a property...
I've not tested anything regarding speed
and I don't have a large codebase to test on, we use many smaller
projects
jvanzyl 2003/09/29 05:32:57
Modified:src/plugins-build/release plugin.jelly
Log:
o note about changing the display version.
Revision ChangesPath
1.18 +1 -0 maven/src/plugins-build/release/plugin.jelly
Index: plugin.jelly
vmassol 2003/09/29 06:08:47
maven/src/plugins-build/caller/xdocs - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
vmassol 2003/09/29 06:08:58
Added: src/plugins-build/caller .cvsignore project.properties
plugin.properties project.xml plugin.jelly
src/plugins-build/caller/xdocs goals.xml navigation.xml
properties.xml index.xml
vmassol 2003/09/29 06:25:12
Modified:src/plugins-build/caller .cvsignore
Log:
one more ignore file
Revision ChangesPath
1.2 +1 -0 maven/src/plugins-build/caller/.cvsignore
Index: .cvsignore
Hi (dIon),
The html2xdoc plugin generates target files in
src/test/plugin-test/target. I think a better solution is to tell the
spawned maven to generate them in the main target/ directory (by
changing the maven.build.dir value maybe). What do you think?
The other solution is to cvs ignore
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-865
Here is an overview of the issue:
jvanzyl 2003/09/29 07:12:21
Modified:aspectj/xdocs changes.xml
Log:
o notice of movement
Revision ChangesPath
1.4 +5 -0 maven-plugins/aspectj/xdocs/changes.xml
Index: changes.xml
===
RCS
jvanzyl 2003/09/29 07:22:21
Removed: src/plugins-build/plexus .cvsignore NOTES.txt plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/plexus/src/main/org/apache/maven/plexus
Hi,
Now that we have the ability to download plugins in a relatively simple
way we need to start giving plugins their own separate lives apart from
the Maven core.
I am starting this morning with the following plugins:
- castor
- codeswitcher
- junitdoclet
- summit
- sea
- runner
Other
jvanzyl 2003/09/29 07:51:58
Removed: src/plugins-build/castor .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/castor/xdocs .cvsignore changes.xml
examples.xml goals.xml index.xml
jvanzyl 2003/09/29 07:54:31
Removed: src/plugins-build/codeswitcher .cvsignore plugin.jelly
plugin.properties project.properties project.xml
Log:
o plugin has been moved to maven-plugins
-
jvanzyl 2003/09/29 07:57:10
Removed: src/plugins-build/junitdoclet .cvsignore plugin.jelly
plugin.properties project.properties project.xml
Log:
o plugin have moved to maven-plugins.
-
To
jvanzyl 2003/09/29 08:00:18
Removed: src/plugins-build/summit .cvsignore NOTES.txt plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/summit/xdocs .cvsignore changes.xml
goals.xml index.xml
jvanzyl 2003/09/29 08:01:12
Removed: src/plugins-build/sea .cvsignore plugin.jelly project.xml
sea-tar
src/plugins-build/sea/src/plugin-resources sea-header
Log:
o plugin moved to maven-plugins
jvanzyl 2003/09/29 08:09:32
Removed: src/plugins-build/shell .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/shell/xdocs changes.xml goals.xml
index.xml navigation.xml
jvanzyl 2003/09/29 08:11:45
Removed: src/plugins-build/release .cvsignore NOTES.txt plugin.jelly
project.properties project.xml releaseplan.xml
src/plugins-build/release/src/main/org/apache/maven/release
vmassol 2003/09/29 08:14:19
Modified:src/plugins-build/war plugin.jelly project.xml
src/plugins-build/war/xdocs changes.xml
Log:
Use the new caller plugin
Revision ChangesPath
1.31 +3 -2 maven/src/plugins-build/war/plugin.jelly
Index:
Hi,
There are definitely a few plugins that have been committed on behalf of
those who do not have apache commit privs. These plugins should probably
move off the apache boxes because the original authors are at our mercy
to commit changes which just isn't scalable.
The the sourceforge
jvanzyl 2003/09/29 08:23:21
Removed: src/plugins-build/hibernate .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/hibernate/src/main/org/apache/maven/hibernate/beans
jvanzyl 2003/09/29 09:11:27
Removed: src/plugins-build/antlr .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/antlr/xdocs .cvsignore changes.xml
goals.xml index.xml navigation.xml
jvanzyl 2003/09/29 09:16:10
Removed: src/plugins-build/latex .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/latex/xdocs .cvsignore changes.xml
goals.xml index.xml navigation.xml
jvanzyl 2003/09/29 09:23:31
Removed: src/plugins-build/junitdoclet/xdocs .cvsignore changes.xml
goals.xml index.xml navigation.xml properties.xml
Log:
o cleaning out some stray files.
-
To
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-866
Here is an overview of the issue:
Dion or Ben
Could you add 1.0-rc2 version into jira for maven project for trace bug
fixes between rc1 and rc2.
Thanks
Emmanuel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Mon, 2003-09-29 at 12:49, Emmanuel Venisse wrote:
Dion or Ben
Could you add 1.0-rc2 version into jira for maven project for trace bug
fixes between rc1 and rc2.
Done.
Ben is on vaction btw.
Thanks
Emmanuel
-
To
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Mon, 29 Sep 2003 2:43 PM
Fixed today
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-866
Here is an
The following comment has been added to this issue:
Author: Jason Chaffee
Created: Mon, 29 Sep 2003 2:49 PM
Body:
This is a pretty big show stopper for my use of Maven. For jakarta projects that use
Maven it isn't because their dependencies are located at ibiblio. However, I
evenisse2003/09/29 12:32:27
Modified:xdocs/reference/developers developer-guide.xml
Log:
Fix MAVEN-849.
Revision ChangesPath
1.2 +1 -1 maven/xdocs/reference/developers/developer-guide.xml
Index: developer-guide.xml
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Mon, 29 Sep 2003 2:52 PM
Fixed
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-849
Here is an overview
We should probably also check if there are volunteers in the developer base
to look after them. For example, I think the IDEA plugin came from a
non-committer and I've basically rewritten it since and would be happy to
take it over.
- Brett
-Original Message-
From: Jason van Zyl
On Tue, 30 Sep 2003, Brett Porter wrote:
We should probably also check if there are volunteers in the developer base
to look after them. For example, I think the IDEA plugin came from a
non-committer and I've basically rewritten it since and would be happy to
take it over.
I wrote the IDEA
On Mon, 2003-09-29 at 18:20, Brett Porter wrote:
We should probably also check if there are volunteers in the developer base
to look after them. For example, I think the IDEA plugin came from a
non-committer and I've basically rewritten it since and would be happy to
take it over.
Certainly,
I'd say leave it as is in the release, but make sure we get it right next
time.
I really need to look at integrating the release portions of the SCM plugin
and the release plugin properly sometime close to 1.0 too.
As far as releasing this week - I'm not confident I'll have something of
that
On Mon, 2003-09-29 at 18:20, Brett Porter wrote:
We should probably also check if there are volunteers in the developer base
to look after them. For example, I think the IDEA plugin came from a
non-committer and I've basically rewritten it since and would be happy to
take it over.
Ok, so
The following issue has been updated:
Updater: Jason Chaffee (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 5:55 PM
Comment:
Providing fix to release plugin.
Changes:
Attachment changed to SnapshotResolver.java
The following issue has been updated:
Updater: Jason Chaffee (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 6:55 PM
Comment:
I attached the wrong file...one that didn't work. I have attached one that works.
This is a quick fix for how the release plugin is currently written.
If your happy to do it, go for it. I was going to do that and cruisecontrol.
I'm undecided about SCM.
- Brett
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 September 2003 8:36 AM
To: Maven Developers List
Subject: RE: Plugins that have no
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Mon, 29 Sep 2003 7:00 PM
Body:
I will apply this patch but in the future please try not to change the coding format.
Patches are also easier to integrate because we can easily see what the
On Mon, 2003-09-29 at 19:38, Brett Porter wrote:
If your happy to do it, go for it. I was going to do that and cruisecontrol.
I'm undecided about SCM.
We'll take the low hanging fruit then first. I'll move IDEA and the
cruisecontrol plugin.
- Brett
-Original Message-
From:
jvanzyl 2003/09/29 16:52:00
Modified:release/src/main/org/apache/maven/release
SnapshotResolver.java
Log:
o MAVEN-542
http://jira.codehaus.org/secure/ViewIssue.jspa?id=11157
Revision ChangesPath
1.13 +185 -175
jvanzyl 2003/09/29 16:52:59
Modified:release project.xml
Log:
o made a change, flipping over to development mode.
Revision ChangesPath
1.22 +1 -1 maven-plugins/release/project.xml
Index: project.xml
Thanks!
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 September 2003 9:51 AM
To: Maven Developers List
Subject: RE: Plugins that have no apache committers
On Mon, 2003-09-29 at 19:38, Brett Porter wrote:
If your happy to do it, go for it.
jvanzyl 2003/09/29 16:56:08
Modified:release/xdocs changes.xml
Log:
o updating changes.
Revision ChangesPath
1.4 +6 -0 maven-plugins/release/xdocs/changes.xml
Index: changes.xml
===
RCS
jvanzyl 2003/09/29 17:01:11
Removed: src/plugins-build/idea .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/idea/src/plugin-resources/templates/v3
project.jelly workspace.jelly
jvanzyl 2003/09/29 17:02:09
Removed: src/plugins-build/cruisecontrol .cvsignore plugin.jelly
plugin.properties project.properties project.xml
src/plugins-build/cruisecontrol/src/plugin-resources
cruisecontrol.jsl
On Mon, 2003-09-29 at 19:54, Brett Porter wrote:
Thanks!
Moved and in maven-plugins if you want to check them out and possibly
update the changes.xml document if you can.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 September 2003 9:51 AM
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Mon, 29 Sep 2003 7:31 PM
Patch has been applied. Many thanks.
-
View the issue:
Brett,
Could you give me a quick rundown of how to download a plugin
and how the mechanism works. I will look at the code for
certain but I just want to push in a little bit of doco now
with all the plugins separated.
maven plugin:download -DartifactId=maven-dbunit-plugin
Howdy,
Anyone know if it is possible to setup sub projects in JIRA. The
separated projects are now little projects of their own but I would like
to group them under the Maven project itself as not to clutter up the
entire dashboard. Having the plugins listed as components doesn't really
work
On Mon, 2003-09-29 at 20:12, Brett Porter wrote:
Brett,
Could you give me a quick rundown of how to download a plugin
and how the mechanism works. I will look at the code for
certain but I just want to push in a little bit of doco now
with all the plugins separated.
maven
Hi,
I'm not sure what happened to the css of late but the maven.apache.org
left hand menu looks horrible.
The leading (line spacing) is far too close together. Is this just
something I'm seeing on Mozilla? The squares with the + symbol in them
also look horrible. Is there any other options like
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 7:52 PM
Comment:
Well duh.
Changes:
Fix Version changed to 1.1
-
For a full history
Vincent Massol [EMAIL PROTECTED] wrote on 29/09/2003 11:28:40 PM:
Hi (dIon),
The html2xdoc plugin generates target files in
src/test/plugin-test/target. I think a better solution is to tell the
spawned maven to generate them in the main target/ directory (by
changing the maven.build.dir
What about the plugins with test projects?
How will those test projects run?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Jason van Zyl [EMAIL PROTECTED] wrote on 30/09/2003 12:28:31 AM:
Hi,
Now that we have the ability to download plugins in a
Why are we moving all the plugins?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED] wrote on 30/09/2003 12:22:21 AM:
jvanzyl 2003/09/29 07:22:21
Removed: src/plugins-build/plexus .cvsignore NOTES.txt
plugin.jelly
The following issue has been updated:
Updater: Jason Chaffee (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 8:07 PM
Comment:
Attaching patch file.
Changes:
Attachment changed to patchfile.txt
The following comment has been added to this issue:
Author: Jason Chaffee
Created: Mon, 29 Sep 2003 8:25 PM
Body:
This a duplicate with MAVEN-670
-
View the issue:
They should be part of the plugin, shouldn't they? Or should they be part of
maven-plugins/touchstone?
And the maven-plugins repository can have a base maven.xml that runs them
all.
- Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30
It affects IE as well. The wrapping is terrible too. Also, I preferred the
smaller navigation bar at the top - the current one has a larger font.
I don't remember when this changed, it was a while back though.
- Brett
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
The following issue has been updated:
Updater: Jason Chaffee (mailto:[EMAIL PROTECTED])
Date: Mon, 29 Sep 2003 9:15 PM
Comment:
I have supplied a patch for this bug and MAVEN-751
Changes:
Attachment changed to patchFile.txt
On Mon, 2003-09-29 at 20:47, [EMAIL PROTECTED] wrote:
What about the plugins with test projects?
How will those test projects run?
Sorry, I don't understand the question. Are you say there are tests for
some plugins that aren't encapsulated with the plugin itself?
--
dIon Gillard,
On Mon, 2003-09-29 at 21:14, Brett Porter wrote:
They should be part of the plugin, shouldn't they? Or should they be part of
maven-plugins/touchstone?
And the maven-plugins repository can have a base maven.xml that runs them
all.
All plugins should be entirely separate entities. If there
On Mon, 2003-09-29 at 21:16, Brett Porter wrote:
It affects IE as well. The wrapping is terrible too. Also, I preferred the
smaller navigation bar at the top - the current one has a larger font.
I don't remember when this changed, it was a while back though.
I would like to change it back.
Last 500 lines of a clean bootstrap build of maven at 20030929-2200
[exec] testPlugin:
[exec] clean:clean:
[exec] [delete] Deleting directory
/usr/local/builds/maven/src/maven/src/plugins-build/checkstyle/src/plugin-test/target
[exec
The following comment has been added to this issue:
Author: Jason Chaffee
Created: Mon, 29 Sep 2003 9:27 PM
Body:
The cvs diff doesn't seem show diffs very well, so I have outlined the diffs below:
changed from:
String timestampVersion = null;
to:
String timestampVersion
AFAIK, the next release is 1.0-final unless there is a pressing need for
another RC.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Emmanuel Venisse [EMAIL PROTECTED] wrote on 30/09/2003 02:49:47 AM:
Dion or Ben
Could you add 1.0-rc2 version into
I'd like to see another RC after fixinf the 18 bugs slated for 1.0-final.
- Brett
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 30 September 2003 2:19 PM
To: Maven Developers List
Subject: Re: [Jira] Maven version
AFAIK, the next release
On Tue, 2003-09-30 at 00:18, [EMAIL PROTECTED] wrote:
AFAIK, the next release is 1.0-final unless there is a pressing need for
another RC.
Right, it's not something we know before hand. We, in light of feedback
from users, decide whether we need another release candidate.
Not sure how JIRA
You can both rename a version in JIRA (so we could rename 1.0-final to rc2
now), and merge two together (if we started targetting to rc3 and decided we
didn't need it and merged it with 1.0 for example).
- Brett
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent:
1 - 100 of 115 matches
Mail list logo
