[jira] Commented: (MPCLOVER-53) Use new clover license as the old one is exiring on 30th of Jan 2006
[ http://jira.codehaus.org/browse/MPCLOVER-53?page=comments#action_57306 ] Guy Rixon commented on MPCLOVER-53: --- So where is it? The download page for the plug-in only shows versions up to 1.10 and v1.10 has the old licence. if you have a v1.11, please release it NOW, it's critical, the old licence has already expired. If you aren't ready to release v1.11, then please do a v1.10.1 with the new licence. > Use new clover license as the old one is exiring on 30th of Jan 2006 > > > Key: MPCLOVER-53 > URL: http://jira.codehaus.org/browse/MPCLOVER-53 > Project: maven-clover-plugin > Type: Task > Reporter: Vincent Massol > Assignee: Vincent Massol > Fix For: 1.11 > > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1723) xdoc goal crashes
xdoc goal crashes - Key: MAVEN-1723 URL: http://jira.codehaus.org/browse/MAVEN-1723 Project: Maven Type: Bug Environment: Windows XP, SUN JDK 1.4.2 build 08 Reporter: Guy Rixon Fix For: 1.1-beta-2 The xdoc goal crashes like this: BUILD FAILED File.. C:\Documents and Settings\gtr\.maven\cache\maven-xdoc-plugin-1.9.2\pl ugin.jelly Element... j:include Line.. 479 Column -1 file:/C:/Documents and Settings/gtr/.maven/cache/maven-xdoc-plugin-1.9.2/plugin- resources/site.jsl:33:-1: file:/C:/Documents and Settings/gtr/. maven/cache/maven-xdoc-plugin-1.9.2/plugin-resources/site.jsl:156:-1: file:/C:/Documents and Settings/gtr/.maven/cache/maven-xdoc-plugin-1. 9.2/plugin-resources/site.jsl:240:-1: You must define an attrib ute called 'defaultValue' for this tag. On investigating the named file in the plug-in, I find this at line 240: The same error occurs whether or not the POM has a . A similar, but less-well described error happens in Maven 1.0.2. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPJAVA-39) Plug-in ignores source generated during Maven run
Plug-in ignores source generated during Maven run - Key: MPJAVA-39 URL: http://jira.codehaus.org/browse/MPJAVA-39 Project: maven-java-plugin Type: Bug Environment: Windows XP SP2; JDK 1.5; Maven 1.0.2; Reporter: Guy Rixon Priority: Critical My project generates its Java source-code and then tries to compile it: I have a custom goal that does both in one run of Maven . The java plug-in ignores the generated source and claims that there are no Java files to compile. If I run java:compile again, without cleaning the directory,then the plug-in notices the source-code and compiles it. It looks like the check for files to compile is done when Maven starts, not when the goals in the Java plug-in are run. This is a BAD design decision and is causing me real grief. Please support generated code. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPTEST-54) Maven crashes when writing JUnit report
Maven crashes when writing JUnit report --- Key: MPTEST-54 URL: http://jira.codehaus.org/browse/MPTEST-54 Project: maven-test-plugin Type: Bug Environment: Windows XP SP2 + JDK 1.5.0 + Xalan 2.6.0 + Maven 1.0.2 + test plug-in 1.5 Reporter: Guy Rixon When writing the JUnit report, Maven crashes with a stack-overflow error. This happens consistently in some Maven projects and not at all in others. It may be that the projects with more tests experience the crash. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1601) XSLT transformations fail with JDK 1.5
XSLT transformations fail with JDK 1.5 -- Key: MAVEN-1601 URL: http://jira.codehaus.org/browse/MAVEN-1601 Project: maven Type: Bug Versions: 1.0.2 Environment: Sun JDK 1.5.0_02. Windows XP SP2 Reporter: Guy Rixon I work with projects that invoke XSLT from maven.xml. To make these work with Sun JDK 1.4.x, I have to set, inside maven.xml, the system property that specifies the XSLT transformer-factory class from Xalan: this works. To work with Sun JDK 1.5.x, I have to set the property to point to a different class, not in the org.apache tree, since Sun ship a different XSLT implementation. When I do this, Maven fails due to a dependency on a class in Xalan. I can work round this by putting the Xalan jar into my Maven installation (i.e. in %MAVEN_HOME$\lib), but my co-workers don't want to modify their copies of Maven. Can Maven please be made independent of the XSLT/JAXP implementation? -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
