Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/39
---
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
+1
On 17 June 2014 05:33, Robert Scholte wrote:
> +1
>
> * maven-ear-plugin-2.9.1-source-release.zip results in BUILD SUCCESS
> * [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated: 0
> approved: 330 licence.
> * SHA1 correct
> * Site is ok
>
> Robert
>
> Op Sun, 15 Jun 2014 1
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46256490
I will push this in right after I cut the 3.2.2.
---
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 pro
Ok, fixed a few more things over the weekend and I think all is good.
If no other problems surface I'll stage it tomorrow morning (EDT).
On Jun 14, 2014, at 2:53 PM, Hervé BOUTEMY wrote:
> Le samedi 14 juin 2014 13:51:21 Jason van Zyl a écrit :
>> So my current plan is to roll in Christian's ch
GitHub user Stephan202 opened a pull request:
https://github.com/apache/maven-surefire/pull/39
Remove JUnit4Provider.java.orig.
The file
`surefire-providers/surefire-junit4/src/main/java/org/apache/maven/surefire/junit4/JUnit4Provider.java.orig`
was accidentally committed in 3274bd
+1
* maven-ear-plugin-2.9.1-source-release.zip results in BUILD SUCCESS
* [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated:
0 approved: 330 licence.
* SHA1 correct
* Site is ok
Robert
Op Sun, 15 Jun 2014 16:23:51 +0200 schreef Karl Heinz Marbaise
:
Hi,
We solved 2
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/22#issuecomment-46200202
You may want to try running the script described in here just to make sure
the Maven ITs are not affected by the change. We have several ITs that
specifically look at log o
GitHub user a-horst opened a pull request:
https://github.com/apache/maven/pull/22
- logging configuration now no longer overwrites the default log level
- logging configuration now no longer overwrites the default log level as
specified in conf/logging/simplelogger.properties (see
On Jun 16, 2014, at 8:22 AM, Nigel Magnay wrote:
> Ah, I'm using 0.9.0.M3, should I downgrade it ? Ideally I'd like to be able
> to support all versions of maven (this is actually being upgraded as things
>> maven 3.0.x aren't working)
>
Then don't use Aether. Look at the technique used in the
Ah, I'm using 0.9.0.M3, should I downgrade it ? Ideally I'd like to be able
to support all versions of maven (this is actually being upgraded as things
> maven 3.0.x aren't working)
It seems a bit messy that if I'm using aether in a module, and I want to
use that module directly in a maven plugin,
You are using Aether 1.0, stick with 0.9.0.M2. Maven itself hasn't upgraded to
1.0. The version used in the core is exported for use in plugins.
On Jun 16, 2014, at 6:06 AM, Nigel Magnay wrote:
> Hi
>
> I have some pre-existing code that uses org.eclipse.aether, that works fine.
>
> However,
Hi
I have some pre-existing code that uses org.eclipse.aether, that works fine.
However, when I reference it and invoke it from a maven-plugin, I get
A required class was missing while executing :
org.eclipse.aether.spi.connector.transport.TransporterFactory
Looking at the urls spat out, it se
That's it... and also note that while Maven complains if the pom at the
specified is not the parent, it will build correctly ...
just resolving the parent from the local repository and not from the disk.
On 16 June 2014 06:05, Barrie Treloar wrote:
> On 16 June 2014 14:12, Stephen Connolly
>
13 matches
Mail list logo
