[jira] Commented: (MPMD-86) Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK 1.5 mode!
[ http://jira.codehaus.org/browse/MPMD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224054#action_224054 ] Bram commented on MPMD-86: -- Same here, I've configured the PMD plugin with: org.apache.maven.plugins maven-pmd-plugin 1.6 /rulesets/basic.xml /rulesets/controversial.xml xml true utf-8 100 And my source builds towards JDK 1.6: org.apache.maven.plugins maven-compiler-plugin 1.6 1.6 With that, I get a lot of warnings on non-1.4 issues like annotations and generics. After configuring the following project property, these warnings disappeared: ... 1.6 > Using JDK 1.5 causes ParseException: Can't use generics unless running in JDK > 1.5 mode! > --- > > Key: MPMD-86 > URL: http://jira.codehaus.org/browse/MPMD-86 > Project: Maven 2.x PMD Plugin > Issue Type: Bug > Components: PMD >Affects Versions: 2.4 > Environment: JAVA 1.5, Maven 2.0.9 >Reporter: Debabrat Panda >Assignee: Benjamin Bentmann > > While running PMD with Maven i am getting parsing error "Error while parsing > ../../../java file" > The errors are > 1. Can't use generics unless running in JDK 1.5 mode! > 2. Can't use static imports when running in JDK 1.4 mode! > Can't use annotations when running in JDK 1.4 mode! > Any help will be appreciated. > Thanks in advance. -- 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: (DOXIA-394) Transitive dependency to old commons-logging through HttpClient causes problems
[ http://jira.codehaus.org/browse/DOXIA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224055#action_224055 ] Lukas Theussl commented on DOXIA-394: - This patch makes the fml module test fail. > Transitive dependency to old commons-logging through HttpClient causes > problems > --- > > Key: DOXIA-394 > URL: http://jira.codehaus.org/browse/DOXIA-394 > Project: Maven Doxia > Issue Type: Bug > Components: Maven plugin >Affects Versions: 1.1.3 >Reporter: isabel drost > Attachments: DOXIA-394.diff > > > The issue (and resulting trouble) is described in more detail over in the > MSITE issue tracker: http://jira.codehaus.org/browse/MSITE-459 > Excluding the dependency entirely solved the problem for me. See attached > diff for the changes I made. -- 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-4700) Incorrect path to global-level plugin registry is formed when maven is started from UNC location
[ http://jira.codehaus.org/browse/MNG-4700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4700. -- Resolution: Won't Fix Assignee: Benjamin Bentmann The plugin registry is obsolete and no longer used. > Incorrect path to global-level plugin registry is formed when maven is > started from UNC location > > > Key: MNG-4700 > URL: http://jira.codehaus.org/browse/MNG-4700 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 2.2.1 >Reporter: DK >Assignee: Benjamin Bentmann > > Maven is located on \\server\share\... (UNC Path). > Path to global-level plugin registry is formed incorrectly for UNC path. It > is converted to absolute path by using current drive letter. > D:\test>\\server\share\tmp\maven\2.2\bin\mvn -V -X -Pproduction > + Error stacktraces are turned on. > Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.5.0_07 > Java home: \\server\share\j2sdk\1.5.0\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and > Settings\test\.m2\plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > 'D:\server\share\tmp\maven\2.2\conf\plugin-registry.xml' > [INFO] Scanning for projects... -- 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: (MPIR-194) [WARNING] Deprecated API called
[
http://jira.codehaus.org/browse/MPIR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224064#action_224064
]
Ståle Tomten commented on MPIR-194:
---
I also got an error after the warning.
{code}
04-Jun-2010 09:21:39[WARNING] Deprecated API called - not
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please
update this plugin.
04-Jun-2010 09:21:40[INFO] Generating "Project Summary" report.
04-Jun-2010 09:21:40[WARNING] Deprecated API called - not
org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please
update this plugin.
04-Jun-2010 09:21:40[INFO]
04-Jun-2010 09:21:40[ERROR] FATAL ERROR
04-Jun-2010 09:21:40[INFO]
04-Jun-2010 09:21:40[INFO] 1
04-Jun-2010 09:21:40[INFO]
04-Jun-2010 09:21:40[INFO] Trace
04-Jun-2010 09:21:40java.lang.ArrayIndexOutOfBoundsException: 1
04-Jun-2010 09:21:40at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableCell(XhtmlSink.java:791)
04-Jun-2010 09:21:40at
org.apache.maven.doxia.module.xhtml.XhtmlSink.tableHeaderCell(XhtmlSink.java:777)
04-Jun-2010 09:21:40at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeaderCell(AbstractMavenReportRenderer.java:267)
04-Jun-2010 09:21:40at
org.apache.maven.reporting.AbstractMavenReportRenderer.tableHeader(AbstractMavenReportRenderer.java:356)
04-Jun-2010 09:21:40at
org.apache.maven.report.projectinfo.ProjectSummaryReport$ProjectSummaryRenderer.renderBody(ProjectSummaryReport.java:107)
04-Jun-2010 09:21:40at
org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:79)
04-Jun-2010 09:21:40at
org.apache.maven.report.projectinfo.ProjectSummaryReport.executeReport(ProjectSummaryReport.java:49)
04-Jun-2010 09:21:40at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:190)
04-Jun-2010 09:21:40at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:144)
04-Jun-2010 09:21:40at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
04-Jun-2010 09:21:40at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
04-Jun-2010 09:21:40at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
04-Jun-2010 09:21:40at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
04-Jun-2010 09:21:40at
org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100)
04-Jun-2010 09:21:40at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
04-Jun-2010 09:21:40at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
04-Jun-2010 09:21:40at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
04-Jun-2010 09:21:40at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
04-Jun-2010 09:21:40at
org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
04-Jun-2010 09:21:40at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
04-Jun-2010 09:21:40at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
04-Jun-2010 09:21:40at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
04-Jun-2010 09:21:40at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
04-Jun-2010 09:21:40at
java.lang.reflect.Method.invoke(Method.java:585)
04-Jun-2010 09:21:40at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
04-Jun-2010 09:21:40at
org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
04-Jun-2010 09:21:40at
org.codeha
[jira] Commented: (MPIR-194) [WARNING] Deprecated API called
[
http://jira.codehaus.org/browse/MPIR-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224069#action_224069
]
Lukas Theussl commented on MPIR-194:
You have to use site-plugin-2.1, see eg
http://www.mail-archive.com/us...@maven.apache.org/msg109240.html
> [WARNING] Deprecated API called
> ---
>
> Key: MPIR-194
> URL: http://jira.codehaus.org/browse/MPIR-194
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Lukas Theussl
>Priority: Minor
>
> Version 2.2 spits out a warning for each generated page:
> {noformat}
> [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink
> instance and no SinkFactory available. Please update this plugin.
> {noformat}
> The warning can be ignored AFAICT but it is annoying and confusing for users.
--
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: (MSITE-456) [regression] Site navigation not generated
[ http://jira.codehaus.org/browse/MSITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224078#action_224078 ] Grzegorz Slowikowski commented on MSITE-456: It does not work for me with site 2.1.1 (from https://repository.apache.org/content/repositories/maven-025) > [regression] Site navigation not generated > -- > > Key: MSITE-456 > URL: http://jira.codehaus.org/browse/MSITE-456 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) > Java version: 1.6.0_16 > Java home: d:\jdk1.6.0_16\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Paul Benedict >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.1.1, 3.0-alpha-1 > > Attachments: MSITE-456.zip > > > My corporate POM locks down the maven-site-plugin to version 2.1. The site of > the corporate POM generates just fine. However, when a child project inherits > from it, that project's site contains no left-hand navigation. Reverting to > 2.0.1 is my workaround. -- 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: (MSITE-456) [regression] Site navigation not generated
[ http://jira.codehaus.org/browse/MSITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224079#action_224079 ] Lukas Theussl commented on MSITE-456: - Your link does not exist and "it does not work" is hard to diagnose. Please give us a chance and be more specific. > [regression] Site navigation not generated > -- > > Key: MSITE-456 > URL: http://jira.codehaus.org/browse/MSITE-456 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) > Java version: 1.6.0_16 > Java home: d:\jdk1.6.0_16\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Paul Benedict >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.1.1, 3.0-alpha-1 > > Attachments: MSITE-456.zip > > > My corporate POM locks down the maven-site-plugin to version 2.1. The site of > the corporate POM generates just fine. However, when a child project inherits > from it, that project's site contains no left-hand navigation. Reverting to > 2.0.1 is my workaround. -- 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-4701) Problems with my repository and junit
Problems with my repository and junit - Key: MNG-4701 URL: http://jira.codehaus.org/browse/MNG-4701 Project: Maven 2 & 3 Issue Type: Bug Components: Artifacts and Repositories, Integration Tests Affects Versions: 2.2.1 Environment: Windows, JVM 1.6_16 Reporter: Ramon Medel Hi, i have a Archiva repository with my own junit library (with another groupid and versionid). When i set this library to test my jpa-spring application, Test don't work, but if i put junit (groupid=junit and version 4.4) library from central repository, tests work. -- 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-4701) Problems with my repository and junit
[ http://jira.codehaus.org/browse/MNG-4701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4701. -- Resolution: Incomplete Assignee: Benjamin Bentmann There isn't sufficient information to anaylze/reproduce the issue. Besides, this doesn't sound like a Maven core bug but more like a configuration issue (e.g. you may need to set the [junitArtifactName|http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#junitArtifactName]), so I suggest you try the [Maven User List|http://maven.apache.org/mail-lists.html] first. > Problems with my repository and junit > - > > Key: MNG-4701 > URL: http://jira.codehaus.org/browse/MNG-4701 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories, Integration Tests >Affects Versions: 2.2.1 > Environment: Windows, JVM 1.6_16 >Reporter: Ramon Medel >Assignee: Benjamin Bentmann > > Hi, i have a Archiva repository with my own junit library (with another > groupid and versionid). When i set this library to test my jpa-spring > application, Test don't work, but if i put junit (groupid=junit and version > 4.4) library from central repository, tests work. -- 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: (MPH-78) effective-pom creates invalid xml because it outputs the Resource.mergeId
effective-pom creates invalid xml because it outputs the Resource.mergeId
-
Key: MPH-78
URL: http://jira.codehaus.org/browse/MPH-78
Project: Maven 2.x Help Plugin
Issue Type: Bug
Affects Versions: 2.1.1
Reporter: Jacob Robertson
Priority: Minor
My organization would like to use the output from the effective-pom goal as
part of the deployed meta data in an ear. This is useful for some of our
scripting that needs properties and dependencyManagement versions resolved
(i.e. from parent poms), and the pom that is currently put in the ear does not
have that information. However, once we start generating the effective-pom.xml
file, any tool that uses xml validation will notice that the mergeId tag is
invalid. This is especially annoying in eclipse, as it marks the whole project
as having an error due to the effective-pom.xml file being in the target
directory under the eclipse project. We can of course turn the xml validation
off for the eclipse project or folder, but this is one additional step to ask a
multitude of developers to take in configuring their projects.
I notice that the EffectivePomMojo class has a "cleanModel" method that appears
to sort the properties. Just to play with this, I added a "cleanResources"
method that calls Resource.setMergeId(null). This technique does in fact work
as I hoped for outputting the xml without the mergeId, but it requires
upgrading this plugin to use at least Maven 2.0.10.
{code}
private static void cleanModel( Model pom )
{
Properties properties = new SortedProperties();
properties.putAll( pom.getProperties() );
pom.setProperties( properties );
cleanResources( pom.getBuild().getResources() );
cleanResources( pom.getBuild().getTestResources() );
}
private static void cleanResources( List resources )
{
for ( Iterator i = resources.iterator(); i.hasNext(); )
{
Resource resource = (Resource) i.next();
resource.setMergeId( null );
}
}
{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
[jira] Created: (MSHADE-81) Poor error reporting
Poor error reporting Key: MSHADE-81 URL: http://jira.codehaus.org/browse/MSHADE-81 Project: Maven 2.x Shade Plugin Issue Type: Bug Reporter: Pete Muir When using XmlAppendingTransformer, I get this (fairly useless) error message: on line 1: Premature end of file. -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) 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:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) ... 19 more Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) at org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) at org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) ... 21 more Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end of file. at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) at org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) ... 24 more Caused by: org.xml.sax.SAXParseException: Premature end of file. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737)
[jira] Commented: (MSHADE-81) Poor error reporting
[ http://jira.codehaus.org/browse/MSHADE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224117#action_224117 ] Pete Muir commented on MSHADE-81: - Actually, printing out resource is a good first step, but not enough, we need the name of the inputstream being worked on :-( > Poor error reporting > > > Key: MSHADE-81 > URL: http://jira.codehaus.org/browse/MSHADE-81 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Reporter: Pete Muir > > When using XmlAppendingTransformer, I get this (fairly useless) error message: > on line 1: Premature end of file. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on > project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: > Error on line 1: Premature end of file. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) > 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:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating > shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end > of file. > at > org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) > ... 19 more > Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: > Error on line 1: Premature end of file. > at > org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) > at > org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) > at > org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) > at > org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) > ... 21 more > Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end > of file. > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) > at > org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) > ... 24 more > Caused by: org.xml.sax.SAXParseException: Premature end of file. > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) > at > com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) > at > com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) > at > com.sun.org.a
[jira] Commented: (MSHADE-81) Poor error reporting
[ http://jira.codehaus.org/browse/MSHADE-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224119#action_224119 ] Pete Muir commented on MSHADE-81: - Without changing the API best bet looks like adding some logging for each file that is transformed around DefaultShader:150 > Poor error reporting > > > Key: MSHADE-81 > URL: http://jira.codehaus.org/browse/MSHADE-81 > Project: Maven 2.x Shade Plugin > Issue Type: Bug >Reporter: Pete Muir > > When using XmlAppendingTransformer, I get this (fairly useless) error message: > on line 1: Premature end of file. -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-shade-plugin:1.3.3:shade (uber-jar) on > project seam: Error creating shaded jar: org.jdom.input.JDOMParseException: > Error on line 1: Premature end of file. > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:124) > 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:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at > org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating > shaded jar: org.jdom.input.JDOMParseException: Error on line 1: Premature end > of file. > at > org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:489) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133) > ... 19 more > Caused by: java.lang.RuntimeException: org.jdom.input.JDOMParseException: > Error on line 1: Premature end of file. > at > org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:89) > at > org.apache.maven.plugins.shade.DefaultShader.resourceTransformed(DefaultShader.java:305) > at > org.apache.maven.plugins.shade.DefaultShader.shade(DefaultShader.java:150) > at > org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:430) > ... 21 more > Caused by: org.jdom.input.JDOMParseException: Error on line 1: Premature end > of file. > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:504) > at org.jdom.input.SAXBuilder.build(SAXBuilder.java:807) > at > org.apache.maven.plugins.shade.resource.XmlAppendingTransformer.processResource(XmlAppendingTransformer.java:85) > ... 24 more > Caused by: org.xml.sax.SAXParseException: Premature end of file. > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:195) > at > com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:174) > at > com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:388) > at > com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1414) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:1059) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:648) > at > com.sun.org.apa
[jira] Commented: (MSITE-456) [regression] Site navigation not generated
[ http://jira.codehaus.org/browse/MSITE-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224118#action_224118 ] Grzegorz Slowikowski commented on MSITE-456: I need some time to prepare simple example project. I checked Paul's attachment and I see that my problem is different - site navigation is not generated for child modules of multimodule build. I will create another JIRA error for it when I'll be ready with example project. > [regression] Site navigation not generated > -- > > Key: MSITE-456 > URL: http://jira.codehaus.org/browse/MSITE-456 > Project: Maven 2.x Site Plugin > Issue Type: Bug >Affects Versions: 2.1 > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) > Java version: 1.6.0_16 > Java home: d:\jdk1.6.0_16\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Paul Benedict >Assignee: Dennis Lundberg >Priority: Critical > Fix For: 2.1.1, 3.0-alpha-1 > > Attachments: MSITE-456.zip > > > My corporate POM locks down the maven-site-plugin to version 2.1. The site of > the corporate POM generates just fine. However, when a child project inherits > from it, that project's site contains no left-hand navigation. Reverting to > 2.0.1 is my workaround. -- 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] Updated: (MPDF-29) Improve figure scaling
[
http://jira.codehaus.org/browse/MPDF-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MPDF-29:
--
Fix Version/s: 1.2
> Improve figure scaling
> --
>
> Key: MPDF-29
> URL: http://jira.codehaus.org/browse/MPDF-29
> Project: Maven 2.x PDF Plugin
> Issue Type: Improvement
>Affects Versions: 1.0
>Reporter: Lukas Theussl
> Fix For: 1.2
>
>
> From a private mail:
> Today, I found an extremely useful tip for how to get the images/graphics
> "right" both in HTML and PDF. As you know and write in the FAQ, there is a
> challenge with scaling the images, especially when using APT.
> I think it would be useful for others, if you could publish this tip on the
> site for the plugin.
> What I did was this:
> I made a copy of the original fo-styles.xslt, names it pdf-config.xml in my
> src/site/resources.
> Then I replaced the following section:
> {code:xml}
>
> auto
> auto
> auto
> auto
>
> {code}
> with this:
> {code:xml}
>
> scale-down-to-fit
> scale-down-to-fit
> 100%
> 100%
>
> {code}
>
> And VOILA, the scaling was perfect!
--
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] Updated: (MPDF-32) PDF generation fails due to velocity template error
[ http://jira.codehaus.org/browse/MPDF-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MPDF-32: -- Fix Version/s: 1.2 > PDF generation fails due to velocity template error > --- > > Key: MPDF-32 > URL: http://jira.codehaus.org/browse/MPDF-32 > Project: Maven 2.x PDF Plugin > Issue Type: Bug >Affects Versions: 1.1 > Environment: Maven 2.0.10 JDK6, XP SP3 >Reporter: Michael Osipov > Fix For: 1.2 > > Attachments: pdf.log > > > I was trying to run mvn pdf:pdf and it suddenly failed. See attached log. The > failing template works flawlessly with the site goal. -- 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-622) The TestNG command line option '-testrunfactory' should be supported.
The TestNG command line option '-testrunfactory' should be supported.
-
Key: SUREFIRE-622
URL: http://jira.codehaus.org/browse/SUREFIRE-622
Project: Maven Surefire
Issue Type: Improvement
Components: TestNG support
Reporter: Orien Madgwick
Attachments: surefire_add_testng_testrunfactory_property_support.patch
Version 5.9 of TestNG added the {{-testrunfactory}} command line option for
registering a custom test runner factory. The Maven Surefire Plugin should
support this option.
Ideally, one should be able to specify the option in the Surefire configuration
of their project's pom.xml file.
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
testrunfactory
org.example.CustomTestRunnerFactory
{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
[jira] Commented: (MNG-2553) Maven Local Settings Model should allow configuration of distributions (distributionManagement)
[ http://jira.codehaus.org/browse/MNG-2553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224216#action_224216 ] Tom Eugelink commented on MNG-2553: --- It is interesting indeed to see it was marked "Won't fix"; I was just looking for exactly this. If I can configure in settings.xml a single repository to get stuff from, why can't I configure a single repository to put stuff in? > Maven Local Settings Model should allow configuration of distributions > (distributionManagement) > --- > > Key: MNG-2553 > URL: http://jira.codehaus.org/browse/MNG-2553 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Settings >Affects Versions: 2.0.4 >Reporter: Jimisola Laursen > > There is a good use case where this would be very useful. > E.g. I develop a plugin in mojo-sandbox and want to test it in an environment > other than the one that I developed it on (e.g. a computer at work). I check > out the plugin to this, build and then want to deploy to another repository > (e..g a company's internal repository). I don't want to fiddle with the > pom.xml of the plugin, just refer to a profile in settings.xml. -- 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
