[jira] (MJAVADOC-406) The functionality of MJAVADOC-398 should be configurable
[
https://jira.codehaus.org/browse/MJAVADOC-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MJAVADOC-406:
-
Priority: Critical (was: Blocker)
> The functionality of MJAVADOC-398 should be configurable
>
>
> Key: MJAVADOC-406
> URL: https://jira.codehaus.org/browse/MJAVADOC-406
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Martin Skurla
>Assignee: Dennis Lundberg
>Priority: Critical
>
> The "functionality"/change behavior of MJAVADOC-398 should definitely be
> configurable.
> In our project we have to manually put a lot of dependencies into
> {{}} section to restore the previously working
> behaviour which is a huge pain and does not scale (as we will be forced to
> update the dependencies every time dependencies are added to projects).
> Please provide a javadoc configuration for turning on/off the "functionality"
> added in MJAVADOC-398.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-406) The functionality of MJAVADOC-398 should be configurable
[
https://jira.codehaus.org/browse/MJAVADOC-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg reassigned MJAVADOC-406:
Assignee: Dennis Lundberg
> The functionality of MJAVADOC-398 should be configurable
>
>
> Key: MJAVADOC-406
> URL: https://jira.codehaus.org/browse/MJAVADOC-406
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
>Reporter: Martin Skurla
>Assignee: Dennis Lundberg
>Priority: Blocker
>
> The "functionality"/change behavior of MJAVADOC-398 should definitely be
> configurable.
> In our project we have to manually put a lot of dependencies into
> {{}} section to restore the previously working
> behaviour which is a huge pain and does not scale (as we will be forced to
> update the dependencies every time dependencies are added to projects).
> Please provide a javadoc configuration for turning on/off the "functionality"
> added in MJAVADOC-398.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-411) Package does not exist warnings
[
https://jira.codehaus.org/browse/MJAVADOC-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353121#comment-353121
]
Dennis Lundberg commented on MJAVADOC-411:
--
We need more info to be able to understand your problem.
Could your problem be the same as MJAVADOC-407?
> Package does not exist warnings
> ---
>
> Key: MJAVADOC-411
> URL: https://jira.codehaus.org/browse/MJAVADOC-411
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Mac OSX, Java 8 Update 20, Maven 3.2.3
>Reporter: Anthony Whitford
>
> Since version 2.10, it appears that Javadoc is warning about missing packages
> when generating javadoc.
> * For the {{javadoc}} goal, the {{compile}} scope classes should be in scope
> * For the {{test-javadoc}} goal, the {{test}} scope classes should be in scope
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-409) Generating Javadoc no longer works with 2.10
[
https://jira.codehaus.org/browse/MJAVADOC-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MJAVADOC-409.
Resolution: Duplicate
> Generating Javadoc no longer works with 2.10
>
>
> Key: MJAVADOC-409
> URL: https://jira.codehaus.org/browse/MJAVADOC-409
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: /Applications/apache-maven/apache-maven-3.0.5
> Java version: 1.6.0_65, vendor: Apple Inc.
> Java home:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"
>Reporter: Wim Deblauwe
>
> If I run javadoc using 2.9, then javadoc is generated without issue:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc}}
> However, using version 2.10, the build fails:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
> There is a very big stack trace. One of the things that is shown is this:
> {noformat}
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl
> cannot be cast to com.sun.javadoc.AnnotationTypeDoc
> [ERROR] at
> com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
> [ERROR] at
> com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> [ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> [ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> [ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
> [ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
> [ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
> @options @packages @argfile
> [ERROR]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg closed MJAVADOC-408.
Resolution: Duplicate
Remember to always specify the versions for each and every plugin you use
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-1098) runOrder=balanced is not working
Miyata Jumpei created SUREFIRE-1098:
---
Summary: runOrder=balanced is not working
Key: SUREFIRE-1098
URL: https://jira.codehaus.org/browse/SUREFIRE-1098
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Affects Versions: 2.17, 2.16, 2.15, 2.14.1, 2.14, 2.13, 2.12.4, 2.12.3,
2.12.2
Environment: JDK 7 on Linux
JUnit 4.11
Reporter: Miyata Jumpei
It seems that the runOrder parameter with balanced value is not working.
For example, I created a project with the following setting.
{code}
maven-surefire-plugin
2.17
classes
balanced
2
false
{code}
Then, execute the following tests.
TestA: 1 second
TestB: 2 seconds
TestC: 3 seconds
TestD: 4 seconds
The expected order is the following from the second time.
Thread 1: TestD → TestA
Thread 2: TestC → TestB
However, the actual order is the following.
Thread 1: TestB → TestD
Thread 2: TestC → TestA
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-411) Package does not exist warnings
Anthony Whitford created MJAVADOC-411:
-
Summary: Package does not exist warnings
Key: MJAVADOC-411
URL: https://jira.codehaus.org/browse/MJAVADOC-411
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.10
Environment: Mac OSX, Java 8 Update 20, Maven 3.2.3
Reporter: Anthony Whitford
Since version 2.10, it appears that Javadoc is warning about missing packages
when generating javadoc.
* For the {{javadoc}} goal, the {{compile}} scope classes should be in scope
* For the {{test-javadoc}} goal, the {{test}} scope classes should be in scope
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-250) NPE on tying to load LICENSE.txt resource from non-jar plugin dependencies
[
https://jira.codehaus.org/browse/MCHECKSTYLE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353115#comment-353115
]
Herve Boutemy commented on MCHECKSTYLE-250:
---
why not put the XML in a jar file?
> NPE on tying to load LICENSE.txt resource from non-jar plugin dependencies
> --
>
> Key: MCHECKSTYLE-250
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-250
> Project: Maven Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.13
>Reporter: Konstantin Pokrovsky
>
> *Steps to reproduce:*
> * Add non jar (XML for example) artifact dependency to plugin dependencies
> section:
> {code:xml}
>
> org.apache.maven.plugins
> maven-checkstyle-plugin
> 2.13
>
>
> anygroup
> anyfile
> xml
>
>
>
> {code}
> * Run _checkstyle:check_
> Result:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check (default-cli) on
> project rt: Execution default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check failed.
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check
> (default-cli) on project rt: Execution default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> 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:317)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:152)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:555)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
> 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:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-checkstyle-plugin:2.13:check failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:115)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 19 common frames omitted
> Caused by: java.lang.NullPointerException: null
> at
> org.codehaus.plexus.resource.loader.JarHolder.getEntries(JarHolder.java:126)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.loadJar(JarResourceLoader.java:100)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.initialize(JarResourceLoader.java:63)
> at
> org.codehaus.plexus.resource.loader.JarResourceLoader.getResource(JarResourceLoader.java:141)
> at
> org.apache.maven.plugin.checkstyle.resource.LicenseResourceManager.getResource(LicenseResourceManager.java:75)
> at
> org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:91)
> at
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getOverridingProperties(DefaultCheckstyleExecutor.java:520)
> at
> org.apache.maven.plugin.checkstyle.exec.DefaultCheckstyleExecutor.getConfiguration(DefaultCheckstyleExecutor.java:347)
> at
>
[jira] (MJAVADOC-407) cannot parse annotations : when generating javadoc
[
https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353114#comment-353114
]
Herve Boutemy commented on MJAVADOC-407:
seems the fix should be MJAVADOC-406
> cannot parse annotations : when generating javadoc
> ---
>
> Key: MJAVADOC-407
> URL: https://jira.codehaus.org/browse/MJAVADOC-407
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux and windows.
> Maven 3.0.4 , JDK 1.6.0.43
>Reporter: jeff porter
>
> See full issue text at :
> http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
> I'm getting the following error when I do
> {noformat}mvn clean deploy -DperformRelease=true
> [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist
> [ERROR] import javax.inject.Named;
> [ERROR]
> [ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol
> [ERROR] symbol: class Named
> [ERROR] @Named("transactionServiceExternal")
> [ERROR]
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl
> cannot be cast to com.sun.javadoc.AnnotationTypeDoc{noformat}
> The POM is this...
> {code:xml}com.xxx
> ts-impl/artifactId>
> 2.4.0-SNAPSHOT
>
>
> javax.inject
> javax.inject
> 1
>
> {code}
> There is only one class...
> {code:java}import javax.inject.Named;
> @Named("transactionServiceExternal")
> public class TransactionServiceExternalImpl
> {
> }{code}
> I get the error with
> jdk1.5.0_22
> jdk1.6.0_29
> jdk1.6.0_43
> jdk1.6.0_43_32bit
> But NOT with...
> jdk1.7.0_05
> Anyone have any ideas?
> Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
>
> I now know that the reason is that the Maven Javadoc Plugin has changed from
> 2.9.1 to 2.10. and this is the cause of the problem.
> I can see this warning...
> [WARNING] 'build.plugins.plugin.version' for
> org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING]
> 'build.plugins.plugin.version' for
> org.apache.maven.plugins:maven-deploy-plugin is missing.
> By setting the following in my pom
> org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar
> I can fix the version back to the last release.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-407) cannot parse annotations : when generating javadoc
[
https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MJAVADOC-407:
---
Description:
See full issue text at :
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
I'm getting the following error when I do
{noformat}mvn clean deploy -DperformRelease=true
[ERROR] Exit code: 1 - .java:3: package javax.inject does not exist
[ERROR] import javax.inject.Named;
[ERROR]
[ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol
[ERROR] symbol: class Named
[ERROR] @Named("transactionServiceExternal")
[ERROR]
[ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
be cast to com.sun.javadoc.AnnotationTypeDoc{noformat}
The POM is this...
{code:xml}com.xxx
ts-impl/artifactId>
2.4.0-SNAPSHOT
javax.inject
javax.inject
1
{code}
There is only one class...
{code:java}import javax.inject.Named;
@Named("transactionServiceExternal")
public class TransactionServiceExternalImpl
{
}{code}
I get the error with
jdk1.5.0_22
jdk1.6.0_29
jdk1.6.0_43
jdk1.6.0_43_32bit
But NOT with...
jdk1.7.0_05
Anyone have any ideas?
Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
I now know that the reason is that the Maven Javadoc Plugin has changed from
2.9.1 to 2.10. and this is the cause of the problem.
I can see this warning...
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING]
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin
is missing.
By setting the following in my pom
org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar
I can fix the version back to the last release.
was:
See full issue text at :
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
I'm getting the following error when I do
{noformat}mvn clean deploy -DperformRelease=true
[ERROR] Exit code: 1 - .java:3: package javax.inject does not exist [ERROR]
import javax.inject.Named; [ERROR] ^ [ERROR]
TransactionServiceExternalImpl.java:5: cannot find symbol [ERROR] symbol: class
Named [ERROR] @Named("transactionServiceExternal") [ERROR] ^ [ERROR]
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast
to com.sun.javadoc.AnnotationTypeDoc{noformat}
The POM is this...
{code:xml}com.xxx
ts-impl/artifactId>
2.4.0-SNAPSHOT
javax.inject
javax.inject
1
{code}
There is only one class...
{code:java}import javax.inject.Named;
@Named("transactionServiceExternal")
public class TransactionServiceExternalImpl
{
}{code}
I get the error with
jdk1.5.0_22
jdk1.6.0_29
jdk1.6.0_43
jdk1.6.0_43_32bit
But NOT with...
jdk1.7.0_05
Anyone have any ideas?
Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
I now know that the reason is that the Maven Javadoc Plugin has changed from
2.9.1 to 2.10. and this is the cause of the problem.
I can see this warning...
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING]
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin
is missing.
By setting the following in my pom
org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar
I can fix the version back to the last release.
> cannot parse annotations : when generating javadoc
> ---
>
> Key: MJAVADOC-407
> URL: https://jira.codehaus.org/browse/MJAVADOC-407
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux and windows.
> Maven 3.0.4 , JDK 1.6.0.43
>Reporter: jeff porter
>
> See full issue text at :
> http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
> I'm getting the following error when I do
> {noformat}mvn clean deploy -DperformRelease=true
> [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist
> [ERROR] import javax.inject.Named;
> [ERROR]
> [ERROR] TransactionServiceExternalImpl.java:5: cannot find symbol
> [ERROR] symbol: class Named
> [ERROR] @Named("transactionServiceExternal")
> [ERROR]
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl
> cannot be cast to com.sun.javadoc.AnnotationTypeDoc{noformat}
> The POM is this...
> {code:xml}com.xxx
> ts-impl/artifactId>
> 2.4.0-SNAPSHOT
>
>
> javax.inject
> javax.inject
> 1
>
> {code}
> There is only one class...
> {code:java}import javax.inject.Named;
> @Named("transactionServiceExternal")
> public class Transaction
[jira] (MJAVADOC-407) cannot parse annotations : when generating javadoc
[
https://jira.codehaus.org/browse/MJAVADOC-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MJAVADOC-407:
---
Description:
See full issue text at :
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
I'm getting the following error when I do
{noformat}mvn clean deploy -DperformRelease=true
[ERROR] Exit code: 1 - .java:3: package javax.inject does not exist [ERROR]
import javax.inject.Named; [ERROR] ^ [ERROR]
TransactionServiceExternalImpl.java:5: cannot find symbol [ERROR] symbol: class
Named [ERROR] @Named("transactionServiceExternal") [ERROR] ^ [ERROR]
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast
to com.sun.javadoc.AnnotationTypeDoc{noformat}
The POM is this...
{code:xml}com.xxx
ts-impl/artifactId>
2.4.0-SNAPSHOT
javax.inject
javax.inject
1
{code}
There is only one class...
{code:java}import javax.inject.Named;
@Named("transactionServiceExternal")
public class TransactionServiceExternalImpl
{
}{code}
I get the error with
jdk1.5.0_22
jdk1.6.0_29
jdk1.6.0_43
jdk1.6.0_43_32bit
But NOT with...
jdk1.7.0_05
Anyone have any ideas?
Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
I now know that the reason is that the Maven Javadoc Plugin has changed from
2.9.1 to 2.10. and this is the cause of the problem.
I can see this warning...
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING]
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin
is missing.
By setting the following in my pom
org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar
I can fix the version back to the last release.
was:
See full issue text at :
http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
I'm getting the following error when I do
mvn clean deploy -DperformRelease=true
[ERROR] Exit code: 1 - .java:3: package javax.inject does not exist [ERROR]
import javax.inject.Named; [ERROR] ^ [ERROR]
TransactionServiceExternalImpl.java:5: cannot find symbol [ERROR] symbol: class
Named [ERROR] @Named("transactionServiceExternal") [ERROR] ^ [ERROR]
java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be cast
to com.sun.javadoc.AnnotationTypeDoc
The POM is this...
com.xxx
ts-impl/artifactId>
2.4.0-SNAPSHOT
javax.inject
javax.inject
1
There is only one class...
import javax.inject.Named;
@Named("transactionServiceExternal")
public class TransactionServiceExternalImpl
{
}
I get the error with
jdk1.5.0_22
jdk1.6.0_29
jdk1.6.0_43
jdk1.6.0_43_32bit
But NOT with...
jdk1.7.0_05
Anyone have any ideas?
Notes: Apache Maven 3.0.4 (r1232337; 2012-01-17 08:44:56+)
I now know that the reason is that the Maven Javadoc Plugin has changed from
2.9.1 to 2.10. and this is the cause of the problem.
I can see this warning...
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing. [WARNING]
'build.plugins.plugin.version' for org.apache.maven.plugins:maven-deploy-plugin
is missing.
By setting the following in my pom
org.apache.maven.plugins maven-javadoc-plugin 2.9.1 attach-javadocs jar
I can fix the version back to the last release.
> cannot parse annotations : when generating javadoc
> ---
>
> Key: MJAVADOC-407
> URL: https://jira.codehaus.org/browse/MJAVADOC-407
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux and windows.
> Maven 3.0.4 , JDK 1.6.0.43
>Reporter: jeff porter
>
> See full issue text at :
> http://stackoverflow.com/questions/25971832/javadoc-generation-failed-classcastexception-com-sun-tools-javadoc-classdocim
> I'm getting the following error when I do
> {noformat}mvn clean deploy -DperformRelease=true
> [ERROR] Exit code: 1 - .java:3: package javax.inject does not exist [ERROR]
> import javax.inject.Named; [ERROR] ^ [ERROR]
> TransactionServiceExternalImpl.java:5: cannot find symbol [ERROR] symbol:
> class Named [ERROR] @Named("transactionServiceExternal") [ERROR] ^ [ERROR]
> java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot be
> cast to com.sun.javadoc.AnnotationTypeDoc{noformat}
> The POM is this...
> {code:xml}com.xxx
> ts-impl/artifactId>
> 2.4.0-SNAPSHOT
>
>
> javax.inject
> javax.inject
> 1
>
> {code}
> There is only one class...
> {code:java}import javax.inject.Named;
> @Named("transactionServiceExternal")
> public class TransactionServiceExternalImpl
> {
> }{code}
> I get
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353111#comment-353111
]
Christian Kohlschütter commented on MJAVADOC-408:
-
We are also affected by this.
Our temporary workaround is to
1. explicitly specify version 2.9.1 in the (parent) POM where possible, and
2. to add the following to ~/.m2/settings.xml (which does not require patching
POMs; the javadoc phase just fails without bringing down the entire build):
{code}
{code}
(...)
{code}
{code}
(...)
{code}
javadoc-fix
false
javadoc-fix
{code}
(...)
{code}
{code}
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-176) Suppress warning output
[ https://jira.codehaus.org/browse/MSHADE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353108#comment-353108 ] Robert Scholte commented on MSHADE-176: --- I would expect that it is already possible with [filters|http://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.html#filters], but I'd need your example to verify it. > Suppress warning output > --- > > Key: MSHADE-176 > URL: https://jira.codehaus.org/browse/MSHADE-176 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Taylor Jones > Fix For: 2.4 > > Attachments: suppressWarnings_option.patch > > > The warnings Shade outputs are useful, but there are some cases where nothing > can actually be done about them. Recently, I encountered this with the Neo4j > libraries; there is one overlapping class between two critical JARs (kernel > and rest), and no way to resolve this via exclusions. > In these cases, everything works just fine. At best, the warnings are just > noise, but we also have some build processes in place that will fail on Maven > warnings. I figured this would be a pretty simple thing to just suppress, but > Shade doesn't seem to have a way to do this. > I've included a simple patchset to address this which adds a new option to > the configuration called . There isn't a unit test > attached, unfortunately. I'm not quite sure how to unit test logging output > in this fashion without something akin to Mockito. I figured you guys > wouldn't appreciate me adding dependencies out of the blue but if a unit test > is required, I can give it a shot. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHADE-176) Suppress warning output
[ https://jira.codehaus.org/browse/MSHADE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353107#comment-353107 ] Taylor Jones commented on MSHADE-176: - I actually wanted to do that initially, but the structure of the code was such that I no longer had anything but the filename by the time the warning was generated. If there is a way to get the Maven coordinates of each file without refactoring, I'd love to do that. I'm worried that changing a large part of that code might break the plugin. > Suppress warning output > --- > > Key: MSHADE-176 > URL: https://jira.codehaus.org/browse/MSHADE-176 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Taylor Jones > Fix For: 2.4 > > Attachments: suppressWarnings_option.patch > > > The warnings Shade outputs are useful, but there are some cases where nothing > can actually be done about them. Recently, I encountered this with the Neo4j > libraries; there is one overlapping class between two critical JARs (kernel > and rest), and no way to resolve this via exclusions. > In these cases, everything works just fine. At best, the warnings are just > noise, but we also have some build processes in place that will fail on Maven > warnings. I figured this would be a pretty simple thing to just suppress, but > Shade doesn't seem to have a way to do this. > I've included a simple patchset to address this which adds a new option to > the configuration called . There isn't a unit test > attached, unfortunately. I'm not quite sure how to unit test logging output > in this fashion without something akin to Mockito. I figured you guys > wouldn't appreciate me adding dependencies out of the blue but if a unit test > is required, I can give it a shot. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEP-454) copy-dependencies with does NOT copy transitive deps
[
https://jira.codehaus.org/browse/MDEP-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353105#comment-353105
]
Robert Scholte commented on MDEP-454:
-
No, the first filtering which is done: only direct dependencies or both direct
and transitive dependencies (based on the excludeTransitive value) .
The next filter is: does the dependency's artifactId match one the
includeArtifactIds-value.
That explains your current result.
> copy-dependencies with does NOT copy transitive deps
> -
>
> Key: MDEP-454
> URL: https://jira.codehaus.org/browse/MDEP-454
> Project: Maven Dependency Plugin
> Issue Type: Improvement
> Components: copy-dependencies
>Affects Versions: 2.8
> Environment: 1. RHEL 6.5,
> 2. mvn -version
> Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
> 2014-02-14T09:37:52-08:00)
> Maven home: /abc/apache-maven-3.2.1
> Java version: 1.7.0_55, vendor: Oracle Corporation
> Java home: /xyz/jdk/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-358.14.1.el6.x86_64", arch: "amd64",
> family: "unix"
>Reporter: Tejas Mulay
>Assignee: Karl-Heinz Marbaise
>Priority: Blocker
> Attachments: console.txt, consumerBanking.zip
>
>
> I would like to copy transitive deps of specific artifacts into a custom
> directory. For that I am using {{copy-dependencies}} goal of dep plugin.
> But the plugin copies only the artifacts which are mentioned in
> {{}} tag and not its transitive deps.
> POM section for reference->
> {code:xml}
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.8
>
>
> Copying dependencies into ${stage}/${pkg_name_ss}/jars
> package
>
> copy-dependencies
>
>
> false
>
> jbpm-executor,jbpm-runtime-manager
> ${stage}/${pkg_name_ss}/jars
> false
> false
> true
>
>
>
>
> {code}
> It is a blocker for me.
> -Tejas.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHADE-176) Suppress warning output
[ https://jira.codehaus.org/browse/MSHADE-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353104#comment-353104 ] Robert Scholte commented on MSHADE-176: --- The reason I ask is to have a look at your usecase. I don't like the idea to have an all-or-nothing flag for warnings. If you would get other warnings, you wouldn't notice them when such a flag was set. Instead you should have a blacklist/whitelist for the warnings, or use the includes/excludes approach. > Suppress warning output > --- > > Key: MSHADE-176 > URL: https://jira.codehaus.org/browse/MSHADE-176 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Taylor Jones > Fix For: 2.4 > > Attachments: suppressWarnings_option.patch > > > The warnings Shade outputs are useful, but there are some cases where nothing > can actually be done about them. Recently, I encountered this with the Neo4j > libraries; there is one overlapping class between two critical JARs (kernel > and rest), and no way to resolve this via exclusions. > In these cases, everything works just fine. At best, the warnings are just > noise, but we also have some build processes in place that will fail on Maven > warnings. I figured this would be a pretty simple thing to just suppress, but > Shade doesn't seem to have a way to do this. > I've included a simple patchset to address this which adds a new option to > the configuration called . There isn't a unit test > attached, unfortunately. I'm not quite sure how to unit test logging output > in this fashion without something akin to Mockito. I figured you guys > wouldn't appreciate me adding dependencies out of the blue but if a unit test > is required, I can give it a shot. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-713) Update maven-reporting-impl to 2.3
[ https://jira.codehaus.org/browse/MASSEMBLY-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise deleted MASSEMBLY-713: -- > Update maven-reporting-impl to 2.3 > -- > > Key: MASSEMBLY-713 > URL: https://jira.codehaus.org/browse/MASSEMBLY-713 > Project: Maven Assembly Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Priority: Minor > > http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 > [Release Notes of maven-reporting-impl > 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] > * Sub-task > ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils > * Bug > ** [MSHARED-328] - use @parameter default-value instead of @parameter > expression in sample > ** [MSHARED-346] - missing properties usually set by m-site-p > (outputEncoding, ...) > * Improvement > ** [MSHARED-348] - support reporting encoding configuration when used as goal > * New Feature > ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields > copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-343) Update maven-reporting-impl to 2.3
[ https://jira.codehaus.org/browse/MCHANGES-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MCHANGES-343: - Fix Version/s: 2.11 > Update maven-reporting-impl to 2.3 > -- > > Key: MCHANGES-343 > URL: https://jira.codehaus.org/browse/MCHANGES-343 > Project: Maven Changes Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.11 > > > http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 > [Release Notes of maven-reporting-impl > 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] > * Sub-task > ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils > * Bug > ** [MSHARED-328] - use @parameter default-value instead of @parameter > expression in sample > ** [MSHARED-346] - missing properties usually set by m-site-p > (outputEncoding, ...) > * Improvement > ** [MSHARED-348] - support reporting encoding configuration when used as goal > * New Feature > ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields > copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-343) Update maven-reporting-impl to 2.3
[ https://jira.codehaus.org/browse/MCHANGES-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MCHANGES-343. Resolution: Fixed Assignee: Karl-Heinz Marbaise Fixed in [r1627139|http://svn.apache.org/r1627139]. > Update maven-reporting-impl to 2.3 > -- > > Key: MCHANGES-343 > URL: https://jira.codehaus.org/browse/MCHANGES-343 > Project: Maven Changes Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Assignee: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.11 > > > http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 > [Release Notes of maven-reporting-impl > 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] > * Sub-task > ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils > * Bug > ** [MSHARED-328] - use @parameter default-value instead of @parameter > expression in sample > ** [MSHARED-346] - missing properties usually set by m-site-p > (outputEncoding, ...) > * Improvement > ** [MSHARED-348] - support reporting encoding configuration when used as goal > * New Feature > ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields > copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-343) Update maven-reporting-impl to 2.3
Karl-Heinz Marbaise created MCHANGES-343: Summary: Update maven-reporting-impl to 2.3 Key: MCHANGES-343 URL: https://jira.codehaus.org/browse/MCHANGES-343 Project: Maven Changes Plugin Issue Type: Improvement Reporter: Karl-Heinz Marbaise Priority: Minor http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 [Release Notes of maven-reporting-impl 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] * Sub-task ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils * Bug ** [MSHARED-328] - use @parameter default-value instead of @parameter expression in sample ** [MSHARED-346] - missing properties usually set by m-site-p (outputEncoding, ...) * Improvement ** [MSHARED-348] - support reporting encoding configuration when used as goal * New Feature ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-713) Update maven-reporting-impl to 2.3
[ https://jira.codehaus.org/browse/MASSEMBLY-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-713: -- Fix Version/s: 2.5 > Update maven-reporting-impl to 2.3 > -- > > Key: MASSEMBLY-713 > URL: https://jira.codehaus.org/browse/MASSEMBLY-713 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 > [Release Notes of maven-reporting-impl > 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] > * Sub-task > ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils > * Bug > ** [MSHARED-328] - use @parameter default-value instead of @parameter > expression in sample > ** [MSHARED-346] - missing properties usually set by m-site-p > (outputEncoding, ...) > * Improvement > ** [MSHARED-348] - support reporting encoding configuration when used as goal > * New Feature > ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields > copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-713) Update maven-reporting-impl to 2.3
Karl-Heinz Marbaise created MASSEMBLY-713: - Summary: Update maven-reporting-impl to 2.3 Key: MASSEMBLY-713 URL: https://jira.codehaus.org/browse/MASSEMBLY-713 Project: Maven Assembly Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Karl-Heinz Marbaise Priority: Minor http://maven.apache.org/shared/maven-reporting-impl/ to version 2.3 [Release Notes of maven-reporting-impl 2.3|http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=18319] * Sub-task ** [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils * Bug ** [MSHARED-328] - use @parameter default-value instead of @parameter expression in sample ** [MSHARED-346] - missing properties usually set by m-site-p (outputEncoding, ...) * Improvement ** [MSHARED-348] - support reporting encoding configuration when used as goal * New Feature ** [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields copy/paste when implementing -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-648) lineEnding in fileSet corrupts jar files
[ https://jira.codehaus.org/browse/MASSEMBLY-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-648: -- Fix Version/s: (was: 2.5) backlog > lineEnding in fileSet corrupts jar files > > > Key: MASSEMBLY-648 > URL: https://jira.codehaus.org/browse/MASSEMBLY-648 > Project: Maven Assembly Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Maven 3.0.5 on Mac Os 10.8.3 with Apple JDK 1.6.0_43 > Maven 3.0.5 on Windows XP with Oracle JDK 1.6.0_31 >Reporter: Anders Hammar >Priority: Minor > Fix For: backlog > > Attachments: assembly-lineEnding.zip > > > I've found a difference in behavior between v2.3 and v2.4 of the plugin. If > lineEnding is set to, for example, unix for a fileSet which contains jar > files, the jar files are modified and corrupt with v2.4. This was not the > case with v2.3. See attached test project. > Not sure if this is an actual bug in the plugin, or rather a misconfiguation > in the project. But the behavioral change between the versions is a fact. :-) > If this is not a bug, maybe we could try to detect misconfiguration like this > and output a warning? -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353100#comment-353100
]
Jeffrey Hagelberg commented on MJAVADOC-408:
FYI - if you have a multi-module build, you can work around it by adding 2.9.1
to the pluginManagement section in the root pom.xml, eg
org.apache.maven.plugins
maven-javadoc-plugin
2.9.1
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353099#comment-353099
]
Jeffrey Hagelberg commented on MJAVADOC-408:
we're seeing this as well in our builds.
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAR-169) exclude settings don't seem to be taken into account
[
https://jira.codehaus.org/browse/MJAR-169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise closed MJAR-169.
Resolution: Won't Fix
Assignee: Karl-Heinz Marbaise
The exclude parameters is intended for classes and not for zip files etc. So i
will close the issue. If you have any objections don't hesitate to reopen the
issue.
> exclude settings don't seem to be taken into account
>
>
> Key: MJAR-169
> URL: https://jira.codehaus.org/browse/MJAR-169
> Project: Maven JAR Plugin
> Issue Type: Bug
>Affects Versions: 2.4
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: C:\apache-maven-3.0.5
> Java version: 1.7.0_15, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.7.0_15\jre
> Default locale: fr_FR, platform encoding: UTF-8
> OS name: "windows 8", version: "6.2", arch: "amd64", family: "windows"
>Reporter: Joel Costigliola
>Assignee: Karl-Heinz Marbaise
>
> I can't get exclude to work, it is maybe my fault but I can't figure out
> what's wrong.
> I'm trying to exclude from the jar to build a zip file and a directory that
> are copied into target/classes for integration tests.
> plugin configuration
> {code:xml}
>
> maven-jar-plugin
>
>
>
> ${project.build.outputDirectory}/webintlab-server-${project.version}-archive.zip
>
> ${project.build.outputDirectory}/webintlab-server-${project.version}
>
>
>
> {code}
> effective pom extract :
> {code:xml}
>
> maven-jar-plugin
> 2.4
>
>
> default-jar
> package
>
> jar
>
>
>
>
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT-archive.zip
>
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT
>
>
>
>
>
>
>
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT-archive.zip
>
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT
>
>
>
> {code}
> In following output extract, *directory webintlab-server-3.5-SNAPSHOT/ is
> added whereas plugin was configured to exclude it*.
> {noformat}
> [DEBUG] Configuring mojo org.apache.maven.plugins:maven-jar-plugin:2.4:jar
> from plugin realm
> ClassRealm[plugin>org.apache.maven.plugins:maven-jar-plugin:2.4, parent:
> sun.misc.Launcher$AppClassLoader@6140c973]
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-jar-plugin:2.4:jar'
> with basic configurator -->
> [DEBUG] (f) classesDirectory =
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes
> [DEBUG] (f) defaultManifestFile =
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes\META-INF\MANIFEST.MF
> [DEBUG] (f) excludes =
> [C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT-archive.zip,
>
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\classes/webintlab-server-3.5-SNAPSHOT]
> [DEBUG] (f) finalName = webintlab-functional-tests-3.5-SNAPSHOT
> [DEBUG] (f) forceCreation = false
> [DEBUG] (f) outputDirectory =
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target
> [DEBUG] (f) project = MavenProject:
> webintlab-functional-tests:webintlab-functional-tests:3.5-SNAPSHOT @
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\pom.xml
> [DEBUG] (f) session = org.apache.maven.execution.MavenSession@41878a17
> [DEBUG] (f) skipIfEmpty = false
> [DEBUG] (f) useDefaultManifestFile = false
> [DEBUG] -- end configuration --
> [DEBUG] isUp2date: false (Resource with newer modification date found.)
> [INFO] Building jar:
> C:\Users\Joel\git\osintlab\webintlab-functional-tests\target\webintlab-functional-tests-3.5-SNAPSHOT.jar
> [DEBUG] adding directory META-INF/
> [DEBUG] adding entry META-INF/MANIFEST.MF
> [DEBUG] adding directory webintlab-server-3.5-SNAPSHOT/
> [DEBUG] adding directory webintlab-server-3.5-SNAPSHOT/apache-activemq-5.8.0/
> [DEBUG] adding directory
> webintlab-server-3.5-SNAPSHOT/apache-activemq-5.8.0/bin/
> [DEBUG] adding directory
> webintlab-server-3.5-SNAPSHOT/apache-activemq-5.8.0/bin/win32
> {noformat}
> I have tried configuring exclude section with relative path but the same
> behavior occured.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAR-172) Manifest entries are in wrong (visual) order
[ https://jira.codehaus.org/browse/MJAR-172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MJAR-172: - Issue Type: Improvement (was: Bug) > Manifest entries are in wrong (visual) order > > > Key: MJAR-172 > URL: https://jira.codehaus.org/browse/MJAR-172 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 2.4 > Environment: Windows 7, IBM JDK 1.6.0, Maven 3.0.4 >Reporter: Anders Hammar >Priority: Minor > > When enabling addDefaultImplementationEntries and/or > addDefaultSpecificationEntries, these added manifest entries are not listed > together, which makes it not so nice visually. This was not the case with > v2.3.x (and prior) of the plugin, where they were added as explained here: > http://maven.apache.org/shared/maven-archiver/examples/manifest.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-161) Non default jars with classifier not attached to project
[ https://jira.codehaus.org/browse/MJAR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MJAR-161. Resolution: Won't Fix Assignee: Karl-Heinz Marbaise I will close the issue. if you have any objections don't hesitate to reopen the issue. > Non default jars with classifier not attached to project > > > Key: MJAR-161 > URL: https://jira.codehaus.org/browse/MJAR-161 > Project: Maven JAR Plugin > Issue Type: Improvement >Reporter: warren crossing >Assignee: Karl-Heinz Marbaise >Priority: Minor > Attachments: maven-jar-attach-non-default.patch > > > I wanted classifier jars to be attached. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-174) NoClassDefFoundError while packaging using maven-jar-plugin:2.4 with Maven 3.1.1
[ https://jira.codehaus.org/browse/MJAR-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MJAR-174: - Fix Version/s: more-investigation > NoClassDefFoundError while packaging using maven-jar-plugin:2.4 with Maven > 3.1.1 > > > Key: MJAR-174 > URL: https://jira.codehaus.org/browse/MJAR-174 > Project: Maven JAR Plugin > Issue Type: Bug > Components: sign >Affects Versions: 2.4 > Environment: Windows, Mac and Linux >Reporter: Maruthi Shanmugam > Fix For: more-investigation > > Attachments: Maven_Error.txt > > > Exception while building with Maven 3.1.1 and maven-jar-plugin:2.4 > Exception pasted for your reference : > WARNING] Error injecting: org.apache.maven.plugin.jar.JarMojo > java.lang.NoClassDefFoundError: > org/codehaus/plexus/components/io/resources/PlexusIoResourceCollection > at java.lang.Class.getDeclaredConstructors0(Native Method) > at java.lang.Class.privateGetDeclaredConstructors(Class.java:2493) > at java.lang.Class.getDeclaredConstructors(Class.java:1901) > at com.google.inject.spi.InjectionPoint.forConstructorOf(InjectionPoi -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-288) JIRA url not fully respected
[
https://jira.codehaus.org/browse/MCHANGES-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen updated MCHANGES-288:
Fix Version/s: (was: 2.11)
2.12
> JIRA url not fully respected
>
>
> Key: MCHANGES-288
> URL: https://jira.codehaus.org/browse/MCHANGES-288
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.8
> Environment: OS XP, maven 3.0.4
>Reporter: Bruno Marti
> Fix For: 2.12
>
> Attachments: jiraPreserveContextLogin.patch
>
>
> Issue url is not fully used by maven-changes-plugin:2.8
> have following issue url:
> {quote}
>
> JIRA
> https://my.ch/prod/jira/?pid=1
>
> {quote}
> with changes-plugin:2.7.1 works well:
> {quote}
> [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.7.1
> [DEBUG] JIRA lives at: https://my.ch/prod/jira
> [DEBUG] Login URL:
> https://my.ch/prod/jira/login.jsp?os_destination=/secure/&os_username=*&os_password=*
> [DEBUG] Successfully logged in into JIRA.
> {quote}
> BUT with changes-plugin:2.8, got error:
> {quote}
> [INFO] Generating "JIRA Report" report--- maven-changes-plugin:2.8
> [DEBUG] JIRA lives at: https://my.ch
> [DEBUG] Login URL:
> https://my.ch/login.jsp?os_destination=/secure/&os_username=*&os_password=*
> [ERROR] Error trying to login into JIRA.
> java.net.SocketException: Connection reset
> {quote}
> Problem is, that the additional context */prod/jira/* gets lost.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
[ https://jira.codehaus.org/browse/MCHANGES-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen closed MCHANGES-334. --- Resolution: Fixed Assignee: Mirko Friedenhagen Fixed in http://svn.apache.org/viewvc?view=revision&revision=1627124 > RestJiraDownloader doesn't honor proxy settings > --- > > Key: MCHANGES-334 > URL: https://jira.codehaus.org/browse/MCHANGES-334 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.10 >Reporter: Guillaume Boucherie >Assignee: Mirko Friedenhagen >Priority: Critical > Fix For: 2.11 > > Attachments: MCHANGES-334.patch > > > Trying to generate an announcement mail with Jira I get a connection timeout > exception. > When I activate debug trace I see that no proxy is used. > By debugging method setupWebClient (line 547) in RestJiraDownloader class I > see that the field proxyHost is always null so the WebClient proxy will never > be initialized properly. > I think we must add a call to getProxyInfo in doExecute method of > RestJiraDownloader before the call to setupWebClient -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
[
https://jira.codehaus.org/browse/MCHANGES-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353093#comment-353093
]
Mirko Friedenhagen commented on MCHANGES-334:
-
I think the proper way to do this is in
{{org.apache.maven.plugin.jira.RestJiraDownloader#setupWebClient}}, because
setting the proxy information is done there.
> RestJiraDownloader doesn't honor proxy settings
> ---
>
> Key: MCHANGES-334
> URL: https://jira.codehaus.org/browse/MCHANGES-334
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.10
>Reporter: Guillaume Boucherie
>Priority: Critical
> Fix For: 2.11
>
> Attachments: MCHANGES-334.patch
>
>
> Trying to generate an announcement mail with Jira I get a connection timeout
> exception.
> When I activate debug trace I see that no proxy is used.
> By debugging method setupWebClient (line 547) in RestJiraDownloader class I
> see that the field proxyHost is always null so the WebClient proxy will never
> be initialized properly.
> I think we must add a call to getProxyInfo in doExecute method of
> RestJiraDownloader before the call to setupWebClient
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-334) RestJiraDownloader doesn't honor proxy settings
[ https://jira.codehaus.org/browse/MCHANGES-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen updated MCHANGES-334: Fix Version/s: 2.11 > RestJiraDownloader doesn't honor proxy settings > --- > > Key: MCHANGES-334 > URL: https://jira.codehaus.org/browse/MCHANGES-334 > Project: Maven Changes Plugin > Issue Type: Bug > Components: jira >Affects Versions: 2.10 >Reporter: Guillaume Boucherie >Priority: Critical > Fix For: 2.11 > > Attachments: MCHANGES-334.patch > > > Trying to generate an announcement mail with Jira I get a connection timeout > exception. > When I activate debug trace I see that no proxy is used. > By debugging method setupWebClient (line 547) in RestJiraDownloader class I > see that the field proxyHost is always null so the WebClient proxy will never > be initialized properly. > I think we must add a call to getProxyInfo in doExecute method of > RestJiraDownloader before the call to setupWebClient -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-307) Check for whitespace on fixVersionIds and statusIds
[
https://jira.codehaus.org/browse/MCHANGES-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen closed MCHANGES-307.
---
Resolution: Fixed
Fixed with http://svn.apache.org/viewvc?view=revision&revision=1627117, thanks.
> Check for whitespace on fixVersionIds and statusIds
> ---
>
> Key: MCHANGES-307
> URL: https://jira.codehaus.org/browse/MCHANGES-307
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.9
>Reporter: Tobias Rübner
>Assignee: Mirko Friedenhagen
> Fix For: 2.11
>
> Attachments: MCHANGES-307.patch
>
>
> On the configuration of the maven changes plugin for the jira-report there
> are some configuration parameters that do not like whitespace.
> I think this will include component, fixVersionIds, statusIds, resolutionIds,
> typeIds and priorityIds.
> The report generation will fail with the follwing error:
> {code}
> org.apache.maven.plugin.MojoFailureException: Could not find status Closed.
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:268)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:249)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:214)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:129)
> at
> org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
> at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
> ...
> {code}
> Note the leading whitespace that came through the definition in the pom file.
> {code}
>
> org.apache.maven.plugins
> maven-changes-plugin
>
> true
> ${jira.user}
> ${jira.password}
> true
> Fixed
> Resolved, Closed
>
>
>
>
> jira-report
>
>
>
>
> {code}
> I possible solution could be to trim the whitespace.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-307) Check for whitespace on fixVersionIds and statusIds
[
https://jira.codehaus.org/browse/MCHANGES-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen reassigned MCHANGES-307:
---
Assignee: Mirko Friedenhagen
> Check for whitespace on fixVersionIds and statusIds
> ---
>
> Key: MCHANGES-307
> URL: https://jira.codehaus.org/browse/MCHANGES-307
> Project: Maven Changes Plugin
> Issue Type: Bug
> Components: jira
>Affects Versions: 2.9
>Reporter: Tobias Rübner
>Assignee: Mirko Friedenhagen
> Fix For: 2.11
>
> Attachments: MCHANGES-307.patch
>
>
> On the configuration of the maven changes plugin for the jira-report there
> are some configuration parameters that do not like whitespace.
> I think this will include component, fixVersionIds, statusIds, resolutionIds,
> typeIds and priorityIds.
> The report generation will fail with the follwing error:
> {code}
> org.apache.maven.plugin.MojoFailureException: Could not find status Closed.
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveOneItem(RestJiraDownloader.java:268)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveList(RestJiraDownloader.java:249)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.resolveIds(RestJiraDownloader.java:214)
> at
> org.apache.maven.plugin.jira.RestJiraDownloader.doExecute(RestJiraDownloader.java:129)
> at
> org.apache.maven.plugin.jira.AdaptiveJiraDownloader.doExecute(AdaptiveJiraDownloader.java:47)
> at
> org.apache.maven.plugin.jira.JiraMojo.executeReport(JiraMojo.java:367)
> ...
> {code}
> Note the leading whitespace that came through the definition in the pom file.
> {code}
>
> org.apache.maven.plugins
> maven-changes-plugin
>
> true
> ${jira.user}
> ${jira.password}
> true
> Fixed
> Resolved, Closed
>
>
>
>
> jira-report
>
>
>
>
> {code}
> I possible solution could be to trim the whitespace.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MWAR-279) WAR plugin fails during incremental build with JDK7
[
https://jira.codehaus.org/browse/MWAR-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl-Heinz Marbaise updated MWAR-279:
-
Fix Version/s: (was: 2.5)
backlog
> WAR plugin fails during incremental build with JDK7
> ---
>
> Key: MWAR-279
> URL: https://jira.codehaus.org/browse/MWAR-279
> Project: Maven WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1, 2.2
> Environment: Windows7 64bit
> maven 3.0.3
> jdk-1.7.0_03
>Reporter: Liya Katz
>Priority: Blocker
> Fix For: backlog
>
>
> Same error for war-plugin 2.2 and 2.1.1
> Appears when running incremental build with jdk 7.
> Build from clean works fine.
> From the log:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project
> xxx-web: Execution default-war of goal
> org.apache.maven.plugins:maven-war-plugin:2.1.1:war failed: Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> [ERROR] Debugging information
> [ERROR] message : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> [ERROR] cause-exception :
> com.thoughtworks.xstream.converters.reflection.ObjectAccessException
> [ERROR] cause-message : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> [ERROR] class : org.apache.maven.plugin.war.util.WebappStructure
> [ERROR] required-type : org.apache.maven.plugin.war.util.WebappStructure
> [ERROR] path: /webapp-structure
> [ERROR] ---
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on
> project skyboxview-system-web: Execution default-war of goal
> org.apache.maven.plugins:maven-war-plugin:2.1.1:war failed: Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> Debugging information
> message : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> cause-exception :
> com.thoughtworks.xstream.converters.reflection.ObjectAccessException
> cause-message : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> class : org.apache.maven.plugin.war.util.WebappStructure
> required-type : org.apache.maven.plugin.war.util.WebappStructure
> path: /webapp-structure
> ---
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:164)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-war of goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war
> failed: Cannot construct org.apache.maven.plugin.war.util.WebappStructure as
> it does not have a no-args constructor : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> Debugging information
> message : Cannot construct
> org.apache.maven.plugin.war.util.WebappStructure as it does not have a
> no-args constructor
> c
[jira] (MDEP-447) Add option to use native tar executable to unpack
[ https://jira.codehaus.org/browse/MDEP-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353091#comment-353091 ] Dan Tran commented on MDEP-447: --- a good progress at plexus-archiver 2.5 which uses commons-compress, 2.5.1 will have support for tar with softlink. > Add option to use native tar executable to unpack > - > > Key: MDEP-447 > URL: https://jira.codehaus.org/browse/MDEP-447 > Project: Maven Dependency Plugin > Issue Type: Improvement > Components: unpack, unpack-dependencies >Affects Versions: 2.8 >Reporter: Dan Tran >Assignee: Dan Tran > > This method is faster and reserve softlinks. This is very edge case. > Link to discussion at user list > http://maven.40175.n5.nabble.com/Use-native-tar-to-unpack-good-bad-idea-td5794712.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5551) check that everything compile and run fine with Java 8
[ https://jira.codehaus.org/browse/MNG-5551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=352907#comment-352907 ] Karl-Heinz Marbaise edited comment on MNG-5551 at 9/23/14 1:52 PM: --- Maven-dependency-plugin version 2.9 voting has started. So the release should be there within a few days (fixes Java 8 issue). maven-dependency-plugin version 2.9 is released. was (Author: khmarbaise): Maven-dependency-plugin version 2.9 voting has started. So the release should be there within a few days (fixes Java 8 issue). > check that everything compile and run fine with Java 8 > -- > > Key: MNG-5551 > URL: https://jira.codehaus.org/browse/MNG-5551 > Project: Maven > Issue Type: Task >Reporter: Herve Boutemy > > Java 8 will be released shortly: we need a good support as soon as possible > Some ASF Jenkins jobs are available to check and see results in a shared > place: > - > [maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8|https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/modules] > there is a [Wiki page too with some problems > tracked|https://cwiki.apache.org/confluence/display/MAVEN/Java+8+Upgrade] -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-341) Externalize JIRA server timeout values to the configuration section
[ https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mirko Friedenhagen closed MCHANGES-341. --- Resolution: Fixed We did test this version successfully internally. > Externalize JIRA server timeout values to the configuration section > --- > > Key: MCHANGES-341 > URL: https://jira.codehaus.org/browse/MCHANGES-341 > Project: Maven Changes Plugin > Issue Type: Improvement >Reporter: Boris Pavlovic >Assignee: Mirko Friedenhagen > Fix For: 2.11 > > > [Based on the StackOverflow > Question|http://stackoverflow.com/questions/25626369/how-to-configure-timeout-for-maven-changes-plugin/25627583#25627583] > > QUESTION: > I have a maven-changes-plugin configured for a build process. Sometimes, JIRA > intranet server is down and the build takes ages waiting for a long timeout > on JIRA. > Is there a way to configure the timeout? > ANSWER: > It does not appear so. The source for the RestJiraDownloader, the class that > queries JIRA for issues, has hard-coded timeout values. Lines 562-566 > indicate a connection timeout of 36 seconds and a receive timeout of 32 > seconds. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-61) Upgrade Locator URL logic to use maven-wagon.
[ https://jira.codehaus.org/browse/MCHECKSTYLE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353089#comment-353089 ] Robert Scholte commented on MCHECKSTYLE-61: --- The plugin leans heavily on Plexus-resources. Replacing it is a good thing, but depending on the solution, it will break backwards compatibility. You could give it a try yourself and share your patch. > Upgrade Locator URL logic to use maven-wagon. > - > > Key: MCHECKSTYLE-61 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-61 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Reporter: Joakim Erdfelt > Labels: plexus-resources > > Upgrade the URL location logic in the Locator to utilize the maven-wagon api. > Current logic utilizes the java URL object. > Using maven-wagon, will allow for many more potential sources, as well as > greater authorization and proxy abilities already built into maven. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5685) Profile with multiple conditions gets activated incorrectly
[
https://jira.codehaus.org/browse/MNG-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Todorov closed MNG-5685.
---
Resolution: Not A Bug
As @rfscholte pointed out, this was a mistake on my side.
> Profile with multiple conditions gets activated incorrectly
> ---
>
> Key: MNG-5685
> URL: https://jira.codehaus.org/browse/MNG-5685
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.2.2, 3.2.3
>Reporter: Martin Todorov
>
> Consider the following simple profile:
> {code}
> ...
>
> some-profile
>
>
> !skipTests
>
> false
>
> ...
>
> ...
> {code}
> I would expect that this profile will not be active by default. Furthermore,
> it will not be active if the tests are skipped.
> However, if you execute:
> {code}
> mvn help:active-profiles
> {code}
> you will see:
> {code}
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO]
>
> [INFO] Building foo-bar: baz 1.0-SNAPSHOT
> [INFO]
>
> [INFO]
> [INFO] --- maven-help-plugin:2.2:active-profiles (default-cli) @
> org.foo.bar:baz ---
> [INFO]
> Active Profiles for Project 'org.foo.bar:baz:jar:1.0-SNAPSHOT':
> The following profiles are active:
> - some-profile (source: org.foo.bar:baz:1.0-SNAPSHOT)
> {code}
> If you pass in -DskipTests, the profile gets disabled, but you shouldn't have
> to do this.
> I believe this is related to MNG-4565.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-70) Support for multiple source folders
[
https://jira.codehaus.org/browse/MCHECKSTYLE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353087#comment-353087
]
Robert Scholte commented on MCHECKSTYLE-70:
---
[~arlol], you probably already guessed the answer: since these are
compileSourceRoots, they are included as well. Maven doesn't distinguish
generated sourceroots from real sourceroots, you can hope that the generated
end up in the target-directory. Up until 2.12 you could only specify 1 source
directory, now you can have more and specify if you want.
I'd love to implement MCHECKSTYLE-187, which would solve this issue as well,
but that will have a huge impact.
> Support for multiple source folders
> ---
>
> Key: MCHECKSTYLE-70
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-70
> Project: Maven Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Jan Palmquist
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 2.13
>
>
> It would be great if this plugin would support multiple source folders added
> by http://mojo.codehaus.org/build-helper-maven-plugin/ (or similar), and by
> default inspect sources from these folders instead of just
> $\{project.build.sourceDirectory}. Correspondingly with respect to test
> sources if those are configured to be included.
> There are other plugins available solving this problem (somehow), eg:
> * http://mojo.codehaus.org/jdepend-maven-plugin/
> * http://mojo.codehaus.org/findbugs-maven-plugin/
> Maybe they can give some inspiration for how to make this possible?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-70) Support for multiple source folders
[
https://jira.codehaus.org/browse/MCHECKSTYLE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MCHECKSTYLE-70:
--
Description:
It would be great if this plugin would support multiple source folders added by
http://mojo.codehaus.org/build-helper-maven-plugin/ (or similar), and by
default inspect sources from these folders instead of just
$\{project.build.sourceDirectory}. Correspondingly with respect to test sources
if those are configured to be included.
There are other plugins available solving this problem (somehow), eg:
* http://mojo.codehaus.org/jdepend-maven-plugin/
* http://mojo.codehaus.org/findbugs-maven-plugin/
Maybe they can give some inspiration for how to make this possible?
was:
It would be great if this plugin would support multiple source folders added by
http://mojo.codehaus.org/build-helper-maven-plugin/ (or similar), and by
default inspect sources from these folders instead of just
${project.build.sourceDirectory}. Correspondingly with respect to test sources
if those are configured to be included.
There are other plugins available solving this problem (somehow), eg:
* http://mojo.codehaus.org/jdepend-maven-plugin/
* http://mojo.codehaus.org/findbugs-maven-plugin/
Maybe they can give some inspiration for how to make this possible?
> Support for multiple source folders
> ---
>
> Key: MCHECKSTYLE-70
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-70
> Project: Maven Checkstyle Plugin
> Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Jan Palmquist
>Assignee: Robert Scholte
>Priority: Minor
> Fix For: 2.13
>
>
> It would be great if this plugin would support multiple source folders added
> by http://mojo.codehaus.org/build-helper-maven-plugin/ (or similar), and by
> default inspect sources from these folders instead of just
> $\{project.build.sourceDirectory}. Correspondingly with respect to test
> sources if those are configured to be included.
> There are other plugins available solving this problem (somehow), eg:
> * http://mojo.codehaus.org/jdepend-maven-plugin/
> * http://mojo.codehaus.org/findbugs-maven-plugin/
> Maybe they can give some inspiration for how to make this possible?
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-410) Get the stylesheet file from an URL
[ https://jira.codehaus.org/browse/MJAVADOC-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353083#comment-353083 ] Anders Hammar commented on MJAVADOC-410: Having a dependency to something outside of your build (e.g. a stylesheet through and external URL) is not very good. If the external source changes, or is removed, your build will change and/or fail. > Get the stylesheet file from an URL > --- > > Key: MJAVADOC-410 > URL: https://jira.codehaus.org/browse/MJAVADOC-410 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 2.10 >Reporter: Vincent Zurczak >Priority: Minor > > Hi, > When we generate Javadoc with the maven-javadoc-plugin, we can use the > *stylesheetfile* parameter to specify a custom CSS file for the generated > HTML pages. > This file can be a local file, as well as a resource located in Maven > dependencies. However, it does not work if the parameter value is set to a > public URL (a static resource on a web server). This would be a nice > enhancement. Initially, I had created a Maven module that would contain such > resources, but it resulted in adding a lot of complexity to my release > process. Having some static resources on a web server is much more simple. > I wanted to submit a patch myself for this feature. > But I was wondering how I could do that. This > [page|http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch] > indicates we should attach a patch file to this issue. I was wondering if > proposing pull requests on the GitHub mirror was also working. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-410) Get the stylesheet file from an URL
Vincent Zurczak created MJAVADOC-410: Summary: Get the stylesheet file from an URL Key: MJAVADOC-410 URL: https://jira.codehaus.org/browse/MJAVADOC-410 Project: Maven Javadoc Plugin Issue Type: Improvement Affects Versions: 2.10 Reporter: Vincent Zurczak Priority: Minor Hi, When we generate Javadoc with the maven-javadoc-plugin, we can use the *stylesheetfile* parameter to specify a custom CSS file for the generated HTML pages. This file can be a local file, as well as a resource located in Maven dependencies. However, it does not work if the parameter value is set to a public URL (a static resource on a web server). This would be a nice enhancement. Initially, I had created a Maven module that would contain such resources, but it resulted in adding a lot of complexity to my release process. Having some static resources on a web server is much more simple. I wanted to submit a patch myself for this feature. But I was wondering how I could do that. This [page|http://maven.apache.org/guides/development/guide-m2-development.html#Creating_and_submitting_a_patch] indicates we should attach a patch file to this issue. I was wondering if proposing pull requests on the GitHub mirror was also working. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-409) Generating Javadoc no longer works with 2.10
[
https://jira.codehaus.org/browse/MJAVADOC-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353080#comment-353080
]
Ida de Groot commented on MJAVADOC-409:
---
Same issue using:
{code}
mvn -version
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-28
04:15:32+0200)
Maven home: D:\maven\apache-maven-3.1.0
Java version: 1.7.0_21, vendor: Oracle Corporation
Java home: C:\Progra~1\Java\jdk1.7.0_21\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
{code}
mvn release:perform would not work until we found out we did not manage the
version of the javadoc plugin.
Adding javadoc plugin with version 2.9.1 to the pluginManagement section made
the release:perform work again:
{code}
org.apache.maven.plugins
maven-javadoc-plugin
2.9.1
{code}
> Generating Javadoc no longer works with 2.10
>
>
> Key: MJAVADOC-409
> URL: https://jira.codehaus.org/browse/MJAVADOC-409
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: /Applications/apache-maven/apache-maven-3.0.5
> Java version: 1.6.0_65, vendor: Apple Inc.
> Java home:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"
>Reporter: Wim Deblauwe
>
> If I run javadoc using 2.9, then javadoc is generated without issue:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc}}
> However, using version 2.10, the build fails:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
> There is a very big stack trace. One of the things that is shown is this:
> {noformat}
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl
> cannot be cast to com.sun.javadoc.AnnotationTypeDoc
> [ERROR] at
> com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
> [ERROR] at
> com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> [ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> [ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> [ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
> [ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
> [ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
> @options @packages @argfile
> [ERROR]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353079#comment-353079
]
Sam Adams commented on MJAVADOC-408:
Same issue for me.
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-409) Generating Javadoc no longer works with 2.10
[
https://jira.codehaus.org/browse/MJAVADOC-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353077#comment-353077
]
Chris Gamache commented on MJAVADOC-409:
I have the same issue. FWIW, the problem is the same using Maven 3.0.5 and
Maven 3.2.2.
> Generating Javadoc no longer works with 2.10
>
>
> Key: MJAVADOC-409
> URL: https://jira.codehaus.org/browse/MJAVADOC-409
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Apache Maven 3.0.5
> (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
> Maven home: /Applications/apache-maven/apache-maven-3.0.5
> Java version: 1.6.0_65, vendor: Apple Inc.
> Java home:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"
>Reporter: Wim Deblauwe
>
> If I run javadoc using 2.9, then javadoc is generated without issue:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc}}
> However, using version 2.10, the build fails:
> {{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
> There is a very big stack trace. One of the things that is shown is this:
> {noformat}
> [ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl
> cannot be cast to com.sun.javadoc.AnnotationTypeDoc
> [ERROR] at
> com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
> [ERROR] at
> com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
> [ERROR] at
> com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
> [ERROR] at
> com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
> [ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
> [ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [ERROR] at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> [ERROR] at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> [ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
> [ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
> [ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
> [ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
> [ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
> [ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
> [ERROR]
> [ERROR] Command line was:
> /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
> @options @packages @argfile
> [ERROR]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-409) Generating Javadoc no longer works with 2.10
[
https://jira.codehaus.org/browse/MJAVADOC-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wim Deblauwe updated MJAVADOC-409:
--
Description:
If I run javadoc using 2.9, then javadoc is generated without issue:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.9:javadoc}}
However, using version 2.10, the build fails:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
There is a very big stack trace. One of the things that is shown is this:
{noformat}
[ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
be cast to com.sun.javadoc.AnnotationTypeDoc
[ERROR] at
com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
[ERROR] at
com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
[ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
[ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
[ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
[ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
@options @packages @argfile
[ERROR]
{noformat}
was:
If I run javadoc using 2.9, then javadoc is generated without issue:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
However, using version 2.10, the build fails:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
There is a very big stack trace. One of the things that is shown is this:
{noformat}
[ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
be cast to com.sun.javadoc.AnnotationTypeDoc
[ERROR] at
com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
[ERROR] at
com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
[ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
[ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
[ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
[ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
@options @packages @argfile
[ERROR]
{noformat}
> Generating Javadoc no longer works with 2.10
>
>
> Key: MJAVADOC-409
>
[jira] (MJAVADOC-409) Generating Javadoc no longer works with 2.10
Wim Deblauwe created MJAVADOC-409:
-
Summary: Generating Javadoc no longer works with 2.10
Key: MJAVADOC-409
URL: https://jira.codehaus.org/browse/MJAVADOC-409
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.10
Environment: Apache Maven 3.0.5
(r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 14:51:28+0100)
Maven home: /Applications/apache-maven/apache-maven-3.0.5
Java version: 1.6.0_65, vendor: Apple Inc.
Java home: /Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.9.4", arch: "x86_64", family: "mac"
Reporter: Wim Deblauwe
If I run javadoc using 2.9, then javadoc is generated without issue:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
However, using version 2.10, the build fails:
{{mvn org.apache.maven.plugins:maven-javadoc-plugin:2.10:javadoc}}
There is a very big stack trace. One of the things that is shown is this:
{noformat}
[ERROR] java.lang.ClassCastException: com.sun.tools.javadoc.ClassDocImpl cannot
be cast to com.sun.javadoc.AnnotationTypeDoc
[ERROR] at
com.sun.tools.javadoc.AnnotationDescImpl.annotationType(AnnotationDescImpl.java:46)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapAnnotations(ClassUseMapper.java:439)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.mapExecutable(ClassUseMapper.java:297)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.util.ClassUseMapper.(ClassUseMapper.java:196)
[ERROR] at
com.sun.tools.doclets.formats.html.ClassUseWriter.generate(ClassUseWriter.java:109)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.generateOtherFiles(HtmlDoclet.java:92)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.startGeneration(AbstractDoclet.java:122)
[ERROR] at
com.sun.tools.doclets.internal.toolkit.AbstractDoclet.start(AbstractDoclet.java:64)
[ERROR] at
com.sun.tools.doclets.formats.html.HtmlDoclet.start(HtmlDoclet.java:42)
[ERROR] at com.sun.tools.doclets.standard.Standard.start(Standard.java:23)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:597)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.invoke(DocletInvoker.java:269)
[ERROR] at com.sun.tools.javadoc.DocletInvoker.start(DocletInvoker.java:143)
[ERROR] at com.sun.tools.javadoc.Start.parseAndExecute(Start.java:340)
[ERROR] at com.sun.tools.javadoc.Start.begin(Start.java:128)
[ERROR] at com.sun.tools.javadoc.Main.execute(Main.java:41)
[ERROR] at com.sun.tools.javadoc.Main.main(Main.java:31)
[ERROR]
[ERROR] Command line was:
/Library/Java/JavaVirtualMachines/1.6.0_65-b14-462.jdk/Contents/Home/bin/javadoc
@options @packages @argfile
[ERROR]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.
[
https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353060#comment-353060
]
Nicolas Liochon commented on SUREFIRE-798:
--
Yeah, it's fine for me. The 2.17 way of presenting test results is great.
> JUnit47 provider could print immediatly the test class name, as JUnit4,
> instead of waiting for the test to finish.
> --
>
> Key: SUREFIRE-798
> URL: https://jira.codehaus.org/browse/SUREFIRE-798
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: Nicolas Liochon
>Priority: Minor
>
> With a test that takes some time, for example
> {noformat}
> public class Test0 {
> @Test
> public void testT0() throws Exception {
> Thread.sleep(6000);
> }
> }
> {noformat}
> With JUnit4, we have first
> {noformat}Running Test0{noformat}
> Then, 6 seconds later
> {noformat}Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 6.002 sec{noformat}
> With JUnit47, we wait for 6 seconds, then the two lines appear simultaneously.
> The former behavior is better, because it allows to kill the test if we know
> that this test should not take so long. It also gives the feeling that you
> know what's going on :-).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHANGES-341) Externalize JIRA server timeout values to the configuration section
[ https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353059#comment-353059 ] Mirko Friedenhagen commented on MCHANGES-341: - I now had the chance to test my changes and had commit another patch http://svn.apache.org/viewvc?view=revision&revision=1626972, I uploaded the new SNAPSHOT as well (https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-changes-plugin/2.11-SNAPSHOT/maven-changes-plugin-2.11-20140923.102115-199.pom) > Externalize JIRA server timeout values to the configuration section > --- > > Key: MCHANGES-341 > URL: https://jira.codehaus.org/browse/MCHANGES-341 > Project: Maven Changes Plugin > Issue Type: Improvement >Reporter: Boris Pavlovic >Assignee: Mirko Friedenhagen > Fix For: 2.11 > > > [Based on the StackOverflow > Question|http://stackoverflow.com/questions/25626369/how-to-configure-timeout-for-maven-changes-plugin/25627583#25627583] > > QUESTION: > I have a maven-changes-plugin configured for a build process. Sometimes, JIRA > intranet server is down and the build takes ages waiting for a long timeout > on JIRA. > Is there a way to configure the timeout? > ANSWER: > It does not appear so. The source for the RestJiraDownloader, the class that > queries JIRA for issues, has hard-coded timeout values. Lines 562-566 > indicate a connection timeout of 36 seconds and a receive timeout of 32 > seconds. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHANGES-341) Externalize JIRA server timeout values to the configuration section
[ https://jira.codehaus.org/browse/MCHANGES-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353059#comment-353059 ] Mirko Friedenhagen edited comment on MCHANGES-341 at 9/23/14 5:21 AM: -- I now had the chance to test my changes and had to commit another patch http://svn.apache.org/viewvc?view=revision&revision=1626972, I uploaded the new SNAPSHOT as well (https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-changes-plugin/2.11-SNAPSHOT/maven-changes-plugin-2.11-20140923.102115-199.pom) was (Author: mfriedenhagen): I now had the chance to test my changes and had commit another patch http://svn.apache.org/viewvc?view=revision&revision=1626972, I uploaded the new SNAPSHOT as well (https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-changes-plugin/2.11-SNAPSHOT/maven-changes-plugin-2.11-20140923.102115-199.pom) > Externalize JIRA server timeout values to the configuration section > --- > > Key: MCHANGES-341 > URL: https://jira.codehaus.org/browse/MCHANGES-341 > Project: Maven Changes Plugin > Issue Type: Improvement >Reporter: Boris Pavlovic >Assignee: Mirko Friedenhagen > Fix For: 2.11 > > > [Based on the StackOverflow > Question|http://stackoverflow.com/questions/25626369/how-to-configure-timeout-for-maven-changes-plugin/25627583#25627583] > > QUESTION: > I have a maven-changes-plugin configured for a build process. Sometimes, JIRA > intranet server is down and the build takes ages waiting for a long timeout > on JIRA. > Is there a way to configure the timeout? > ANSWER: > It does not appear so. The source for the RestJiraDownloader, the class that > queries JIRA for issues, has hard-coded timeout values. Lines 562-566 > indicate a connection timeout of 36 seconds and a receive timeout of 32 > seconds. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MPMD-190) Seperate CPD configuration from PMD i.e. exclude/include paths
John Patrick created MPMD-190: - Summary: Seperate CPD configuration from PMD i.e. exclude/include paths Key: MPMD-190 URL: https://jira.codehaus.org/browse/MPMD-190 Project: Maven PMD Plugin Issue Type: Bug Components: CPD Affects Versions: 3.2 Environment: n/a Reporter: John Patrick CPD highlights lots of warnings in our jpa entity packages and also out dto builders. This is correct lots of tables have the same fields. We can exclude them but this also excludes pmd, ideally we just want to exclude the following paths from CPD but still have PMD checked on them. **/data/entity/*.java **/data/builder/*.java I see two options, either both pmd and cpd get their own nested , or cpd it split into it's own top level plugin. I realise splitting the plugin is a lot of work so giving the option to have their own nest configuration might be simpler... We have about 1000 cpd warnings, of which 90% are specifically around jpa entities or dto builders. Jenkins reports issues but we have the threshold so high it makes it useless... -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-712) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MASSEMBLY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-712: -- Description: [Release Notes plexus-archiver 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress was: Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress > Update version of plexus-archiver to 2.5 > > > Key: MASSEMBLY-712 > URL: https://jira.codehaus.org/browse/MASSEMBLY-712 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Release Notes plexus-archiver > 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-182) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MJAR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MJAR-182: - Description: [Release Notes plexus-archiver 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress was: Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress > Update version of plexus-archiver to 2.5 > > > Key: MJAR-182 > URL: https://jira.codehaus.org/browse/MJAR-182 > Project: Maven JAR Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5.1 > > > [Release Notes plexus-archiver > 2.5|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MWAR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MWAR-320: - Description: [Update plexus-archiver to 2.5.|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress was: Update plexus-archiver to 2.5. Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress > Update version of plexus-archiver to 2.5 > > > Key: MWAR-320 > URL: https://jira.codehaus.org/browse/MWAR-320 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > [Update plexus-archiver to > 2.5.|https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11440&version=20630] > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-182) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MJAR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MJAR-182: - Fix Version/s: 2.5.1 > Update version of plexus-archiver to 2.5 > > > Key: MJAR-182 > URL: https://jira.codehaus.org/browse/MJAR-182 > Project: Maven JAR Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5.1 > > > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-182) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MJAR-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MJAR-182. Resolution: Fixed Assignee: Kristian Rosenvold Fixed by Kristian Rosenvold [r1626943|http://svn.apache.org/r1626943]. > Update version of plexus-archiver to 2.5 > > > Key: MJAR-182 > URL: https://jira.codehaus.org/browse/MJAR-182 > Project: Maven JAR Plugin > Issue Type: Improvement >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5.1 > > > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAR-182) Update version of plexus-archiver to 2.5
Karl-Heinz Marbaise created MJAR-182: Summary: Update version of plexus-archiver to 2.5 Key: MJAR-182 URL: https://jira.codehaus.org/browse/MJAR-182 Project: Maven JAR Plugin Issue Type: Improvement Reporter: Karl-Heinz Marbaise Priority: Minor Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-712) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MASSEMBLY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MASSEMBLY-712. - Resolution: Fixed Assignee: Kristian Rosenvold Fixed by Kristian Rosenvold [r1626943|http://svn.apache.org/r1626943] > Update version of plexus-archiver to 2.5 > > > Key: MASSEMBLY-712 > URL: https://jira.codehaus.org/browse/MASSEMBLY-712 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-712) Update version of plexus-archiver to 2.5
Karl-Heinz Marbaise created MASSEMBLY-712: - Summary: Update version of plexus-archiver to 2.5 Key: MASSEMBLY-712 URL: https://jira.codehaus.org/browse/MASSEMBLY-712 Project: Maven Assembly Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Karl-Heinz Marbaise Priority: Minor Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MASSEMBLY-712) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MASSEMBLY-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MASSEMBLY-712: -- Fix Version/s: 2.5 > Update version of plexus-archiver to 2.5 > > > Key: MASSEMBLY-712 > URL: https://jira.codehaus.org/browse/MASSEMBLY-712 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MWAR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MWAR-320: - Description: Update plexus-archiver to 2.5. Release Notes plexus-archiver 2.5 * Bugs: ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files ** [PLXCOMP-238] - CRC Failure if compress=false * Improvements: ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes ** [PLXCOMP-240] - Convert everything to commons-compress was:Update plexus-archiver to 2.5. > Update version of plexus-archiver to 2.5 > > > Key: MWAR-320 > URL: https://jira.codehaus.org/browse/MWAR-320 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > Update plexus-archiver to 2.5. > Release Notes plexus-archiver 2.5 > * Bugs: > ** [PLXCOMP-13] - Plexus Archiver fails on certain Jars > ** [PLXCOMP-205] - Tar unarchiver does not respect includes/excludes flags > ** [PLXCOMP-216] - Unarchiver extracts files into wrong directory > ** [PLXCOMP-236] - ZipUnArchiver fails to extract large (>4GB) ZIP files > ** [PLXCOMP-238] - CRC Failure if compress=false > * Improvements: > ** [PLXCOMP-153] - TarUnArchiver does not support includes/excludes > ** [PLXCOMP-240] - Convert everything to commons-compress -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MWAR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise closed MWAR-320. Resolution: Fixed Assignee: Kristian Rosenvold Fixed in [r1626943|http://svn.apache.org/r1626943]. > Update version of plexus-archiver to 2.5 > > > Key: MWAR-320 > URL: https://jira.codehaus.org/browse/MWAR-320 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > Update plexus-archiver to 2.5. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MWAR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353047#comment-353047 ] Karl-Heinz Marbaise edited comment on MWAR-320 at 9/23/14 3:43 AM: --- Fixed by Kristian Rosenvold in [r1626943|http://svn.apache.org/r1626943]. was (Author: khmarbaise): Fixed in [r1626943|http://svn.apache.org/r1626943]. > Update version of plexus-archiver to 2.5 > > > Key: MWAR-320 > URL: https://jira.codehaus.org/browse/MWAR-320 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Assignee: Kristian Rosenvold >Priority: Minor > Fix For: 2.5 > > > Update plexus-archiver to 2.5. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
Karl-Heinz Marbaise created MWAR-320: Summary: Update version of plexus-archiver to 2.5 Key: MWAR-320 URL: https://jira.codehaus.org/browse/MWAR-320 Project: Maven WAR Plugin Issue Type: Improvement Affects Versions: 2.5 Reporter: Karl-Heinz Marbaise Priority: Minor Update plexus-archiver to 2.5. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MWAR-320) Update version of plexus-archiver to 2.5
[ https://jira.codehaus.org/browse/MWAR-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl-Heinz Marbaise updated MWAR-320: - Fix Version/s: 2.5 > Update version of plexus-archiver to 2.5 > > > Key: MWAR-320 > URL: https://jira.codehaus.org/browse/MWAR-320 > Project: Maven WAR Plugin > Issue Type: Improvement >Affects Versions: 2.5 >Reporter: Karl-Heinz Marbaise >Priority: Minor > Fix For: 2.5 > > > Update plexus-archiver to 2.5. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SUREFIRE-798) JUnit47 provider could print immediatly the test class name, as JUnit4, instead of waiting for the test to finish.
[
https://jira.codehaus.org/browse/SUREFIRE-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353046#comment-353046
]
Tibor Digana commented on SUREFIRE-798:
---
Nicolas, Can we close this as designed?
Another alternative with forked process sounds like another bug.
BTW, Since of surefire 2.17 you can define the timeout in Junit 4.7+ parallel.
It allows you to see previous logs and gives you chance to see what tests have
started/executed till the timeout.
> JUnit47 provider could print immediatly the test class name, as JUnit4,
> instead of waiting for the test to finish.
> --
>
> Key: SUREFIRE-798
> URL: https://jira.codehaus.org/browse/SUREFIRE-798
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Junit 4.7+ (parallel) support
>Affects Versions: 2.10
> Environment: all
>Reporter: Nicolas Liochon
>Priority: Minor
>
> With a test that takes some time, for example
> {noformat}
> public class Test0 {
> @Test
> public void testT0() throws Exception {
> Thread.sleep(6000);
> }
> }
> {noformat}
> With JUnit4, we have first
> {noformat}Running Test0{noformat}
> Then, 6 seconds later
> {noformat}Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed:
> 6.002 sec{noformat}
> With JUnit47, we wait for 6 seconds, then the two lines appear simultaneously.
> The former behavior is better, because it allows to kill the test if we know
> that this test should not take so long. It also gives the feeling that you
> know what's going on :-).
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MNG-1388) Transitive Dependencies in a profile are not used
[ https://jira.codehaus.org/browse/MNG-1388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353044#comment-353044 ] Wiebke Timm commented on MNG-1388: -- *bump* > Transitive Dependencies in a profile are not used > - > > Key: MNG-1388 > URL: https://jira.codehaus.org/browse/MNG-1388 > Project: Maven > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 2.0 > Environment: Windows XP using Maven 2.0. >Reporter: Damian Bradicich > > I have a jar project file that defines a dependency inside a certain profile. > If I then include that project inside of another war project, the > dependencies defined in the jar project's profile isn't getting transferred > over to the war. > Ie we have this: > A depends on SQL or Oracle depending on profile > B depends on A. > If sql profile is active, I would expect that when I build B, it pulls > the transitive dependancy on sql from A. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-408) changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
[
https://jira.codehaus.org/browse/MJAVADOC-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=353042#comment-353042
]
jeff porter commented on MJAVADOC-408:
--
I've had the same issue: see : http://jira.codehaus.org/browse/MJAVADOC-407
And yep with 100+ repo's it is a huge pain to specify the javadoc version.
> changing maven-javadoc-plugin from version 2.9.1 to 2.10 breaks the build
> -
>
> Key: MJAVADOC-408
> URL: https://jira.codehaus.org/browse/MJAVADOC-408
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10
> Environment: Linux, Windows 7, Oracle Java 1.6.0_45, maven 3.0.5
>Reporter: Volker Seibt
>Priority: Critical
> Attachments: console.log, pom.xml, pom.xml
>
>
> build is startet with {{mvn -U clean deploy -DperformRelease=true}}
> and worked fine for several weeks without any changes.
> From today it produces the content of the attached console.log.
> We did not specify a version for maven-javadoc-plugin. After secifying
> maven-javadoc-plugin:2.9.1 in the parent pom everything works fine again.
> (pom.xml (12 kB) - parent-pom, pom.xml (3 kB) pom of project which breaks the
> build
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
