Hi Robert Kristian,
Early Access build for JDK 8u60 b18 http://jdk8.java.net/download.html
is available on java.net, summary of changes are listed here.
http://www.java.net/download/jdk8u60/changes/jdk8u60-b18.html
As we enter the later phases of development for JDK 8u60, please log any
https://issues.apache.org/jira/browse/MNG-5840
Can some other people see if this test case I attached to this issue is
replicated in their environments?
I've been badly bitten by this a couple of times (and worse for me, I have
a project that needs 3.3.1+ to build due to bugs that were only
On 5 June 2015 at 10:58, Tamas Cservenak ta...@cservenak.net wrote:
Same here, testcase does same as for you:
https://gist.github.com/cstamas/dd6a000e97b2c5333f01
But isn’t this the intended way?
If parent found on relative path, it takes precendence over one coming
from local/remote repo?
It still seems correct as per the quote provided above, even if it didn't
used to work this way. Is there anywhere else where it specifies the
behaviour that you've come to expect?
I see a few cases:
gid + aid = error or at least warning for no version, unless ../pom.xml
exists
gid + aid + ver =
Your tar file is polluted with ._ stuff that ends up laying around the
place. Aside from that:
3.1.1 succeeds.
3.3.3 fails
The description of what is wrong/your expectation could be better.
I guess I would expect it to fail, but fail because relative path POM
version doesn't match that
Same here, testcase does same as for you:
https://gist.github.com/cstamas/dd6a000e97b2c5333f01
But isn’t this the intended way?
If parent found on relative path, it takes precendence over one coming from
local/remote repo?
As per http://maven.apache.org/pom.html#Inheritance
Notice the
I expect it to pass because the local repository has the correct version.
Consider the case where you have separate GIT roots for your different
modules (because they have a separate release lifecycle)
Your parent project will have version 4-SNAPSHOT
The sibling child project will reference
Fred: does
https://issues.apache.org/jira/browse/MNG-5840?focusedCommentId=14574303page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14574303
explain the issue better?
On 5 June 2015 at 11:05, Fred Cooke fred.co...@gmail.com wrote:
Your tar file is polluted with ._
On 5 June 2015 at 13:04, Fred Cooke fred.co...@gmail.com wrote:
It still seems correct as per the quote provided above, even if it didn't
used to work this way. Is there anywhere else where it specifies the
behaviour that you've come to expect?
I see a few cases:
gid + aid = error or at
If this is the behaviour we all agree to, and I think we do, you need to write
an IT as well. If you have great, if you haven’t please do so. Otherwise it’s
just potentially going to regress again.
On Jun 5, 2015, at 6:26 AM, steph...@apache.org wrote:
Repository: maven
Updated Branches:
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/97
[SUREFIRE-1067] Nested causes conflated with wrapper exception
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Tibor17/maven-surefire s2
The Apache Maven team is pleased to announce the release of the Apache
Maven Assembly Plugin, version 2.5.5
The Assembly Plugin for Maven is primarily intended to allow users to aggregate
the project output along with its dependencies, modules, site documentation,
and other files into a single
I'll see if I can create an integration test from my test case
On 5 June 2015 at 14:27, Jason van Zyl ja...@takari.io wrote:
If this is the behaviour we all agree to, and I think we do, you need to
write an IT as well. If you have great, if you haven’t please do so.
Otherwise it’s just
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/95
---
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 closed the pull request at:
https://github.com/apache/maven-shared/pull/9
---
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
15 matches
Mail list logo