[jira] [Created] (MCHECKSTYLE-296) Issue tracking has stale link
Andrew Gaul created MCHECKSTYLE-296: --- Summary: Issue tracking has stale link Key: MCHECKSTYLE-296 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-296 Project: Maven Checkstyle Plugin Issue Type: Improvement Reporter: Andrew Gaul Priority: Minor https://maven.apache.org/plugins/maven-checkstyle-plugin/issue-tracking.html links to: http://jira.codehaus.org/browse/MCHECKSTYLE instead of: https://issues.apache.org/jira/browse/MCHECKSTYLE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
Andrew Gaul created MCHECKSTYLE-297: --- Summary: pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566156#comment-14566156 ] ASF GitHub Bot commented on MCHECKSTYLE-297: GitHub user andrewgaul opened a pull request: https://github.com/apache/maven-plugins/pull/53 MCHECKSTYLE-297: Add licenses stanza This allows license compliance tools like VersionEye to categorize dependencies. You can merge this pull request into a Git repository by running: $ git pull https://github.com/andrewgaul/maven-plugins licenses-stanza Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-plugins/pull/53.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #53 commit 19ac6f71a8cfbc113b3857e84a773fdf749ed35a Author: Andrew Gaul and...@gaul.org Date: 2015-05-30T19:18:38Z MCHECKSTYLE-297: Add licenses stanza This allows license compliance tools like VersionEye to categorize dependencies. pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MSHADE-189) Null Pointer Exception when minimizeJar set to true (Maven 3.3.1)
[
https://issues.apache.org/jira/browse/MSHADE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566231#comment-14566231
]
Michael Ennen commented on MSHADE-189:
--
I was running mvn install -e -X from the terminal built into IntelliJ IDEA.
Sorry about that. I tried using the regular windows terminal (cmd.exe) and here
is the stack trace now:
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
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.MojoExecutionException: Error creating
shaded jar: null
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:566)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
... 20 more
Caused by: java.lang.RuntimeException
at org.objectweb.asm.MethodVisitor.visitParameter(Unknown Source)
at org.objectweb.asm.MethodVisitor.visitParameter(Unknown Source)
at org.objectweb.asm.ClassReader.b(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.objectweb.asm.ClassReader.accept(Unknown Source)
at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:194)
at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:130)
at
org.apache.maven.plugins.shade.filter.MinijarFilter.addDependencyToClasspath(MinijarFilter.java:101)
at
org.apache.maven.plugins.shade.filter.MinijarFilter.init(MinijarFilter.java:81)
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:805)
at
org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:458)
... 22 more
Null Pointer Exception when minimizeJar set to true (Maven 3.3.1)
-
Key: MSHADE-189
URL: https://issues.apache.org/jira/browse/MSHADE-189
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 2.3
Environment: Windows 7
Reporter: Michael Ennen
Fix For: waiting-for-feedback
Maven version info:
Apache Maven 3.3.1 (cab6659f9874fa96462afef40fcf6bc033d58c1c;
2015-03-13T13:10:27-07:00)
Maven home: C:\apache-maven-3.3.1
Java version: 1.8.0_40, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_40\jre
Default locale: en_US, platform encoding: Cp1252
OS name: windows 7, version: 6.1, arch: amd64, family: dos
Ran maven with:
install -e -X
POM:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-shade-plugin/artifactId
version2.3/version
executions
execution
idshade-core/id
phasepackage/phase
goals
goalshade/goal
/goals
configuration
minimizeJartrue/minimizeJar
dependencyReducedPomLocation${project.build.directory}/dependency-reduced-pom.xml/dependencyReducedPomLocation
/configuration
/execution
/executions
/plugin
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:2.3:shade (shade-core) on project
core: Error
[jira] [Commented] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566278#comment-14566278 ] ASF GitHub Bot commented on MCHECKSTYLE-297: Github user andrewgaul closed the pull request at: https://github.com/apache/maven-plugins/pull/53 pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MCHECKSTYLE-297. --- Resolution: Won't Fix pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566208#comment-14566208 ] Karl Heinz Marbaise edited comment on MCHECKSTYLE-297 at 5/30/15 9:37 PM: -- The [ASF parent|http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?view=markup] contains the correct license tag from which the checkstyle plugin etc. is inheriting. maven-checkstyle-plugin inherits from maven-plugin (parent) where maven-plugin parent inherits from maven parent and from ASF.. http://maven.apache.org/pom/ That's the idea of a general parent(s) to avoid repeating several things which is the same for a large number of project. So there is no need to add the license entry into the maven-checkstyle-plugin pom file. was (Author: khmarbaise): The [ASF parent|http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?view=markup] contains the correct license tag from which the checkstyle plugin etc. are inheriting. That's the idea of a general parent to avoid repeating several things which is the same for a large number of project. So there is no need to add the license entry into the maven-checkstyle-plugin pom file. pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566277#comment-14566277 ] Andrew Gaul commented on MCHECKSTYLE-297: - Thank you for your feedback! I filed an issue with VersionEye: https://bitbucket.org/versioneye/versioneye/issue/82/license-not-recognized-for-maven pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-297) pom.xml does not specify licenses stanza
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566208#comment-14566208 ] Karl Heinz Marbaise commented on MCHECKSTYLE-297: - The [ASF parent|http://svn.apache.org/viewvc/maven/pom/tags/apache-16/pom.xml?view=markup] contains the correct license tag from which the checkstyle plugin etc. are inheriting. That's the idea of a general parent to avoid repeating several things which is the same for a large number of project. So there is no need to add the license entry into the maven-checkstyle-plugin pom file. pom.xml does not specify licenses stanza Key: MCHECKSTYLE-297 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-297 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.15 Reporter: Andrew Gaul Priority: Minor This allows license compliance tools like VersionEye to categorize dependencies. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MCHECKSTYLE-296) Issue tracking has stale link
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14566204#comment-14566204 ] Karl Heinz Marbaise commented on MCHECKSTYLE-296: - The pom file is already changed according to the new location, but the web site of the plugin will be published with the next next release (2.16) accordingly. Issue tracking has stale link - Key: MCHECKSTYLE-296 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-296 Project: Maven Checkstyle Plugin Issue Type: Improvement Reporter: Andrew Gaul Priority: Minor https://maven.apache.org/plugins/maven-checkstyle-plugin/issue-tracking.html links to: http://jira.codehaus.org/browse/MCHECKSTYLE instead of: https://issues.apache.org/jira/browse/MCHECKSTYLE -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MCOMPILER-240) Generated sources directory should not be added to compiler's source roots
[
https://issues.apache.org/jira/browse/MCOMPILER-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Varga updated MCOMPILER-240:
--
Affects Version/s: 3.3
Generated sources directory should not be added to compiler's source roots
--
Key: MCOMPILER-240
URL: https://issues.apache.org/jira/browse/MCOMPILER-240
Project: Maven Compiler Plugin
Issue Type: Bug
Affects Versions: 3.2, 3.3
Environment: Apache Maven 3.2.5
(12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T18:29:23+01:00)
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-11M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
Java(TM) SE Runtime Environment (build 1.7.0_45-b18)
Java HotSpot(TM) 64-Bit Server VM (build 24.45-b08, mixed mode)
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
Reporter: Tibor Varga
Attachments:
Generated_sources_directory_added_to_source_roots_after_compilation.patch,
code-generation-test-case.tar.bz2
I am using annotation processors with Maven and I keep getting errors when
compiling with generated sources already present from a previous run.
I have modified one of the test cases submitted for
[MCOMPILER-157|http://jira.codehaus.org/browse/MCOMPILER-157] to induce the
error by generating a source file _as source file_ rather than as a resource.
Untar the test case and run {{mvn clean test -q mvn test -q}} to verify.
What I found is that {{AbstractCompilerMojo}} in version 3.2 of the compiler
plugin adds the generated sources directory to the compiler's source root
list, and that has two undesirable effects:
# Sources generated in the previous run will be stale the next time around
and cause recompilation.
# The compiler will consider the previously generated source files to be
initial inputs.
The first one is mostly harmless but the second one is deadly, as it breaks
the processing environment of the annotation processors.
From the {{javax.annotation.Filer}} documentation in JDK 8:
bq. During each run of an annotation processing tool, a file with a given
pathname may be created only once. Any subsequent attempt to create the same
file during a run will throw a FilerException [...] The initial inputs to the
tool are considered to be created by the zeroth round; therefore, attempting
to create a source or class file corresponding to one of those inputs will
result in a FilerException.
Thus by adding the generated sources directory to the compiler's source
roots, the compiler plugin causes annotation processors to inadvertently
break their contract with the compiler.
I get the expected behavior when lines 511-540 in {{AbstractCompilerMojo}}
are moved after the compiler invocation, say to line 806. See the attached
patch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MWAR-346) Fix broken links
Johannes Ernst created MWAR-346: --- Summary: Fix broken links Key: MWAR-346 URL: https://issues.apache.org/jira/browse/MWAR-346 Project: Maven WAR Plugin Issue Type: Documentation Reporter: Johannes Ernst Page https://maven.apache.org/plugins/maven-war-plugin/ bottom: link Exclusion of Maven Descriptors does not go to https://maven.apache.org/plugins/maven-war-plugin/http://maven.apache.org/guides/mini/guide-archive-configuration.html Page https://maven.apache.org/plugins/maven-war-plugin/issue-tracking.html: link to issues.apache.org not codehaus. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-192) Upgrade maven-invoker to 1.10
[ https://issues.apache.org/jira/browse/MSHADE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-192: --- Environment: (was: Upgrade maven-invoker to 1.10) Upgrade maven-invoker to 1.10 - Key: MSHADE-192 URL: https://issues.apache.org/jira/browse/MSHADE-192 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 2.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MSHADE-192) Upgrade maven-invoker to 1.10
[ https://issues.apache.org/jira/browse/MSHADE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHADE-192: --- Description: Upgrade maven-invoker to 1.10 Upgrade maven-invoker to 1.10 - Key: MSHADE-192 URL: https://issues.apache.org/jira/browse/MSHADE-192 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 2.4 Upgrade maven-invoker to 1.10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHADE-192) Upgrade maven-invoker to 1.10
Karl Heinz Marbaise created MSHADE-192: -- Summary: Upgrade maven-invoker to 1.10 Key: MSHADE-192 URL: https://issues.apache.org/jira/browse/MSHADE-192 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 2.4 Environment: Upgrade maven-invoker to 1.10 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 2.4 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (MSHADE-192) Upgrade maven-invoker to 1.10
[ https://issues.apache.org/jira/browse/MSHADE-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise resolved MSHADE-192. Resolution: Fixed Fixed in [r1682588|http://svn.apache.org/r1682588] Upgrade maven-invoker to 1.10 - Key: MSHADE-192 URL: https://issues.apache.org/jira/browse/MSHADE-192 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 2.4 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 2.4 Upgrade maven-invoker to 1.10 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
