Nope, ya got me.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 09/09/2003 02:43:33 PM:
> I didn't revert all your modifications. I don't remove the test for
verify
> that the source file exist reportin
I didn't revert all your modifications. I don't remove the test for verify
that the source file exist reporting by Gilles Dodinet.
I test the plugin with many project and it works fine but not on maven
project, it's curious.
If I run maven jcoverage, it works fine, but "maven jcoverage site" or ad
Last 500 lines of a clean bootstrap build of maven at 20030908-2200
[exec] Copying 1 file to
/usr/local/builds/maven/src/maven/src/plugins-build/webserver/target/classes/plugin-resources
[exec] Copying 4 files to
/usr/local/builds/maven/src/maven/src/plugins-build/webserver/target
dion2003/09/08 17:30:34
Added: src/plugins-build/examples/simple-java LICENSE.txt
Log:
Add license
Revision ChangesPath
1.1 maven/src/plugins-build/examples/simple-java/LICENSE.txt
<>
---
dion2003/09/08 17:28:38
Modified:
src/plugins-build/examples/simple-java/src/test/org/apache/maven/examples/simplejava
TestSimpleJava.java
Log:
Make it a test case
Revision ChangesPath
1.2 +1 -1
maven/src/plugins-build/examples/simp
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 8 Sep 2003 7:30 PM
Body:
It was fixed in MAVEN-531, post beta 10
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue
This causes jcoverage to fail when running against Maven.
Any ideas why?
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
[EMAIL PROTECTED] wrote on 08/09/2003 11:39:51 PM:
> evenisse2003/09/08 06:39:51
>
> Modified:src/plugins-
> build/jcoverag
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-799
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Ben Walding (mailto:[EMAIL PROTECTED])
Date: Mon, 8 Sep 2003 6:29 PM
Comment:
Odd title problem
Changes:
summary changed from Allow uberjar conf can
--
The following comment has been added to this issue:
Author: gilles dodinet
Created: Mon, 8 Sep 2003 3:47 PM
Body:
Emmanuel,
I thougth i was missing something since the jcoverage report displays informations
about the test classes coverage, that doesnot really make sense. I hope
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Mon, 8 Sep 2003 3:08 PM
Changes:
Component changed to plugin-deploy
Component changed from plugin-dist
The following comment has been added to this issue:
Author: Oliver Noelle
Created: Mon, 8 Sep 2003 11:51 AM
Body:
> You understand that ant property doesn't change a variable if it's > already set,
> right?
> > => How does maven handle properties that get set multiple times
> >
Can we use DefaultProjectUnmarshaller with XmlPullParser instead of
betwixt/digester.
With this, we can replace parser.nextText() with strip(parser.nextText)
Emmanuel
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Saturday, September
evenisse2003/09/08 06:39:51
Modified:src/plugins-build/jcoverage/src/main/org/apache/maven/jcoveragereport
CoverageReport.java
Log:
Remove bad existence check on file. We must don't check the existence beacause we
want to generate this file. It's html files.
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Mon, 8 Sep 2003 8:24 AM
Body:
All works fine for me.
Could you send us more informations.
- project definition
- ProjectAggregatorTest is unit test source?
- a reproductible sample
- ...
---
Done.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Emmanuel Venisse" <[EMAIL PROTECTED]> wrote on 08/09/2003 07:51:45 PM:
> I don't like the plugin.jelly patch. If project is configure correctly,
> jcoverage plugin doesn't use unit test source.
> Could
The following issue has been updated:
Updater: Steve Vaughan (mailto:[EMAIL PROTECTED])
Date: Mon, 8 Sep 2003 7:11 AM
Comment:
Updated plugin.jelly
Changes:
Attachment changed to plugin.jelly
-
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Mon, 8 Sep 2003 7:45 AM
Done. Thanks.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-798
Here is an ove
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 8 Sep 2003 7:43 AM
It seems this is not a cactus maven plugin issue and was due to a bad zip in Eric's
project.
-
View the issue:
evenisse2003/09/08 05:30:34
Modified:src/plugins-build/jalopy plugin.jelly
src/plugins-build/jalopy/xdocs changes.xml
Log:
Fixed MAVEN-798. Add Test source formatting.
Revision ChangesPath
1.4 +12 -4 maven/src/plugins-build/jalopy/plugin.jelly
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Mon, 8 Sep 2003 7:38 AM
Body:
How to know if a project is a plugin?
-
View the issue:
http://jira.codehaus.org/secure/ViewIss
Message:
The following issue has been reopened.
Reopener: Emmanuel Venisse
Date: Mon, 8 Sep 2003 7:24 AM
Unit test source directory isn't necessary for jcoverage plugin. I think you have
another problem.
-
View the
evenisse2003/09/08 05:05:09
Modified:src/plugins-build/plugin plugin.jelly
src/plugins-build/plugin/xdocs changes.xml
Log:
Revert Maven-791
Revision ChangesPath
1.15 +4 -18 maven/src/plugins-build/plugin/plugin.jelly
Index: plugin.jelly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-798
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Mon, 8 Sep 2003 6:15 AM
Body:
I think we should close this issue.. It seems to be that one of the jar's in my
project is bad.. However, I can't figure out which one. I need to patch the cactus
Message:
The following issue has been reopened.
Reopener: dion gillard
Date: Mon, 8 Sep 2003 6:24 AM
Why do plugins need a plugin.jelly file?
Couldn't they simply be adding jars to a classpath?
-
View the issue:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-797
Here is an overview of the issue:
--
"Michal Maczka" <[EMAIL PROTECTED]> wrote on 08/09/2003 07:03:12 PM:
> I am not complaing :) ... but wouldn't it be better to
> to solve this issue by inheriting
>
> maven.license.licenseFile
> and
> maven.checkstyle.header.file
>
> from parent project for all plugins?
>
> We need to implemen
[EMAIL PROTECTED] wrote on 08/09/2003 07:15:20 PM:
> evenisse2003/09/08 02:15:20
>
> Modified:src/plugins-build/plugin plugin.jelly
>src/plugins-build/plugin/xdocs changes.xml
> Log:
> Fixed MAVEN-791. Check if project is a plugin.
>
> Revision ChangesPath
>
dion2003/09/08 04:15:16
Modified:src/plugins-build/jcoverage plugin.jelly
Log:
Revert MAVEN-795
Revision ChangesPath
1.3 +2 -15 maven/src/plugins-build/jcoverage/plugin.jelly
Index: plugin.jelly
I don't like the plugin.jelly patch. If project is configure correctly,
jcoverage plugin doesn't use unit test source.
Could you revert plugin.jelly changes.
I think the problem describe by Gilles Dodinet is due to another problem.
Thanks.
Emmanuel
- Original Message -
From: <[EMAIL PRO
Message:
The following issue has been closed.
Resolver: Emmanuel Venisse
Date: Mon, 8 Sep 2003 4:50 AM
Done. Check if project.xml and plugin.jelly exist in basedir.
-
View the issue:
http://jira.codehaus.org/secu
evenisse2003/09/08 02:31:28
Modified:src/plugins-build/torque plugin.jelly
src/plugins-build/torque/xdocs changes.xml
Log:
Fix prereqs of torque:om-zip goal.
Revision ChangesPath
1.9 +1 -1 maven/src/plugins-build/torque/plugin.jelly
Index: p
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, September 07, 2003 4:51 PM
> To: [EMAIL PROTECTED]
> Subject: cvs commit: maven/src/plugins-build/xdoc/xdocs faq.fml
> navigation.xml
>
> dion2003/09/07 07:50:33
>
> Modified:src/plugi
evenisse2003/09/08 02:15:20
Modified:src/plugins-build/plugin plugin.jelly
src/plugins-build/plugin/xdocs changes.xml
Log:
Fixed MAVEN-791. Check if project is a plugin.
Revision ChangesPath
1.14 +20 -4 maven/src/plugins-build/plugin/plugin.jelly
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, September 08, 2003 12:24 AM
> To: 'Maven Developers List'
> Subject: RE: clarify plugin version loading
>
>
> > AD 2 & 3
> >
> > We can easily use information which we have in POM:
> >
> >
> >
> >
36 matches
Mail list logo
