[jira] Created: (MPXDOC-131) Allow velocity in user-documentation and expose pom

2005-02-11 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-131

Here is an overview of the issue:
-
Key: MPXDOC-131
Summary: Allow velocity in user-documentation and expose pom
   Type: Improvement

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin

   Assignee: Arnaud HERITIER
   Reporter: Ignacio G. Mac Dowell

Created: Fri, 11 Feb 2005 5:07 AM
Updated: Fri, 11 Feb 2005 5:07 AM

Description:
Currently, we can't directly use the pom or velocity in user-documentation. 

JSL is applied to the user-docs as-is. I suggest having a property called 
maven.docs.src.templates (defaults to false) that when set to true treats 
user-docs as templates.

Then, slightly modify the goal xdoc:jelly-transform.

We need to var's:

j:set var=mergeUserDocs value=${maven.docs.src.templates}/
j:set var=hasUserDocs value=${maven.docs.src.available}/

If both evaluate to true then velocity:merge the user docs before doing jsl. If 
they evaluate to false do as before.

It would probably be nice to be able to use jelly as well as user-supplied docs.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MPXDOC-131) Allow velocity in user-documentation and expose pom

2005-02-11 Thread jira
The following issue has been updated:

Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
   Date: Fri, 11 Feb 2005 5:12 AM
Comment:
Maybe it would be nice to be able to use .jelly also as user-docs. If anybody 
is interested I'll supply the patch.
Changes:
 Attachment changed to plugin.jelly.patch
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPXDOC-131?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-131

Here is an overview of the issue:
-
Key: MPXDOC-131
Summary: Allow velocity in user-documentation and expose pom
   Type: Improvement

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin

   Assignee: Arnaud HERITIER
   Reporter: Ignacio G. Mac Dowell

Created: Fri, 11 Feb 2005 5:07 AM
Updated: Fri, 11 Feb 2005 5:12 AM

Description:
Currently, we can't directly use the pom or velocity in user-documentation. 

JSL is applied to the user-docs as-is. I suggest having a property called 
maven.docs.src.templates (defaults to false) that when set to true treats 
user-docs as templates.

Then, slightly modify the goal xdoc:jelly-transform.

We need to var's:

j:set var=mergeUserDocs value=${maven.docs.src.templates}/
j:set var=hasUserDocs value=${maven.docs.src.available}/

If both evaluate to true then velocity:merge the user docs before doing jsl. If 
they evaluate to false do as before.

It would probably be nice to be able to use jelly as well as user-supplied docs.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MPXDOC-131) Allow velocity in user-documentation and expose pom

2005-02-11 Thread jira
The following issue has been updated:

Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
   Date: Fri, 11 Feb 2005 5:13 AM
Comment:
Default user-doc-templates to false
Changes:
 Attachment changed to plugin.properties.patch
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPXDOC-131?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-131

Here is an overview of the issue:
-
Key: MPXDOC-131
Summary: Allow velocity in user-documentation and expose pom
   Type: Improvement

 Status: Open
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin

   Assignee: Arnaud HERITIER
   Reporter: Ignacio G. Mac Dowell

Created: Fri, 11 Feb 2005 5:07 AM
Updated: Fri, 11 Feb 2005 5:13 AM

Description:
Currently, we can't directly use the pom or velocity in user-documentation. 

JSL is applied to the user-docs as-is. I suggest having a property called 
maven.docs.src.templates (defaults to false) that when set to true treats 
user-docs as templates.

Then, slightly modify the goal xdoc:jelly-transform.

We need to var's:

j:set var=mergeUserDocs value=${maven.docs.src.templates}/
j:set var=hasUserDocs value=${maven.docs.src.available}/

If both evaluate to true then velocity:merge the user docs before doing jsl. If 
they evaluate to false do as before.

It would probably be nice to be able to use jelly as well as user-supplied docs.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Nacho G. Mac Dowell
Hi all, I was trying to use ${pom.properties} and I found it is an 
ArrayList of Strings in the form property:elementName:...:. I was 
thinking it might be useful to have them as Nodes. What do you think? 
The problem I am facing is that I have quite a few external links in my 
documentation and I would like to keep them separate from the docs. I 
first thought of  putting them in the project.properties, but some of 
these links are quite tied to the project (actually the project I am 
talking about is JaxMe) and It would be nice if I could have them in the 
pom. Also, if I put them in the project.properties I only have access 
(at least to my knowledge) when not using dots (.) in the key. I was 
thinking of something like this:

properties
   
jaxme-jelly-tag-libraryhttp://jakarta.apache.org/commons/jelly/libs/jaxme/index.html/jaxme-jelly-tag-library
   .
/properties

and then access them as: 
${project.properties.getChild(jaxme-jelly-tag-library)} or something 
similar.

This way we would (easily) avoid the problem that arised when moving 
from nagoya in apache. Other suggestions are very welcome.

I would also like to draw attention to bug #MPXDOC-131 which gives 
direct access to velocity in user-documentation when 
maven.docs.src.templates=true. I know I can use maven.xml for this but I 
beleive it is easier to use it this way. There are no side-effects 
(maven.docs.src.templates defaults to false) and quite a few benefits!

Regards,
Nacho G. Mac Dowell
PD: Does anybody know where I can find org.apache.maven.project.Model? 
It is now in a separate artifact, but what project? Thanks!

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


RE: [MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Maczka Michal


 -Original Message-
 From: Nacho G. Mac Dowell [mailto:[EMAIL PROTECTED]
 Sent: Friday, February 11, 2005 1:29 PM
 To: dev@maven.apache.org
 Subject: [MAVEN] ${pom.properties} is a ArrayList of String?
 
 
 Hi all, I was trying to use ${pom.properties} and I found it is an 
 ArrayList of Strings in the form property:elementName:...:. I was 
 thinking it might be useful to have them as Nodes. What do you think? 

[..]
 
 properties
 
 jaxme-jelly-tag-libraryhttp://jakarta.apache.org/commons/jel
 ly/libs/jaxme/index.html/jaxme-jelly-tag-library
 .
 /properties
 
 and then access them as: 
 ${project.properties.getChild(jaxme-jelly-tag-library)} or 
 something 
 similar.
 
 This way we would (easily) avoid the problem that arised when moving 
 from nagoya in apache. Other suggestions are very welcome.



Maybe it is a stupid question:

why don't you use project.properties file for that and do is like this:

jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jelly/libs/jaxme/i
ndex.html

?


 
 I would also like to draw attention to bug #MPXDOC-131 which gives 
 direct access to velocity in user-documentation when 
 maven.docs.src.templates=true. I know I can use maven.xml for 
 this but I 
 beleive it is easier to use it this way. There are no side-effects 
 (maven.docs.src.templates defaults to false) and quite a few benefits!
 
 Regards,
 
 Nacho G. Mac Dowell
 
 PD: Does anybody know where I can find 
 org.apache.maven.project.Model? 
 It is now in a separate artifact, but what project? Thanks!
 
 

http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/


michal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Nacho G. Mac Dowell

Maybe it is a stupid question:
why don't you use project.properties file for that and do is like this:
jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jelly/libs/jaxme/i
ndex.html
?
Actually this is what I am doing at the moment. I have:
link-jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jelly/libs/jaxme/index.html
It is probably a better aproach for this, specially when resource 
bundles come in. The thing is that I didn't like mixing contents (a 
link) with maven configuration (project.properties).

I just thought it would be useful to be able to navigate through the 
properties (from the pom). I suppose this is for performance reasons. If 
this is the case it is agood enough reason for me.

http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/
I didn't find org.apache.maven.project.Model there... no sources either.
Regards,
Nacho

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Maven reactor loader and fmt

2005-02-11 Thread Siveton Vincent
Hi every body,

I have a question regarding maven:reactor.

I am currently updating a plugin that is using the fmt tags.
http://jakarta.apache.org/commons/jelly/libs/fmt/tags.html

To achieve it, the first step is to copy my bundle directly in the following
plugin directory ie:
${user.home}\.maven\cache\thePlugin\plugin-resources\temp\${myBundle}.proper
ties
Why? Because of the setBundle tags:
fmt:setBundle basename=plugin-resources.temp.${myBundle} var=myMsg /

I have no problem to call the main goal of the plugin: I find the bundle
that I copied and fmt tags worked.

However, if I am using maven:reactor, a loader problem appears:
* if the bundle was already copied in the plugin resources, the bundle is
correctly found, then it works very well.
* if the bundle doesnt exist on the start up, I need to copy my bundle in
the plugin resources. In the specific case, Maven reactor doesnt find the
bundle (exactly the goal of the plugin called by maven:reactor).

Well, my god feeling is that the maven:reactor loads the environnement of
all plugins at the start up and doesnt update it if it changes. 
Is there a way to reload (automatically or manually) the environnement for a
given plugin?

Thanks for your response!

Cheers,

Vincent


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (MPXDOC-132) Links starting with https are not considered external links

2005-02-11 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-132

Here is an overview of the issue:
-
Key: MPXDOC-132
Summary: Links starting with https are not considered external links
   Type: Bug

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin
   Versions:
 1.8
 1.9

   Assignee: Arnaud HERITIER
   Reporter: Ignacio G. Mac Dowell

Created: Fri, 11 Feb 2005 8:26 AM
Updated: Fri, 11 Feb 2005 8:26 AM

Description:
A link starting with https is not considered as an external link.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MPXDOC-132) Links starting with https are not considered external links

2005-02-11 Thread jira
The following issue has been updated:

Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
   Date: Fri, 11 Feb 2005 8:28 AM
Comment:
-  j:when test=${href.startsWith('http://')}
+  j:when test=${href.startsWith('http://') or 
href.startsWith('https://')}
Changes:
 Attachment changed to site.jsl.patch
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPXDOC-132?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MPXDOC-132

Here is an overview of the issue:
-
Key: MPXDOC-132
Summary: Links starting with https are not considered external links
   Type: Bug

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-xdoc-plugin
   Versions:
 1.8
 1.9

   Assignee: Arnaud HERITIER
   Reporter: Ignacio G. Mac Dowell

Created: Fri, 11 Feb 2005 8:26 AM
Updated: Fri, 11 Feb 2005 8:28 AM

Description:
A link starting with https is not considered as an external link.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (MAVEN-1567) No way to include App type dependency in classpath

2005-02-11 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1567

Here is an overview of the issue:
-
Key: MAVEN-1567
Summary: No way to include App type dependency in classpath
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Versions:
 1.0.2

   Assignee: 
   Reporter: Havard Bjastad

Created: Fri, 11 Feb 2005 8:43 AM
Updated: Fri, 11 Feb 2005 8:43 AM

Description:
We have created a Java application, using maven-javaapp-plugin. This plugin 
creates an executable jar file, registered as type 'app' in Maven (and it's 
repository). There are two problems with this:

1. There is no way to add support for new types in Maven. When another module 
depends on a module of type 'app', Maven is unable to find it.
Workaround: Specify the full jar file name in the dependency tag.

2. The 'app' type module is not included in the classpath of the dependent 
module. This is the biggest problem, as it is hardcoded in the 
isAddedToClasspath() method of org.apache.maven.project.Dependency that only 
modules of type 'jar' and 'ejb' gets added to the classpath. I have tried to 
modify the maven.dependency.classpath in maven.xml, but it doesn't seem to work.



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (MPCLOVER-29) Invalid xml in latest xdocs/changes.xml

2005-02-11 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-29

Here is an overview of the issue:
-
Key: MPCLOVER-29
Summary: Invalid xml in latest xdocs/changes.xml
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven-clover-plugin
   Versions:
 1.7

   Assignee: 
   Reporter: Matthias Kerkhoff

Created: Fri, 11 Feb 2005 9:29 AM
Updated: Fri, 11 Feb 2005 9:29 AM

Description:
The latest version of xdocs/changes.xml has some invalid xml near the end of 
the file.

/bodybodybody

 should be replaced with

/body




-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Maczka Michal


 -Original Message-
 From: Nacho G. Mac Dowell [mailto:[EMAIL PROTECTED]
 Sent: Friday, February 11, 2005 2:14 PM
 To: Maven Developers List
 Subject: Re: [MAVEN] ${pom.properties} is a ArrayList of String?
 
 
 
 Maybe it is a stupid question:
 
 why don't you use project.properties file for that and do is 
 like this:
 
 jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jel
 ly/libs/jaxme/i
 ndex.html
 
 ?
 
 Actually this is what I am doing at the moment. I have:
 
 link-jaxme-jelly-tag-library=http://jakarta.apache.org/commons
 /jelly/libs/jaxme/index.html
 
 It is probably a better aproach for this, specially when resource 
 bundles come in. The thing is that I didn't like mixing contents (a 
 link) with maven configuration (project.properties).
 
 I just thought it would be useful to be able to navigate through the 
 properties (from the pom). I suppose this is for performance 
 reasons. If 
 this is the case it is agood enough reason for me.
 

The only real difference for maven1 is that project.properties file is not
deploy to the repository.
So project.properties are usually just good enough. 

  http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/
 
 I didn't find org.apache.maven.project.Model there... no 
 sources either.
 

java classes are generated from the model file which you can find in that
project.

 Regards,
 
 Nacho
 
 

michal

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153404 - maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 06:36:14 2005
New Revision: 153404

URL: http://svn.apache.org/viewcvs?view=revrev=153404
Log:
MPCLOVER-29: fixed typo

Modified:
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153403r2=153404
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 06:36:14 
2005
@@ -128,5 +128,5 @@
 release version=1.0 date=unknown
   action dev=vmassol type=addThese changes did not exist at that 
time. Please refer to CVS for history changes before version 1.1./action
 /release
-  /bodybodybody
+  /body
 /document



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (MPCLOVER-29) Invalid xml in latest xdocs/changes.xml

2005-02-11 Thread jira
Message:

   The following issue has been closed.

   Resolver: Vincent Massol
   Date: Fri, 11 Feb 2005 9:52 AM

Thanks and sorry for the pb. Unfortunately our tests do not include plugin web 
site generation... I should have tried it.
-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-29

Here is an overview of the issue:
-
Key: MPCLOVER-29
Summary: Invalid xml in latest xdocs/changes.xml
   Type: Bug

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: 5 minutes
 Time Spent: Unknown
  Remaining: 5 minutes

Project: maven-clover-plugin
   Fix Fors:
 1.7
   Versions:
 1.7

   Assignee: Vincent Massol
   Reporter: Matthias Kerkhoff

Created: Fri, 11 Feb 2005 9:29 AM
Updated: Fri, 11 Feb 2005 9:52 AM

Description:
The latest version of xdocs/changes.xml has some invalid xml near the end of 
the file.

/bodybodybody

 should be replaced with

/body




-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Nacho G. Mac Dowell
Silly me...  :-[ 

I saw properties might get deprecated so I'll stick with project.properties
Regards
Nacho
Maczka Michal wrote:
 

-Original Message-
From: Nacho G. Mac Dowell [mailto:[EMAIL PROTECTED]
Sent: Friday, February 11, 2005 2:14 PM
To: Maven Developers List
Subject: Re: [MAVEN] ${pom.properties} is a ArrayList of String?

   

Maybe it is a stupid question:
why don't you use project.properties file for that and do is 
 

like this:
   

jaxme-jelly-tag-library=http://jakarta.apache.org/commons/jel
 

ly/libs/jaxme/i
   

ndex.html
?
 

Actually this is what I am doing at the moment. I have:
link-jaxme-jelly-tag-library=http://jakarta.apache.org/commons
/jelly/libs/jaxme/index.html
It is probably a better aproach for this, specially when resource 
bundles come in. The thing is that I didn't like mixing contents (a 
link) with maven configuration (project.properties).

I just thought it would be useful to be able to navigate through the 
properties (from the pom). I suppose this is for performance 
reasons. If 
this is the case it is agood enough reason for me.

   

The only real difference for maven1 is that project.properties file is not
deploy to the repository.
So project.properties are usually just good enough. 

 

http://cvs.apache.org/viewcvs.cgi/maven-components/maven-model/
 

I didn't find org.apache.maven.project.Model there... no 
sources either.

   

java classes are generated from the model file which you can find in that
project.
 

Regards,
Nacho
   

michal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[jira] Closed: (MPCLOVER-18) Stop Clover re-running tests if they've already run

2005-02-11 Thread jira
Message:

   The following issue has been closed.

   Resolver: Vincent Massol
   Date: Fri, 11 Feb 2005 10:52 AM

Done. Added new maven.clover.execute.during.report (defaults to true).
-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-18

Here is an overview of the issue:
-
Key: MPCLOVER-18
Summary: Stop Clover re-running tests if they've already run
   Type: Wish

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Fix Fors:
 1.7
   Versions:
 1.6

   Assignee: Vincent Massol
   Reporter: Matt Read

Created: Fri, 25 Jun 2004 1:00 PM
Updated: Fri, 11 Feb 2005 10:52 AM

Description:
If both the junit-report and clover-report are registered the tests execute 
twice. Would it be possible to either provide a setting to disable this or 
detect whether tests have already been run?

This might be similar to the property in the Cactus plugin - 
cactus.execute.during.report.

Thanks,
Matt.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153414 - maven/maven-1/plugins/trunk/clover/src/plugin-test/testDontExecuteInReportAndNoReportGenerated maven/maven-1/plugins/trunk/clover/src/plugin-test/testRunCloverOnlyOnce maven/maven-1/plugins/trunk/clover/src/plugin-test/testSiteReportAndXmlReportGeneration

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 07:40:41 2005
New Revision: 153414

URL: http://svn.apache.org/viewcvs?view=revrev=153414
Log:
Added ignore files

Modified:

maven/maven-1/plugins/trunk/clover/src/plugin-test/testDontExecuteInReportAndNoReportGenerated/
   (props changed)
maven/maven-1/plugins/trunk/clover/src/plugin-test/testRunCloverOnlyOnce/   
(props changed)

maven/maven-1/plugins/trunk/clover/src/plugin-test/testSiteReportAndXmlReportGeneration/
   (props changed)

Propchange: 
maven/maven-1/plugins/trunk/clover/src/plugin-test/testDontExecuteInReportAndNoReportGenerated/
--
--- svn:ignore (added)
+++ svn:ignore Fri Feb 11 07:40:41 2005
@@ -0,0 +1 @@
+target

Propchange: 
maven/maven-1/plugins/trunk/clover/src/plugin-test/testRunCloverOnlyOnce/
--
--- svn:ignore (added)
+++ svn:ignore Fri Feb 11 07:40:41 2005
@@ -0,0 +1 @@
+target

Propchange: 
maven/maven-1/plugins/trunk/clover/src/plugin-test/testSiteReportAndXmlReportGeneration/
--
--- svn:ignore (added)
+++ svn:ignore Fri Feb 11 07:40:41 2005
@@ -0,0 +1 @@
+target



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153415 - maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 07:44:51 2005
New Revision: 153415

URL: http://svn.apache.org/viewcvs?view=revrev=153415
Log:
fixed typo

Modified:
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153414r2=153415
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 07:44:51 
2005
@@ -39,7 +39,7 @@
 database file.
   /action
   action dev=vmassol type=fix issue=MPCLOVER-28
-codeclover:off/clover should now reset correctly the 
+codeclover:off/code should now reset correctly the 
 codemaven.build.dest/code property that codeclover:on/code
 modifies. Note that the reported error has been fixed even though I
 have not been able to reproduce the problem (and hence we don't have



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153417 - maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 08:15:22 2005
New Revision: 153417

URL: http://svn.apache.org/viewcvs?view=revrev=153417
Log:
Fixed Cenqua's URL

Modified:
maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml

Modified: maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml?view=diffr1=153416r2=153417
==
--- maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/navigation.xml Fri Feb 11 08:15:22 
2005
@@ -25,7 +25,7 @@
   body
 links
   item name=Maven  href=http://maven.apache.org//
-  item name=Clover href=http://www.thecortex.net/clover//
+  item name=Clover href=http://cenqua.com/clover//
 /links
 menu name=Overview
   item name=Goals href=/goals.html/



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Trying to build the xdoc plugin

2005-02-11 Thread Vincent Massol
Hi,

I'm trying to build the xdoc plugin from SVN trunk. I got:


C:\dev\maven\maven-1\plugins\xdocmaven clean plugin:install
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Tentative de tlchargement de commons-jelly-1.0-RC1.jar.
165K downloaded
Tentative de tlchargement de commons-jelly-tags-jsl-1.1-SNAPSHOT.jar.
Response content length is not known
ATTENTION: Impossible de tlcharger
commons-jelly-tags-jsl-1.1-SNAPSHOT.jar.
Tentative de tlchargement de commons-jelly-tags-log-1.0.jar.
10K downloaded
Tentative de tlchargement de commons-jelly-tags-velocity-1.0.jar.
10K downloaded
Tentative de tlchargement de maven-model-3.0.0-SNAPSHOT.jar.
Response content length is not known
ATTENTION: Impossible de tlcharger maven-model-3.0.0-SNAPSHOT.jar.
Le processus ne peut continuer  cause des dpendances manquantes suivantes:

commons-jelly-tags-jsl-1.1-SNAPSHOT.jar
maven-model-3.0.0-SNAPSHOT.jar

Total time: 17 seconds
Finished at: Fri Feb 11 17:25:19 CET 2005

C:\dev\maven\maven-1\plugins\xdoc

Is it normal that the 2 artifacts mentioned are not on ibiblio?

Thanks
-Vincent




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Using the new site plugin from svn trunk?

2005-02-11 Thread Vincent Massol
Hi,

I have built the site plugin from svn trunk and when I was trying to use it
upload a plugin web site, I got:

[snip]

site:local-deploy-init:
[echo]
  site clean = false
  siteDirectory =
/home/brett/public_html/maven-stage-site/reference/plugins/clover/


site:remote-deploy-init:
[echo]
  siteAddress = www.apache.org
  siteUsername = vmassol


site:rsyncdeploy:
[echo] rsyncing...
[exec] mkdir:
/home/brett/public_html/maven-stage-site/reference/plugins/clover:
Permission denied
[exec] [ERROR] Result: 1

BUILD FAILED
File.. C:\Documents and Settings\Vincent
Massol\.maven\cache\maven-site-plugin-1.6.1-SNAPSHOT\plugin.jelly
Element... exec
Line.. 306
Column 58
Execute failed: java.io.IOException: CreateProcess: rsync -az target/docs/*
[EMAIL PROTECTED]:/home/brett/public_html/maven-s
tage-site/reference/plugins/clover/ error=2
Total time: 16 seconds
Finished at: Fri Feb 11 17:50:36 CET 2005

Is it normal that it is referencing brett's home directory? :-)

Thanks
-Vincent




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153422 - in maven/maven-1/plugins/trunk/clover: plugin.jelly plugin.properties xdocs/changes.xml xdocs/properties.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 09:06:48 2005
New Revision: 153422

URL: http://svn.apache.org/viewcvs?view=revrev=153422
Log:
MPCLOVER-25: Added codemaven.clover.includes/code and 
codemaven.clover.excludes/code properties to specify what files to 
include/exclude from the Cloverification. Thanks to Michael Gaffney.

Modified:
maven/maven-1/plugins/trunk/clover/plugin.jelly
maven/maven-1/plugins/trunk/clover/plugin.properties
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
maven/maven-1/plugins/trunk/clover/xdocs/properties.xml

Modified: maven/maven-1/plugins/trunk/clover/plugin.jelly
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/plugin.jelly?view=diffr1=153421r2=153422
==
--- maven/maven-1/plugins/trunk/clover/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/clover/plugin.jelly Fri Feb 11 09:06:48 2005
@@ -140,9 +140,9 @@
 flushinterval=500
 
   j:forEach var=srcDir items=${srcDirs}
-ant:fileset dir=${srcDir}
-  ant:include name=**/*.java/
-/ant:fileset
+ant:fileset dir=${srcDir} 
+includes=${maven.clover.includes} 
+excludes=${maven.clover.excludes}/
   /j:forEach
 
   !-- Conditionally instrument test code --
@@ -153,9 +153,9 @@
 u:tokenize var=testDirs 
delim=${testSrcSetString}/u:tokenize
 
 j:forEach var=testDir items=${testDirs}
-  ant:fileset dir=${testDir}
-ant:include name=**/*.java/
-  /ant:fileset
+  ant:fileset dir=${testDir}
+  includes=${maven.clover.includes} 
+  excludes=${maven.clover.excludes}/
 /j:forEach
 
   /j:if

Modified: maven/maven-1/plugins/trunk/clover/plugin.properties
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/plugin.properties?view=diffr1=153421r2=153422
==
--- maven/maven-1/plugins/trunk/clover/plugin.properties (original)
+++ maven/maven-1/plugins/trunk/clover/plugin.properties Fri Feb 11 09:06:48 
2005
@@ -47,11 +47,15 @@
 maven.clover.license.path = 
${plugin.getDependencyPath('clover:clover-license')}
 
 # What are the reports that should be generated
-maven.clover.report.html=true
-maven.clover.report.xml=false
-maven.clover.report.swing=false
+maven.clover.report.html = true
+maven.clover.report.xml = false
+maven.clover.report.swing = false
 
 # Decide whether to execute generate Clover data during the site report 
 # generation or not. If false, the plugin will only generate Clover reports
 # based on an existing Clover database. 
 maven.clover.execute.during.report = true
+
+# List of files to include/exclude from Cloverification
+maven.clover.includes = **/*.java
+maven.clover.excludes =

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153421r2=153422
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 09:06:48 
2005
@@ -26,6 +26,11 @@
   /properties
   body
 release version=1.7-SNAPSHOT date=in SVN
+  action dev=vmassol type=add issue=MPCLOVER-25 due-to=Michael 
Gaffney
+Added codemaven.clover.includes/code and 
+codemaven.clover.excludes/code properties to specify what files
+to include/exclude from the Cloverification.
+  /action
   action dev=vmassol type=update issue=MPCLOVER-18
 Added new codemaven.clover.execute.during.report/code property 
 to control whether or not the codeclover-report/code

Modified: maven/maven-1/plugins/trunk/clover/xdocs/properties.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/properties.xml?view=diffr1=153421r2=153422
==
--- maven/maven-1/plugins/trunk/clover/xdocs/properties.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/properties.xml Fri Feb 11 09:06:48 
2005
@@ -134,6 +134,26 @@
 codetrue/code
   /td
 /tr
+tr
+  tdmaven.clover.includes/td
+  tdYes/td
+  td
+List of files to include in the Cloverification.
+  /td
+  td
+code**/*.java/code
+  /td
+/tr
+tr
+  tdmaven.clover.excludes/td
+  tdYes/td
+  td
+List of files to exclude from the Cloverification.
+  /td
+  td
+code/code
+  /td
+/tr
   /table
 /section
   /body



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL 

[jira] Closed: (MPCLOVER-25) Allow which files are instrumented to be configurable

2005-02-11 Thread jira
Message:

   The following issue has been closed.

   Resolver: Vincent Massol
   Date: Fri, 11 Feb 2005 12:21 PM

Done.  Thanks.
-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-25

Here is an overview of the issue:
-
Key: MPCLOVER-25
Summary: Allow which files are instrumented to be configurable
   Type: Improvement

 Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Fix Fors:
 1.7
   Versions:
 1.7

   Assignee: Vincent Massol
   Reporter: Michael Gaffney

Created: Tue, 12 Oct 2004 11:48 AM
Updated: Fri, 11 Feb 2005 12:21 PM

Description:
I think it would very useful if a user could configure which files are included 
and/or excluded from being instrumented.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153424 - in maven/maven-1/plugins/trunk/clover: plugin.jelly xdocs/changes.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 09:22:40 2005
New Revision: 153424

URL: http://svn.apache.org/viewcvs?view=revrev=153424
Log:
MPCLOVER-22: Open Clover report page in a new window in the same manner as it's 
done for the Javadoc and XRef reports. Thanks to Mike Gabelmann.

Modified:
maven/maven-1/plugins/trunk/clover/plugin.jelly
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/clover/plugin.jelly
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/plugin.jelly?view=diffr1=153423r2=153424
==
--- maven/maven-1/plugins/trunk/clover/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/clover/plugin.jelly Fri Feb 11 09:22:40 2005
@@ -332,6 +332,7 @@
 name=Clover 
 pluginName=maven-clover-plugin 
 link=clover/index
+target=_blank
 description=Clover test coverage report./
 /j:if
   /goal

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153423r2=153424
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 09:22:40 
2005
@@ -26,6 +26,10 @@
   /properties
   body
 release version=1.7-SNAPSHOT date=in SVN
+  action dev=vmassol type=update issue=MPCLOVER-22 due-to=Mike 
Gabelmann
+Open Clover report page in a new window in the same manner as it's 
+done for the Javadoc and XRef reports.
+  /action
   action dev=vmassol type=add issue=MPCLOVER-25 due-to=Michael 
Gaffney
 Added codemaven.clover.includes/code and 
 codemaven.clover.excludes/code properties to specify what files



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (MPCLOVER-22) new window

2005-02-11 Thread jira
Message:

   The following issue has been closed.

   Resolver: Vincent Massol
   Date: Fri, 11 Feb 2005 12:36 PM

Done. Thanks.
-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-22

Here is an overview of the issue:
-
Key: MPCLOVER-22
Summary: new window
   Type: Improvement

 Status: Closed
   Priority: Minor
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Fix Fors:
 1.7

   Assignee: Vincent Massol
   Reporter: mike gabelmann

Created: Thu, 2 Sep 2004 5:05 PM
Updated: Fri, 11 Feb 2005 12:36 PM
Environment: all

Description:
Accessing the clover report for a project should open a new browser window. 
This would mimic the way the Javadoc and Xref reports function.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153425 - maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 09:24:10 2005
New Revision: 153425

URL: http://svn.apache.org/viewcvs?view=revrev=153425
Log:
Fixed attribution... Sorry for the mistake.

Modified:
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153424r2=153425
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 09:24:10 
2005
@@ -26,7 +26,7 @@
   /properties
   body
 release version=1.7-SNAPSHOT date=in SVN
-  action dev=vmassol type=update issue=MPCLOVER-22 due-to=Mike 
Gabelmann
+  action dev=vmassol type=update issue=MPCLOVER-22 due-to=Maarten 
Coene
 Open Clover report page in a new window in the same manner as it's 
 done for the Javadoc and XRef reports.
   /action



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



svn commit: r153426 - in maven/maven-1/plugins/trunk/clover: plugin.jelly xdocs/changes.xml

2005-02-11 Thread vmassol
Author: vmassol
Date: Fri Feb 11 09:40:41 2005
New Revision: 153426

URL: http://svn.apache.org/viewcvs?view=revrev=153426
Log:
MPCLOVER-21: Do not create a Clover report link when the project has no tests.

Modified:
maven/maven-1/plugins/trunk/clover/plugin.jelly
maven/maven-1/plugins/trunk/clover/xdocs/changes.xml

Modified: maven/maven-1/plugins/trunk/clover/plugin.jelly
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/plugin.jelly?view=diffr1=153425r2=153426
==
--- maven/maven-1/plugins/trunk/clover/plugin.jelly (original)
+++ maven/maven-1/plugins/trunk/clover/plugin.jelly Fri Feb 11 09:40:41 2005
@@ -327,7 +327,7 @@
  
   --
   goal name=maven-clover-plugin:register
-j:if test=${sourcesPresent == 'true'}
+j:if test=${unitTestSourcesPresent == 'true'}
   doc:registerReport 
 name=Clover 
 pluginName=maven-clover-plugin 
@@ -343,7 +343,7 @@
  
   --
   goal name=maven-clover-plugin:deregister
-j:if test=${sourcesPresent == 'true'}
+j:if test=${unitTestSourcesPresent == 'true'}
   doc:deregisterReport name=Clover/
 /j:if
   /goal

Modified: maven/maven-1/plugins/trunk/clover/xdocs/changes.xml
URL: 
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/xdocs/changes.xml?view=diffr1=153425r2=153426
==
--- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original)
+++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Fri Feb 11 09:40:41 
2005
@@ -2,7 +2,7 @@
 
 !-- 
 /*
- * Copyright 2001-2004 The Apache Software Foundation.
+ * Copyright 2001-2005 The Apache Software Foundation.
  * 
  * Licensed under the Apache License, Version 2.0 (the License);
  * you may not use this file except in compliance with the License.
@@ -26,6 +26,9 @@
   /properties
   body
 release version=1.7-SNAPSHOT date=in SVN
+  action dev=vmassol type=fix issue=MPCLOVER-21
+Do not create a Clover report link when the project has no tests.
+  /action
   action dev=vmassol type=update issue=MPCLOVER-22 due-to=Maarten 
Coene
 Open Clover report page in a new window in the same manner as it's 
 done for the Javadoc and XRef reports.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (MPCLOVER-21) Invalid clover link in the site when no test is present

2005-02-11 Thread jira
Message:

   The following issue has been closed.

   Resolver: Vincent Massol
   Date: Fri, 11 Feb 2005 12:54 PM

Fixed. Thanks.
-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-21

Here is an overview of the issue:
-
Key: MPCLOVER-21
Summary: Invalid clover link in the site when no test is present
   Type: Bug

 Status: Closed
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Fix Fors:
 1.7

   Assignee: Vincent Massol
   Reporter: Julien Kirch

Created: Thu, 22 Jul 2004 9:32 AM
Updated: Fri, 11 Feb 2005 12:54 PM

Description:
When a project contains no test, the clover report is not generated but the 
clover report link is added to the site navigation pane.



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Commented: (MPCLOVER-27) Clover plugin does not work when using AspectJ plugin

2005-02-11 Thread jira
The following comment has been added to this issue:

 Author: Vincent Massol
Created: Fri, 11 Feb 2005 12:56 PM
   Body:
Alex, I have not been able to reproduce your problem. Is it still hapening? 
Could you please give more data so that I can try to reproduce it? Thanks.
-
View this comment:
  http://jira.codehaus.org/browse/MPCLOVER-27?page=comments#action_29803

-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-27

Here is an overview of the issue:
-
Key: MPCLOVER-27
Summary: Clover plugin does not work when using AspectJ plugin
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Versions:
 1.6

   Assignee: 
   Reporter: Alex Ruiz

Created: Fri, 7 Jan 2005 9:16 AM
Updated: Fri, 11 Feb 2005 12:56 PM

Description:
I don't know if this is a bug or I am something wrong.  I'm using both Clover 
and AspectJ plugins in my project.  Clover does not work if I have this lines 
in my maven.xml file:
preGoal name=java:compile
attainGoal name=aspectj/
/preGoal
And when I remove 'attainGoal name=aspectj/' Clover works perfectly.

Thank you.


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (MPCLOVER-6) historical report for clover

2005-02-11 Thread jira
The following issue has been updated:

Updater: Vincent Massol (mailto:[EMAIL PROTECTED])
   Date: Fri, 11 Feb 2005 12:57 PM
Comment:
I'll apply this for Clover plugin 1.8. I'd like to release Clover plugin 1.7 
now.
Changes:
 assignee changed to Vincent Massol
 Version changed to 1.6
 Version changed from 1.2
 Fix Version changed from 1.7
-
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MPCLOVER-6?page=history

-
View the issue:
  http://jira.codehaus.org/browse/MPCLOVER-6

Here is an overview of the issue:
-
Key: MPCLOVER-6
Summary: historical report for clover
   Type: Improvement

 Status: Open
   Priority: Minor

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-clover-plugin
   Versions:
 1.6

   Assignee: Vincent Massol
   Reporter: Simon Matic Langford

Created: Tue, 22 Jul 2003 3:34 AM
Updated: Fri, 11 Feb 2005 12:57 PM
Environment: clover required

Description:
Does a historical clover report if there are results spanning more than one day.

Changes to plugin.jelly:

37a38,42
   doc:registerReport
 name=Clover Historical
 pluginName=maven-clover-plugin
 link=clover-history/historical
 description=Clover test coverage historical report./
48a54
 attainGoal name=clover:historic-report/
82a89,92

 j:set
   var=cloverHistoryReportDirectory
   
 value=${pom.getPluginContext('maven-xdoc-plugin').getVariable('maven.docs.dest')}/clover-history/
89a100
 ant:mkdir dir=${cloverHistoryReportDirectory}/
126c137
   current
---
   ant:current
130c141
   /current
---
   /ant:current
150a162,192

   goal
 name=clover:historic-report
 description=Generate HTML test coverage reports with Clover
 attainGoal name=clover:test/
 ant:clover-historypoint historyDir=${maven.clover.historic.dir}/
 attainGoal name=java:compile/
   ant:taskdef name=check-clover-history
   classname=org.apache.maven.clover.CheckCloverHistoryTask
   classpath=${maven.build.dest}
   /
 ant:check-clover-history
   historyDir=${maven.clover.historic.dir}
   property=cloverHistoryOk
   value=true
 /
 j:if test=${cloverHistoryOk == 'true'}
   ant:clover-report
 ant:historical
   title=${pom.name} - ${pom.currentVersion}
   outfile=${cloverHistoryReportDirectory}
   historyDir=${maven.clover.historic.dir}
   ant:overview /
   ant:coverage /
   ant:metrics /
   ant:movers range=10 interval=1w /
   ant:format type=html orderBy=ElementsCoveredAsc/
 /ant:historical
   /ant:clover-report
 /j:if
   /goal

New Ant task org/apache/maven/clover/CheckCloverHistoryTask.java:
===
package org.apache.maven.clover;

import java.io.IOException;
import java.io.File;
import java.util.Vector;

import org.apache.tools.ant.Task;
import org.apache.tools.ant.BuildException;

/**
 * @author a href=mailto:[EMAIL PROTECTED]Simon Matic Langford/a
 * @version 1.0
 */
public class CheckCloverHistoryTask extends Task
{
  /**
   * Location of the clover history files.
   */
  private String historyDir = null;
  /**
   * Property to set if 2 or more days of data found.
   */
  private String property = null;
  /**
   * Value of property to set if 2 or more days of data found.
   */
  private String value = null;

  /**
   * @see #historyDir
   */
  public String getHistoryDir()
  {
return historyDir;
  }

  /**
   * @see #historyDir
   */
  public void setHistoryDir(String historyDir)
  {
this.historyDir = historyDir;
  }

  /**
   * @see #property
   */
  public String getProperty()
  {
return property;
  }

  /**
   * @see #property
   */
  public void setProperty(String property)
  {
this.property = property;
  }

  /**
   * @see #value
   */
  public String getValue()
  {
return value;
  }

  /**
   * @see #value
   */
  public void setValue(String value)
  {
this.value = value;
  }

  /**
   * Sets the property if at least 2 seperate days of clover
   * history data found.
   */
  public void execute() throws BuildException
  {
File dir = new File(historyDir);
String[] filenames = dir.list();
Vector v = new Vector();
for (int i=0; ifilenames.length; i++)
{
  String date = getDateBit(filenames[i]);
  if (v.contains(date))
  {
getProject().setProperty(property,value);
log(Found 2 different days.);
return;
  }
  else
  {
v.addElement(date);
  }
}
log(Found only 1 

[VOTE] Release Clover plugin 1.7?

2005-02-11 Thread Vincent Massol
Hi,

I've been making several changes to the Clover plugin:

  action dev=vmassol type=fix issue=MPCLOVER-21
Do not create a Clover report link when the project has no tests.
  /action
  action dev=vmassol type=update issue=MPCLOVER-22
due-to=Maarten Coene
Open Clover report page in a new window in the same manner as it's 
done for the Javadoc and XRef reports.
  /action
  action dev=vmassol type=add issue=MPCLOVER-25 due-to=Michael
Gaffney
Added codemaven.clover.includes/code and 
codemaven.clover.excludes/code properties to specify what files
to include/exclude from the Cloverification.
  /action
  action dev=vmassol type=update issue=MPCLOVER-18
Added new codemaven.clover.execute.during.report/code property 
to control whether or not the codeclover-report/code
goal builds Cloverify the sources and execute the tests
(defaults to true).
  /action
  action dev=vmassol type=update issue=MPCLOVER-24
Deprecated codemaven.clover.database.dir/code property and
replaced it with a codemaven.cover.database/code property that
contains not only the database directory but also the name of the
database file.
  /action
  action dev=vmassol type=fix issue=MPCLOVER-28
codeclover:off/code should now reset correctly the 
codemaven.build.dest/code property that codeclover:on/code
modifies. Note that the reported error has been fixed even though I
have not been able to reproduce the problem (and hence we don't have
a test for it).
  /action
  action dev=vmassol type=update issue=MPCLOVER-26
Upgraded Clover to version 1.3.4.
  /action

I'd like to release Clover plugin 1.7.

Here's my +1

Thanks
-Vincent




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if they've already run

2005-02-11 Thread Read, Matt
Mainly for things like the pretty JUnit report. The report is really useful and 
if a continuous integration build reports failed tests I want anyone on the 
team to easily find out where it failed. The Junit report is great for this but 
it's only available if I regenerate the site - continuously.

Matt.

-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED] 
Sent: 10 February 2005 20:17
To: 'Maven Developers List'
Cc: [EMAIL PROTECTED]
Subject: RE: [jira] Commented: (MPCLOVER-18) Stop Clover re-running tests if 
they've already run


Hi Matt,

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 Sent: jeudi 10 fvrier 2005 14:56
 To: [EMAIL PROTECTED]
 Subject: [jira] Commented: (MPCLOVER-18) Stop Clover re-running tests 
 if they've already run
 
 The following comment has been added to this issue:
 
  Author: Matt Read
 Created: Thu, 10 Feb 2005 8:55 AM
Body:
 Yep, that would solve my immediate (well, immediate 7 months ago) 
 problems.
 
 I agree with you completely on your general consideration point. For 
 the kind of projects that I'm generally involved with, Maven simply 
 will not scale sufficiently to support continuous integration. I find 
 myself slipping back to nightly builds for more and more of the goals 
 as the codebase grows.

But then why do you wish to continuously generate the web site? I'm doing 
continuous integration with Maven on one big project (every 2 hours roughly) 
and it works very well. We don't generate the web site every 2 hours (only once 
a day at night). That said we could do it easily (it would cost 10 minutes more 
per project which is not a big deal if you parallelize your builds).

Thanks
-Vincent





This e-mail is confidential and intended solely for the use of the 
individual(s) to whom it is addressed.  If you are not the intended recipient, 
be advised that you have received this e-mail in error and that any use, 
dissemination, forwarding, printing, copying of , or any action taken in 
reliance upon, it is strictly prohibited and may be illegal.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [VOTE] Release Clover plugin 1.7?

2005-02-11 Thread Brett Porter
+1
Vincent Massol wrote:
Hi,
I've been making several changes to the Clover plugin:
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Using the new site plugin from svn trunk?

2005-02-11 Thread Brett Porter
Vincent Massol wrote:
Hi,
I have built the site plugin from svn trunk and when I was trying to use it
upload a plugin web site, I got:
 

http://marc.theaimsgroup.com/?l=turbine-maven-devm=110645238621134w=2
Please don't publish the main Maven site though - just do it for 
plugins. My home directory is used because we don't have anywhere else 
to put a staging site.

As far as rsync goes, you can set maven.site.deploy.method=ssh if you 
don't have it installed.

Cheers,
Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: Trying to build the xdoc plugin

2005-02-11 Thread Brett Porter
Vincent Massol wrote:
Hi,
I'm trying to build the xdoc plugin from SVN trunk. I got:
C:\dev\maven\maven-1\plugins\xdocmaven clean plugin:install
__  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
Tentative de tlchargement de commons-jelly-1.0-RC1.jar.
165K downloaded
Tentative de tlchargement de commons-jelly-tags-jsl-1.1-SNAPSHOT.jar.
Response content length is not known
ATTENTION: Impossible de tlcharger
commons-jelly-tags-jsl-1.1-SNAPSHOT.jar.
Tentative de tlchargement de commons-jelly-tags-log-1.0.jar.
10K downloaded
Tentative de tlchargement de commons-jelly-tags-velocity-1.0.jar.
10K downloaded
Tentative de tlchargement de maven-model-3.0.0-SNAPSHOT.jar.
Response content length is not known
ATTENTION: Impossible de tlcharger maven-model-3.0.0-SNAPSHOT.jar.
Le processus ne peut continuer  cause des dpendances manquantes suivantes:
commons-jelly-tags-jsl-1.1-SNAPSHOT.jar
 

Oops - I didn't mean to commit that! Please set it back to 1.0.
maven-model-3.0.0-SNAPSHOT.jar
 

http://cvs.apache.org/repository/maven/jars/
Is it normal that the 2 artifacts mentioned are not on ibiblio?
 

Yes, the policy I've been given (which is yet to be documented) is that 
unreleased JARs are not to go into www.apache.org/dist/java-repository, 
and must go to cvs.apache.org/repository.

Make sure you are honouring the maven.repo.remote setting in 
plugin-parent/project.properties.

Cheers,
Brett
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [MAVEN] ${pom.properties} is a ArrayList of String?

2005-02-11 Thread Brett Porter
Yes, in fact on svn HEAD for Maven they are already a java.util.Properties
- Brett
Nacho G. Mac Dowell wrote:
Silly me...  :-[
I saw properties might get deprecated so I'll stick with 
project.properties


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[jira] Closed: (MAVENUPLOAD-299) Wrapper 3.1.2

2005-02-11 Thread jira
Message:

   The following issue has been closed.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-299

Here is an overview of the issue:
-
Key: MAVENUPLOAD-299
Summary: Wrapper 3.1.2
   Type: Task

 Status: Closed
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Carlos Sanchez
   Reporter: Johan Sjöberg

Created: Thu, 10 Feb 2005 3:57 PM
Updated: Fri, 11 Feb 2005 6:16 PM

Description:
Upload request for wrapper 3.1.2 


-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


[jira] Commented: (MPIDEA-14) Add source path/jar for dependencies

2005-02-11 Thread jira
The following comment has been added to this issue:

 Author: Michael Hinterseher
Created: Fri, 11 Feb 2005 8:47 PM
   Body:
To add sourcecode to the IDEA JARS replace the
SOURCE/
tag in module.jelly file with
SOURCES
  root 
url=jar://$$HOME$$/.maven/repository/${dep.groupId}/jars/${dep.artifactId}-${dep.version}-src.zip!/${dep.artifactId}-${dep.version}/src/java
 /
/SOURCES

It would be good if somebody, who has write access to the project could add 
this lines.
The statement could be improved to add only source if the file exists. This 
would avoid uggly red lines in the project.
Jet I haven't spend time to figure out how.

-
View this comment:
  http://jira.codehaus.org/browse/MPIDEA-14?page=comments#action_29813

-
View the issue:
  http://jira.codehaus.org/browse/MPIDEA-14

Here is an overview of the issue:
-
Key: MPIDEA-14
Summary: Add source path/jar for dependencies
   Type: New Feature

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-idea-plugin

   Assignee: 
   Reporter: Adrian Tarau

Created: Mon, 29 Nov 2004 5:50 PM
Updated: Fri, 11 Feb 2005 8:47 PM

Description:
I have a few suggestions for impruving this gread plugin.

First, a good feature is to be able to specify in a dependency properties the 
path to the dependency sources:

properties
   idea.depend.srcc:\work\project1\src\java/idea.depend.src
/properties



-
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Re: [VOTE] Release Clover plugin 1.7?

2005-02-11 Thread Alex Karasulu
Been waiting for this one.
+1
Cheers,
Alex
Brett Porter wrote:
+1
Vincent Massol wrote:
Hi,
I've been making several changes to the Clover plugin:
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]