dion2004/06/29 23:49:07
Modified:.maven.xml
Log:
Dashboard is currently broken in multiproject test mode
Revision ChangesPath
1.7 +1 -0 maven-plugins/maven.xml
Index: maven.xml
=
dion2004/06/29 23:47:24
Modified:dist/src/plugin-test maven.xml
Log:
Stop breakage on version change
Revision ChangesPath
1.5 +1 -1 maven-plugins/dist/src/plugin-test/maven.xml
Index: maven.xml
Sure, it just seems weird to me to have changed the source code, but
the project version number is unchanged.
On Wed, 30 Jun 2004 07:45:31 +0200, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
> Hi dIon,
>
> The changes.xml file is supposed to contain only user-visible changes (i.e
> changes that i
Hi Brett,
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mercredi 30 juin 2004 01:54
> To: Maven Developers List
> Subject: Re: RC4, releases and votes
>
> IIRC I did that about a week beforehand - although I could be confused.
>
> Anyway, the Maven 1.0 relea
Hi dIon,
The changes.xml file is supposed to contain only user-visible changes (i.e
changes that interest the plugin users). For all other changes we have the
changelog report.
Thanks
-Vincent
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: mercredi 30 juin 20
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 30 Jun 2004 1:30 AM
Body:
The plugin currently works with JMeter 1.8.x, and hasn't been tested against 2.0
Do you have a small sample JMeter file for us to look at?
-
dion2004/06/29 22:25:56
Modified:latka/src/plugin-test project.xml maven.xml
Log:
Check results can be parsed at least
Revision ChangesPath
1.2 +7 -1 maven-plugins/latka/src/plugin-test/project.xml
Index: project.xml
=
dion2004/06/29 22:02:53
Modified:latka/src/plugin-test maven.xml
Log:
Reminder
Revision ChangesPath
1.2 +2 -0 maven-plugins/latka/src/plugin-test/maven.xml
Index: maven.xml
===
RCS fil
dion2004/06/29 22:01:34
Modified:latka/src/plugin-test file1.jmx
Log:
*** keyword substitution change ***
Revision ChangesPath
1.2 +1276 -1276maven-plugins/latka/src/plugin-test/file1.jmx
http://cvs.apache.org/viewcvs/maven-plugins/latka/src/plugin-test/fi
dion2004/06/29 22:01:01
maven-plugins/latka/src/plugin-test - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
dion2004/06/29 21:46:16
Modified:latka/xdocs index.xml changes.xml goals.xml
latkaproject.xml
Log:
Document JMeter version tested against
Revision ChangesPath
1.4 +5 -2 maven-plugins/latka/xdocs/index.xml
Index: index.xml
=
Done.
I'm assuming from this that any changes to the plugin tests is not to
be recorded other than in the commit message, and that this includes
adding plugin test projects as well.
Is this right?
On Wed, 30 Jun 2004 12:05:35 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote:
>
> I'm happy to go ba
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1353
Here is an overview of the issue:
-
Key:
dion2004/06/29 21:20:54
Modified:xdoc/src/plugin-test project.xml
xdoc/xdocs changes.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.3 +1 -1 maven-plugins/xdoc/src/plugin-test/project.xml
dion2004/06/29 21:19:27
Modified:html2xdoc/src/plugin-test project.xml
html2xdoc/xdocs changes.xml
html2xdoc project.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.4 +1 -1
dion2004/06/29 21:18:36
Modified:gump/src/plugin-test project.xml
gump/xdocs changes.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.4 +1 -1 maven-plugins/gump/src/plugin-test/project.xml
dion2004/06/29 21:17:55
Modified:faq project.xml
faq/src/plugin-test project.xml
faq/xdocs changes.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.36 +1 -1 maven-plugin
dion2004/06/29 21:17:04
Modified:dist/src/plugin-test project.xml
dist/xdocs changes.xml
dist project.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.3 +1 -1 maven-plug
dion2004/06/29 21:16:05
Modified:clean/xdocs changes.xml
clean/src/plugin-test project.xml
cleanproject.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.12 +0 -3 maven-pl
dion2004/06/29 21:15:06
Modified:checkstyle/src/plugin-test project.xml
checkstyle/xdocs changes.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.5 +1 -1 maven-plugins/checkstyle/src/plugi
> > > Do we really care about sourceModifications? Should we generate it for
> > > everything, or will this double up?
> >
> > I never used sourceModifications in my projects. I'm not sure that it is very
> > usefull to use it
> in the javadoc plugin.
>
> Where sourcemods is handy is for generate
dion2004/06/29 21:14:08
Modified:changes/xdocs changes.xml
changes/src/plugin-test project.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.26 +0 -1 maven-plugins/changes/xdocs/changes.xml
dion2004/06/29 21:13:01
Modified:artifact/xdocs changes.xml
artifact/src/plugin-test project.xml
Log:
Remove tests changes from documentation and version increase per Brett
Revision ChangesPath
1.24 +0 -1 maven-plugins/artifact/xdocs/changes.x
On Wed, 30 Jun 2004 06:03:06 +0200, Arnaud Heritier
<[EMAIL PROTECTED]> wrote:
>
> >
> > Do we really care about sourceModifications? Should we generate it for
> > everything, or will this double up?
>
> I never used sourceModifications in my projects. I'm not sure that it is very
> usefull to u
>
> Do we really care about sourceModifications? Should we generate it for
> everything, or will this double up?
I never used sourceModifications in my projects. I'm not sure that it is very usefull
to use it in the javadoc plugin.
>
> That check can also check for the existence of JDK 1.4+ w
I'm happy to go back and remove them.
Let me know if u want it done.
On Wed, 30 Jun 2004 10:08:19 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> dIon,
>
> Bumping the version of the plugin because the test changed seems backwards to
> me. Isn't that why a plugin test has a project of its ow
dIon,
Bumping the version of the plugin because the test changed seems backwards to
me. Isn't that why a plugin test has a project of its own?
Probably likewise for the changes entry. I don't believe non-functional changes
should go in changes.xml.
Cheers,
Brett
Quoting [EMAIL PROTECTED]:
> di
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1352
Here is an overview of the issue:
-
Key:
Do we really care about sourceModifications? Should we generate it for
everything, or will this double up?
That check can also check for the existence of JDK 1.4+ where the bugs in
javadoc are fixed IIRC.
- Brett
Quoting Heritier Arnaud <[EMAIL PROTECTED]>:
> Hello guys,
>
> Several weeks
IIRC I did that about a week beforehand - although I could be confused.
Anyway, the Maven 1.0 release will be very light on changes. I won't be
releasing any plugins unless I did specific work on them and think they are ready.
If anyone has a plugin release they want to do by Maven 1.0, please fi
I've got no hassle with the PMC deciding in private when a release is.
Notification that it's upcoming would help me do things I might've
been sitting on, or other people could have issues not yet in Jira
that they'd prefer addressed before the release.
On Wed, 30 Jun 2004 09:05:52 +1000, Brett P
I'm happy to hold these on the dev list in future (usually do anyway) - but it's
my understanding that it is the PMC that is responsible for this type of vote so
hopefully this wasn't an issue.
Cheers,
Brett
Quoting Emmanuel Venisse <[EMAIL PROTECTED]>:
>
> - Original Message -
> From:
given that one modifies the
#template.properties
maven.genapp.repackage=${src-dir-nm},${tst-dir-nm}
and that if one should insert a
to expose said properties such as
src-dir-nm=alt.srcdirnm
why is it that when plugin.jelly gets around to parsing the "maven.genapp.repackage"
value pair w
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1351
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1350
Here is an overview of the issue:
-
Key:
vmassol 2004/06/29 13:41:14
Modified:changes/xdocs changes.xml
Log:
Fixed hasty copy-paste...
Revision ChangesPath
1.25 +1 -1 maven-plugins/changes/xdocs/changes.xml
Index: changes.xml
===
vmassol 2004/06/29 13:40:28
Modified:changes/src/plugin-resources/images rss.png
changes/src/plugin-resources changes2rss.jsl
Log:
Binary --> Ascii
Revision ChangesPath
1.2 +1 -1 maven-plugins/changes/src/plugin-resources/images/rss.png
vmassol 2004/06/29 13:39:56
Modified:changes project.xml plugin.jelly
changes/src/plugin-resources changes.jsl
changes/xdocs changes.xml
Added: changes/src/plugin-resources/images rss.png
changes/src/plugin-resources changes2rss.jsl
vmassol 2004/06/29 13:39:49
maven-plugins/changes/src/plugin-resources/images - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
The following comment has been added to this issue:
Author: Charles Crouch
Created: Tue, 29 Jun 2004 3:42 PM
Body:
I have also noticed that my custom goal is getting executed twice.
Here is a snippet of maven.xml
When ever I run java:compile, jar:install or mult
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1349
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1348
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPCRUISECONTROL-5
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Charles Crouch (mailto:[EMAIL PROTECTED])
Date: Tue, 29 Jun 2004 11:43 AM
Comment:
Changes to plugin.jelly as a patch
Changes:
Attachment changed to plugin.jelly.patch
---
The following issue has been updated:
Updater: Jon Strayer (mailto:[EMAIL PROTECTED])
Date: Tue, 29 Jun 2004 11:10 AM
Comment:
Here is the patch file for the project.xml. As you can see, all I did was add a
dependency for the cactus plugin.
Changes:
Attachment cha
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVA-22
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVENUPLOAD-151
Here is an overview of the issue:
-
dion2004/06/29 06:55:38
Modified:xdoc/xdocs changes.xml
xdoc/src/plugin-test maven.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.56 +1 -0 maven-plugins/xdoc/xdocs/changes.xml
Index: changes.xml
===
dion2004/06/29 06:43:16
Modified:java/xdocs changes.xml
java/src/plugin-test maven.xml
java project.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.12 +3 -0 maven-plugins/java/xdocs/changes.xml
Index: c
> -Original Message-
> From: Jerome Lacoste [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 29, 2004 2:03 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Plugin properties suggestion
>
> On Tue, 2004-06-29 at 13:49, Eric Pugh wrote:
> > I like the idea..
>
> me too
>
> > Would the next l
dion2004/06/29 06:20:23
Modified:html2xdoc/src/plugin-test maven.xml
html2xdoc/xdocs changes.xml
html2xdoc project.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.3 +3 -10 maven-plugins/html2xdoc/src/plugin-test
dion2004/06/29 06:14:36
Modified:gump/src/plugin-test maven.xml
gump/xdocs changes.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.3 +3 -6 maven-plugins/gump/src/plugin-test/maven.xml
Index: maven.xml
=
dion2004/06/29 06:09:59
Modified:faq project.xml
faq/src/plugin-test maven.xml
faq/xdocs changes.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.35 +1 -1 maven-plugins/faq/project.xml
Index: project.xm
dion2004/06/29 06:03:39
Modified:dist/src/plugin-test maven.xml
dist/xdocs changes.xml
dist project.xml
Log:
Reinstate plugin tests
Revision ChangesPath
1.4 +3 -12 maven-plugins/dist/src/plugin-test/maven.xml
Index: mav
The following comment has been added to this issue:
Author: Eirik Maus
Created: Tue, 29 Jun 2004 8:48 AM
Body:
More details:
The failing code is near the start of method:
org.apache.maven.plugin.PluginManager.processDependencies()
it looks like this:
ForeheadClassLoader proje
dion2004/06/29 05:45:58
Modified:clean/xdocs changes.xml
clean/src/plugin-test maven.xml
cleanproject.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.11 +3 -0 maven-plugins/clean/xdocs/changes.xml
Index
dion2004/06/29 05:43:04
Modified:checkstyle/xdocs changes.xml
checkstyle/src/plugin-test maven.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.34 +1 -0 maven-plugins/checkstyle/xdocs/changes.xml
Index: changes.xml
=
Why don't you unzip/unjar your dependecy and use "normal" way of processing
resources?
I am myself using zips as dependencies (type = "zip" ) - and I am unzipping
them to folder
like traget/resources
Then I use section for selecting/filtering strings in those
files.
I created "zip-plugin" for t
The following issue has been updated:
Updater: Maarten Coene (mailto:[EMAIL PROTECTED])
Date: Tue, 29 Jun 2004 8:04 AM
Comment:
patch for plugin.jelly
Changes:
Attachment changed to plugin.jelly.patch
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1347
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAVADOC-30
Here is an overview of the issue:
-
Ke
On Tue, 2004-06-29 at 13:49, Eric Pugh wrote:
> I like the idea..
me too
> Would the next logical step be to verify as well that
> anything in plugin.properties was listed in the properties.xml file? It
> seems that pretty much anything in plugin.properties should be documented.
sounds good t
dion2004/06/29 04:56:33
Modified:changes project.xml
changes/src/plugin-test maven.xml
changes/xdocs changes.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.30 +1 -1 maven-plugins/changes/project.xml
Index
Hi -
I have tried unsuccessfully several times to unsubscribe from the maven
developers list (both via email and through the web site). I don't think my
emails are getting through. Can anyone provide me with help in unsubscribing
from this list?
Thank you.
-
David L. Paterline
Principal Engineer
dion2004/06/29 04:52:49
Modified:artifact/xdocs changes.xml
artifact/src/plugin-test maven.xml
Log:
Use assert taglib in plugin test
Revision ChangesPath
1.23 +1 -0 maven-plugins/artifact/xdocs/changes.xml
Index: changes.xml
===
I like the idea.. Would the next logical step be to verify as well that
anything in plugin.properties was listed in the properties.xml file? It
seems that pretty much anything in plugin.properties should be documented.
You could also apply the same logic to goals as well.
Eric
> -Original M
dion2004/06/29 04:41:06
Modified:plugin/xdocs changes.xml
plugin project.xml plugin.jelly
Log:
Add assertFileNotFound tag to assert taglib
Revision ChangesPath
1.25 +3 -0 maven-plugins/plugin/xdocs/changes.xml
Index: changes.xml
=
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1346
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Joachim Bader
Created: Tue, 29 Jun 2004 6:59 AM
Body:
ready for commit
the dependend issue MAVENUPLOAD-134 is commited
-
View this comment:
http://jira.
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPPLUGIN-20
Here is an overview of the issue:
-
Key
- Original Message -
From: "Dion Gillard" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 29, 2004 12:26 PM
Subject: Re: RC4, releases and votes
> On Tue, 29 Jun 2004 12:29:12 +0200, Emmanuel Venisse
> <[EMAIL PROTECTED]> wrote:
>
> > We voted f
On Tue, 29 Jun 2004 12:29:12 +0200, Emmanuel Venisse
<[EMAIL PROTECTED]> wrote:
> We voted for release on the PMC list.
Cool.
> > Is there going to be one for 1.0?
Any ideas on this one?
-
To unsubscribe, e-mail: [EMAIL PROTE
Hi,
This is a suggestion of how to create and document plugin properties easier.
- Create an xml file called properties.xml with the following DTD.
In the plugin project:
- Process it to generate the properties.xml xdoc using
maven-plugin-plugin
- Process it to generate the plugin.properties file
- Original Message -
From: "Dion Gillard" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, June 29, 2004 12:18 PM
Subject: RC4, releases and votes
> I've been sick lately, so I may have missed something, but was there a
> vote/call for release on the de
I've been sick lately, so I may have missed something, but was there a
vote/call for release on the dev list for RC4?
Is there going to be one for 1.0?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:
Hi,
I need a way to extract resources from dependency artifacts, and am thinking
about a "maven-extract-plugin". I post this to know if anyone is working on
it and to get your comments.
The best approach I see is to add a property to the dependency with nested
resource tags as specified in pom bu
Hello guys,
Several weeks ago, I added the functionnality to use the
"maven.compile.src.set" in the javadoc plugin.
I also added like in others plugins, a patternset to exclude or
include files depending on the pom.build.sourceModifications
To use the patternset I needed to give i
On Tue, 2004-06-29 at 09:18, Vincent Massol wrote:
> > -Original Message-
> > From: Brett Porter [mailto:[EMAIL PROTECTED]
> > Sent: mardi 29 juin 2004 07:53
> > To: Maven Developers List
> > Subject: Re: [checkstyle] First try at generating a RSS feed - Feedback
> > wanted
> >
> > I'll ta
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1345
Here is an overview of the issue:
-
Key:
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Tue, 29 Jun 2004 5:02 AM
Set default maven.scm.method to cvs
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-13
Here is an over
carlos 2004/06/29 02:03:37
Modified:scm plugin.properties project.xml
scm/xdocs changes.xml
Log:
Set default maven.scm.method to cvs
Revision ChangesPath
1.6 +1 -1 maven-plugins/scm/plugin.properties
Index: plugin.properties
carlos 2004/06/29 01:54:42
Modified:aspectj/xdocs changes.xml goals.xml index.xml properties.xml
aspectj project.xml
Log:
Changed mail
Revision ChangesPath
1.19 +1 -1 maven-plugins/aspectj/xdocs/changes.xml
Index: changes.xml
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPXDOC-112
Here is an overview of the issue:
-
Key:
carlos 2004/06/29 01:48:36
Modified:xdoc/xdocs changes.xml
xdoc/src/plugin-resources/templates cvs-usage.xml
xdoc project.xml
Log:
Add instructions to checkout with maven to cvs-usage page
Revision ChangesPath
1.55 +3 -0 maven-
The following comment has been added to this issue:
Author: Joerg Schaible
Created: Tue, 29 Jun 2004 4:14 AM
Body:
Well, there are two reasons for changing the project name:
1) Maven only uses the artifactId for the Eclipse project name. This may clash with an
artifact of another
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Tue, 29 Jun 2004 3:56 AM
Body:
Actually it's not possible to configure it.
If you define in your project.xml some sourceModifications, then the javadoc plugin
will use it.
I will propose today on
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: mardi 29 juin 2004 07:53
> To: Maven Developers List
> Subject: Re: [checkstyle] First try at generating a RSS feed - Feedback
> wanted
>
> I'll take a look.
>
> Is this generic enough to be used in other report
87 matches
Mail list logo
