[jira] Reopened: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[
http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christian Moser reopened SUREFIRE-711:
--
Thanks for the fast fix!
Unfortunately, the leak seems still not fixed in 2.8-SNAPSHOT.
I still got:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryErr
or---
constituent[0]: file:/D:/MNet/Tools/maven/lib/aether-api-1.8.jarException in thr
ead "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
I verified that the class JUnit4Provider in surefire-provider:2.8-SNAPSHOT
contains the following lines:
public Iterator getSuites()
{
this.testsToRun = scanClassPath();
this.reporterFactory.close();
return this.testsToRun.iterator();
}
Perhaps, there's another leak.
> OutOfMemoryError while building multi module projects
> -
>
> Key: SUREFIRE-711
> URL: http://jira.codehaus.org/browse/SUREFIRE-711
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.7.2
> Environment: Win 7 32bit
>Reporter: Christian Moser
>Assignee: Kristian Rosenvold
>Priority: Critical
> Fix For: 2.8
>
> Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG
>
>
> We're getting out of memory errors since we've updated to surefire 2.7.2 from
> 2.6.
> Please check the attached jvisualvm pics they show the same build execution
> with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be
> interesting.
> it seems like 2.7.2 is not unloading classes after processing.
> We found out that if we skip tests with -DskipTests=true, the exception won't
> occur.
> The build consists of several multi module projects.
>
> ..\..\BaseSys\trunk (multimodule)
> ..\..\MagIC\trunk (multimodule)
> ..\..\StabNet\trunk (multimodule)
> ..\..\tiamo\trunk (multimodule)
> ..\..\TiBase\trunk (multimodule)
> ..\..\VIVA\trunk (multimodule)
>
>
> [ERROR] Java heap space -> [Help 1]---Exception in
> thread "main" jav
> lang.OutOfMemoryError: Java heap space
> at java.util.Arrays.copyOf(Arrays.java:2786)
> at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
> at java.io.PrintStream.write(PrintStream.java:430)
> at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44)
> at java.io.PrintStream.write(PrintStream.java:430)
> at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
> at java.io.PrintStream.write(PrintStream.jav
[jira] Updated: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Moser updated SUREFIRE-711: - Attachment: surefire2-8-SNAPSHOT.JPG jvisualvm output with fixed version > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG, > surefire2-8-SNAPSHOT.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- 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] Issue Comment Edited: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[
http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258500#action_258500
]
Christian Moser edited comment on SUREFIRE-711 at 3/4/11 2:42 AM:
--
Thanks for the fast fix!
Unfortunately, the leak seems still not fixed in 2.8-SNAPSHOT.
I still got:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryErr
or---
constituent[0]: file:/D:/MNet/Tools/maven/lib/aether-api-1.8.jarException in thr
ead "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
I verified that the class JUnit4Provider in surefire-provider:2.8-SNAPSHOT in
my local repository contains the following lines:
public Iterator getSuites()
{
this.testsToRun = scanClassPath();
this.reporterFactory.close();
return this.testsToRun.iterator();
}
Perhaps, there's another leak.
was (Author: onmomo):
Thanks for the fast fix!
Unfortunately, the leak seems still not fixed in 2.8-SNAPSHOT.
I still got:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/OutOfMemoryErr
or---
constituent[0]: file:/D:/MNet/Tools/maven/lib/aether-api-1.8.jarException in thr
ead "main" java.lang.OutOfMemoryError: Java heap space
at java.util.Arrays.copyOf(Arrays.java:2786)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42)
at java.io.PrintStream.write(PrintStream.java:430)
at org.apac
[jira] Commented: (MJAVADOC-304) failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta
[
http://jira.codehaus.org/browse/MJAVADOC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258509#action_258509
]
Felix Simmendinger commented on MJAVADOC-304:
-
This bug is very nasty since you have to configure your release plugin to use
preparationGoals "clean install" otherwise thirdparty javadoc references will
fail the build as those dependencies aren't present in the classpath of javadoc.
> failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta
>
>
> Key: MJAVADOC-304
> URL: http://jira.codehaus.org/browse/MJAVADOC-304
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.7
>Reporter: Sebastian Annies
> Attachments: MJAVADOC-304_IT_Test.patch, MJAVADOC-304_Patch.patch
>
>
> {{failOnError}} works for the case that javadoc:jar is executed. This
> invocation calls {{execute()}} and then {{generate(sink, locale)}}. The
> generate is surrounded with a try/catch-block catching any exception thrown
> by the javadoc generation. In case of {{failOnError==false}} the exception
> does not interrupt the build. That perfectly ok!
> {{failOnError}} does not work if it is called during site generation. During
> site generation only {{generate(sink, locale}} is called which misses the
> try/catch guard for failures during generation of javadoc.
> Effectively you cannot ignore failures during site generation.
--
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: (MSITE-524) Duplicate registration of doxia-module-docbook-simplifed
[
http://jira.codehaus.org/browse/MSITE-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-524:
Component/s: Maven 3
> Duplicate registration of doxia-module-docbook-simplifed
>
>
> Key: MSITE-524
> URL: http://jira.codehaus.org/browse/MSITE-524
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: Maven 3
>Affects Versions: 3.0-beta-3
> Environment: Apache Maven 3.0 (r1004208; 2010-10-04 13:50:56+0200)
> Java version: 1.6.0_21
> Java home: D:\java\jdk\jre
> Default locale: cs_CZ, platform encoding: Cp1250
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>Reporter: Petr Prochazka
>Priority: Blocker
> Attachments: maven-site.zip, site-debug.log, site.log
>
>
> I have project site with page written in simplified docbook and I obtain
> exception:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on
> project mave
> n-site-error: Error during page generation: Files 'docbook\index.xml' clashes
> with existing 'D:\Projects-test\maven-site
> \src\site\docbook\index.xml'. -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-site-plugi
> n:3.0-beta-3:site (default-site) on project maven-site-error: Error during
> page generation
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:203)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:314)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:445)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:168)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:132)
> 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 during page
> generation
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:127)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195)
> ... 19 more
> Caused by: org.apache.maven.doxia.siterenderer.RendererException: Files
> 'docbook\index.xml' clashes with existing 'D:\Pr
> ojects-test\maven-site\src\site\docbook\index.xml'.
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.addModuleFiles(DefaultSiteRenderer.java:259)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.locateDocumentFiles(DefaultSiteRenderer.java:168)
> at
> org.apache.maven.plugins.site.AbstractSiteRenderingMojo.locateDocuments(AbstractSiteRenderingMojo.java:411)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:148)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:122)
> ... 21 more{noformat}
> I use this setting of plugin:
> {noformat}
> maven-site-plugin
> 3.0-beta-3
>
>
> org.apache.maven.doxia
> doxia-module-docbook-simple
> 1.1.3
>
>
> {noformat}
> Does anyone have any idea?
> Thanks
> Petr
> Test maven project and full log is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectl
[jira] Updated: (MSITE-472) Navigation links from maven-project-info-reports disappear when using maven-site-plugin 3.0-beta-1-SNAPSHOT and POM references parent POM
[ http://jira.codehaus.org/browse/MSITE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-472: Component/s: Maven 3 > Navigation links from maven-project-info-reports disappear when using > maven-site-plugin 3.0-beta-1-SNAPSHOT and POM references parent POM > - > > Key: MSITE-472 > URL: http://jira.codehaus.org/browse/MSITE-472 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: Maven 3, multi module >Affects Versions: 3.0-beta-1 > Environment: Maven 3.0-alpha-7, JDK 6 >Reporter: Michael Pilquist > Attachments: site-parent-issue.zip > > > If a project has a parent POM, no navigation links are generated in the > submodule's site. The parent site has navigation however. This behavior > occurs both when parent is in the reactor and when it is not. > Attached is a very simple multimodule build consisting of a single parent POM > and a JAR module. After running "mvn clean install site", observe that > target/site/index.html has the proper navigation but > parent-usage-test/target/site/index.html has an empty navigation panel. > This may be a bug in project-info-reports but since it works correctly when > there's no parent POM, I thought this was the correct project. -- 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: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
http://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl updated MSITE-484:
Component/s: Maven 3
> Support adding and overriding report plugins in new maven-site-plugin 3.x
> reportPlugins configuration format
>
>
> Key: MSITE-484
> URL: http://jira.codehaus.org/browse/MSITE-484
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: inheritance, Maven 3
>Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
> Environment: 3.0-beta-1-SNAPSHOT
>Reporter: Michael Pilquist
>Assignee: Olivier Lamy
> Fix For: 3.0-beta-4
>
> Attachments: site-cfg-inheritance.zip
>
>
> When using the new configuration format for reportPlugins, it appears that
> there's no way to:
> - Add a report plugin to a submodule
> - Override the configuration of a report plugin in a submodule
> Using the old section, both of these use cases were supported.
> For large, multi-module builds, it is problematic having to respecify all
> reporting plugins in any submodule pom that needs to either add an additional
> reporting plugin or change the configuration of a reporting plugin.
> Attached is a sample project that has a parent POM configured with
> project-info-reports and javadoc plugin and a submodule configured with jxr
> plugin and javadoc plugin. The relevant output is here:
> {code}
> [INFO]
>
> [INFO] Building parent 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
> [INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
> (included: [**], excluded: [])
> [INFO]
> [INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
> ---
> [INFO] configuring reportPlugin
> org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
> [INFO] configuring reportPlugin
> org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
> ...
> [INFO]
>
> [INFO] Building parent-usage-test 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
> ---
> [INFO]
> [INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @
> parent-usage-test ---
> [INFO] configuring reportPlugin org.apache.maven.plugins:maven-jxr-plugin:2.1
> [INFO] configuring reportPlugin
> org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
> {code}
> Looking at the maven-site-plugin code, it appears the the reportPlugins
> parameter is just a regular array parameter. AFAIK, there's no way to merge
> list configuration items. Other plugins have worked around this by defining
> additional mojo parameters (e.g., maven-eclipse-plugin and buildCommands /
> additionalBuildCommands --
> http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
> This isn't the most flexible option though as it only solves 1 level
> inheritance.
--
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: (MSITE-560) make maven-site-plugin 3.x work both with Maven 2.2 and Maven 3.x
[ http://jira.codehaus.org/browse/MSITE-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl updated MSITE-560: Component/s: Maven 3 > make maven-site-plugin 3.x work both with Maven 2.2 and Maven 3.x > - > > Key: MSITE-560 > URL: http://jira.codehaus.org/browse/MSITE-560 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Improvement > Components: Maven 3 >Affects Versions: 3.0-beta-3 >Reporter: Herve Boutemy > > maintaining 2 branches in parallel is not easy, and mojo and reporting code > is exactly the same: there are not so much differences -- 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-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds
[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258513#action_258513 ] Stevo Slavic commented on MNG-4583: --- Are there any means to configure Maven not to print this warning? In my case a multi-module project uses activated profile only in a single module. If this is not supported, maybe support could be added, e.g. to allow one to specify profile names for which this warning should not be printed. > warning printed when a pom does not use an activated profile is poorly worded > and also should not be printed for multi-module builds > > > Key: MNG-4583 > URL: http://jira.codehaus.org/browse/MNG-4583 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.11, 2.2.1, 3.0-alpha-6 >Reporter: Ian Springer >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 3.0-alpha-6 > > Attachments: MNG-4583.zip > > > This is a followup to http://jira.codehaus.org/browse/MNG-3641. Refer to that > issue for the background. > The current warning message is: > "Profile with id: '" + explicitProfileId + "' has not been activated." > I think this message is misleading, because the profile actually is activated > - it's just not used at all in the pom being processed. I suggest changing > the message to something like: > "Profile with id '" + explicitProfileId + "' is activated, but this pom does > not contain any usages of the profile." > Also, I don't think it makes sense to print this warning at all in a > multi-module build. In the large multi-module project I work on, we have a > number of profiles that are only used in a handful of the 50 or so modules. -- 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: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-711. --- Resolution: Fixed Take 2 is out in r1077870, updated 2.8-SNAPSHOT deployed. The *interesting* thing about your error report is that it basically describes 2 different problems. One is that you're describing a possible difference between 2.6 and 2.7.X in terms of classloading and unloading within the actual surefire plugin performin directory scanning. The *other* issue is the stacktrace you're including, where the recursive TeeStream invocation shows another (different) incarnation of SUREFIRE-495, this time not between the individual tests classes of a single surefire run but between the modules in the reactor. This leak should be much smaller than SUREFIRE-495, but may still be fairly large - especially for a large reactor like yours. I suspect it's the second of the two that's causing the misery here, and this is the issue I have fixed now. I am closing this issue as fixed again, feel free to reopen if necessary. And if you don't mind, please see if the class-loading/unloading difference between 2.6->2.8-SNAPSHOT is still present and upload the nice graphs, even it if doesn't cause your build to fail. > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG, > surefire2-8-SNAPSHOT.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.writ
[jira] Commented: (MNG-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds
[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258516#action_258516 ] Benjamin Bentmann commented on MNG-4583: The warning is supposed to only show up when not a single project within the reactor was affected by the profile. So consider to provide an example project to prove otherwise. > warning printed when a pom does not use an activated profile is poorly worded > and also should not be printed for multi-module builds > > > Key: MNG-4583 > URL: http://jira.codehaus.org/browse/MNG-4583 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.11, 2.2.1, 3.0-alpha-6 >Reporter: Ian Springer >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 3.0-alpha-6 > > Attachments: MNG-4583.zip > > > This is a followup to http://jira.codehaus.org/browse/MNG-3641. Refer to that > issue for the background. > The current warning message is: > "Profile with id: '" + explicitProfileId + "' has not been activated." > I think this message is misleading, because the profile actually is activated > - it's just not used at all in the pom being processed. I suggest changing > the message to something like: > "Profile with id '" + explicitProfileId + "' is activated, but this pom does > not contain any usages of the profile." > Also, I don't think it makes sense to print this warning at all in a > multi-module build. In the large multi-module project I work on, we have a > number of profiles that are only used in a handful of the 50 or so modules. -- 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-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds
[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258517#action_258517 ] Stevo Slavic commented on MNG-4583: --- It seems this is m2eclipse issue - checked, it doesn't get printed in CLI, only in eclipse for incremental builds. > warning printed when a pom does not use an activated profile is poorly worded > and also should not be printed for multi-module builds > > > Key: MNG-4583 > URL: http://jira.codehaus.org/browse/MNG-4583 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Profiles >Affects Versions: 2.0.11, 2.2.1, 3.0-alpha-6 >Reporter: Ian Springer >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 3.0-alpha-6 > > Attachments: MNG-4583.zip > > > This is a followup to http://jira.codehaus.org/browse/MNG-3641. Refer to that > issue for the background. > The current warning message is: > "Profile with id: '" + explicitProfileId + "' has not been activated." > I think this message is misleading, because the profile actually is activated > - it's just not used at all in the pom being processed. I suggest changing > the message to something like: > "Profile with id '" + explicitProfileId + "' is activated, but this pom does > not contain any usages of the profile." > Also, I don't think it makes sense to print this warning at all in a > multi-module build. In the large multi-module project I work on, we have a > number of profiles that are only used in a handful of the 50 or so modules. -- 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: (MSITE-527) Issue warning if run from Maven 3
[ http://jira.codehaus.org/browse/MSITE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-527. --- Resolution: Fixed Fix Version/s: 2.3 Assignee: Lukas Theussl Done in [r1077894|http://svn.apache.org/viewvc?rev=1077894&view=rev] > Issue warning if run from Maven 3 > - > > Key: MSITE-527 > URL: http://jira.codehaus.org/browse/MSITE-527 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Jesse Glick >Assignee: Lukas Theussl >Priority: Minor > Fix For: 2.3 > > > The 2.x plugin should issue a warning linking to e.g. > http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html if > you attempt to run it from Maven 3.x. -- 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: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Moser updated SUREFIRE-711: - Attachment: surefire2-8-SNAPSHOT-fix2.JPG Second fix did the trick. Surefire 2.8-SNAPSHOT does even unload more classes than 2.6. Thanks and good job! > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG, > surefire2-8-SNAPSHOT-fix2.JPG, surefire2-8-SNAPSHOT.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- 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: (MSITE-357) staging should execute some phase of the lifecycle
[ http://jira.codehaus.org/browse/MSITE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed MSITE-357. --- Resolution: Won't Fix Assignee: Lukas Theussl Staging has been completely decoupled from site generation, it just a local file deploy now, see MSITE-533. The site has to be generated separately before running site:stage. > staging should execute some phase of the lifecycle > -- > > Key: MSITE-357 > URL: http://jira.codehaus.org/browse/MSITE-357 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug > Components: site:stage(-deploy) >Affects Versions: 2.0-beta-7 >Reporter: Brian Fox >Assignee: Lukas Theussl > > As much as i hate having to fork the lifecycle, with site:stage, there is no > way to generate other artifacts. In my use case, i'm using assembly to > generate a zip file (in the enforcer-api project) at pre-site, which works > fine if i mvn site or mvn site-deploy, but doesn't get created when you do a > site:stage. -- 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: (MSITE-528) Improve documentation using M3-aware profile
[
http://jira.codehaus.org/browse/MSITE-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukas Theussl closed MSITE-528.
---
Resolution: Fixed
Assignee: Lukas Theussl (was: Olivier Lamy)
Applied in [r1077958|http://svn.apache.org/viewvc?rev=1077958&view=rev]. Thanks!
> Improve documentation using M3-aware profile
>
>
> Key: MSITE-528
> URL: http://jira.codehaus.org/browse/MSITE-528
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.0-beta-3
>Reporter: Robert Scholte
>Assignee: Lukas Theussl
>Priority: Minor
> Fix For: 3.0-beta-4
>
> Attachments: maven3-docfix.patch
>
>
> The documention assumes you have specified the m-site-p version inside the
> {{pluginManagement}} section, but it's also valid to define the version in
> the {{plugins}} section.
> The site should mention this as well
--
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: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258541#action_258541 ] Kristian Rosenvold commented on SUREFIRE-711: - Out of general curiosity, could you give me some stats on this issue: 2.6 vs 2.7.2 vs 2.8-SNAPSHOT: Total build time difference and perhaps [INFO] Final Memory: 9M/157M at the end of the build for each version ? This bug has been here in one form or another since 2.4.X. > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG, > surefire2-8-SNAPSHOT-fix2.JPG, surefire2-8-SNAPSHOT.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- 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] Issue Comment Edited: (SUREFIRE-711) OutOfMemoryError while building multi module projects
[ http://jira.codehaus.org/browse/SUREFIRE-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258541#action_258541 ] Kristian Rosenvold edited comment on SUREFIRE-711 at 3/4/11 9:28 AM: - Out of general curiosity, could you give me some stats on this issue: 2.6 vs 2.7.2 vs 2.7.3-SNAPSHOT vs 2.8-SNAPSHOT: Total build time difference and perhaps [INFO] Final Memory: 9M/157M at the end of the build for each version ? This bug has been here in one form or another since 2.4.X. was (Author: krosenvold): Out of general curiosity, could you give me some stats on this issue: 2.6 vs 2.7.2 vs 2.8-SNAPSHOT: Total build time difference and perhaps [INFO] Final Memory: 9M/157M at the end of the build for each version ? This bug has been here in one form or another since 2.4.X. > OutOfMemoryError while building multi module projects > - > > Key: SUREFIRE-711 > URL: http://jira.codehaus.org/browse/SUREFIRE-711 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 2.7.2 > Environment: Win 7 32bit >Reporter: Christian Moser >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 2.8 > > Attachments: surefire-log.zip, surefire2-6-0.JPG, surefire2-7-2.JPG, > surefire2-8-SNAPSHOT-fix2.JPG, surefire2-8-SNAPSHOT.JPG > > > We're getting out of memory errors since we've updated to surefire 2.7.2 from > 2.6. > Please check the attached jvisualvm pics they show the same build execution > with 2.6 and 2.7.2. The attached "log.txt" and "log -X.txt" might also be > interesting. > it seems like 2.7.2 is not unloading classes after processing. > We found out that if we skip tests with -DskipTests=true, the exception won't > occur. > The build consists of several multi module projects. > > ..\..\BaseSys\trunk (multimodule) > ..\..\MagIC\trunk (multimodule) > ..\..\StabNet\trunk (multimodule) > ..\..\tiamo\trunk (multimodule) > ..\..\TiBase\trunk (multimodule) > ..\..\VIVA\trunk (multimodule) > > > [ERROR] Java heap space -> [Help 1]---Exception in > thread "main" jav > lang.OutOfMemoryError: Java heap space > at java.util.Arrays.copyOf(Arrays.java:2786) > at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:44) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) > at java.io.PrintStream.write(PrintStream.java:430) > at org.apache.maven.surefire.util.TeeStream.write(TeeStream.java:42) -- 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: (SCM-612) maven-release-plugin causes mercurial scm provider to fail when only a module is released
maven-release-plugin causes mercurial scm provider to fail when only a module
is released
-
Key: SCM-612
URL: http://jira.codehaus.org/browse/SCM-612
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-mercurial (hg)
Affects Versions: 1.4, 1.5
Reporter: Andreas Ebbert-Karroum
Problem as described on the [maven-users mailing
list|http://maven.40175.n5.nabble.com/How-to-release-a-single-module-in-a-Mercurial-repository-tp3406421p3406421.html].
Basically it is not possible to release a single module from a multi-module
project with mercurial as scm provider.
h2. When trying with current 1.5-SNAPSHOT:
{code}
Caused by: org.apache.maven.scm.ScmException: This provider doesn't support
tagging subsets of a directory
at
org.apache.maven.scm.provider.hg.command.tag.HgTagCommand.executeTagCommand(HgTagCommand.java:77)
at
org.apache.maven.scm.command.tag.AbstractTagCommand.executeCommand(AbstractTagCommand.java:81)
at
org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59)
... 29 more
{code}
h2. When trying with 1.4 release
It is more complicated, but also does not work. It boils down to having a
mandatory pom.xml in the repository root and scm url messed up during the
release:prepare and release:perform phases. See mentioned email for more
details.
--
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: (SUREFIRE-708) Test-classified but compile-scoped dependency causes NoClassDefFoundError: org/junit/runner/notification/RunListener
[
http://jira.codehaus.org/browse/SUREFIRE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-708.
---
Resolution: Incomplete
I am not able to reproduce the issue using the enclosed pom using maven 2.2.1,
3.02 or 3.03. Please feel free to re-open this issue if you have additional
information or optimally a complete mini-project that fails.
> Test-classified but compile-scoped dependency causes NoClassDefFoundError:
> org/junit/runner/notification/RunListener
>
>
> Key: SUREFIRE-708
> URL: http://jira.codehaus.org/browse/SUREFIRE-708
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.7.2
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac"
>Reporter: Andreas Sewe
>Priority: Blocker
> Attachments: pom.xml
>
>
> I have a real-world project which has a {{test}}-classified third-party
> dependency that is (out of necessity) {{compile}}-scoped rather then
> {{test}}-scoped (as the test-JAR unfortunately contains classes also useful
> outside of a testing context). This constellation causes the
> {{maven-surefire-plugin}} to fail with a {{NoClassDefFoundError}}, thus
> effectively preventing the project from being build:
> {quote}
> java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getConstructor0(Class.java:2699)
> at java.lang.Class.getConstructor(Class.java:1657)
> at
> org.apache.maven.surefire.util.ReflectionUtils.getConstructor(ReflectionUtils.java:76)
> at
> org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:129)
> at
> org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:198)
> at
> org.apache.maven.surefire.booter.ProviderFactory.createProvider(ProviderFactory.java:72)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:146)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> Caused by: java.lang.ClassNotFoundException:
> org.junit.runner.notification.RunListener
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:93)
> ... 11 more
> {quote}
> Attached is a minimal Maven project (just the POM; whether there are test
> sources present doesn't change the outcome) that reproduces this problem.
--
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: (SUREFIRE-703) surefire-junit47doesn't work with redirectTestOutputToFile option
[ http://jira.codehaus.org/browse/SUREFIRE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258558#action_258558 ] Kristian Rosenvold commented on SUREFIRE-703: - redirectTestOutputToFile will be subject to a revision in the release after 2.8 and this issue will have to wait until then. Thanks for the IT > surefire-junit47doesn't work with redirectTestOutputToFile option > - > > Key: SUREFIRE-703 > URL: http://jira.codehaus.org/browse/SUREFIRE-703 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.7.2 >Reporter: Will May > Attachments: surefire-junit47-it.patch > > > If you have the redirectTestOutputToFile option set and use the > surefire-junit47 provider (through using the parallel test option or through > forcing it), then the output file will just contain a single newline and so > the console logging will be completely lost. > Attached is an integration test showing this issue which was based off of the > fork-consoleOutput integration test. -- 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: (SUREFIRE-634) setting "java.library.path" via systemPropertyVariables or systemProperties is not working
[
http://jira.codehaus.org/browse/SUREFIRE-634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-634.
---
Resolution: Fixed
Fix Version/s: 2.8
Assignee: Kristian Rosenvold
Surefire now emits a warning log message upon attempting to set this property.
Fixed in r1078097
> setting "java.library.path" via systemPropertyVariables or systemProperties
> is not working
> --
>
> Key: SUREFIRE-634
> URL: http://jira.codehaus.org/browse/SUREFIRE-634
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.5
> Environment: Windows 7 (x64)
>Reporter: Daniel Rothmaler
>Assignee: Kristian Rosenvold
>Priority: Minor
> Fix For: 2.8
>
>
> I tried to set "java.library.path" for my tests, to use an native windows dll
> (in my case jawin.dll).
> Id tried to do this the following way:
>
> ${basedir}/src/main/runtime/lib/
>
> I also tried to use the older , with
> "${project.build.directory}/lib/" as base (with copied libs of cause), with
> an absolute path and with different fork modes; but nothing worked.
> The only way to get it going was to use "":
> -Djava.library.path=${basedir}/src/main/runtime/lib/
--
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: (SUREFIRE-659) Maven PDF plugin:showSuccess=false creates empty table causing error
[ http://jira.codehaus.org/browse/SUREFIRE-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold updated SUREFIRE-659: Attachment: (was: surefire659testcase.patch) > Maven PDF plugin:showSuccess=false creates empty table causing error > > > Key: SUREFIRE-659 > URL: http://jira.codehaus.org/browse/SUREFIRE-659 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Report Plugin >Affects Versions: 2.6 > Environment: maven 2.2.1, surefire 2.6, maven-pdf-plugin >Reporter: Darren Hartford > > The problem is that for > showSuccess=false an empty table is written but fo expects some > tableRows even if they are empty. > Cheers, > -Lukas > Darren Hartford wrote: > > Hey all, > > Not sure where to put this issue, but using the surefire-report(2.6) with > > showSuccess=false, with the maven-pdf-plugin (1.1) breaks. This is using a > > multi-module/aggregate report approach, maven 2.2.1. With > > showSuccess=true, everything works fine. > > > > Basic intent is to, on a release, create an aggregate/summary PDF of the > > release, but some of the items. such as the surefire-report, are too > > verbose. > > > > > > org.apache.maven.plugins > > maven-surefire-report-plugin > > 2.6 > > > > > >false > > true > > > > > > > > > > > > > > > > Error > > === > > [ERROR] BUILD ERROR > > [INFO] > > > > [INFO] Error during document generation: Error creating PDF from > > /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: > > org.apache.fop.fo.ValidationException: > > file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): > > fo:table-body is missing child elements. > > Required Content Model: marker* (table-row+|table-cell+) > > > > [INFO] > > > > [DEBUG] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: Error during > > document generation: Error creating PDF from > > /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: > > org.apache.fop.fo.ValidationException: > > file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): > > fo:table-body is missing child elements. > > Required Content Model: marker* (table-row+|table-cell+) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:584) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > at java.lang.reflect.Method.invoke(Method.java:616) > > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > > at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > Caused by: org.apache.maven.plugin.MojoExecutionException: Error during > > document generation: Error creating PDF from > > /dev//target/pdf/maven-pdf-plugin-doc-3.6.fo: > > org.apache.fop.fo.ValidationException: > > file:/dev//target/pdf/maven-pdf-plugin-doc-3.6.fo:3089:16: Error(3089/16): > > fo:table-body is missing child elements. > > Required Content Model: marker* (table-row+|table-cell+) > > at org.apache.maven.plugins.pdf.PdfMojo.generatedPdf(PdfMojo.java:574) > > at org.apache.maven.plugins.pdf.PdfMojo.execute(PdfMojo.java:391) > > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:453) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) > > ... 16 more > > Caused by: org.apache.maven.doxia.do
[jira] Created: (MCHANGES-228) Changes report does not have tags for action type images, so tips do not display in many browsers
Changes report does not have tags for action type images, so tips do
not display in many browsers
-
Key: MCHANGES-228
URL: http://jira.codehaus.org/browse/MCHANGES-228
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: changes.xml
Affects Versions: 2.4
Reporter: SebbASF
The HTML generated for a changes report contains tags for the images, but
it also needs tags otherwise the hover text does not appear in many
browsers.
Sample of current output:
{code}
{code}
How it should look:
{code}
{code}
I've created a sample HTML page to make it easy to test using a browser:
http://people.apache.org/~sebb/maven/alt_title.html
Only IE displays the alt text; FF, Opera and Chrome don't.
All 4 browsers display the title text.
According to http://www.w3schools.com/tags/tag_IMG.asp
{quote}
Tip: The alt attribute is meant to be used as an alternative text if the image
is not available, not as a mouse-over text. To show a mouse-over text on images
or image-maps, use the title attribute, like this:
{quote}
--
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: (SUREFIRE-610) Surefire plugin aborts if target directory contains files/dirs
[ http://jira.codehaus.org/browse/SUREFIRE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-610. --- Resolution: Cannot Reproduce Assignee: Kristian Rosenvold Feel free to reopen this issue if additional details are availble. > Surefire plugin aborts if target directory contains files/dirs > -- > > Key: SUREFIRE-610 > URL: http://jira.codehaus.org/browse/SUREFIRE-610 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Surefire Plugin >Affects Versions: 2.5 > Environment: Windows XP, Windows 2003k, Ubuntu, Maven 2.0.9, Maven > 2.2.1 >Reporter: Randall Fidler >Assignee: Kristian Rosenvold > > If there are files in the target directory when the plugin is run, > specifically when tests are run inconjunction with the release:perform plugin > goal, the plugin seems to simply terminate. The overall build is failed due > to there being test failures, but the build shows no test failures (i.e. <<< > FAILURE!) and none of the surefire reports list any test failures. It's > important to note that there will be only part of your test reports you > expect (say 50%) as the plugin appears to stop before it has executed all > tests. I believe what occurs is the plugin tries to create a report, say for > test G, and finds in the target directory that the reports files for test G > already exist that's where it pukes. As a result, you will have reports for > tests A-F and nothing more; all of these reports will NOT list any > error/failure. Also important to note is that there is no summary you > usually see, i.e. Tests: 100 Failures: 0 Errors: 0, after the surefire plugin > runs - you only see the stats for the last test and then information from the > "main" maven thread saying the build failed due to test failures. > It would be ideal if: > a) the surefire plugin could remove any surefire reports prior to execution > or > b) fail the build but provide a reason why, e.g. "could not write the test > report for test G" -- 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: (SUREFIRE-554) Offer excludes/includes setting of -Denv.vars passthrough of forked test-runner
[ http://jira.codehaus.org/browse/SUREFIRE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kristian Rosenvold closed SUREFIRE-554. --- Resolution: Won't Fix Since SUREFIRE-121 now works, this issue seems needlessly complex. Feel free to re-open with revised use-case descriptions argumenting for the required flexibility. > Offer excludes/includes setting of -Denv.vars passthrough of forked > test-runner > --- > > Key: SUREFIRE-554 > URL: http://jira.codehaus.org/browse/SUREFIRE-554 > Project: Maven Surefire > Issue Type: Improvement > Components: process forking >Affects Versions: 2.4.3 >Reporter: manuel aldana > > Offer a possiblity to passthrough env-setting from maven CLI to the forked > test-runner. To avoid a passthrough of all -D parameters enable default and > configurable excludes. > It will avoid a lot of confusion and maven trouble when using CLI params to > pass them to the test runner. > For discussion see also > http://www.nabble.com/passing-through--D-params-from-CLI-to-other-plugins-td24188981.html -- 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: (MCHANGES-228) Changes report does not have tags for action type images, so tips do not display in many browsers
[
http://jira.codehaus.org/browse/MCHANGES-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MCHANGES-228.
Resolution: Duplicate
> Changes report does not have tags for action type images, so tips do
> not display in many browsers
> -
>
> Key: MCHANGES-228
> URL: http://jira.codehaus.org/browse/MCHANGES-228
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes.xml
>Affects Versions: 2.4
>Reporter: SebbASF
>
> The HTML generated for a changes report contains tags for the images,
> but it also needs tags otherwise the hover text does not appear in
> many browsers.
> Sample of current output:
> {code}
>
> {code}
> How it should look:
> {code}
>
> {code}
> I've created a sample HTML page to make it easy to test using a browser:
> http://people.apache.org/~sebb/maven/alt_title.html
> Only IE displays the alt text; FF, Opera and Chrome don't.
> All 4 browsers display the title text.
> According to http://www.w3schools.com/tags/tag_IMG.asp
> {quote}
> Tip: The alt attribute is meant to be used as an alternative text if the
> image is not available, not as a mouse-over text. To show a mouse-over text
> on images or image-maps, use the title attribute, like this: src="angry.gif" alt="Angry face" title="Angry face" />
> {quote}
--
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: (SUREFIRE-708) Test-classified but compile-scoped dependency causes NoClassDefFoundError: org/junit/runner/notification/RunListener
[
http://jira.codehaus.org/browse/SUREFIRE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258599#action_258599
]
Andreas Sewe commented on SUREFIRE-708:
---
With respect to the test project's completeness: the {{pom.xml}} is all you
need, but if you really want to, feel free to add {{src/main/java}} and
{{src/test/java}} directories; this doesn't change anything.
However, it seems that deleting the local repository fixed the problem for me.
:-) I'll try to figure out what the difference were between the new and the old
local repository.
> Test-classified but compile-scoped dependency causes NoClassDefFoundError:
> org/junit/runner/notification/RunListener
>
>
> Key: SUREFIRE-708
> URL: http://jira.codehaus.org/browse/SUREFIRE-708
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.7.2
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac"
>Reporter: Andreas Sewe
>Priority: Blocker
> Attachments: pom.xml
>
>
> I have a real-world project which has a {{test}}-classified third-party
> dependency that is (out of necessity) {{compile}}-scoped rather then
> {{test}}-scoped (as the test-JAR unfortunately contains classes also useful
> outside of a testing context). This constellation causes the
> {{maven-surefire-plugin}} to fail with a {{NoClassDefFoundError}}, thus
> effectively preventing the project from being build:
> {quote}
> java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getConstructor0(Class.java:2699)
> at java.lang.Class.getConstructor(Class.java:1657)
> at
> org.apache.maven.surefire.util.ReflectionUtils.getConstructor(ReflectionUtils.java:76)
> at
> org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:129)
> at
> org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:198)
> at
> org.apache.maven.surefire.booter.ProviderFactory.createProvider(ProviderFactory.java:72)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:146)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> Caused by: java.lang.ClassNotFoundException:
> org.junit.runner.notification.RunListener
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:93)
> ... 11 more
> {quote}
> Attached is a minimal Maven project (just the POM; whether there are test
> sources present doesn't change the outcome) that reproduces this problem.
--
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: (SUREFIRE-708) Test-classified but compile-scoped dependency causes NoClassDefFoundError: org/junit/runner/notification/RunListener
[
http://jira.codehaus.org/browse/SUREFIRE-708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258600#action_258600
]
Kristian Rosenvold commented on SUREFIRE-708:
-
I did just about what you said and guess what, it works here too ;) We'll leave
the issue closed until further notice.
> Test-classified but compile-scoped dependency causes NoClassDefFoundError:
> org/junit/runner/notification/RunListener
>
>
> Key: SUREFIRE-708
> URL: http://jira.codehaus.org/browse/SUREFIRE-708
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading, Maven Surefire Plugin
>Affects Versions: 2.7.2
> Environment: Apache Maven 3.0.2 (r1056850; 2011-01-09 01:58:10+0100)
> Java version: 1.6.0_22, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.6.6", arch: "x86_64", family: "mac"
>Reporter: Andreas Sewe
>Priority: Blocker
> Attachments: pom.xml
>
>
> I have a real-world project which has a {{test}}-classified third-party
> dependency that is (out of necessity) {{compile}}-scoped rather then
> {{test}}-scoped (as the test-JAR unfortunately contains classes also useful
> outside of a testing context). This constellation causes the
> {{maven-surefire-plugin}} to fail with a {{NoClassDefFoundError}}, thus
> effectively preventing the project from being build:
> {quote}
> java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener
> at java.lang.Class.getDeclaredConstructors0(Native Method)
> at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
> at java.lang.Class.getConstructor0(Class.java:2699)
> at java.lang.Class.getConstructor(Class.java:1657)
> at
> org.apache.maven.surefire.util.ReflectionUtils.getConstructor(ReflectionUtils.java:76)
> at
> org.apache.maven.surefire.util.ReflectionUtils.instantiateOneArg(ReflectionUtils.java:129)
> at
> org.apache.maven.surefire.booter.SurefireReflector.instantiateProvider(SurefireReflector.java:198)
> at
> org.apache.maven.surefire.booter.ProviderFactory.createProvider(ProviderFactory.java:72)
> at
> org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:146)
> at
> org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
> at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
> Caused by: java.lang.ClassNotFoundException:
> org.junit.runner.notification.RunListener
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> at
> org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:93)
> ... 11 more
> {quote}
> Attached is a minimal Maven project (just the POM; whether there are test
> sources present doesn't change the outcome) that reproduces this problem.
--
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-79) mechanism for local preview of a multiproject site tree
[ http://jira.codehaus.org/browse/MSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=258626#action_258626 ] Lukas Theussl commented on MSITE-79: site:stage now (v. 2.3-snap) behaves as noted above, see MSITE-533. However, site:run cannot be used to preview the multi-module build tree, it only works on the current site. > mechanism for local preview of a multiproject site tree > --- > > Key: MSITE-79 > URL: http://jira.codehaus.org/browse/MSITE-79 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: New Feature > Components: site:run >Reporter: Brett Porter > > currently difficult as they are in target/site/*, where the links rely on ./ -- 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: (MAVENUPLOAD-2813) Jericho HTML Parser 3.2
Jericho HTML Parser 3.2 --- Key: MAVENUPLOAD-2813 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2813 Project: Maven Upload Requests Issue Type: Task Reporter: Martin Jericho Jericho HTML Parser is a java library allowing analysis and manipulation of parts of an HTML document, including server-side tags, while reproducing verbatim any unrecognised or invalid HTML. -- 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
