[jira] (MRELEASE-851) javaHome is ignored and inherited unexpected

2015-03-31 Thread Robert Scholte (JIRA)

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

Robert Scholte updated MRELEASE-851:


Description: 
The release: mojos have a configuration {{javaHome}} which defaults to 
$\{java.home}. From reading the documentation it seems like this is used to 
propagate the JAVA version of the marent process to the invoked build of 
prepare and perform. This inheritance is important in order to properly support 
compiles. The documentation does not mention that the option is ignored.

The following proposed patch might be able to solve the problem by setting the 
JAVA_HOME variable as documented. This also helps some situations where CI 
servers not reliable replicate builds.

The patch does not include it, but most likely it should also be noted that 
{{MAVEN_SKIP_RC=true}} should be added to the child's env.

https://github.com/apache/maven-release/pull/5



  was:
The release: mojos have a configuration javaHome which defaults to 
${java.home}. From reading the documentation it seems like this is used to 
propagate the JAVA version of the marent process to the invoked build of 
prepare and perform. This inheritance is important in order to properly support 
compiles. The documentation does not mention that the option is ignored.

The following proposed patch might be able to solve the problem by setting the 
JAVA_HOME variable as documented. This also helps some situations where CI 
servers not reliable replicate builds.

The patch does not include it, but most likely it should also be noted that 
MAVEN_SKIP_RC=true should be added to the child's env.

https://github.com/apache/maven-release/pull/5




 javaHome is ignored and inherited unexpected
 

 Key: MRELEASE-851
 URL: https://jira.codehaus.org/browse/MRELEASE-851
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Bernd Eckenfels
  Labels: github-pullrequest

 The release: mojos have a configuration {{javaHome}} which defaults to 
 $\{java.home}. From reading the documentation it seems like this is used to 
 propagate the JAVA version of the marent process to the invoked build of 
 prepare and perform. This inheritance is important in order to properly 
 support compiles. The documentation does not mention that the option is 
 ignored.
 The following proposed patch might be able to solve the problem by setting 
 the JAVA_HOME variable as documented. This also helps some situations where 
 CI servers not reliable replicate builds.
 The patch does not include it, but most likely it should also be noted that 
 {{MAVEN_SKIP_RC=true}} should be added to the child's env.
 https://github.com/apache/maven-release/pull/5



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


[jira] (MRELEASE-851) javaHome is ignored and inherited unexpected

2013-11-09 Thread Robert Scholte (JIRA)

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

Robert Scholte updated MRELEASE-851:


Labels: github-pullrequest  (was: )

 javaHome is ignored and inherited unexpected
 

 Key: MRELEASE-851
 URL: https://jira.codehaus.org/browse/MRELEASE-851
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Bernd Eckenfels
  Labels: github-pullrequest

 The release: mojos have a configuration javaHome which defaults to 
 ${java.home}. From reading the documentation it seems like this is used to 
 propagate the JAVA version of the marent process to the invoked build of 
 prepare and perform. This inheritance is important in order to properly 
 support compiles. The documentation does not mention that the option is 
 ignored.
 The following proposed patch might be able to solve the problem by setting 
 the JAVA_HOME variable as documented. This also helps some situations where 
 CI servers not reliable replicate builds.
 The patch does not include it, but most likely it should also be noted that 
 MAVEN_SKIP_RC=true should be added to the child's env.
 https://github.com/apache/maven-release/pull/5

--
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] (MRELEASE-851) javaHome is ignored and inherited unexpected

2013-10-24 Thread Bernd Eckenfels (JIRA)

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

Bernd Eckenfels updated MRELEASE-851:
-

Description: 
The release: mojos have a configuration javaHome which defaults to 
${java.home}. From reading the documentation it seems like this is used to 
propagate the JAVA version of the marent process to the invoked build of 
prepare and perform. This inheritance is important in order to properly support 
compiles. The documentation does not mention that the option is ignored.

The following proposed patch might be able to solve the problem by setting the 
JAVA_HOME variable as documented. This also helps some situations where CI 
servers not reliable replicate builds.

The patch does not include it, but most likely it should also be noted that 
MAVEN_SKIP_RC=true should be added to the child's env.

https://github.com/apache/maven-release/pull/5



  was:
The release: mojos have a configuration javaHome which defaults to 
${java.home}. From reading the documentation it seems like this is used to 
propagate the JAVA version of the marent process to the invoked build of 
prepare and perform. This inheritance is important in order to properly support 
compiles. The documentation does not mention that the option is ignored.

The following proposed patch might be able to solve the problem by setting the 
JAVA_HOME variable as documented. This also helps some situations where CI 
servers not reliable replicate builds.

The patch does not include it, but most likely it should also be noted that 
MAVEN_SKIP_RC=true should be added to the child's env.




 javaHome is ignored and inherited unexpected
 

 Key: MRELEASE-851
 URL: https://jira.codehaus.org/browse/MRELEASE-851
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Bernd Eckenfels

 The release: mojos have a configuration javaHome which defaults to 
 ${java.home}. From reading the documentation it seems like this is used to 
 propagate the JAVA version of the marent process to the invoked build of 
 prepare and perform. This inheritance is important in order to properly 
 support compiles. The documentation does not mention that the option is 
 ignored.
 The following proposed patch might be able to solve the problem by setting 
 the JAVA_HOME variable as documented. This also helps some situations where 
 CI servers not reliable replicate builds.
 The patch does not include it, but most likely it should also be noted that 
 MAVEN_SKIP_RC=true should be added to the child's env.
 https://github.com/apache/maven-release/pull/5

--
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] (MRELEASE-851) javaHome is ignored and inherited unexpected

2013-10-24 Thread Bernd Eckenfels (JIRA)

[ 
https://jira.codehaus.org/browse/MRELEASE-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=334626#comment-334626
 ] 

Bernd Eckenfels commented on MRELEASE-851:
--

Seems I forgot the link, added it. I will also add a sample pom which can 
reproduce the problem (but I am not familiar with testing harness to make a 
unit test out of it)

 javaHome is ignored and inherited unexpected
 

 Key: MRELEASE-851
 URL: https://jira.codehaus.org/browse/MRELEASE-851
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Bernd Eckenfels

 The release: mojos have a configuration javaHome which defaults to 
 ${java.home}. From reading the documentation it seems like this is used to 
 propagate the JAVA version of the marent process to the invoked build of 
 prepare and perform. This inheritance is important in order to properly 
 support compiles. The documentation does not mention that the option is 
 ignored.
 The following proposed patch might be able to solve the problem by setting 
 the JAVA_HOME variable as documented. This also helps some situations where 
 CI servers not reliable replicate builds.
 The patch does not include it, but most likely it should also be noted that 
 MAVEN_SKIP_RC=true should be added to the child's env.
 https://github.com/apache/maven-release/pull/5

--
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] (MRELEASE-851) javaHome is ignored and inherited unexpected

2013-10-23 Thread Bernd Eckenfels (JIRA)
Bernd Eckenfels created MRELEASE-851:


 Summary: javaHome is ignored and inherited unexpected
 Key: MRELEASE-851
 URL: https://jira.codehaus.org/browse/MRELEASE-851
 Project: Maven Release Plugin
  Issue Type: Bug
Affects Versions: 2.4.1
Reporter: Bernd Eckenfels


The release: mojos have a configuration javaHome which defaults to 
${java.home}. From reading the documentation it seems like this is used to 
propagate the JAVA version of the marent process to the invoked build of 
prepare and perform. This inheritance is important in order to properly support 
compiles. The documentation does not mention that the option is ignored.

The following proposed patch might be able to solve the problem by setting the 
JAVA_HOME variable as documented. This also helps some situations where CI 
servers not reliable replicate builds.

The patch does not include it, but most likely it should also be noted that 
MAVEN_SKIP_RC=true should be added to the child's env.



--
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