+1
On 24 March 2015 at 05:45, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11130&version=20684
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%20%3D%
> 20MCOMPILER%20AN
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/75
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/83
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hello there, I now have a workaround. I am setting:
${maven.home}
in maven-release-manager/pom.xml and use this to set:
releaseEnvironment.setMavenHome( new File( System.getProperty(
"injectedMavenHome" ) ) );
in the testcase.
Works fine from the command line.
Regards Mirko
--
http://illegals
Am Wed, 25 Mar 2015 21:01:53 +0100
schrieb Mirko Friedenhagen :
> - however this will not help with IDEs like Eclipse or Intellij which
> use their own code to invoke stuff.
I guess it is better when you pass it as a system property:
-Dmaven.home="${M2_HOME}"
that way you dont need to export it
Hi Mirko,
On 3/25/15 9:31 PM, Mirko Friedenhagen wrote:
What I do not understand is, that
https://builds.apache.org/view/All/job/maven-release/261/consoleFull
is just running fine with Maven 3.0.5. Two wild guesses:
- it is because we do not use a Jenkins freestyle job but a beloved by
Stephen ;
What I do not understand is, that
https://builds.apache.org/view/All/job/maven-release/261/consoleFull
is just running fine with Maven 3.0.5. Two wild guesses:
- it is because we do not use a Jenkins freestyle job but a beloved by
Stephen ;-) Maven job.
- or maybe something changed with shellshock,
+1
Dan
> On Mar 25, 2015, at 4:10 PM, Karl Heinz Marbaise wrote:
>
> Hi,
>
> here is my +1.
>
> Two more binding VOTE's needed.
>
> Kind regards
> Karl Heinz Marbaise
>
> On 3/23/15 7:45 PM, Karl Heinz Marbaise wrote:
>> Hi,
>>
>> We solved 5 issues:
>> http://jira.codehaus.org/secure/Re
Unfortunately, we may not use Assume in this testcase because it is
derived from PlexusTestcase and this one does fail on
AssumptionViolated as well. As a dirty workaround we could just return
when System.getenv("M2_HOME") is null.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https:/
+1
On Mar 25, 2015, at 4:10 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> here is my +1.
>
> Two more binding VOTE's needed.
>
> Kind regards
> Karl Heinz Marbaise
>
> On 3/23/15 7:45 PM, Karl Heinz Marbaise wrote:
>> Hi,
>>
>> We solved 5 issues:
>> http://jira.codehaus.org/secure/ReleaseNote.j
Hi,
here is my +1.
Two more binding VOTE's needed.
Kind regards
Karl Heinz Marbaise
On 3/23/15 7:45 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 5 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11130&version=20684
There are still a couple of issues left in JIRA:
http://
Hello,
further inspection of the problem leads to a possible solution:
- the shell script does retrieve M2_HOME, however, as it is not
exported it is not available furtheron.
- so a quick fix would be to export M2_HOME directly before invoking
exec "$JAVACMD" ...
- however this will not help with
12 matches
Mail list logo
