dion2003/11/26 22:54:17
Modified:webserver project.xml
Log:
Fix version name
Revision ChangesPath
1.17 +1 -1 maven-plugins/webserver/project.xml
Index: project.xml
===
RCS file: /home/c
Jörg Schaible <[EMAIL PROTECTED]> wrote on 26/11/2003
11:49:11 PM:
> Hello,
>
> currently I fight with the Jelly script for a plugin extension and I got
> stuck. See the following example:
>
> Having following properties:
> all=y,x
> prop.x=1
> prop.y=2
> prop.z=0
>
> I would like to iterate
dion2003/11/26 22:51:08
Modified:simian maven.xml
Log:
Use pluginVar tag
Revision ChangesPath
1.3 +4 -2 maven-plugins/simian/maven.xml
Index: maven.xml
===
RCS file: /home/cvs/maven-
dion2003/11/26 22:49:53
Modified:sea plugin.jelly
Log:
Removed unnecessary use of pom.getPluginContext
Revision ChangesPath
1.5 +3 -3 maven-plugins/sea/plugin.jelly
Index: plugin.jelly
dion2003/11/26 22:49:05
Modified:repository/src/plugin-resources repository-audit.xml
Log:
Add poolman
Revision ChangesPath
1.33 +7 -0
maven-plugins/repository/src/plugin-resources/repository-audit.xml
Index: repository-audit.xml
The following comment has been added to this issue:
Author: Matt Johnson
Created: Thu, 27 Nov 2003 12:25 AM
Body:
Sorry I didn't clarify earlier - the patch works for me on both JDK1.3.1 and JDK1.4
-
View the issue
Where did this discussion end up.
>From what I can tell, I suggested we re-use the element with
a new , and then discussion stalled.
Is that it?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---
> I've always liked this idea and actually tried to do it in
> Turbine but nobody went for it. I think it clearly separates
> the docs and we can actually give out perms to doco folk (if
> we ever get some :-)) and not worry about them punching the core.
>
> +1
>
I've put it in JIRA to do for
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1056
Here is an overview of the issue:
-
On Wed, 2003-11-26 at 17:59, Brett Porter wrote:
> > I would say the normal site should point at the current
> > release docs and then use your scheme to point at any number
> > of desired branches.
>
> I agree. This was the original plan I think. I like the way Cactus does it
> too, in the top
> I would say the normal site should point at the current
> release docs and then use your scheme to point at any number
> of desired branches.
I agree. This was the original plan I think. I like the way Cactus does it
too, in the top right nav link.
But in the interim, we just keep doing what
On Wed, 2003-11-26 at 17:25, Vincent Massol wrote:
> Some ideas... :-)
>
> Why not 2 web sites:
>
> - maven.apache.org pointing to HEAD
> - maven.apache.org/1.0/ pointing to MAVEN-1_0-BRANCH
I think we need a site for the current release as well. And I suppose
any number of arbitrary branches th
On Wed, 2003-11-26 at 17:13, Brett Porter wrote:
> Just a thought... should the main site now be generated from
> MAVEN-1_0-BRANCH or HEAD?
>
> I'm +1 for the branch as it is the next release and all changes made there
> will go to HEAD eventually.
Yah, I agree. Whatever branch is slated for the
Some ideas... :-)
Why not 2 web sites:
- maven.apache.org pointing to HEAD
- maven.apache.org/1.0/ pointing to MAVEN-1_0-BRANCH
I prefer this way. On the Cactus project I tried the opposite (i.e.
default pointing to latest release) and it didn't work that well. After
a few weeks we swapped to HE
So I'm an elephant?
Brain ... Can't... Cope. Must .. Get... Coffee.
> -Original Message-
> From: Ben Walding [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 November 2003 9:25 AM
> To: Maven Developers List
> Subject: Re: CVS changes
>
>
> How do you know if you have an elephant in your
How do you know if you have an elephant in your computer?
Footprints on your C drive.
Brett Porter wrote:
I'm sorry, but I don't have a clue what you are talking about.
- Brett
-Original Message-
From: Aaron Anodide [mailto:[EMAIL PROTECTED]
Sent: Thursday, 27 November 2003 8:53 AM
Just a thought... should the main site now be generated from
MAVEN-1_0-BRANCH or HEAD?
I'm +1 for the branch as it is the next release and all changes made there
will go to HEAD eventually.
I think we need to resurrect that plan for general site publishing rules
from earlier in the year and fle
I'm sorry, but I don't have a clue what you are talking about.
- Brett
> -Original Message-
> From: Aaron Anodide [mailto:[EMAIL PROTECTED]
> Sent: Thursday, 27 November 2003 8:53 AM
> To: 'Maven Developers List'
> Subject: RE: CVS changes
>
>
> Brett,
>
> Is your footprints on the C
Brett,
Is your footprints on the C drive?
Aaron
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 26, 2003 4:35 PM
To: 'Maven Developers List'; [EMAIL PROTECTED]
Subject: RE: CVS changes
Hi Vincent,
Yes, that is a good practice. I split changes.
Hi Vincent,
Yes, that is a good practice. I split changes.xml so that the right changes
went on the right branch. I didn't add any entries for the stuff that I
merged which was done by others. I will add comments to the version on the
branch soon about the changes made to the contexts, and that sh
vmassol 2003/11/26 13:21:54
Modified:ear/xdocs changes.xml
ear project.xml
Log:
Continue work for 1.4 version
Revision ChangesPath
1.12 +3 -0 maven-plugins/ear/xdocs/changes.xml
Index: changes.xml
==
vmassol 2003/11/26 13:17:55
Modified:ear/xdocs navigation.xml changes.xml
ear plugin.properties project.xml
Log:
Prepare for 1.3 release
Revision ChangesPath
1.3 +7 -3 maven-plugins/ear/xdocs/navigation.xml
Index: navigation.xml
=
vmassol 2003/11/26 13:11:35
Modified:ejb/xdocs changes.xml
ejb project.xml
Log:
continue work for version 1.3
Revision ChangesPath
1.10 +3 -0 maven-plugins/ejb/xdocs/changes.xml
Index: changes.xml
==
vmassol 2003/11/26 13:08:02
Modified:ejb plugin.properties project.properties project.xml
Log:
A few more things I have forgotten before the 1.2 release...
Revision ChangesPath
1.5 +1 -1 maven-plugins/ejb/plugin.properties
Index: plugin.properties
=
vmassol 2003/11/26 13:00:47
Modified:ejb .cvsignore
Log:
ignore build.properties
Revision ChangesPath
1.2 +1 -0 maven-plugins/ejb/.cvsignore
Index: .cvsignore
===
RCS file: /home/cvs/
vmassol 2003/11/26 12:59:41
Modified:ejb/xdocs changes.xml navigation.xml
ejb project.xml
Log:
Release version 1.2
Revision ChangesPath
1.9 +6 -4 maven-plugins/ejb/xdocs/changes.xml
Index: changes.xml
=
Hi,
I have a custom tag in the issuetracker plugin:
[...]
[...]
This tag calls some java class.
Now, I'm trying to use this tag from the changes plugin. I get a
ClassNotFoundException on org.apache.maven.issuetracker.IssueFinder.
This does no
Jason van Zyl wrote on Wednesday, November 26, 2003 4:56 PM:
> On Wed, 2003-11-26 at 10:55, Jason van Zyl wrote:
>> It might be easier to just keep attaching patches and comments to the
>> same issue. With comments you can tell me what's applicable and
>> what's not. It's easier to see all these pa
James Strachan wrote:
On 26 Nov 2003, at 08:39, Nicola Ken Barozzi wrote:
...
Look in Forrest, we are doing just that since some time now.
http://xml.apache.org/forrest/forrest-issues.html
If you want to grab the stylesheet, go ahead, it's Apache-licensed ;-)
I took a quick look at the page - and m
Jason van Zyl wrote on Wednesday, November 26, 2003 4:55 PM:
> On Wed, 2003-11-26 at 10:05, Jörg Schaible wrote:
>> Since I do not have the rights to remove an obsolete attachment from
>> JIRA, you may just use the attachment with the highest ID in ist URL
>> if patch files with the same name exis
On Wed, 2003-11-26 at 10:55, Jason van Zyl wrote:
> On Wed, 2003-11-26 at 10:05, Jörg Schaible wrote:
> > Hello Jason,
> >
> > Jörg Schaible wrote on Tuesday, November 25, 2003 6:52 PM:
> > > Jörg Schaible wrote on Tuesday, November 25, 2003 5:07 PM:
> > >> My fear was obviously reasonable. I'll g
On Wed, 2003-11-26 at 10:05, Jörg Schaible wrote:
> Hello Jason,
>
> Jörg Schaible wrote on Tuesday, November 25, 2003 6:52 PM:
> > Jörg Schaible wrote on Tuesday, November 25, 2003 5:07 PM:
> >> My fear was obviously reasonable. I'll get the CVS update and create
> >> the patches again (also for
On Wed, 2003-11-26 at 10:41, Vincent Massol wrote:
> Jason,
>
> How do we subscribe to these lists? I tried sending an email to
> [EMAIL PROTECTED] but it did not succeed.
Sorry, I was thinking of the old turbine days for some reason ... they
are:
wagon-dev
wagon-users
wagon-cvs
Sorry about tha
On 26 Nov 2003, at 08:39, Nicola Ken Barozzi wrote:
James Strachan wrote:
On all the OS projects I work (actually on the commercial ones too :)
I'd like to do all change management & issue tracking on JIRA. I like
the changes.xml report in Maven as well; I wonder has anyone figured
out how to
Jason,
How do we subscribe to these lists? I tried sending an email to
[EMAIL PROTECTED] but it did not succeed.
Thanks
-Vincent
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 16:30
> To: Maven Developers List
> Subject: Importing Wagon
>
>
On Wed, 2003-11-26 at 10:31, Vincent Massol wrote:
> > -Original Message-
> > From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Sent: 26 November 2003 16:22
> > To: Maven Developers List
> > Subject: Re: Adding explicit plugin dependencies
> >
> > On Wed, 2003-11-26 at 03:55, Vincent Masso
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 16:22
> To: Maven Developers List
> Subject: Re: Adding explicit plugin dependencies
>
> On Wed, 2003-11-26 at 03:55, Vincent Massol wrote:
> > Hi,
> >
> > I'd like to start adding explicit depe
Howdy,
Before I get too far into my day I'm going to import Wagon. All the
mailing lists are setup:
maven-wagon-dev
maven-wagon-users (I think we got the plural but no biggie)
maven-wagon-cvs
I'm going to import the code and then we'll be ready to roll.
Another note is that I will be sending ma
On Wed, 2003-11-26 at 03:55, Vincent Massol wrote:
> Hi,
>
> I'd like to start adding explicit dependencies for maven plugins.
+1
The plugin dependency mechanism will need a little adjusting but that's
not that big of a deal. I'm not sure how much of the dependency
resolving code Brett merged f
On Wed, 2003-11-26 at 03:55, Vincent Massol wrote:
> Hi,
>
> Initially I had started putting some logic for accessing issue trackers
> in the changes plugin (that was the first plugin requiring this
> information). However, I also need it for the dashboard plugin (I'm
> currently adding an aggrega
The following comment has been added to this issue:
Author: Archimedes Trajano
Created: Wed, 26 Nov 2003 9:14 AM
Body:
I don't have the rights, use the bigger one
-
View the issue:
http://jira.codehaus.org/secur
Hello Jason,
Jörg Schaible wrote on Tuesday, November 25, 2003 6:52 PM:
> Jörg Schaible wrote on Tuesday, November 25, 2003 5:07 PM:
>> My fear was obviously reasonable. I'll get the CVS update and create
>> the patches again (also for MAVEN-1052 and MAVEN-1053). May I sent a
>> consolidated patch
vmassol 2003/11/26 07:04:02
Modified:dashboard/xdocs authoring.xml
Log:
Added missing part about telling the dashboard plugin to use the custom aggregator
Revision ChangesPath
1.2 +8 -0 maven-plugins/dashboard/xdocs/authoring.xml
Index: authoring.xml
===
vmassol 2003/11/26 07:00:10
Modified:dashboard/xdocs changes.xml navigation.xml
Added: dashboard/xdocs authoring.xml
Log:
Start of an Aggregator authoring guide
Revision ChangesPath
1.9 +3 -0 maven-plugins/dashboard/xdocs/changes.xml
Index: changes
Hello,
currently I fight with the Jelly script for a plugin extension and I got stuck. See
the following example:
Having following properties:
all=y,x
prop.x=1
prop.y=2
prop.z=0
I would like to iterate over the properties "prop." defined in "all":
${all}
prop.${i}:${prop[i]}
The s
Brett,
Very cool. I haven't checked yet but have you been careful about adding
information to the top level changes.xml file so that we know what has
been added in 1.1 vs 1.0? It would be a good practice that committers
use this file I think.
Thanks
-Vincent
> -Original Message-
> From:
Hi,
Just a brief not to let everyone know I've done the CVS branch switch.
All changes for 1.0 need to go on the MAVEN-1_0-BRANCH branch, while the
1.1 free for all can take place on CVS HEAD :)
I'll turn my attention to repairing the remaining reactor bugs on the
branch next week.
Cheers,
Br
brett 2003/11/26 03:55:13
Modified:.project.xml
Log:
start next version
Revision ChangesPath
1.318 +1 -1 maven/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven/project.
brett 2003/11/26 03:45:18
Modified:.Tag: MAVEN-1_0-BRANCH build-bootstrap.xml
project.xml
src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
AntProjectBuilder.java MavenSession.java
MavenUtils.j
James Strachan wrote:
On all the OS projects I work (actually on the commercial ones too :)
I'd like to do all change management & issue tracking on JIRA. I like
the changes.xml report in Maven as well; I wonder has anyone figured out
how to get JIRA to generate this report (i.e. something lik
The following comment has been added to this issue:
Author: Vincent Massol
Created: Wed, 26 Nov 2003 4:58 AM
Body:
Which patch should I use. There are 2 patches with the same name! Could you please
remove the one that shouldn't be used? If you don't have the rights,please tell me
vmassol 2003/11/26 02:51:09
Modified:dashboard/xdocs index.xml
Log:
Make sure users understand that the dashboard plugin is to be used when you have
several subpojects only.
Revision ChangesPath
1.3 +5 -0 maven-plugins/dashboard/xdocs/index.xml
Index: ind
brett 2003/11/26 02:26:31
Removed: src/plugins-build/clean Tag: MAVEN_RC2_UNSTABLE .cvsignore
plugin.jelly plugin.properties project.properties
project.xml
src/plugins-build/clean/src/plugin-test Tag:
brett 2003/11/26 01:59:47
Modified:.Tag: MAVEN_RC2_UNSTABLE build-bootstrap.xml
maven.xml project.properties
src/bootstrap/org/apache/maven Tag: MAVEN_RC2_UNSTABLE
BootstrapTask.java
xdocs/misc Tag: M
> -Original Message-
> From: Jean-François El Fouly [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 10:15
> To: [EMAIL PROTECTED]
> Subject: Re: new plugin: issuetracker
>
> A 09:55 26/11/2003 +0100, vous avez écrit :
> >Hi,
> >
> >Initially I had started putting some logic for access
Hi,
we're also working on this, the upcoming JIRA version 2.5.2 will allow the addition of
custom fields (ie fixfor/affected versions) to the RSS feed (atlassian missed this in
the current release). We have an XSL that transforms the RSS feed to changes.xml..
although I must say that the chang
A 09:55 26/11/2003 +0100, vous avez écrit :
Hi,
Initially I had started putting some logic for accessing issue trackers
in the changes plugin (that was the first plugin requiring this
information). However, I also need it for the dashboard plugin (I'm
currently adding an aggregator that counts the
Ryan Hoegg wrote on Tuesday, November 25, 2003 9:43 PM:
> I wrote the first pass at genapp templates, and all this stuff sounds
> great. One thing I'd like to see as well is the ability for other
> installed plugins to define additional templates somehow.
> Maybe allow
> template namespaces that l
brett 2003/11/26 01:08:31
Modified:touchstone-partner plugin.jelly
Log:
extra tests
Revision ChangesPath
1.5 +14 -0 maven-plugins/touchstone-partner/plugin.jelly
Index: plugin.jelly
===
R
Hi,
I'd like to start adding explicit dependencies for maven plugins. Now
that each plugin can be downloaded separately, I think this is a
required step: Let's say I release a new version of plugin X. However,
for this plugin to run I've also modified another plugin Y. When the end
user runs "mave
Hi,
Initially I had started putting some logic for accessing issue trackers
in the changes plugin (that was the first plugin requiring this
information). However, I also need it for the dashboard plugin (I'm
currently adding an aggregator that counts the numbers of open bugs per
project).
I have
Yes but how do you get the map of fixfor ids?
Thanks
-Vincent
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 26 November 2003 09:07
> To: Maven Developers List
> Subject: RE: generating changes.xml from JIRA
>
> Jira has an xml format that can be accesse
Jira has an xml format that can be accessed via URL, e.g.
http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10030&fixfor=10245&resolutionIds=-1&sorter/field=priority&sorter/order=DESC&tempMax=25&reset=true
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/pe
Hi James,
I was looking into this too! However, I don't know how to get the
information from JIRA (apart from writing our own Jelly script that is
run inside JIRA). I looked into the JIRA forums briefly and couldn't
find an answer. Maybe we should post a question? I fear the answer is
jelly which
The following issue has been updated:
Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED])
Date: Wed, 26 Nov 2003 1:35 AM
Comment:
Use this patch instead, it has documentation updates. Along with a change to the
issue tracking URL (it was pointing to the wrong one) I have added
The following comment has been added to this issue:
Author: Vincent Massol
Created: Wed, 26 Nov 2003 1:34 AM
Body:
Hi Archimedes,
Hehe, jelly is a bit hard initially. However you can always have a look in the
plugin.jelly files that you have on your computer (they are in [user ho
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Wed, 26 Nov 2003 1:26 AM
Cool. Again this plugin is not meant to work for a single project. If you wish to
submit some patches (documentation or code), I'll gladly apply it. Thanks.
---
On Wed, 26 Nov 2003, Brett Porter <[EMAIL PROTECTED]> wrote:
> Say Maven changes something that breaks some else's build - this is
> probably of interest to both Maven and the gumped project as soon as
> possible. On the other hand, if Maven is broken (heaven forbid!),
> you really don't want to s
The following issue has been updated:
Updater: Archimedes Trajano (mailto:[EMAIL PROTECTED])
Date: Wed, 26 Nov 2003 1:21 AM
Comment:
This is my attempt to do it. Seems to work on my copy, but I am not sure if the patch
works well.
Changes:
Attachment changed to jb
Hi James,
I've been thinking about this a while since dion originally suggested it. As
far as we have gotten was Vincent adding in an issue number to the changes
report.
I guess the next step is to take the versions specified and suck any issues
out of JIRA's XML that are "fixed for" that version
70 matches
Mail list logo
