all done.
Enjoy!! :-)
On 8 October 2014 07:58, Olivier Lamy wrote:
> Sure I will later today.
>
> --
> Olivier
>
> On 8 Oct 2014 03:54, "John Casey" wrote:
>>
>> Right, well I should have seen that coming...I can't push to the canonical
>> git repo, so I can't tag, and can't run the release:prep
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/52
---
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 Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/52
[SUREFIRE-1082] Parallelization does not work as expected when using jUn...
...it Parameterized
This is not a fix.
Commit only IT.
The IT proves expected behavior in [SUREFIRE
I'm having some trouble understanding this result:
https://builds.apache.org/job/maven-plugins-ITs-m3-windows/751/consoleFull
It looks like it's having trouble because it's using snapshots of other
plugins that are being built in that job. It doesn't appear to run the
compiler plugin integrati
Sure I will later today.
--
Olivier
On 8 Oct 2014 03:54, "John Casey" wrote:
> Right, well I should have seen that coming...I can't push to the canonical
> git repo, so I can't tag, and can't run the release:prepare step. Duh!
>
> @Olivier, would you mind pushing that release?
>
> Thanks!
>
> -j
Github user Tibor17 closed the pull request at:
https://github.com/apache/maven-surefire/pull/51
---
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
I think it's fixed now; I added a jdk min version to the failing IT.
We'll see what Jenkins thinks of it now.
On 10/07/2014 01:56 PM, Robert Scholte wrote:
https://builds.apache.org/job/maven-plugins-ITs-m3-windows/ws/maven-compiler-plugin/target/it/MCOMPILER-157/build.log
Keep in mind that t
Hi,
We solved 4 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11147&version=20597
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MSOURCES%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Stagin
Hi,
currently i'm faced with a strange thing which i currently don't
understand...
I'm trying to upgrade maven-war-plugin to Maven 2.2.1 dependencies...
So i have changed mavenVersion property in maven-war-plugin pom to 2.2.1
and compiled but i got a compile error:
[ERROR]
/Users/kama/ap
https://builds.apache.org/job/maven-plugins-ITs-m3-windows/ws/maven-compiler-plugin/target/it/MCOMPILER-157/build.log
Keep in mind that this IT fails on our buildserver.
I think it requires a different version of the JDK.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-p
Right, well I should have seen that coming...I can't push to the
canonical git repo, so I can't tag, and can't run the release:prepare
step. Duh!
@Olivier, would you mind pushing that release?
Thanks!
-john
On 10/06/2014 01:14 PM, John Casey wrote:
Thanks, I'll give it a shot tomorrow most
Hi
I think I found a bug in Maven when working in forked lifecycle, like
"cobertura" lifecycle.
Look at these two example projects:
http://sbt-compiler-maven-plugin.googlecode.com/svn/tmp/bug-in-forked-lifecycle/
There are logs from "mvn test -X", "mvn cobertura:cobertura -X" and "mvn
site -X" ex
12 matches
Mail list logo