[jira] Commented: (MJXR-19) JXR Plugin ignores the reporting output directory when generating cross reference
[ http://jira.codehaus.org/browse/MJXR-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87850 ] Vincent Siveton commented on MJXR-19: - Should be rev 433277 > JXR Plugin ignores the reporting output directory when generating cross > reference > - > > Key: MJXR-19 > URL: http://jira.codehaus.org/browse/MJXR-19 > Project: Maven 2.x JXR Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Eric Helfrich > Fix For: 2.1 > > Attachments: module.zip > > > The JXR Plugin ignores the reporting outputDirectory when generating the > cross reference and puts it in target/site instead -- 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
[jira] Commented: (MJXR-20) empty index.html when site is staged.
[ http://jira.codehaus.org/browse/MJXR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87851 ] Vincent Siveton commented on MJXR-20: - Should be rev 433277 > empty index.html when site is staged. > - > > Key: MJXR-20 > URL: http://jira.codehaus.org/browse/MJXR-20 > Project: Maven 2.x JXR Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Jörg Hohwiller > Fix For: 2.1 > > > The JXR report works fine with "mvn site" but fails for "mvn site:stage" > (empty index.html). > Could you please evaluate MSITE-138 and MSITE-120. > Thank you very much. -- 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
[jira] Commented: (MSOURCES-12) size of source jar grows and grows
[
http://jira.codehaus.org/browse/MSOURCES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87860
]
Niall Pemberton commented on MSOURCES-12:
-
This looks like a duplicate of MSOURCES-6 which is resolved in the version
2.0.3 that was being voted on recently.
> size of source jar grows and grows
> --
>
> Key: MSOURCES-12
> URL: http://jira.codehaus.org/browse/MSOURCES-12
> Project: Maven 2.x Sources Plugin
> Issue Type: Bug
>Affects Versions: 2.0.2
>Reporter: Matthias Weßendorf
>
> I am seeing this, when using the 2.0.2 source plugin inside my release
> profile and runing
> mvn release:perform -Prelease
> [INFO] Building jar:
> d:\Apache\_release\last\target\checkout\maven-faces-plugin\target\maven-faces-plugin-1.0.0-incubating-javadoc.jar
> [INFO] Preparing source:jar
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [WARNING] Removing: jar from forked lifecycle, to prevent recursive
> invocation.
> [INFO] [scm:update {execution: getting-scm.revision}]
> [INFO] Executing: svn --non-interactive update
> [INFO] Working directory:
> d:\Apache\_release\last\target\checkout\maven-faces-plugin
> [INFO] Storing revision in 'scm.revision' project property.
> [INFO] [source:jar {execution: attach-sources}]
> [INFO] Building jar:
> d:\Apache\_release\last\target\checkout\maven-faces-plugin\target\maven-faces-plugin-1.0.0-incubating-sources.jar
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error creating source archive: Problem creating jar: There is not
> enough space on the disk (and the archive is probably corrupt but I could not
> delete it)
> [INFO]
>
> [INFO] For more information, run Maven with the -e switch
> [INFO]
>
> [INFO] Total time: 8 minutes 42 seconds
> [INFO] Finished at: Wed Feb 14 09:13:58 CET 2007
> [INFO] Final Memory: 15M/31M
> [INFO]
>
> [INFO]
>
> [ERROR] BUILD ERROR
> This work around helped (instead using the 2.0.2 maven-source-plugin)
>
>
> maven-antrun-plugin
>
>
> generate-resources
>
>
>
>
>
>
>
>
>
>
>
> run
>
>
>
>
--
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
[jira] Commented: (MPXDOC-200) [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6
[ http://jira.codehaus.org/browse/MPXDOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87869 ] Shinobu Kawai commented on MPXDOC-200: -- This is due to a jelly bug [1] due to a change in the java6 ClassLoader implementation [2]. [1] https://issues.apache.org/jira/browse/JELLY-274 [2] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6446627 > [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6 > > > Key: MPXDOC-200 > URL: http://jira.codehaus.org/browse/MPXDOC-200 > Project: maven-xdoc-plugin > Issue Type: Bug > Environment: java version "1.6.0-beta2" > Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86) > Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing) > Win 2K > Maven 1.1 RC 1 from Oct 2006 >Reporter: Benoit Xhenseval >Priority: Critical > > Hi > Issue discussed on > http://www.nabble.com/-m1.1-rc1--javadoc-does-not-generate-anything...-tf2220969.html > Here is the log: > xdoc:init: > [echo] Generates the directory structure required for xdocs > xdoc:i18n-validation: > [echo] Validation of the locale entries > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... j:arg > Line.. 666 > Column 70 > [Ljava.lang.Object; > Total time : 1 minutes 9 seconds > Finished at : 12 October 2006 13:54:00 BST > --- > I though that the issue may be related to generics and calling this > invokeStatic on java.util.Arrays > but this seems to work when I try at home with JDK 1.5.08 however, I'm having > trouble with JDK 6-b2 > May be the interface has changed or one cannot use the following jelly code: > var="availableLocales"/> > var="availableLocalesAsList"> > > > I have checked the API for JDK6 and it seems to be the same... > A simple maven site or maven multiproject:site under JDK 6 should confirm the > issue, works fine under 1.5 > Definitely something around this "asList" call... > Benoit -- 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
[jira] Commented: (MPXDOC-200) [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6
[ http://jira.codehaus.org/browse/MPXDOC-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87872 ] Shinobu Kawai commented on MPXDOC-200: -- I applied a workaround to SVN, but looks like I don't have permission to resolve this bug... > [m1.1-RC1 Oct06] maven-xdoc-plugin-1.10.1-SNAPSHOT fails under JDK 6 > > > Key: MPXDOC-200 > URL: http://jira.codehaus.org/browse/MPXDOC-200 > Project: maven-xdoc-plugin > Issue Type: Bug > Environment: java version "1.6.0-beta2" > Java(TM) SE Runtime Environment (build 1.6.0-beta2-b86) > Java HotSpot(TM) Client VM (build 1.6.0-beta2-b86, mixed mode, sharing) > Win 2K > Maven 1.1 RC 1 from Oct 2006 >Reporter: Benoit Xhenseval >Priority: Critical > > Hi > Issue discussed on > http://www.nabble.com/-m1.1-rc1--javadoc-does-not-generate-anything...-tf2220969.html > Here is the log: > xdoc:init: > [echo] Generates the directory structure required for xdocs > xdoc:i18n-validation: > [echo] Validation of the locale entries > BUILD FAILED > File.. file:/C:/Documents and > Settings/xhensevb/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly > Element... j:arg > Line.. 666 > Column 70 > [Ljava.lang.Object; > Total time : 1 minutes 9 seconds > Finished at : 12 October 2006 13:54:00 BST > --- > I though that the issue may be related to generics and calling this > invokeStatic on java.util.Arrays > but this seems to work when I try at home with JDK 1.5.08 however, I'm having > trouble with JDK 6-b2 > May be the interface has changed or one cannot use the following jelly code: > var="availableLocales"/> > var="availableLocalesAsList"> > > > I have checked the API for JDK6 and it seems to be the same... > A simple maven site or maven multiproject:site under JDK 6 should confirm the > issue, works fine under 1.5 > Definitely something around this "asList" call... > Benoit -- 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
[jira] Created: (NMAVEN-5) Support for Adding Compile-time References from the GAC
Support for Adding Compile-time References from the GAC --- Key: NMAVEN-5 URL: http://jira.codehaus.org/browse/NMAVEN-5 Project: NMaven Issue Type: Improvement Environment: Windows, Linux, Mono, Microsoft Reporter: Shane Isbell NMaven currently supports compile-time reference from the local maven repo on the file system: these dependencies are specified within the pom build file. In some circumstances, the artifacts cannot be legally distributed (Microsoft); so I need a way for adding compile-time references from the GAC itself. This improvement does not preclude the ability to import the artifacts from the GAC into the local maven repo, it only extends the types of dependencies that NMaven recognizes. -- 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
[jira] Commented: (MJXR-15) Parameter sourcePaths like it exists in Javadoc plugin added
[ http://jira.codehaus.org/browse/MJXR-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_87891 ] Martin Zeltner commented on MJXR-15: I hope you will include it. I can not imagine any vote against it (full backward compatibility). Yes, it is the equivalent of the "-sourcepath". Jxr is just a report. You will not violate any convention with a report. Cheers, Martin > Parameter sourcePaths like it exists in Javadoc plugin added > > > Key: MJXR-15 > URL: http://jira.codehaus.org/browse/MJXR-15 > Project: Maven 2.x JXR Plugin > Issue Type: Improvement >Affects Versions: 2.1 > Environment: WinXp >Reporter: Martin Zeltner > Attachments: patch_maven-jxr-plugin_parameter-sourcePaths-added.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > I've added the parameter "sourcePaths". If this parameter is set the jxr > plugin will take the java sources from the given paths instead of the root > source path. If it is not set the plugin will work as before. This is very > useful to define own sets of jxr report pages. > Cheers, > Martin -- 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
[jira] Created: (MASSEMBLY-184) components are not interpolated - i.e., ${params} are not substituted
components are not interpolated - i.e., ${params} are not substituted
-
Key: MASSEMBLY-184
URL: http://jira.codehaus.org/browse/MASSEMBLY-184
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2
Environment: all
Reporter: John J. Franey
Attachments: CompInterpol.diff
Components are no more than the extension of an Assembly. As such, they ought
to also be interpolated. Why is there the current restriction that the
${param} will be replaced when it appears in an Assembly, but not if it appears
in a Component?
Without interpolating Components, it will not be possible to refactor a
component out of an assembly if it contains a ${param} to be replaced.
Attached is a diff with the code change and a test case. The change: the call
to merge components into the assembly now appears before assembly's
interpolation in the DefaultAssemblyReader, not after.
Regards,
John
--
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
[jira] Closed: (MNG-2740) maven-core has compile errors under src/test
[ http://jira.codehaus.org/browse/MNG-2740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Franz Allan Valencia See closed MNG-2740. - Resolution: Fixed fixed in -r509077 > maven-core has compile errors under src/test > > > Key: MNG-2740 > URL: http://jira.codehaus.org/browse/MNG-2740 > Project: Maven 2 > Issue Type: Bug > Components: Bootstrap & Build >Affects Versions: 2.1 > Environment: -r492039 >Reporter: Franz Allan Valencia See > > I tried building with both maven-2.0.4 and maven-2.1-SNAPSHOT to no avail > [INFO] [compiler:testCompile] > Compiling 5 source files to > D:\sources\maven\components\maven-core\target\test-classes > [INFO] Error for project: Maven Core (during install) > [INFO] > > [INFO] Compilation failure > D:\sources\maven\components\maven-core\src\test\java\org\apache\maven\plugin\PluginParameterExpressionEvaluatorTest.java:[202,33] > cannot find symbol > symbol : constructor ReactorManager(java.util.List) > location: class org.apache.maven.execution.ReactorManager -- 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
[jira] Created: (SUREFIRE-288) Surefire tries to instantiate nested TestCase classes
Surefire tries to instantiate nested TestCase classes - Key: SUREFIRE-288 URL: http://jira.codehaus.org/browse/SUREFIRE-288 Project: Maven Surefire Issue Type: Bug Components: JUnit 3.x support, Junit 4.x support Affects Versions: 2.0 (2.2 plugin) Environment: Windows XP, Java 1.4.2 Reporter: Stephen Coy If a JUnit TestCase contains any kind of nested class (static or not), Surefire feels obliged to try and instantiate it. This will fail with access violations if the class is not public. Work around seems to be to make the nested class public, but surely Surefire has no business doing this anyway? Here is a sample stack trace: org.apache.maven.surefire.booter.SurefireExecutionException: Unable to instantiate POJO 'class au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent'; nested exception is java.lang.InstantiationException: au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent; nested exception is org.apache.maven.surefire.testset.TestSetFailedException: Unable to instantiate POJO 'class au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent'; nested exception is java.lang.InstantiationException: au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent org.apache.maven.surefire.testset.TestSetFailedException: Unable to instantiate POJO 'class au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent'; nested exception is java.lang.InstantiationException: au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent java.lang.InstantiationException: au.com.optus.eFulfilment.sap.test.moduleTest.TestSapOrderComponent$MySapOrderComponent at java.lang.Class.newInstance0(Class.java:293) at java.lang.Class.newInstance(Class.java:261) at org.apache.maven.surefire.testset.PojoTestSet.(PojoTestSet.java:52) at org.apache.maven.surefire.junit.JUnitDirectoryTestSuite.createTestSet(JUnitDirectoryTestSuite.java:61) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(AbstractDirectoryTestSuite.java:93) at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(Surefire.java:147) at org.apache.maven.surefire.Surefire.run(Surefire.java:108) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225) at org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:747) -- 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
[jira] Created: (MNG-2833) XMLSchema 1.2 has invalid md5 and sha1 files in Maven2 repository
XMLSchema 1.2 has invalid md5 and sha1 files in Maven2 repository - Key: MNG-2833 URL: http://jira.codehaus.org/browse/MNG-2833 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Affects Versions: 2.0.5 Reporter: Thomas Hallgren Priority: Critical The XmlSchema-1.2.jar as published in http://repo1.maven.org/maven2/org/apache/ws/commons/schema/XmlSchema/1.2/ has invalid md5 and sha1 files . Looking at dates it seems it's been replaced some 9 days after the md5 and sha1 was uploaded. The same file comes with correct md5 and sha1 in the maven 1 repo. -- 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
[jira] Moved: (MEV-500) XMLSchema 1.2 has invalid md5 and sha1 files in Maven2 repository
[ http://jira.codehaus.org/browse/MEV-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez moved MNG-2833 to MEV-500: - Priority: (was: Critical) Affects Version/s: (was: 2.0.5) Component/s: (was: Artifacts and Repositories) Invalid POM Complexity: (was: Intermediate) Workflow: jira (was: Maven New) Key: MEV-500 (was: MNG-2833) Project: Maven Evangelism (was: Maven 2) > XMLSchema 1.2 has invalid md5 and sha1 files in Maven2 repository > - > > Key: MEV-500 > URL: http://jira.codehaus.org/browse/MEV-500 > Project: Maven Evangelism > Issue Type: Bug > Components: Invalid POM >Reporter: Thomas Hallgren > > The XmlSchema-1.2.jar as published in > http://repo1.maven.org/maven2/org/apache/ws/commons/schema/XmlSchema/1.2/ has > invalid md5 and sha1 files . Looking at dates it seems it's been replaced > some 9 days after the md5 and sha1 was uploaded. > The same file comes with correct md5 and sha1 in the maven 1 repo. -- 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
