[jira] (MNG-5518) @Parameter annotation requires property element to use command-line -D
Robert Patrick created MNG-5518: --- Summary: @Parameter annotation requires property element to use command-line -D Key: MNG-5518 URL: https://jira.codehaus.org/browse/MNG-5518 Project: Maven 2 & 3 Issue Type: Bug Components: Plugin API Affects Versions: 3.1.0, 3.0.4 Environment: Windows 7 Pro 64 bit, JDK 1.7.0_40 Reporter: Robert Patrick Attachments: annotations.zip When writing a plugin using the Maven Java annotations, the @Parameter annotation currently requires the property element to allow the goal to receive configuration information from the command-line using -DparamName=value even though the goal works fine without it when using a POM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5518) @Parameter annotation requires property element to use command-line -D
[ https://jira.codehaus.org/browse/MNG-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333061#comment-333061 ] Anders Hammar commented on MNG-5518: I think this is as intended. Some params we might not want configurable from command line. Possibly the javadocs should be improved here? > @Parameter annotation requires property element to use command-line -D > -- > > Key: MNG-5518 > URL: https://jira.codehaus.org/browse/MNG-5518 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.0.4, 3.1.0 > Environment: Windows 7 Pro 64 bit, JDK 1.7.0_40 >Reporter: Robert Patrick > Attachments: annotations.zip > > > When writing a plugin using the Maven Java annotations, the @Parameter > annotation currently requires the property element to allow the goal to > receive configuration information from the command-line using > -DparamName=value even though the goal works fine without it when using a POM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5518) @Parameter annotation requires property element to use command-line -D
[ https://jira.codehaus.org/browse/MNG-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333062#comment-333062 ] Robert Patrick commented on MNG-5518: - This is a behavior change from plugins using the javadoc-style annotations, which supported all parameters being expressed from the command-line. Given that I can always specify them from a POM, I don't understand why it is important to not allow me to specify them from the command-line. > @Parameter annotation requires property element to use command-line -D > -- > > Key: MNG-5518 > URL: https://jira.codehaus.org/browse/MNG-5518 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.0.4, 3.1.0 > Environment: Windows 7 Pro 64 bit, JDK 1.7.0_40 >Reporter: Robert Patrick > Attachments: annotations.zip > > > When writing a plugin using the Maven Java annotations, the @Parameter > annotation currently requires the property element to allow the goal to > receive configuration information from the command-line using > -DparamName=value even though the goal works fine without it when using a POM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5518) @Parameter annotation requires property element to use command-line -D
[ https://jira.codehaus.org/browse/MNG-5518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333064#comment-333064 ] Anders Hammar commented on MNG-5518: IIRC you had to specify it in a similar fassion with the old javadoc-style annotations as well. Sometimes you don't want a parameter to be specifiable from command-line because it would break some best practice, such as reproducibility for example. > @Parameter annotation requires property element to use command-line -D > -- > > Key: MNG-5518 > URL: https://jira.codehaus.org/browse/MNG-5518 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugin API >Affects Versions: 3.0.4, 3.1.0 > Environment: Windows 7 Pro 64 bit, JDK 1.7.0_40 >Reporter: Robert Patrick > Attachments: annotations.zip > > > When writing a plugin using the Maven Java annotations, the @Parameter > annotation currently requires the property element to allow the goal to > receive configuration information from the command-line using > -DparamName=value even though the goal works fine without it when using a POM. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5517) Supporting semver like syntax for tag
[ https://jira.codehaus.org/browse/MNG-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333069#comment-333069 ] Dennis Lundberg commented on MNG-5517: -- As far as I understand it, version ranges are not part of the Semantic Versioning specification at all. See http://semver.org/ The page you refer to contains conventions for the node-js project, which has their own style for specifying version ranges. > Supporting semver like syntax for tag > --- > > Key: MNG-5517 > URL: https://jira.codehaus.org/browse/MNG-5517 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Dependencies, POM >Reporter: Vijay Dharap >Priority: Minor > > node js and its corresponding package manager - npm - follows semvar notation > to depict the dependencies. > The supported syntax variations for version specification can be seen here. > https://github.com/isaacs/node-semver#ranges > I find their syntax to be much more intuitive and subsequently user friendly > than what is followed in current maven dependency tag > (http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-project-dependencies.html#pom-relationships-sect-version-ranges). > Hope we can make the pom xml little more user friendly by adapting similar > version specification syntax. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-215) Add config parameter "skipTest", deprecate "skip"
Matthew Adams created MCOMPILER-215: --- Summary: Add config parameter "skipTest", deprecate "skip" Key: MCOMPILER-215 URL: https://jira.codehaus.org/browse/MCOMPILER-215 Project: Maven Compiler Plugin Issue Type: Improvement Reporter: Matthew Adams Priority: Minor Currently, the name of the config parameter to skip test compilation is "skip". Issue MCOMPILER-132 provided the config parameter "skipMain" to skip main compilation. For symmetry and the principle of least surprise, the parameter "skip" should be deprecated and a new parameter, "skipTest", should be added, which would behave exactly as "skip" does today. Parameter "skip" should be supported indefinitely; a warning might be nice, directing the developer to the new "skipTest" config parameter. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-377) Unable to access the package-list file
Archimedes Trajano created MJAVADOC-377:
---
Summary: Unable to access the package-list file
Key: MJAVADOC-377
URL: https://jira.codehaus.org/browse/MJAVADOC-377
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.9.1
Environment: Windows
Reporter: Archimedes Trajano
Priority: Minor
Getting the following warning (not an error that stops the build, but I am
trying to figure out how to get rid of it.)
Javadoc Warnings Unable to access the package-list file at
.../target/javadoc-bundle-options/
The configuration looks like
true
false
false
true
private
org.umlgraph.doclet.UmlGraphDoc
org.umlgraph
umlgraph
${umlgraph-doclet.version}
-views
true
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5519) org.apache.maven.plugins.annotations.Parameter has incorrect RetentionPolicy
Martin Gainty created MNG-5519:
--
Summary: org.apache.maven.plugins.annotations.Parameter has
incorrect RetentionPolicy
Key: MNG-5519
URL: https://jira.codehaus.org/browse/MNG-5519
Project: Maven 2 & 3
Issue Type: Bug
Components: Plugin API
Affects Versions: 3.0.5
Environment: JDK 1.7
MAVEN 3.0.5
Reporter: Martin Gainty
package org.apache.maven.plugins.annotations;
import java.lang.annotation.RetentionPolicy;
@Documented
@Retention( RetentionPolicy.CLASS )
@Target( { ElementType.FIELD } )
@Inherited
public @interface Parameter
RetentionPolicy parameters:
CLASS
Annotations are to be recorded in the class file by the compiler but need NOT
be retained by the VM at run time.
RUNTIME
Annotations are to be recorded in the class file by the compiler and RETAINED
by the VM at run time, so they may be read reflectively.
SOURCE
Annotations are to be discarded by the compiler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5520) RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
Martin Gainty created MNG-5520:
--
Summary: RuntimePolicy is incorrect for
org.apache.maven.plugins.annotations.Parameter
Key: MNG-5520
URL: https://jira.codehaus.org/browse/MNG-5520
Project: Maven 2 & 3
Issue Type: Bug
Components: Plugin API
Affects Versions: 3.0.4
Environment: JDK 1.7
MAVN 3.0.5
Reporter: Martin Gainty
Priority: Minor
Attachments: RobertPatrickAnnotationsTest.zip
looks like we need to hire you to check our code..(provided you work for free)
package org.apache.maven.plugins.annotations;
import java.lang.annotation.RetentionPolicy;
@Documented
@Retention( RetentionPolicy.CLASS )
@Target( { ElementType.FIELD } )
@Inherited
public @interface Parameter
RetentionPolicy parameters:
CLASS
Annotations are to be recorded in the class file by the compiler but need NOT
be retained by the VM at run time.
RUNTIME
Annotations are to be recorded in the class file by the compiler and RETAINED
by the VM at run time, so they may be read reflectively.
SOURCE
Annotations are to be discarded by the compiler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5520) RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
[
https://jira.codehaus.org/browse/MNG-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333114#comment-333114
]
Stuart McCulloch commented on MNG-5520:
---
IIRC those Java5 annotations are only used by the maven-plugin-plugin to
generate META-INF/maven/plugin.xml and are not used by the core Maven runtime,
in which case a retention policy of CLASS is ok:
http://svn.apache.org/viewvc?view=revision&revision=1338003
The main benefit of using them is that if you extend a Maven plugin then the
maven-plugin-plugin can see the Java5 annotations retained in the class file,
whereas javadoc annotations are only in the source.
See http://jira.codehaus.org/browse/MPLUGIN-56 for the original use-case
> RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
> -
>
> Key: MNG-5520
> URL: https://jira.codehaus.org/browse/MNG-5520
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.0.4
> Environment: JDK 1.7
> MAVN 3.0.5
>Reporter: Martin Gainty
>Priority: Minor
> Attachments: RobertPatrickAnnotationsTest.zip
>
>
> looks like we need to hire you to check our code..(provided you work for free)
> package org.apache.maven.plugins.annotations;
> import java.lang.annotation.RetentionPolicy;
> @Documented
> @Retention( RetentionPolicy.CLASS )
> @Target( { ElementType.FIELD } )
> @Inherited
> public @interface Parameter
> RetentionPolicy parameters:
> CLASS
> Annotations are to be recorded in the class file by the compiler but need NOT
> be retained by the VM at run time.
>
> RUNTIME
> Annotations are to be recorded in the class file by the compiler and
> RETAINED by the VM at run time, so they may be read reflectively.
>
> SOURCE
> Annotations are to be discarded by the compiler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5520) RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
[
https://jira.codehaus.org/browse/MNG-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5520.
--
Resolution: Not A Bug
> RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
> -
>
> Key: MNG-5520
> URL: https://jira.codehaus.org/browse/MNG-5520
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.0.4
> Environment: JDK 1.7
> MAVN 3.0.5
>Reporter: Martin Gainty
>Priority: Minor
> Attachments: RobertPatrickAnnotationsTest.zip
>
>
> looks like we need to hire you to check our code..(provided you work for free)
> package org.apache.maven.plugins.annotations;
> import java.lang.annotation.RetentionPolicy;
> @Documented
> @Retention( RetentionPolicy.CLASS )
> @Target( { ElementType.FIELD } )
> @Inherited
> public @interface Parameter
> RetentionPolicy parameters:
> CLASS
> Annotations are to be recorded in the class file by the compiler but need NOT
> be retained by the VM at run time.
>
> RUNTIME
> Annotations are to be recorded in the class file by the compiler and
> RETAINED by the VM at run time, so they may be read reflectively.
>
> SOURCE
> Annotations are to be discarded by the compiler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5520) RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
[
https://jira.codehaus.org/browse/MNG-5520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333115#comment-333115
]
Jason van Zyl commented on MNG-5520:
Stuart is correct. They are only used during build time. We like to limit any
classpath scanning and generate metadata for all components/plugins upfront.
> RuntimePolicy is incorrect for org.apache.maven.plugins.annotations.Parameter
> -
>
> Key: MNG-5520
> URL: https://jira.codehaus.org/browse/MNG-5520
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.0.4
> Environment: JDK 1.7
> MAVN 3.0.5
>Reporter: Martin Gainty
>Priority: Minor
> Attachments: RobertPatrickAnnotationsTest.zip
>
>
> looks like we need to hire you to check our code..(provided you work for free)
> package org.apache.maven.plugins.annotations;
> import java.lang.annotation.RetentionPolicy;
> @Documented
> @Retention( RetentionPolicy.CLASS )
> @Target( { ElementType.FIELD } )
> @Inherited
> public @interface Parameter
> RetentionPolicy parameters:
> CLASS
> Annotations are to be recorded in the class file by the compiler but need NOT
> be retained by the VM at run time.
>
> RUNTIME
> Annotations are to be recorded in the class file by the compiler and
> RETAINED by the VM at run time, so they may be read reflectively.
>
> SOURCE
> Annotations are to be discarded by the compiler.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-295) Non reliable killing of processes by CommandLineUtils
[ https://jira.codehaus.org/browse/MSHARED-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333120#comment-333120 ] Andrey Klochkov commented on MSHARED-295: - Kristian, the patch is there, would you review it? :-) > Non reliable killing of processes by CommandLineUtils > - > > Key: MSHARED-295 > URL: https://jira.codehaus.org/browse/MSHARED-295 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-shared-utils >Reporter: Andrey Klochkov > Attachments: MSHARED-295.patch > > > CommandLineUtils is used in Maven-Surefire to start forks which execute > tests. It is a well known issue that sometimes child processes are not killed > correctly. This is a known limitation of JVM, and the only reliable way to > implement it would be platform specific. > Bug report in Surefire JIRA: > http://jira.codehaus.org/browse/SUREFIRE-773 > JVM bug report. It's Windows specific, but the problem exists on Linux and > OSX as well. > http://bugs.sun.com/view_bug.do?bug_id=4770092 > I'm proposing either 1) to implement several platform specific > implementations of ProcessHook or 2) to make the mechanism of killing > processes extendable for clients of the library. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (ARCHETYPE-422) Unable to find resource 'archetype-resources/*/pom.xml'
[ https://jira.codehaus.org/browse/ARCHETYPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333121#comment-333121 ] Alex Heneveld commented on ARCHETYPE-422: - In case it helps, I hit this error in a different way: I was using the `maven-replace-plugin` to copy from a known-good copy of the project into the `archetype-resources` tree in the `compile` phase. I switched it to do the copy in the `clean` phase instead and all is okay. So maybe the error here is happening because the `archetype-resources/pom.xml` file which maven opens (at the start of compile phase?) is replaced when it later goes to read from it. > Unable to find resource 'archetype-resources/*/pom.xml' > --- > > Key: ARCHETYPE-422 > URL: https://jira.codehaus.org/browse/ARCHETYPE-422 > Project: Maven Archetype > Issue Type: Bug > Components: Generator > Environment: Windows 7, Apache Maven 3.0.4 (r1232337; 2012-01-17 > 00:44:56-0800) > Java version: 1.6.0_30, vendor: Sun Microsystems Inc. >Reporter: Aleksei Serov >Priority: Minor > Attachments: archetype.zip > > > I am running a mvn archetype:generate on multi-module project archetype I > have created using mvn archetype:create-from-project and mvn install. > Archetype attached. > I get: > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-archetype-plugin:2.2:generate (default-cli) on > project standalone-pom: > org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error > merging velocity templates: Unable to find resource > 'archetype-resources/*/pom.xml' -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-archetype-plugin:2.2:generate > (default-cli) on project standalone-pom: > org.apache.maven.archetype.exception.ArchetypeGenerationFailure: Error > merging velocity templates: Unable to find resource > 'archetype-resources/*/pom.xml' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
