[jira] [Created] (MPLUGIN-334) Upgrade mave-surefire/failsafe-plugin 2.21.0

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MPLUGIN-334:
---

 Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0
 Key: MPLUGIN-334
 URL: https://issues.apache.org/jira/browse/MPLUGIN-334
 Project: Maven Plugin Tools
  Issue Type: Dependency upgrade
Affects Versions: 3.6
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.6






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MPLUGIN-333) Upgrade parent to 31

[Karl Heinz Marbaise (JIRA)]

Karl Heinz Marbaise created MPLUGIN-333:
---

 Summary: Upgrade parent to 31
 Key: MPLUGIN-333
 URL: https://issues.apache.org/jira/browse/MPLUGIN-333
 Project: Maven Plugin Tools
  Issue Type: Dependency upgrade
Affects Versions: 3.6
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.6






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] olamy commented on issue #9: upgrade to ASM 6.1.1

[GitBox]

olamy commented on issue #9: upgrade to ASM 6.1.1
URL: https://github.com/apache/maven-plugin-tools/pull/9#issuecomment-386460786
 
 
   any jira issue?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] aldaris commented on issue #9: upgrade to ASM 6.1.1

[GitBox]

aldaris commented on issue #9: upgrade to ASM 6.1.1
URL: https://github.com/apache/maven-plugin-tools/pull/9#issuecomment-386445551
 
 
   With ASM 6.1.1 maven-plugin-plugin would also support JDK10.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] Tibor17 commented on issue #184: Donate current sources from junit-platform-surefire-provider

[GitBox]

Tibor17 commented on issue #184: Donate current sources from 
junit-platform-surefire-provider
URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-386425187
 
 
   @sormuras 
   The branch contains all your changes now.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] sormuras commented on issue #184: Donate current sources from junit-platform-surefire-provider

[GitBox]

sormuras commented on issue #184: Donate current sources from 
junit-platform-surefire-provider
URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-386411693
 
 
   Sure. Go ahead.
   
   I am still waiting for the ASF git permissions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[GitHub] Tibor17 commented on issue #184: Donate current sources from junit-platform-surefire-provider

[GitBox]

Tibor17 commented on issue #184: Donate current sources from 
junit-platform-surefire-provider
URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-386396527
 
 
   @sormuras 
   I should perhaps squash all 4 commits in the branch 
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=shortlog;h=refs/heads/1330
 and add the last commit `4d9173e `.
   Do you have permissions in ASF git?


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Commented] (MNG-6240) Duplicate components in plugin extension realm when plugin depends on maven-aether-resolver

[Alexandru Baxanean (JIRA)]

[ 
https://issues.apache.org/jira/browse/MNG-6240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462826#comment-16462826
 ] 

Alexandru Baxanean commented on MNG-6240:
-

3.3.9 has the issue as well. At least is has MDEPLOY-221

> Duplicate components in plugin extension realm when plugin depends on 
> maven-aether-resolver
> ---
>
> Key: MNG-6240
> URL: https://issues.apache.org/jira/browse/MNG-6240
> Project: Maven
>  Issue Type: Bug
>  Components: Class Loading
>Affects Versions: 3.5.0
>Reporter: Guillaume Boué
>Assignee: Guillaume Boué
>Priority: Major
> Fix For: 3.5.2
>
>
> When a plugin extension has a dependency on {{maven-aether-resolver}}, the 
> components of this artifact are added into the plugin realm even though Maven 
> Core already provides them. This is a regression introduced by the rename of 
> this module to {{maven-resolver-provider}} in 3.5.0.
> This rename has kept all the classes of {{maven-aether-resolver}} for 
> compatibility, therefore the old artifact name also needs to be exported by 
> Maven Core in {{extension.xml}}.
> A visible side-effect of this is MDEPLOY-221, where the two 
> {{MetadataGeneratorFactory}} components of {{maven-aether-provider}} (which 
> are {{SnapshotMetadataGeneratorFactory}} and 
> {{VersionsMetadataGeneratorFactory}}) are present twice as Guice bindings, 
> and wrong metadata information is deployed as a consequence. This is due to 
> the Flex Mojos plugin extension which depends on {{maven-aether-resolver}} 
> used in the build.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (WAGON-487) Saved password with french accent breaks deployment

[Michael Osipov (JIRA)]

[ 
https://issues.apache.org/jira/browse/WAGON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462683#comment-16462683
 ] 

Michael Osipov commented on WAGON-487:
--

Please use a more recent version of Wagon, ideally from master. Also log with 
Wireshark or enable logging on HTTPClient. I'd like to see the Base64 string of 
the basic response.

> Saved password with french accent breaks deployment
> ---
>
> Key: WAGON-487
> URL: https://issues.apache.org/jira/browse/WAGON-487
> Project: Maven Wagon
>  Issue Type: New Feature
>  Components: wagon-http
>Affects Versions: 2.12
>Reporter: Dominique Jean-Prost
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> I cannot deploy any artifact to my sonatype nexus instance when using a 
> pasword with french accetn, like 'é'.
> This instance needs authentication to deploy.
> My test : 
> # Check authentication against nexus directly with a password containing 
> accent : OK
> # Check deploy with clear password in {{settings.xml}} with no accent : OK
> # Check deploy with encrypted password in {{settings.xml}} with no accent : OK
> # Check deploy with clear password in {{settings.xml}} with accent : KO
> # Check deploy with encrypted password in {{settings.xml}} with accent : KO
> After many minutes of debugging, I managed to verify that my password is 
> correctly "read" in the settings {{org.apache.maven.settings.Server}} : it 
> has nothing to do with {{settings.xml}} XML encoding.
> When finally wagon enters the game, the http header with authentication basic 
> contains a '? ' instead of my 'é'. I managed to narrow the problem to 
> {{org.apache.maven.wagon.providers.http.httpclient.impl.auth.BasicScheme}} 
> which I think is the cuplrit by not dealing correctly with charset encoding 
> in the {{authenticate}} method.
> I came to the end of what I can do for the moment, appart of changing my 
> password to remove the accent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MNG-6402) Maven Projekt do not see the version of imported POM in DependencyMangement

[Rong Li (JIRA)]

Rong Li created MNG-6402:


 Summary: Maven Projekt do not see the version of imported POM in 
DependencyMangement
 Key: MNG-6402
 URL: https://issues.apache.org/jira/browse/MNG-6402
 Project: Maven
  Issue Type: Bug
  Components: Dependencies
Affects Versions: 3.5.2
Reporter: Rong Li


We have following imported dependency in our pom.xml:
{code:java}



my.company
company-dependency-management
1.0.0-SNAPSHOT
pom
import

   

{code}

We want to use some plugins to ensure that this dependency should not be 
SNAPSHOT-version before release, but this dependency will be resolved with the 
list of imported dependencies in the effective pom.xml. There is no chance to 
get this SNAPSHOT-version.




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set

[Matthieu Brouillard (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Brouillard updated SCM-885:

External issue URL: https://github.com/apache/maven-scm/pull/70

PR submitted at https://github.com/apache/maven-scm/pull/70

> GitChangeLogCommand is wrong when only endVersion is set
> 
>
> Key: SCM-885
> URL: https://issues.apache.org/jira/browse/SCM-885
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Priority: Major
>
> Invoking execution of a GitChangeLogCommand where only the end revision has 
> been set produces a wrong out.
> +Actual result:+
> {{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}
> +Expected result:+ only the end revison SHA1 is used without the two dots
> {{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462306#comment-16462306
 ] 

ASF GitHub Bot commented on SCM-885:


McFoggy opened a new pull request #70: [SCM-885] allow to use only endVersion 
in GitChangeLogCommand
URL: https://github.com/apache/maven-scm/pull/70
 
 
   On a GitChangeLogCommand setting only endVersion allows to retrieve
   commits from project start until the commit corresponding to endVersion.
   
   fixes #SCM-885
   
   Signed-off-by: Matthieu Brouillard 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> GitChangeLogCommand is wrong when only endVersion is set
> 
>
> Key: SCM-885
> URL: https://issues.apache.org/jira/browse/SCM-885
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Priority: Major
>
> Invoking execution of a GitChangeLogCommand where only the end revision has 
> been set produces a wrong out.
> +Actual result:+
> {{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}
> +Expected result:+ only the end revison SHA1 is used without the two dots
> {{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] McFoggy opened a new pull request #70: [SCM-885] allow to use only endVersion in GitChangeLogCommand

[GitBox]

McFoggy opened a new pull request #70: [SCM-885] allow to use only endVersion 
in GitChangeLogCommand
URL: https://github.com/apache/maven-scm/pull/70
 
 
   On a GitChangeLogCommand setting only endVersion allows to retrieve
   commits from project start until the commit corresponding to endVersion.
   
   fixes #SCM-885
   
   Signed-off-by: Matthieu Brouillard 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Created] (SCM-886) Tests with checkin rely on global git config

[Matthieu Brouillard (JIRA)]

Matthieu Brouillard created SCM-886:
---

 Summary: Tests with checkin rely on global git config
 Key: SCM-886
 URL: https://issues.apache.org/jira/browse/SCM-886
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-gitexe
Affects Versions: 1.9.5
Reporter: Matthieu Brouillard


Inside maven-scm-provider-gitexe project, the two following tests 
`GitCheckInCommandNoBranchTest.testCheckinNoBranch` and 
`GitCheckInCommandTest.testCheckinAfterRename` expect a global user.name and 
user.email to be set.

On installations where .gitconfig contains the following:

{{[user]}}
{{useConfigOnly = true}}

The tests will fail.

It would be better after repository creation to configure a user name & email 
at project level.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] olamy commented on issue #184: Donate current sources from junit-platform-surefire-provider

[GitBox]

olamy commented on issue #184: Donate current sources from 
junit-platform-surefire-provider
URL: https://github.com/apache/maven-surefire/pull/184#issuecomment-386257099
 
 
   awesome!!


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Updated] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set

[Matthieu Brouillard (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SCM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matthieu Brouillard updated SCM-885:

Description: 
Invoking execution of a GitChangeLogCommand where only the end revision has 
been set produces a wrong out.

+Actual result:+

{{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}

+Expected result:+ only the end revison SHA1 is used without the two dots

{{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}

  was:
Invoking execution of a GitChangeLogCommand where only the end revision has 
been set produces a wrong out.

+Actual result:+

{{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}

+Expected result:+ only the end revison SHA1 is used without the two dots

{{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}


> GitChangeLogCommand is wrong when only endVersion is set
> 
>
> Key: SCM-885
> URL: https://issues.apache.org/jira/browse/SCM-885
> Project: Maven SCM
>  Issue Type: Bug
>  Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Matthieu Brouillard
>Priority: Major
>
> Invoking execution of a GitChangeLogCommand where only the end revision has 
> been set produces a wrong out.
> +Actual result:+
> {{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}
> +Expected result:+ only the end revison SHA1 is used without the two dots
> {{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SCM-885) GitChangeLogCommand is wrong when only endVersion is set

[Matthieu Brouillard (JIRA)]

Matthieu Brouillard created SCM-885:
---

 Summary: GitChangeLogCommand is wrong when only endVersion is set
 Key: SCM-885
 URL: https://issues.apache.org/jira/browse/SCM-885
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-gitexe
Affects Versions: 1.9.5
Reporter: Matthieu Brouillard


Invoking execution of a GitChangeLogCommand where only the end revision has 
been set produces a wrong out.

+Actual result:+

{{git whatchanged --date=iso  ..END_REVISION_SHA1 -- PROJECT_PATH}}

+Expected result:+ only the end revison SHA1 is used without the two dots

{{git whatchanged --date=iso  END_REVISION_SHA1 -- PROJECT_PATH}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] sormuras opened a new pull request #184: Donate current sources from junit-platform-surefire-provider

[GitBox]

sormuras opened a new pull request #184: Donate current sources from 
junit-platform-surefire-provider
URL: https://github.com/apache/maven-surefire/pull/184
 
 
   This commit includes enhancements and bug fixes that were applied since the 
initial code donation.
   
   History of changes: 
https://github.com/junit-team/junit5/commits/master/junit-platform-surefire-provider
   
   Addresses https://issues.apache.org/jira/browse/SUREFIRE-1330
   


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

[jira] [Comment Edited] (WAGON-487) Saved password with french accent breaks deployment

[Dominique Jean-Prost (JIRA)]

[ 
https://issues.apache.org/jira/browse/WAGON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462077#comment-16462077
 ] 

Dominique Jean-Prost edited comment on WAGON-487 at 5/3/18 8:04 AM:


Well, I still cannot manage to get it done.
 I added this to my {{settings.xml}}
{code:xml}

...


repo-snapshots
djeanprost
passwordé
 





http.auth.credential-charset

UTF-8







...


{code}
I copied 
{{J:\git\maven-wagon\wagon-providers\wagon-http\target\wagon-http-2.13-SNAPSHOT-shaded.jar}}
 to {{C:\bin\apache-maven-3.5.3\lib\ext\wagon-http-2.13-SNAPSHOT-shaded.jar}} 
and tried to deploy my artifact, but it still doesn't work.
 I tried with another password, same configuration, and it's ok.

Actually, I'm not sure the setup I discribed is ok. Can you confirm it is ? 
Thank you.
{code:java}
 mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; 
support was removed in 8.0
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 
2018-02-24T20:49:05+01:00)
Maven home: C:\bin\apache-maven-3.5.3\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation
Java home: C:\bin\jdk1.8.0_152\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{code}


was (Author: djeanprost):
Well, I still cannot manage to get it done.
 I added this to my {{settings.xml}}
{code:xml}

c:/maven-repository


repo-snapshots
djeanprost
passwordé
 





http.auth.credential-charset

UTF-8







{code}
I copied 
{{J:\git\maven-wagon\wagon-providers\wagon-http\target\wagon-http-2.13-SNAPSHOT-shaded.jar}}
 to {{C:\bin\apache-maven-3.5.3\lib\ext\wagon-http-2.13-SNAPSHOT-shaded.jar}} 
and tried to deploy my artifact, but it still doesn't work.
 I tried with another password, same configuration, and it's ok.

Actually, I'm not sure the setup I discribed is ok. Can you confirm it is ? 
Thank you.
{code:java}
 mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; 
support was removed in 8.0
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 
2018-02-24T20:49:05+01:00)
Maven home: C:\bin\apache-maven-3.5.3\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation
Java home: C:\bin\jdk1.8.0_152\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{code}

> Saved password with french accent breaks deployment
> ---
>
> Key: WAGON-487
> URL: https://issues.apache.org/jira/browse/WAGON-487
> Project: Maven Wagon
>  Issue Type: New Feature
>  Components: wagon-http
>Affects Versions: 2.12
>Reporter: Dominique Jean-Prost
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> I cannot deploy any artifact to my sonatype nexus instance when using a 
> pasword with french accetn, like 'é'.
> This instance needs authentication to deploy.
> My test : 
> # Check authentication against nexus directly with a password containing 
> accent : OK
> # Check deploy with clear password in {{settings.xml}} with no accent : OK
> # Check deploy with encrypted password in {{settings.xml}} with no accent : OK
> # Check deploy with clear password in {{settings.xml}} with accent : KO
> # Check deploy with encrypted password in {{settings.xml}} with accent : KO
> After many minutes of debugging, I managed to verify that my password is 
> correctly "read" in the settings {{org.apache.maven.settings.Server}} : it 
> has 

[jira] [Commented] (WAGON-487) Saved password with french accent breaks deployment

[Dominique Jean-Prost (JIRA)]

[ 
https://issues.apache.org/jira/browse/WAGON-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16462077#comment-16462077
 ] 

Dominique Jean-Prost commented on WAGON-487:


Well, I still cannot manage to get it done.
 I added this to my {{settings.xml}}
{code:xml}

c:/maven-repository


repo-snapshots
djeanprost
passwordé
 





http.auth.credential-charset

UTF-8







{code}
I copied 
{{J:\git\maven-wagon\wagon-providers\wagon-http\target\wagon-http-2.13-SNAPSHOT-shaded.jar}}
 to {{C:\bin\apache-maven-3.5.3\lib\ext\wagon-http-2.13-SNAPSHOT-shaded.jar}} 
and tried to deploy my artifact, but it still doesn't work.
 I tried with another password, same configuration, and it's ok.

Actually, I'm not sure the setup I discribed is ok. Can you confirm it is ? 
Thank you.
{code:java}
 mvn --version
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=512M; 
support was removed in 8.0
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 
2018-02-24T20:49:05+01:00)
Maven home: C:\bin\apache-maven-3.5.3\bin\..
Java version: 1.8.0_152, vendor: Oracle Corporation
Java home: C:\bin\jdk1.8.0_152\jre
Default locale: fr_FR, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
{code}

> Saved password with french accent breaks deployment
> ---
>
> Key: WAGON-487
> URL: https://issues.apache.org/jira/browse/WAGON-487
> Project: Maven Wagon
>  Issue Type: New Feature
>  Components: wagon-http
>Affects Versions: 2.12
>Reporter: Dominique Jean-Prost
>Priority: Critical
> Fix For: waiting-for-feedback
>
>
> I cannot deploy any artifact to my sonatype nexus instance when using a 
> pasword with french accetn, like 'é'.
> This instance needs authentication to deploy.
> My test : 
> # Check authentication against nexus directly with a password containing 
> accent : OK
> # Check deploy with clear password in {{settings.xml}} with no accent : OK
> # Check deploy with encrypted password in {{settings.xml}} with no accent : OK
> # Check deploy with clear password in {{settings.xml}} with accent : KO
> # Check deploy with encrypted password in {{settings.xml}} with accent : KO
> After many minutes of debugging, I managed to verify that my password is 
> correctly "read" in the settings {{org.apache.maven.settings.Server}} : it 
> has nothing to do with {{settings.xml}} XML encoding.
> When finally wagon enters the game, the http header with authentication basic 
> contains a '? ' instead of my 'é'. I managed to narrow the problem to 
> {{org.apache.maven.wagon.providers.http.httpclient.impl.auth.BasicScheme}} 
> which I think is the cuplrit by not dealing correctly with charset encoding 
> in the {{authenticate}} method.
> I came to the end of what I can do for the moment, appart of changing my 
> password to remove the accent.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)