[jira] (SCM-766) Correct the source location on the site

2014-07-17 Thread Karl-Heinz Marbaise (JIRA) 
Karl-Heinz Marbaise created SCM-766:
---

 Summary: Correct the source location on the site
 Key: SCM-766
 URL: https://jira.codehaus.org/browse/SCM-766
 Project: Maven SCM
  Issue Type: Task
  Components: maven-plugin
Affects Versions: 1.10
Reporter: Karl-Heinz Marbaise
Priority: Minor


The location which is linked on the site seemed to be wrong.
The following seemed to be the correct one.
https://git-wip-us.apache.org/repos/asf?p=maven-scm.git;a=tree




--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1085) Documentation incorrect for running single integration test

2014-07-17 Thread Karsten Ohme (JIRA) 
Karsten Ohme created SUREFIRE-1085:
--

 Summary: Documentation incorrect for running single integration 
test
 Key: SUREFIRE-1085
 URL: https://jira.codehaus.org/browse/SUREFIRE-1085
 Project: Maven Surefire
  Issue Type: Improvement
  Components: documentation
Reporter: Karsten Ohme
Priority: Minor


The online documentation for Failsafe which describes [Running a Single 
Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html]
 shows:
bq.mvn -Dit.test=ITCircle verify

The it.test parameter does not seem to work. Rather, the same parameter as 
Surefire (-Dtest=foo) appears to also work for Failsafe.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1085) Documentation incorrect for running single integration test

2014-07-17 Thread Karsten Ohme (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karsten Ohme updated SUREFIRE-1085:
---

Affects Version/s: 2.12

 Documentation incorrect for running single integration test
 ---

 Key: SUREFIRE-1085
 URL: https://jira.codehaus.org/browse/SUREFIRE-1085
 Project: Maven Surefire
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.12
Reporter: Karsten Ohme
Priority: Minor

 The online documentation for Failsafe which describes [Running a Single 
 Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html]
  shows:
 bq.mvn -Dit.test=ITCircle verify
 The it.test parameter does not seem to work. Rather, the same parameter as 
 Surefire (-Dtest=foo) appears to also work for Failsafe.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1085) Documentation incorrect for running single integration test

2014-07-17 Thread Karsten Ohme (JIRA) 

 [ 
https://jira.codehaus.org/browse/SUREFIRE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karsten Ohme updated SUREFIRE-1085:
---

Complexity: Novice  (was: Intermediate)

 Documentation incorrect for running single integration test
 ---

 Key: SUREFIRE-1085
 URL: https://jira.codehaus.org/browse/SUREFIRE-1085
 Project: Maven Surefire
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.12
Reporter: Karsten Ohme
Priority: Minor

 The online documentation for Failsafe which describes [Running a Single 
 Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html]
  shows:
 bq.mvn -Dit.test=ITCircle verify
 The it.test parameter does not seem to work. Rather, the same parameter as 
 Surefire (-Dtest=foo) appears to also work for Failsafe.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SUREFIRE-1085) Documentation incorrect for running single integration test

2014-07-17 Thread Karsten Ohme (JIRA) 

[ 
https://jira.codehaus.org/browse/SUREFIRE-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349897#comment-349897
 ] 

Karsten Ohme commented on SUREFIRE-1085:


There was already such a bug report, but it was closed. -Dit.test=... does not 
work. So I cannot understand, why this was closed. With -Dit.test=.. no tests 
at all are executed, so this parameter seems to be not ignored but incorrectly 
interpreted.

 Documentation incorrect for running single integration test
 ---

 Key: SUREFIRE-1085
 URL: https://jira.codehaus.org/browse/SUREFIRE-1085
 Project: Maven Surefire
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.12
Reporter: Karsten Ohme
Priority: Minor

 The online documentation for Failsafe which describes [Running a Single 
 Test|http://maven.apache.org/plugins/maven-failsafe-plugin/examples/single-test.html]
  shows:
 bq.mvn -Dit.test=ITCircle verify
 The it.test parameter does not seem to work. Rather, the same parameter as 
 Surefire (-Dtest=foo) appears to also work for Failsafe.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories

2014-07-17 Thread Mark Ingram (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349899#comment-349899
 ] 

Mark Ingram commented on MNG-5663:
--

This was caused by the changes for MNG-5639. The resolution failures are seen 
with nested import POMs. 

I have created a failing integration test and will begin investigating a fix.

Regards,
Mark

 [regression] resolution of import-scoped transitive dependencies ignores 
 additional repositories
 

 Key: MNG-5663
 URL: https://jira.codehaus.org/browse/MNG-5663
 Project: Maven
  Issue Type: Bug
  Components: Artifacts and Repositories, Dependencies
Affects Versions: 3.2.2
Reporter: Fred Bricon

 We (JBoss) use BOM poms extensively, notably in a number of project 
 archetypes or project examples available via JBoss Tools and Red Hat 
 Developer Studio . Some of these BOM poms (and their dependencies) are 
 available from a dedicated Maven repository 
 (http://maven.repository.redhat.com/techpreview/all/). 
 Maven 3.2.2 introduced a regression that breaks resolution of these BOM 
 dependencies, by ignoring additional repositories during artifact resolution.
 {noformat}
 project xmlns=http://maven.apache.org/POM/4.0.0; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/xsd/maven-4.0.0.xsd;
   modelVersion4.0.0/modelVersion
   groupIdfoo/groupId
   artifactIdbar/artifactId
   version0.0.1-SNAPSHOT/version
   dependencyManagement
   dependencies
   dependency
   groupIdorg.jboss.bom.wfk/groupId
   
 artifactIdjboss-javaee-6.0-with-tools/artifactId
   version2.4.0-redhat-2/version
   typepom/type
   scopeimport/scope
   /dependency
   /dependencies
   /dependencyManagement
   repositories
   repository
   idredhat-techpreview-all-repository/id
   
 urlhttp://maven.repository.redhat.com/techpreview/all//url
   /repository
   /repositories
 /project
 {noformat}
 yields :
 {noformat}
 ➜  bar  mvn compile
 [INFO] Scanning for projects...
 Downloading: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
 Downloaded: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
  (8 KB at 5.1 KB/sec)
 Downloading: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
 Downloaded: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
  (7 KB at 6.8 KB/sec)
 Downloading: 
 http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
 [ERROR] The build could not read 1 project - [Help 1]
 [ERROR]
 [ERROR]   The project foo:bar:0.0.1-SNAPSHOT 
 (/Users/fbricon/Dev/workspaces/runtime-hosted/bar/pom.xml) has 2 errors
 [ERROR] Non-resolvable import POM: Could not find artifact 
 org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final-redhat-4 in central 
 (http://repo.maven.apache.org/maven2) @ 
 org.jboss.bom.wfk:jboss-javaee-6.0-with-tools:[unknown-version], 
 /Users/fbricon/Dev/maven/repository/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom,
  line 42, column 25 - [Help 2]
 [ERROR] 'dependencies.dependency.version' for 
 javax.enterprise:cdi-api:jar is missing. @ line 27, column 15
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
 [ERROR] [Help 2] 
 http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
 ➜  bar
 {noformat}
 This kind of resolution used to work in maven 3.2.1 and before. The missing 
 pom is available at 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SCM-765) jgit provider commits changes with system user instead of passed username

2014-07-17 Thread Karl-Heinz Marbaise (JIRA) 

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

Karl-Heinz Marbaise updated SCM-765:


Fix Version/s: 1.10

 jgit provider commits changes with system user instead of passed username
 -

 Key: SCM-765
 URL: https://jira.codehaus.org/browse/SCM-765
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.9
Reporter: Dominik Bartholdi
 Fix For: 1.10


 When using the jgit provider over http, it allows to define username / 
 password like this:
 {code}
 mvn release:prepare release:perform -Dresume=false -Dusername=myuser 
 -Dpassword=XXX
 {code}
 But the commit will not be done with the given user but with the system user 
 who started the process, instead the passed user is only used for transport. 
 Well that might be fine in the first thought, but it will mean in the git 
 repository it is not recorded who really did make the release. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MPLUGIN-271) Usage of defaultValues for a List.. Parameter seemed not to be working

2014-07-17 Thread Karl-Heinz Marbaise (JIRA) 
Karl-Heinz Marbaise created MPLUGIN-271:
---

 Summary: Usage of defaultValues for a List.. Parameter seemed 
not to be working
 Key: MPLUGIN-271
 URL: https://jira.codehaus.org/browse/MPLUGIN-271
 Project: Maven Plugin Tools
  Issue Type: Bug
  Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Karl-Heinz Marbaise


Currently the following seemed to be not working:
{code:java}
@Parameter( defaultValue = */pom.xml )
private ListString pomIncludes;
{code}




--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MPLUGIN-271) Usage of defaultValues for a List.. Parameter seemed not to be working

2014-07-17 Thread Karl-Heinz Marbaise (JIRA) 

 [ 
https://jira.codehaus.org/browse/MPLUGIN-271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl-Heinz Marbaise updated MPLUGIN-271:


Priority: Critical  (was: Major)

 Usage of defaultValues for a List.. Parameter seemed not to be working
 

 Key: MPLUGIN-271
 URL: https://jira.codehaus.org/browse/MPLUGIN-271
 Project: Maven Plugin Tools
  Issue Type: Bug
  Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Karl-Heinz Marbaise
Priority: Critical

 Currently the following seemed to be not working:
 {code:java}
 @Parameter( defaultValue = */pom.xml )
 private ListString pomIncludes;
 {code}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCOMPILER-228) cannot assign a value to final variable in lamda

2014-07-17 Thread Robert Kish (JIRA) 
Robert Kish created MCOMPILER-228:
-

 Summary: cannot assign a value to final variable in lamda
 Key: MCOMPILER-228
 URL: https://jira.codehaus.org/browse/MCOMPILER-228
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.1
 Environment: Windows 7 64 bit, Maven 3.2.2, JDK 64 bit 8u5
Reporter: Robert Kish
Priority: Minor
 Attachments: FinalExample.java

Code example compiles in Eclipse, but not with Maven Compiler Plugin. Code is 
like below (inside a lamda expression)
final x;
if (some condition)
x = a;
else if (some other condition)
x = b;
else 
x = c;

See attached example source.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project MediaIndexer: Compilation failure: Compilation failure:
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[11,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[14,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[17,13] 
cannot assign a value to final variable compareTo

The workaround is to remove final for the variable and just ensure that the 
value is assigned in each code path.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5663) [regression] resolution of import-scoped transitive dependencies ignores additional repositories

2014-07-17 Thread Jason van Zyl (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349932#comment-349932
 ] 

Jason van Zyl commented on MNG-5663:


Thanks for looking into that Mark!

 [regression] resolution of import-scoped transitive dependencies ignores 
 additional repositories
 

 Key: MNG-5663
 URL: https://jira.codehaus.org/browse/MNG-5663
 Project: Maven
  Issue Type: Bug
  Components: Artifacts and Repositories, Dependencies
Affects Versions: 3.2.2
Reporter: Fred Bricon

 We (JBoss) use BOM poms extensively, notably in a number of project 
 archetypes or project examples available via JBoss Tools and Red Hat 
 Developer Studio . Some of these BOM poms (and their dependencies) are 
 available from a dedicated Maven repository 
 (http://maven.repository.redhat.com/techpreview/all/). 
 Maven 3.2.2 introduced a regression that breaks resolution of these BOM 
 dependencies, by ignoring additional repositories during artifact resolution.
 {noformat}
 project xmlns=http://maven.apache.org/POM/4.0.0; 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
   xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 
 http://maven.apache.org/xsd/maven-4.0.0.xsd;
   modelVersion4.0.0/modelVersion
   groupIdfoo/groupId
   artifactIdbar/artifactId
   version0.0.1-SNAPSHOT/version
   dependencyManagement
   dependencies
   dependency
   groupIdorg.jboss.bom.wfk/groupId
   
 artifactIdjboss-javaee-6.0-with-tools/artifactId
   version2.4.0-redhat-2/version
   typepom/type
   scopeimport/scope
   /dependency
   /dependencies
   /dependencyManagement
   repositories
   repository
   idredhat-techpreview-all-repository/id
   
 urlhttp://maven.repository.redhat.com/techpreview/all//url
   /repository
   /repositories
 /project
 {noformat}
 yields :
 {noformat}
 ➜  bar  mvn compile
 [INFO] Scanning for projects...
 Downloading: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
 Downloaded: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom
  (8 KB at 5.1 KB/sec)
 Downloading: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
 Downloaded: 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/bom/wfk/jboss-wfk-bom-parent/2.4.0-redhat-2/jboss-wfk-bom-parent-2.4.0-redhat-2.pom
  (7 KB at 6.8 KB/sec)
 Downloading: 
 http://repo.maven.apache.org/maven2/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom
 [ERROR] The build could not read 1 project - [Help 1]
 [ERROR]
 [ERROR]   The project foo:bar:0.0.1-SNAPSHOT 
 (/Users/fbricon/Dev/workspaces/runtime-hosted/bar/pom.xml) has 2 errors
 [ERROR] Non-resolvable import POM: Could not find artifact 
 org.jboss.spec:jboss-javaee-6.0:pom:3.0.2.Final-redhat-4 in central 
 (http://repo.maven.apache.org/maven2) @ 
 org.jboss.bom.wfk:jboss-javaee-6.0-with-tools:[unknown-version], 
 /Users/fbricon/Dev/maven/repository/org/jboss/bom/wfk/jboss-javaee-6.0-with-tools/2.4.0-redhat-2/jboss-javaee-6.0-with-tools-2.4.0-redhat-2.pom,
  line 42, column 25 - [Help 2]
 [ERROR] 'dependencies.dependency.version' for 
 javax.enterprise:cdi-api:jar is missing. @ line 27, column 15
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
 switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions, please 
 read the following articles:
 [ERROR] [Help 1] 
 http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
 [ERROR] [Help 2] 
 http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
 ➜  bar
 {noformat}
 This kind of resolution used to work in maven 3.2.1 and before. The missing 
 pom is available at 
 http://maven.repository.redhat.com/techpreview/all/org/jboss/spec/jboss-javaee-6.0/3.0.2.Final-redhat-4/jboss-javaee-6.0-3.0.2.Final-redhat-4.pom



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5605) ssh-wagon hangs

2014-07-17 Thread Jason van Zyl (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349933#comment-349933
 ] 

Jason van Zyl commented on MNG-5605:


Did how did you use the different versions? Did you also make sure you were 
using the different versions of jsch? Wagon 2.4 uses 0.1.44-1, while Wagon 2.6 
uses 0.1.50.

 ssh-wagon hangs
 ---

 Key: MNG-5605
 URL: https://jira.codehaus.org/browse/MNG-5605
 Project: Maven
  Issue Type: Bug
  Components: Deployment
Affects Versions: 3.2.1
Reporter: Frank Cornelis
Priority: Blocker

 When releasing (using maven-release-plugin) via Maven 3.1.1 everything works 
 as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden 
 hangs on the second ssh upload.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MNG-5605) ssh-wagon hangs

2014-07-17 Thread Allan (JIRA) 

[ 
https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349934#comment-349934
 ] 

Allan commented on MNG-5605:


I assumed that locking the version in the extension declaration would use the 
same version regardless of which version of maven I'm using.
{code:xml}
build
...
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ssh/artifactId
version2.6/version
/extension
/build
{code}

Is that not the case?

Also, I didn't do anything else to control the jsch version.

 ssh-wagon hangs
 ---

 Key: MNG-5605
 URL: https://jira.codehaus.org/browse/MNG-5605
 Project: Maven
  Issue Type: Bug
  Components: Deployment
Affects Versions: 3.2.1
Reporter: Frank Cornelis
Priority: Blocker

 When releasing (using maven-release-plugin) via Maven 3.1.1 everything works 
 as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden 
 hangs on the second ssh upload.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCOMPILER-228) cannot assign a value to final variable in lamda

2014-07-17 Thread Robert Scholte (JIRA) 

 [ 
https://jira.codehaus.org/browse/MCOMPILER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MCOMPILER-228:
-

Description: 
Code example compiles in Eclipse, but not with Maven Compiler Plugin. Code is 
like below (inside a lamda expression)
{code}
final x;
if (some condition)
x = a;
else if (some other condition)
x = b;
else 
x = c;
{code}
See attached example source.
{noformat}
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project MediaIndexer: Compilation failure: Compilation failure:
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[11,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[14,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[17,13] 
cannot assign a value to final variable compareTo
{noformat}
The workaround is to remove final for the variable and just ensure that the 
value is assigned in each code path.

  was:
Code example compiles in Eclipse, but not with Maven Compiler Plugin. Code is 
like below (inside a lamda expression)
final x;
if (some condition)
x = a;
else if (some other condition)
x = b;
else 
x = c;

See attached example source.

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on 
project MediaIndexer: Compilation failure: Compilation failure:
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[11,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[14,13] 
cannot assign a value to final variable compareTo
[ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[17,13] 
cannot assign a value to final variable compareTo

The workaround is to remove final for the variable and just ensure that the 
value is assigned in each code path.


 cannot assign a value to final variable in lamda
 

 Key: MCOMPILER-228
 URL: https://jira.codehaus.org/browse/MCOMPILER-228
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.1
 Environment: Windows 7 64 bit, Maven 3.2.2, JDK 64 bit 8u5
Reporter: Robert Kish
Priority: Minor
 Attachments: FinalExample.java


 Code example compiles in Eclipse, but not with Maven Compiler Plugin. Code is 
 like below (inside a lamda expression)
 {code}
 final x;
 if (some condition)
 x = a;
 else if (some other condition)
 x = b;
 else 
 x = c;
 {code}
 See attached example source.
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
 on project MediaIndexer: Compilation failure: Compilation failure:
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[11,13] 
 cannot assign a value to final variable compareTo
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[14,13] 
 cannot assign a value to final variable compareTo
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[17,13] 
 cannot assign a value to final variable compareTo
 {noformat}
 The workaround is to remove final for the variable and just ensure that the 
 value is assigned in each code path.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (MCOMPILER-228) cannot assign a value to final variable in lamda

2014-07-17 Thread Robert Scholte (JIRA) 

 [ 
https://jira.codehaus.org/browse/MCOMPILER-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte updated MCOMPILER-228:
-

Attachment: MCOMPILER-228.patch

Attaching example as integration test. I've reproduces it with {{Java version: 
1.8.0, vendor: Oracle Corporation}}
I need to verify this with the most recent version of JDK8. If that still has 
the same issue, we'll report it to Oracle.

 cannot assign a value to final variable in lamda
 

 Key: MCOMPILER-228
 URL: https://jira.codehaus.org/browse/MCOMPILER-228
 Project: Maven Compiler Plugin
  Issue Type: Bug
Affects Versions: 3.1
 Environment: Windows 7 64 bit, Maven 3.2.2, JDK 64 bit 8u5
Reporter: Robert Kish
Priority: Minor
 Attachments: FinalExample.java, MCOMPILER-228.patch


 Code example compiles in Eclipse, but not with Maven Compiler Plugin. Code is 
 like below (inside a lamda expression)
 {code}
 final x;
 if (some condition)
 x = a;
 else if (some other condition)
 x = b;
 else 
 x = c;
 {code}
 See attached example source.
 {noformat}
 [ERROR] Failed to execute goal 
 org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) 
 on project MediaIndexer: Compilation failure: Compilation failure:
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[11,13] 
 cannot assign a value to final variable compareTo
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[14,13] 
 cannot assign a value to final variable compareTo
 [ERROR] /C:/MAPS/MediaIndexer/src/main/java/example/FinalExample.java:[17,13] 
 cannot assign a value to final variable compareTo
 {noformat}
 The workaround is to remove final for the variable and just ensure that the 
 value is assigned in each code path.



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SCM-765) jgit provider commits changes with system user instead of passed username

2014-07-17 Thread Dominik Bartholdi (JIRA) 

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

Dominik Bartholdi reassigned SCM-765:
-

Assignee: Dominik Bartholdi

 jgit provider commits changes with system user instead of passed username
 -

 Key: SCM-765
 URL: https://jira.codehaus.org/browse/SCM-765
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.9
Reporter: Dominik Bartholdi
Assignee: Dominik Bartholdi
 Fix For: 1.10


 When using the jgit provider over http, it allows to define username / 
 password like this:
 {code}
 mvn release:prepare release:perform -Dresume=false -Dusername=myuser 
 -Dpassword=XXX
 {code}
 But the commit will not be done with the given user but with the system user 
 who started the process, instead the passed user is only used for transport. 
 Well that might be fine in the first thought, but it will mean in the git 
 repository it is not recorded who really did make the release. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

[jira] (SCM-765) jgit provider commits changes with system user instead of passed username

2014-07-17 Thread Dominik Bartholdi (JIRA) 

[ 
https://jira.codehaus.org/browse/SCM-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=349944#comment-349944
 ] 

Dominik Bartholdi commented on SCM-765:
---

PR placed https://github.com/apache/maven-scm/pull/16

 jgit provider commits changes with system user instead of passed username
 -

 Key: SCM-765
 URL: https://jira.codehaus.org/browse/SCM-765
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.9
Reporter: Dominik Bartholdi
 Fix For: 1.10


 When using the jgit provider over http, it allows to define username / 
 password like this:
 {code}
 mvn release:prepare release:perform -Dresume=false -Dusername=myuser 
 -Dpassword=XXX
 {code}
 But the commit will not be done with the given user but with the system user 
 who started the process, instead the passed user is only used for transport. 
 Well that might be fine in the first thought, but it will mean in the git 
 repository it is not recorded who really did make the release. 



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)