Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1199
Here is an overview of the issue:
---
Brett Porter <[EMAIL PROTECTED]> wrote on 15/03/2004 12:55:34 PM:
> Plugins are released independantly, and while Maven comes bundled with
the
> latest set and new features are regularly added, you are welcome to use
your
> own stable set, and enforce that by plugin dependencies in project.xml.
On Monday 15 March 2004 09:55, Brett Porter wrote:
Dion, Brett...
> This has been the focus for about 6 months.
:o)
> In terms of core, RC2 is basically RC1 with bugfixes and internal clean up.
> The current road map for 1.0 has no featuritis :) All new features get
> pushed to maven 1.1. Every
Niclas Hedhman <[EMAIL PROTECTED]> wrote on 15/03/2004 12:41:00 PM:
> On Monday 15 March 2004 08:11, [EMAIL PROTECTED] wrote:
> > As part of the ongoing process of decoupling the core, I think we
should
> > split the jelly tags out from the maven cvs repository into a
maven-tags
> > repository.
Hi Niclas,
This has been the focus for about 6 months.
In terms of core, RC2 is basically RC1 with bugfixes and internal clean up.
The current road map for 1.0 has no featuritis :) All new features get
pushed to maven 1.1. Everything that works on RC1 right now should work on
MAVEN-1_0-BRANCH.
P
> For my curiosity, reason for -1 on the werkz additions (not
> that I was
> thinking about it, but)
Its (unfortunately) very much tied into the way the plugin manager works and
vice-versa. And it'll disappear (or be much thinner) in maven2 anyway, as
none of the plugin handling is tied to J
On Monday 15 March 2004 08:11, [EMAIL PROTECTED] wrote:
> As part of the ongoing process of decoupling the core, I think we should
> split the jelly tags out from the maven cvs repository into a maven-tags
> repository.
Hi,
I am using Maven only because Avalon decided at some point to adapt it, a
Brett Porter <[EMAIL PROTECTED]> wrote on 15/03/2004 12:04:02 PM:
> +0 to doing it for the maven: tags, -1 for the werkz additions (which I
> don't think you are referring to anyway).
For my curiosity, reason for -1 on the werkz additions (not that I was
thinking about it, but)
> There may
+0 to doing it for the maven: tags, -1 for the werkz additions (which I
don't think you are referring to anyway).
There may be a problem here anyway because of the classloaders - so if they
are split, I'm not sure if you can use different versions across projects.
I'm ok with this happening if th
As part of the ongoing process of decoupling the core, I think we should
split the jelly tags out from the maven cvs repository into a maven-tags
repository.
One of the issues with maven releases has been that new tags are
introduced, and the tags are part of the core maven jar. This would help
Message:
The following issue has been closed.
Resolver: Ben Walding
Date: Sun, 14 Mar 2004 6:04 PM
Done
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1198
Here is an overview of the i
evenisse2004/03/14 07:47:54
Modified:maven-plugins/maven-scm-plugin project.xml
maven-plugins/maven-scm-plugin/src/java/org/apache/maven/plugin
ScmPlugin.java
maven-plugins/maven-scm-plugin/src/resources/META-INF/maven
The following issue has been updated:
Updater: Sean Kelly (mailto:[EMAIL PROTECTED])
Date: Sun, 14 Mar 2004 10:38 AM
Comment:
project.xml file for JEP
Changes:
Attachment changed to project.xml
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1198
Here is an overview of the issue:
---
evenisse2004/03/14 07:02:34
Modified:pdf/xdocs changes.xml
Log:
Add some due-to.
Revision ChangesPath
1.12 +5 -5 maven-plugins/pdf/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/c
15 matches
Mail list logo
