[ANN] Maven Clover Plugin 1.7 released
The maven team is pleased to announce the Maven Clover Plugin 1.7 release! http://maven.apache.org/reference/plugins/clover/ The Clover plugin allows measuring test coverage using Clover (http://www.cenqua.com/clover). Changes in this version include: New Features: o Added maven.clover.includesand maven.clover.excludesproperties to specify what files to include/exclude from the Cloverification. Issue: MPCLOVER-25. Thanks to Michael Gaffney. Fixed bugs: o Do not create a Clover report link when the project has no tests. Issue: MPCLOVER-21. o clover:offshould now reset correctly the maven.build.destproperty that clover:onmodifies. 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). Issue: MPCLOVER-28. Changes: o Open Clover report page in a new window in the same manner as it's done for the Javadoc and XRef reports. Issue: MPCLOVER-22. Thanks to Maarten Coene. o Added new maven.clover.execute.during.reportproperty to control whether or not the clover-reportgoal builds Cloverify the sources and execute the tests (defaults to true). Issue: MPCLOVER-18. o Deprecated maven.clover.database.dirproperty and replaced it with a maven.cover.databaseproperty that contains not only the database directory but also the name of the database file. Issue: MPCLOVER-24. o Upgraded Clover to version 1.3.4. Issue: MPCLOVER-26. To automatically install the plugin, type the following on a single line: maven plugin:download -DgroupId=maven -DartifactId=maven-clover-plugin -Dversion=1.7 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-clover-plugin-1.7.jar Have fun! -The maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Releasing a Maven plugin - To where?
Hi, I've just released the Clover 1.7 plugin. I've used the default settings from SVN trunk and the SCM plugin has put the artifacts on cvs.apache.org. Is that the right place? Isn't cvs.apache.org for SNAPSHOTs only and www.apache.org for released versions? Should I have changed the property maven.repo.list to be maven.repo.list=apache (instead of the default maven.repo.list=apachecvs)? Also, would you know how frequently is cvs.apache.org synced with ibiblio? Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing a Maven plugin - To where?
Hi, Hi Vincent, I've just released the Clover 1.7 plugin. I've used the default settings from SVN trunk and the SCM plugin has put the artifacts on cvs.apache.org. Is that the right place? Isn't cvs.apache.org for SNAPSHOTs only and www.apache.org for released versions? Should I have changed the property maven.repo.list to be maven.repo.list=apache (instead of the default maven.repo.list=apachecvs)? Yes, it's www.apache.org. cvs.apache.org is used only for snapshots. Also, would you know how frequently is cvs.apache.org synced with ibiblio? cvs.apache.org is never synchronized with ibiblio. We synchronized only www.apache.org every 4 hours. Emmanuel Thanks -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Remote repository mirror mirrors.sunsite.dk/maven has invalid content?
Hi, I posted a message yesterday concerning this very annoying problem to the users list, but did not get an anwser. So I'm trying the dev list instead and hope to hear *if* this is an apache problem, or a sunsite problem. The mirror now shows the distribution of maven instead of the remote repository contents. Can someone please look at this, because in Europe it is not feasable to use ibiblio as it is across the ocean and it gets quite cramped sometimes. With regards, Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remote repository mirror mirrors.sunsite.dk/maven has invalid content?
I will contact the mirror hosts. I'm not aware of any arrangement we had with them to do this, and assumed they were a pure ibiblio mirror. They do have: http://mirrors.sunsite.dk/apache/dist/java-repository/, which is a mirror of Apache releases. - Brett Martijn Dashorst wrote: Hi, I posted a message yesterday concerning this very annoying problem to the users list, but did not get an anwser. So I'm trying the dev list instead and hope to hear *if* this is an apache problem, or a sunsite problem. The mirror now shows the distribution of maven instead of the remote repository contents. Can someone please look at this, because in Europe it is not feasable to use ibiblio as it is across the ocean and it gets quite cramped sometimes. With regards, Martijn - 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]
RE: Releasing a Maven plugin - To where? (SOLVED)
Ok, I've republished to www.apache.org. After talking to Brett on IRC I confirm that released versions should go to www.apache.org and not cvs.apache.org (which is for SNAPSHOT versions). Thanks -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: mardi 15 février 2005 09:20 To: 'Maven Developers List' Subject: Releasing a Maven plugin - To where? Hi, I've just released the Clover 1.7 plugin. I've used the default settings from SVN trunk and the SCM plugin has put the artifacts on cvs.apache.org. Is that the right place? Isn't cvs.apache.org for SNAPSHOTs only and www.apache.org for released versions? Should I have changed the property maven.repo.list to be maven.repo.list=apache (instead of the default maven.repo.list=apachecvs)? Also, would you know how frequently is cvs.apache.org synced with ibiblio? Thanks -Vincent - 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]
Re: Releasing a Maven plugin - To where? (SOLVED)
The releasing plugins documentation on svn head actually reflects this, but has not yet been published live due to the incomplete site re-org, in case anyone is looking for it. Vincent Massol wrote: Ok, I've republished to www.apache.org. After talking to Brett on IRC I confirm that released versions should go to www.apache.org and not cvs.apache.org (which is for SNAPSHOT versions). Thanks -Vincent -Original Message- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: mardi 15 février 2005 09:20 To: 'Maven Developers List' Subject: Releasing a Maven plugin - To where? Hi, I've just released the Clover 1.7 plugin. I've used the default settings from SVN trunk and the SCM plugin has put the artifacts on cvs.apache.org. Is that the right place? Isn't cvs.apache.org for SNAPSHOTs only and www.apache.org for released versions? Should I have changed the property maven.repo.list to be maven.repo.list=apache (instead of the default maven.repo.list=apachecvs)? Also, would you know how frequently is cvs.apache.org synced with ibiblio? Thanks -Vincent - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remote repository mirror mirrors.sunsite.dk/maven has invalid content?
OK Thanks. All the other mirrors still work, but they are really slow ;-) Just installed maven-proxy to fix the ibiblio slowness. Seems to work greatly, but could do better on the documentation and getting an official 1.0. Martijn Brett Porter wrote: I will contact the mirror hosts. I'm not aware of any arrangement we had with them to do this, and assumed they were a pure ibiblio mirror. They do have: http://mirrors.sunsite.dk/apache/dist/java-repository/, which is a mirror of Apache releases. - Brett Martijn Dashorst wrote: Hi, I posted a message yesterday concerning this very annoying problem to the users list, but did not get an anwser. So I'm trying the dev list instead and hope to hear *if* this is an apache problem, or a sunsite problem. The mirror now shows the distribution of maven instead of the remote repository contents. Can someone please look at this, because in Europe it is not feasable to use ibiblio as it is across the ocean and it gets quite cramped sometimes. With regards, Martijn - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remote repository mirror mirrors.sunsite.dk/maven has invalid content?
sunsite.dk got back to me very quickly - great service! It was an accident, and they have already started restoring it, but it will take some time to rebuild. Regards, Brett Martijn Dashorst wrote: OK Thanks. All the other mirrors still work, but they are really slow ;-) Just installed maven-proxy to fix the ibiblio slowness. Seems to work greatly, but could do better on the documentation and getting an official 1.0. Martijn Brett Porter wrote: I will contact the mirror hosts. I'm not aware of any arrangement we had with them to do this, and assumed they were a pure ibiblio mirror. They do have: http://mirrors.sunsite.dk/apache/dist/java-repository/, which is a mirror of Apache releases. - Brett Martijn Dashorst wrote: Hi, I posted a message yesterday concerning this very annoying problem to the users list, but did not get an anwser. So I'm trying the dev list instead and hope to hear *if* this is an apache problem, or a sunsite problem. The mirror now shows the distribution of maven instead of the remote repository contents. Can someone please look at this, because in Europe it is not feasable to use ibiblio as it is across the ocean and it gets quite cramped sometimes. With regards, Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPPDF-31) Cannot insert logo image to PDF
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPPDF-31
Here is an overview of the issue:
-
Key: MPPDF-31
Summary: Cannot insert logo image to PDF
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-pdf-plugin
Versions:
2.2
Assignee: Arnaud HERITIER
Reporter: Oleg F. Vlasenko
Created: Tue, 15 Feb 2005 4:46 AM
Updated: Tue, 15 Feb 2005 4:46 AM
Environment: Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
Description:
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so the
prefix ${maven.xdoc.src}is not concatenated to the path. And so the file
YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set
var=maven.pdf.companyLogo${maven.xdoc.src}${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
-
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: (MPPDF-31) Cannot insert logo image to PDF
The following comment has been added to this issue:
Author: Oleg F. Vlasenko
Created: Tue, 15 Feb 2005 4:50 AM
Body:
This response was written by Arnaud HERITIER :
I didn't notice it with my projects or maven itself :
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
logo/images/apache-maven-project.png/logo
/organization
inceptionYear2001/inceptionYear
packageorg.apache.maven/package
logo/images/maven-small.gif/logo
I'll test it a little bit more.
Thx for your help.
Arnaud
-
View this comment:
http://jira.codehaus.org/browse/MPPDF-31?page=comments#action_29891
-
View the issue:
http://jira.codehaus.org/browse/MPPDF-31
Here is an overview of the issue:
-
Key: MPPDF-31
Summary: Cannot insert logo image to PDF
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-pdf-plugin
Versions:
2.2
Assignee: Arnaud HERITIER
Reporter: Oleg F. Vlasenko
Created: Tue, 15 Feb 2005 4:46 AM
Updated: Tue, 15 Feb 2005 4:50 AM
Environment: Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
Description:
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so the
prefix ${maven.xdoc.src}is not concatenated to the path. And so the file
YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set
var=maven.pdf.companyLogo${maven.xdoc.src}${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
-
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]
Réf. : [jira] Commented: (MPPDF-31) Cannot insert logo image to PDF
Perhaps a problem with the gif format ?
Julien Kirch
Extranet
[EMAIL PROTECTED] - 15/02/2005 10:51
Veuillez répondre à dev@maven.apache.org
Pour : dev
cc :
Objet : [jira] Commented: (MPPDF-31) Cannot insert logo image to PDF
The following comment has been added to this issue:
Author: Oleg F. Vlasenko
Created: Tue, 15 Feb 2005 4:50 AM
Body:
This response was written by Arnaud HERITIER :
I didn't notice it with my projects or maven itself :
organization
nameApache Software Foundation/name
urlhttp://www.apache.org//url
logo/images/apache-maven-project.png/logo
/organization
inceptionYear2001/inceptionYear
packageorg.apache.maven/package
logo/images/maven-small.gif/logo
I'll test it a little bit more.
Thx for your help.
Arnaud
-
View this comment:
http://jira.codehaus.org/browse/MPPDF-31?page=comments#action_29891
-
View the issue:
http://jira.codehaus.org/browse/MPPDF-31
Here is an overview of the issue:
-
Key: MPPDF-31
Summary: Cannot insert logo image to PDF
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-pdf-plugin
Versions:
2.2
Assignee: Arnaud HERITIER
Reporter: Oleg F. Vlasenko
Created: Tue, 15 Feb 2005 4:46 AM
Updated: Tue, 15 Feb 2005 4:50 AM
Environment: Windows XP professional version 2002 and
Linux Red Hat / Maven 1.0.2 / maven-pdf-plugin-2.2.1
Description:
Fragment of text of project.xml:
?xml version=1.0 encoding=UTF-8?
project
...
organization
logo/images/XXX.gif/logo
/organization
logo/images/YYY.gif/logo
...
Fragment of text of maven.xml:
postGoal name=site
attainGoal name=pdf/
/postGoal
In compile time the error is generated.
...
[java] [ERROR] Error while creating area : Error while recovering Image
Informations (file:/images/YYY.gif) : /images/YYY.gif (No such file or
directory)
...
As I understand the problem is connected with following code:
j:if test=not ${maven.pdf.projectLogo.startsWith('http://')}
maven:makeAbsolutePath
var=maven.pdf.projectLogo
basedir=${maven.xdoc.src}
path=${maven.pdf.projectLogo}
trim=true/
/j:if
logo/images/YYY.gif/logo includes the path which is absolute. And so
the prefix ${maven.xdoc.src}is not concatenated to the path. And so the
file YYY.gif cannot be found.
I have simplified code and YYY.gif was found:
j:if test=${not maven.pdf.companyLogo.startsWith('http://')}
j:set var=maven.pdf.companyLogo${maven.xdoc.src}
${maven.pdf.companyLogo}/j:set
/j:if
I think this problem can be resolved by more general way.
-
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]
This message and any attachments (the message) is
intended solely for the addressees and is confidential.
If you receive this message in error, please delete it and
immediately notify the sender. Any use not in accord with
its purpose, any dissemination or disclosure, either whole
or partial, is prohibited except formal approval. The internet
can not guarantee the integrity of this message.
BNP PARIBAS (and its subsidiaries) shall (will) not
therefore be liable for the message if modified.
-
Ce message et toutes les pieces jointes (ci-apres le
message) sont etablis a l'intention exclusive de ses
destinataires et sont confidentiels. Si vous recevez ce
message par erreur, merci de le detruire et d'en avertir
immediatement l'expediteur. Toute utilisation de ce
message non conforme a sa destination, toute diffusion
ou toute publication, totale ou partielle, est interdite, sauf
autorisation expresse. L'internet ne permettant pas
d'assurer l'integrite de ce message, BNP PARIBAS (et ses
filiales) decline(nt) toute responsabilite au titre de ce
message, dans l'hypothese ou il aurait ete modifie.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-131) Allow velocity in user-documentation and expose pom
The following comment has been added to this issue:
Author: Ignacio G. Mac Dowell
Created: Tue, 15 Feb 2005 7:30 AM
Body:
The patch submitted fails when there is a directory with xdocs under the xdocs
directory. The problem is that velocity:merge doesn't seem to like generating a
file with no parentFile (directory). I am going to submit 4 patches:
1. Tests
2. Src
3. Docs
4. Cumulative (all 3)
for easier review.
regards
-
View this comment:
http://jira.codehaus.org/browse/MPXDOC-131?page=comments#action_29895
-
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: Tue, 15 Feb 2005 7:30 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
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:31 AM
Comment:
Tests for MPXDOC-131
Changes:
Attachment changed to last.test.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: Tue, 15 Feb 2005 7:31 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
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:32 AM
Comment:
Src for MPXDOC-131
Changes:
Attachment changed to last.main.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: Tue, 15 Feb 2005 7:32 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
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:32 AM
Comment:
Docs patch for MPXDOC-131
Changes:
Attachment changed to last.docs.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: Tue, 15 Feb 2005 7:32 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
The following issue has been updated:
Updater: Ignacio G. Mac Dowell (mailto:[EMAIL PROTECTED])
Date: Tue, 15 Feb 2005 7:33 AM
Comment:
Cumulative patch with tests, src and docs
Changes:
Attachment changed to last.cumulative.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: Tue, 15 Feb 2005 7:33 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]
svn commit: r153968 - in maven/maven-1/plugins/trunk/junit-report: plugin.jelly xdocs/changes.xml xdocs/goals.xml
Author: brett Date: Tue Feb 15 14:50:54 2005 New Revision: 153968 URL: http://svn.apache.org/viewcvs?view=revrev=153968 Log: fix documentation Modified: maven/maven-1/plugins/trunk/junit-report/plugin.jelly maven/maven-1/plugins/trunk/junit-report/xdocs/changes.xml maven/maven-1/plugins/trunk/junit-report/xdocs/goals.xml Modified: maven/maven-1/plugins/trunk/junit-report/plugin.jelly URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/junit-report/plugin.jelly?view=diffr1=153967r2=153968 == --- maven/maven-1/plugins/trunk/junit-report/plugin.jelly (original) +++ maven/maven-1/plugins/trunk/junit-report/plugin.jelly Tue Feb 15 14:50:54 2005 @@ -44,6 +44,9 @@ !-- C R E A T E J U N I T X M L R E P O R T -- !-- == -- + goal name=junit-report +prereqs=junit-report:report/ + goal name=maven-junit-report-plugin:report prereqs=junit-report:report/ Modified: maven/maven-1/plugins/trunk/junit-report/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/junit-report/xdocs/changes.xml?view=diffr1=153967r2=153968 == --- maven/maven-1/plugins/trunk/junit-report/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/junit-report/xdocs/changes.xml Tue Feb 15 14:50:54 2005 @@ -26,6 +26,7 @@ /properties body release version=1.5.1-SNAPSHOT date=in CVS + action dev=brett type=fixFix documentation, add default goal/action action dev=brett type=fix issue=MPJUNITREPORT-7Fix HTML problems by disabling jsl's pretty printing/action /release release version=1.5 date=2004-03-07 Modified: maven/maven-1/plugins/trunk/junit-report/xdocs/goals.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/junit-report/xdocs/goals.xml?view=diffr1=153967r2=153968 == --- maven/maven-1/plugins/trunk/junit-report/xdocs/goals.xml (original) +++ maven/maven-1/plugins/trunk/junit-report/xdocs/goals.xml Tue Feb 15 14:50:54 2005 @@ -30,9 +30,9 @@ descriptionGenerate a report from the test results/description /goal goal -namejunit-report:generate/name +namejunit-report:report/name descriptionGenerate a report from the test results/description /goal /goals /body -/document \ No newline at end of file +/document - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPSITE-23) Rsync fail
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSITE-23
Here is an overview of the issue:
-
Key: MPSITE-23
Summary: Rsync fail
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-site-plugin
Components:
plugin
Versions:
1.6
Assignee:
Reporter: Oscar Picasso
Created: Tue, 15 Feb 2005 5:58 PM
Updated: Tue, 15 Feb 2005 5:58 PM
Environment: OS: linux redhat 8.0
Java: 1.5
Description:
On site:rsyncdeploy, get the following:
[exec] building file list ... done
[exec] link_stat target/docs/* : No such file or directory
[exec] wrote 25 bytes read 20 bytes 90.00 bytes/sec
[exec] rsync error: some files could not be transferred (code 23) at
main.c(620)
[exec] total size is 0 speedup is 0.00
[exec] [ERROR] Result: 23
BUILD SUCCESSFUL
In plugin.jelly I have added some echo/ to see what could happen:
echo${maven.rsync.executable}/echo
echo-avz ${rsyncArgs} ${relativeDocsDest}/* [EMAIL
PROTECTED]:${siteDirectory}/echo
I used the output to launch the command from the shell command line and it
works fine.
I also added exec dir=. executable=pwd/ to check it the directory was
correct and it was.
So it seems that all the parameters to execute the rsync are good but the
command failed when used from the plugin.
-
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: (MPSITE-23) Rsync fail
The following comment has been added to this issue:
Author: Brett Porter
Created: Tue, 15 Feb 2005 6:05 PM
Body:
It looks like target/docs is empty. Did you run site first?
-
View this comment:
http://jira.codehaus.org/browse/MPSITE-23?page=comments#action_29932
-
View the issue:
http://jira.codehaus.org/browse/MPSITE-23
Here is an overview of the issue:
-
Key: MPSITE-23
Summary: Rsync fail
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-site-plugin
Components:
plugin
Versions:
1.6
Assignee:
Reporter: Oscar Picasso
Created: Tue, 15 Feb 2005 5:58 PM
Updated: Tue, 15 Feb 2005 6:05 PM
Environment: OS: linux redhat 8.0
Java: 1.5
Description:
On site:rsyncdeploy, get the following:
[exec] building file list ... done
[exec] link_stat target/docs/* : No such file or directory
[exec] wrote 25 bytes read 20 bytes 90.00 bytes/sec
[exec] rsync error: some files could not be transferred (code 23) at
main.c(620)
[exec] total size is 0 speedup is 0.00
[exec] [ERROR] Result: 23
BUILD SUCCESSFUL
In plugin.jelly I have added some echo/ to see what could happen:
echo${maven.rsync.executable}/echo
echo-avz ${rsyncArgs} ${relativeDocsDest}/* [EMAIL
PROTECTED]:${siteDirectory}/echo
I used the output to launch the command from the shell command line and it
works fine.
I also added exec dir=. executable=pwd/ to check it the directory was
correct and it was.
So it seems that all the parameters to execute the rsync are good but the
command failed when used from the plugin.
-
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: (MPSITE-23) Rsync fail
The following comment has been added to this issue:
Author: Oscar Picasso
Created: Tue, 15 Feb 2005 10:23 PM
Body:
I did run site and targets/docs was not empty.
I've with both java 1.5.0 and java 1.4.2 and got the same error.
It's weird because the plugin seem to use the right command.
I added the following to the site:rsync goal.
...
!-- added --
echo${maven.rsync.executable}/echo
echo-avz ${rsyncArgs} ${relativeDocsDest}/* [EMAIL
PROTECTED]:${siteDirectory}/echo
exec dir=. executable=pwd/
!-- end added --
exec dir=. executable=${maven.rsync.executable}
arg line=-avz ${rsyncArgs} ${relativeDocsDest}/* [EMAIL
PROTECTED]:${siteDirectory}/
/exec
...
The output gave:
site:rsyncdeploy:
[echo] rsync
[echo] -avz target/docs/* [EMAIL PROTECTED]:/tmp/site-test
[exec] /home/oscar/workspace/db-je
...
From the output above I copied and paste to make the following command from
the /home/oscar/workspace/db-je directory:
rsync -avz target/docs/* [EMAIL PROTECTED]:/tmp/site-test
It worked perfectly.
By the way, what does exec do? Just calling one of the Runtime.exec() method?
-
View this comment:
http://jira.codehaus.org/browse/MPSITE-23?page=comments#action_29940
-
View the issue:
http://jira.codehaus.org/browse/MPSITE-23
Here is an overview of the issue:
-
Key: MPSITE-23
Summary: Rsync fail
Type: Bug
Status: Unassigned
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-site-plugin
Components:
plugin
Versions:
1.6
Assignee:
Reporter: Oscar Picasso
Created: Tue, 15 Feb 2005 5:58 PM
Updated: Tue, 15 Feb 2005 10:23 PM
Environment: OS: linux redhat 8.0
Java: 1.5
Description:
On site:rsyncdeploy, get the following:
[exec] building file list ... done
[exec] link_stat target/docs/* : No such file or directory
[exec] wrote 25 bytes read 20 bytes 90.00 bytes/sec
[exec] rsync error: some files could not be transferred (code 23) at
main.c(620)
[exec] total size is 0 speedup is 0.00
[exec] [ERROR] Result: 23
BUILD SUCCESSFUL
In plugin.jelly I have added some echo/ to see what could happen:
echo${maven.rsync.executable}/echo
echo-avz ${rsyncArgs} ${relativeDocsDest}/* [EMAIL
PROTECTED]:${siteDirectory}/echo
I used the output to launch the command from the shell command line and it
works fine.
I also added exec dir=. executable=pwd/ to check it the directory was
correct and it was.
So it seems that all the parameters to execute the rsync are good but the
command failed when used from the plugin.
-
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: r154007 - in maven/maven-1/plugins/trunk/clover: project.xml xdocs/changes.xml
Author: vmassol Date: Tue Feb 15 23:52:10 2005 New Revision: 154007 URL: http://svn.apache.org/viewcvs?view=revrev=154007 Log: work for version 1.8 is open... Modified: maven/maven-1/plugins/trunk/clover/project.xml maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Modified: maven/maven-1/plugins/trunk/clover/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/clover/project.xml?view=diffr1=154006r2=154007 == --- maven/maven-1/plugins/trunk/clover/project.xml (original) +++ maven/maven-1/plugins/trunk/clover/project.xml Tue Feb 15 23:52:10 2005 @@ -23,7 +23,7 @@ pomVersion3/pomVersion idmaven-clover-plugin/id nameMaven Clover Plugin/name - currentVersion1.7/currentVersion + currentVersion1.8-SNAPSHOT/currentVersion descriptionThe Clover plugin allows measuring test coverage using Clover (http://www.cenqua.com/clover)./description shortDescriptionProduce Clover reports/shortDescription urlhttp://maven.apache.org/reference/plugins/clover//url 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=154006r2=154007 == --- maven/maven-1/plugins/trunk/clover/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/clover/xdocs/changes.xml Tue Feb 15 23:52:10 2005 @@ -25,6 +25,8 @@ author email=[EMAIL PROTECTED]Emmanuel Venisse/author /properties body +release version=1.8 date=in SVN +/release release version=1.7 date=2005-02-14 action dev=vmassol type=fix issue=MPCLOVER-21Do not create a Clover report link when the project has no tests./action action dev=vmassol type=update issue=MPCLOVER-22 due-to=Maarten CoeneOpen 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]
