> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 23 April 2004 01:38
> To: 'Maven Developers List'
> Subject: RE: [Q] Setting a property so that it's visible from another
> plugin
[snip]
> > In my case at work, we are using beta 10. We want to move to
> > rc2
brett 2004/04/22 20:19:28
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenSession.java MavenUtils.java
src/java/org/apache/maven/cli Tag: MAVEN-1_0-BRANCH App.java
src/java/org/apache/maven/jelly Tag: MAVEN-1_0-BRANCH
The following comment has been added to this issue:
Author: Dan Tran
Created: Thu, 22 Apr 2004 9:26 PM
Body:
I am looking for jelly tag to traverse a directory and its sub
with capability to dertermine if a node is a directory.
This way I can implement the xdocs feature I suggeste
On Thu, 2004-04-22 at 20:02, Brett Porter wrote:
> Something dion raised a while back, but I propose that we do the following
> for RC3:
>
> - Create a subdirectory (new project) maven-jelly-tags in the existing maven
> CVS tree
> - copy maven/src/java/org/apache/maven/jelly/tags/maven/* and
> mav
Something dion raised a while back, but I propose that we do the following
for RC3:
- Create a subdirectory (new project) maven-jelly-tags in the existing maven
CVS tree
- copy maven/src/java/org/apache/maven/jelly/tags/maven/* and
maven/src/java/org/apache/maven/jelly/tags/BaseTag*.java + package
Brett Porter wrote:
Great - thanks Stephen. IIRC I fixed the manifest problems for the next
release of the JAR plugin (or at least assigned the issue to myself to do by
then :)
That's terrific news.
Let me know if you want any additional help/feedback on this one.
Cheers, Stephen.
--
|---
Great - thanks Stephen. IIRC I fixed the manifest problems for the next
release of the JAR plugin (or at least assigned the issue to myself to do by
then :)
Cheers,
Brett
> -Original Message-
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]
> Sent: Friday, 23 April 2004 9:46 AM
> To:
Brett Porter wrote:
I was speaking to some Atlassian folk last night and they are also on
beta-10, as is Avalon. I wonder how many others have decided to stick with
it?
Just for reference - Avalon builds have been updated to work with RC2.
Some tweaking was needed on the site generation and some
> Just to summarize: I'm +1 to add a new setter tag and make it
> available for plugins. I may even be able to add it sometime
> tomorrow if others Maven committers also agree.
>
> I think we have 2 solutions:
>
> 1/ We deprecate pluginVar, and create a new tag called
> something like: getPlug
Yes, I think we should do point releases if necessary.
The PMC have also been discussing future versioning strategy so that what a
beta and an RC are clearer for future releases.
Cheers,
Brett
> -Original Message-
> From: Heritier Arnaud [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 22 Ap
> It might still be a good idea to have a core maven plugin
> containing for example the jelly tags so that previous users
> can also upgrade to newer versions of the plugins.
I actually like Dion's idea better - a tag library JAR that plugins can
include in the same way as, say, jelly-tags-xml.
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Thu, 22 Apr 2004 5:16 PM
Body:
Thx a lot.
I submitted a similar patch some days ago (MPXDOC-97).
I'll see as soon as possible with the dev team if we can apply it.
-
vmassol 2004/04/22 13:01:43
Modified:xdocs/reference Tag: MAVEN-1_0-BRANCH dirlayout.xml
Log:
removed iutest directory which has been deprecated a long time ago. Cactus tests
location is defined by the Cactus plugin (it defaults to src/test-cactus).
Revision ChangesPath
The following issue has been updated:
Updater: Harald Ommang (mailto:[EMAIL PROTECTED])
Date: Thu, 22 Apr 2004 3:26 PM
Comment:
This patch (relative to maven-plugins/xdoc) adds the target feature with a minor
modification to plugin.jelly and site.jsl.
Changes:
Atta
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPXDOC-99
Here is an overview of the issue:
The following comment has been added to this issue:
Author: Dan Tran
Created: Thu, 22 Apr 2004 1:16 PM
Body:
Since I am new to jelly, it will take sometimes, but it is well worth the effort.
-
View this comment:
evenisse2004/04/22 09:45:19
Modified:xdocsTag: MAVEN-1_0-BRANCH changes.xml
Log:
MAVEN-1226.
Revision ChangesPath
No revision
No revision
1.14.4.10 +1 -0 maven/xdocs/changes.xml
Index: changes.xml
===
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 22 Apr 2004 12:39 PM
Body:
Do you have a patch?
-
View this comment:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Thu, 22 Apr 2004 12:30 PM
Body:
It works for me, but I work with rc3. Perhaps we fixed a bug in maven core.
-
View this comment:
The following comment has been added to this issue:
Author: Dan Tran
Created: Thu, 22 Apr 2004 11:31 AM
Body:
I replace my local pluggin.jelly with the one in cvs. The problem is still there.
-
View this comment:
Just to summarize: I'm +1 to add a new setter tag and make it available
for plugins. I may even be able to add it sometime tomorrow if others
Maven committers also agree.
I think we have 2 solutions:
1/ We deprecate pluginVar, and create a new tag called something like:
getPluginVar. We add anoth
Just to summarize: I'm +1 to add a new setter tag and make it available
for plugins. I may even be able to add it sometime tomorrow if others
Maven committers also agree.
I think we have 2 solutions:
1/ We deprecate pluginVar, and create a new tag called something like:
getPluginVar. We add anoth
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 22 April 2004 09:23
> To: 'Maven Developers List'
> Subject: RE: Maven extensions (was RE: [Q] Setting a property so that
it's
> visible from another plugin)
>
> Dion was going to do this last year (actually make
Ok, I was forgetting that you don't have to upgrade to a newer version
of the plugins... :-)
It might still be a good idea to have a core maven plugin containing for
example the jelly tags so that previous users can also upgrade to newer
versions of the plugins.
In my case at work, we are using b
Did you already define if after the 1.0 release we will apply a release strategy like
httpd, tomcat and others ??
It will help us to produce distributions more often.
Another interest is to not afraid users with terms like RC or beta.
Arnaud.
-Message d'origine-
De : Brett Porter [mail
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPCHANGES-7
Here is an overview of the issue:
--
brett 2004/04/22 00:34:57
Modified:changes/src/main/org/apache/maven/changes
ReleaseVersion.java
changes/xdocs changes.xml
Added: changes/src/test/org/apache/maven/changes
ReleaseVersionTest.java
chan
brett 2004/04/22 00:34:16
maven-plugins/changes/src/test/org/apache/maven/changes - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
brett 2004/04/22 00:33:19
maven-plugins/changes/src/test/org/apache/maven - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
brett 2004/04/22 00:32:46
maven-plugins/changes/src/test/org/apache - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
brett 2004/04/22 00:32:14
maven-plugins/changes/src/test-data - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
brett 2004/04/22 00:32:14
maven-plugins/changes/src/test/org - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Dion was going to do this last year (actually make a tags JAR), but nothing
came of it.
The only plugin that requires RC3+ is multiproject for the reactor tag, and
you wouldn't want to upgrade multiproject other than to get the memory
enhancements that come with the new tag.
To be honest, I'd rat
> production and you just simply can't break them completely,
> even though it's a beta or rc... :-)
You don't have to upgrade either.
> At least, we should make an attempt not to break them. For
Have I broken anything since rc1 that hasn't been fixed? My goal was 100%
compatibility and I've a
I think we already have a mechanism to provide extensions to Maven: it's
called a plugin! Thus an even better solution for adding the setter tag
is to move all the existing Maven Jelly tags to a plugin of its own.
That will allow maven b10, rc1, etc users to automatically get the new
features witho
35 matches
Mail list logo
