Hi Bernd,
Bernd wrote:
Hello,
I am not sure where to get the codehaus.org JIRA account. Do I have to
contact somebody at Apache or Codehaus?
xircles.codehaus.org (you need a full account, an account to manage the
mailing lists only is not enough for JIRA).
- Jörg
Hello,
there are some bugs[1] in regard to Jenkins/Maven-Release-Plugin where the
forked maven instance picks up the wrong Java version (and therefore
creates problems with compiler settings-bootclasspath and similiar).
There are some Jenkins discussions around that, but I think the actual
Hi Berndt,
If I understand correctly your issue is actually not a maven one but
related to maven integration in Jenkins.
This is not the right mailing list for this issue, please address it to
Jenkins developers ml.
About your patch attachment, it didn't go through the ml. It's generally
better to
Hello,
my Issue is that the maven Release plugin fails to set-up a reproduceable
environment and that it confusingly even has unused mojo attributes (which are
documented to solve the problem but are nowhere honored).
I was mentioning the CI Environment only to make clear that it is a known
Hello,
I am not sure where to get the codehaus.org JIRA account. Do I have to
contact somebody at Apache or Codehaus?
Anyway, meanwhile the (proposed) changed are here:
https://github.com/ecki/maven-release/compare/apache:trunk...topic-javahome
Greetings
Bernd
2013/10/22 Baptiste Mathus
