[jira] (WAGON-402) Upgrade Apache HttpClient based wagon provider to HttpClient 4.3
[ https://jira.codehaus.org/browse/WAGON-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333123#comment-333123 ] Oleg Kalnichevski commented on WAGON-402: - Olivier I am still having difficulty getting a grip on the pull request workflow in GitHub, so I am not entirely sure you are getting notified of additional changes to my private branch. There are three more change sets I would like you to review and if accepted pull to the official repository. Oleg > Upgrade Apache HttpClient based wagon provider to HttpClient 4.3 > > > Key: WAGON-402 > URL: https://jira.codehaus.org/browse/WAGON-402 > Project: Maven Wagon > Issue Type: Improvement > Components: wagon-http >Reporter: Oleg Kalnichevski >Priority: Minor > Attachments: maven-wagen-httpclient-4.3.patch > > > Please consider upgrading wagon-http to Apache HttpClient 4.3. Version 4.3 > comes with a number of improvements, new configuration APIs probably being > the most relevant for wagen-http, and is also expected to be somewhat faster > than 4.2. > The patch attached removes references to deprecated APIs and replaces them > with equivalent newer ones while trying to preserve the overall design and > structure. If this patch gets accepted I could also try to re-work things > slightly in order to reduce total code footprint and optimize the use of > HttpClient functionality. > Please note that the patch breaks full binary compatibility with the latest > stable version due to removal of deprecated HttpClient classes used in the > public APIs. I hope this is acceptable. > Oleg > Oleg -- 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] (MASSEMBLY-574) includeBaseDirectory is ignored in version 2.2.1
[
https://jira.codehaus.org/browse/MASSEMBLY-574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333127#comment-333127
]
Ignat Alexeyenko commented on MASSEMBLY-574:
Any updates on that? Having this issue with shared assembly in the plugin
version 2.4.
--
Cheers, Ignat.
> includeBaseDirectory is ignored in version 2.2.1
>
>
> Key: MASSEMBLY-574
> URL: https://jira.codehaus.org/browse/MASSEMBLY-574
> Project: Maven Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2.1
> Environment: fedora 15, maven 2.2.1
>Reporter: lillian angel
>
> "includeBaseDirectory" is ignored in 2.2.1, had to revert to 2.2-beta-2 for
> this to work
> {code:xml}
> xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>
> xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0
> http://maven.apache.org/xsd/assembly-1.1.0.xsd";>
> dependencies
>
> jar
>
> false
>
>
> false
>
>
> META-INF/spring.handlers
> META-INF/spring.schemas
> META-INF/spring.tooling
>
>
> runtime
>
>
>
>
> lib
>
>
>
> {code}
--
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
[
https://jira.codehaus.org/browse/MNG-5519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=333129#comment-333129
]
Stuart McCulloch commented on MNG-5519:
---
This appears to be a duplicate of MNG-5520
> 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-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=333130#comment-333130
]
Stuart McCulloch commented on MNG-5518:
---
According to http://maven.apache.org/developers/mojo-api-specification.html the
javadoc-style @parameter had the following behaviour:
"NOTE: If neither default-value nor expression are specified, the parameter
can only be configured from the POM. The use of '${' and '}' is required to
delimit actual expressions which may be evaluated"
Also in the Java5 annotation the 'expression' attribute was renamed to
'property' and the need for '${' and '}' was dropped:
https://jira.codehaus.org/browse/MPLUGIN-196
So there is some consistency here in that it is possible to define a parameter
that cannot be overridden from the command-line, and an additional attribute is
required ('expression'/'default-value' for the javadoc annotation, 'property'
for the Java5 annotation) to enable the command-line support.
> @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=333130#comment-333130
]
Stuart McCulloch edited comment on MNG-5518 at 9/21/13 7:23 PM:
According to http://maven.apache.org/developers/mojo-api-specification.html the
javadoc-style @parameter had the following behaviour:
"NOTE: If neither default-value nor expression are specified, the parameter
can only be configured from the POM. The use of '$\{' and '}' is required to
delimit actual expressions which may be evaluated"
Also in the Java5 annotation the 'expression' attribute was renamed to
'property' and the need for '$\{' and '}' was dropped:
https://jira.codehaus.org/browse/MPLUGIN-196
So there is some consistency here in that it is possible to define a parameter
that cannot be overridden from the command-line, and an additional attribute is
required ('expression'/'default-value' for the javadoc annotation, 'property'
for the Java5 annotation) to enable the command-line support.
was (Author: mcculls):
According to http://maven.apache.org/developers/mojo-api-specification.html
the javadoc-style @parameter had the following behaviour:
"NOTE: If neither default-value nor expression are specified, the parameter
can only be configured from the POM. The use of '${' and '}' is required to
delimit actual expressions which may be evaluated"
Also in the Java5 annotation the 'expression' attribute was renamed to
'property' and the need for '${' and '}' was dropped:
https://jira.codehaus.org/browse/MPLUGIN-196
So there is some consistency here in that it is possible to define a parameter
that cannot be overridden from the command-line, and an additional attribute is
required ('expression'/'default-value' for the javadoc annotation, 'property'
for the Java5 annotation) to enable the command-line support.
> @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
