+1:
3.5.1 works in my project like a charm ;-)
On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12338964&styleName=Text&projectId=12316922
>
> There are 35
I have no issue build maven 3.5.2-SNAPSHOT with clean verify at top level,
but the following build fails
mvn clean verify -f apache-maven
C:\views\dev\maven\maven>mvn clean verify -f apache-maven
[INFO] Scanning for projects...
[INFO]
[INFO]
-
I wonder if mng-6275 is affecting that plugin
On Mon 11 Sep 2017 at 01:00, Mark Derricutt wrote:
> +0 non-commital -
>
> Tested on our tiles/osgi based projects and all seems to work, but for
> some reason - one project that uses the
> org.openqa.selenium.phantomjs.PhantomJSDriverService seems t
just tested "mvn verify" on Maven (did not build it previously, then no 3.5.2-
SNAPSHOT artifact in my local repo), and works like a charm (as expected since
artifacts are resolved from reactor)
I can't reproduce the issue: does anybody else have same problems?
Regards,
Hervé
Le dimanche 10 se
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
Thank you.
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apa
Github user Fuud closed the pull request at:
https://github.com/apache/maven-surefire/pull/114
---
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
We solved 24 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12340297
There are 101 issues left in JIRA:
https://issues.apache.org/jira/i#issues/?jql=project+%3D+SUREFIRE+AND+status+%3D+Open+ORDER+BY+priority+DESC
Staging repo:
https://repository.apa
+0 non-commital -
Tested on our tiles/osgi based projects and all seems to work, but for some
reason - one project that uses the
org.openqa.selenium.phantomjs.PhantomJSDriverService seems to blowing up when
using 3.5.1 - need to do some more digging and see if I can spot whats going on.
Will t
+1
On 9 September 2017 at 23:52, Karl Heinz Marbaise wrote:
> Hi,
>
> this is the VOTE for the first public release for Maven JMod Plugin...
>
> We solved 1 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12321433&version=12341363
>
> There are currently no issues l
+1
On 11 September 2017 at 03:45, Stephane Nicoll
wrote:
> +1
>
> Thanks!
>
> On Sat, Sep 9, 2017 at 2:34 PM, Karl Heinz Marbaise
> wrote:
>
> > Hi,
> >
> > We solved 7 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12317227&version=12341254
> >
> > There are
Might just be the test is looking for an implementation class not available
on those jres. Do you have the failure messages
On Sun 10 Sep 2017 at 22:29, Tibor Digana
wrote:
> You think it has to do you the commit fixing Class Loader issue or the
> previous commits as well?
>
> On Sun, Sep 10, 20
Looks like 3.5.1 not able to resolve snapshot dependencies
i just clone out apache-maven and, change directory to apache-maven and
build from there
here is error
[ERROR] Failed to execute goal on project apache-maven: Could not resolve
dependencies for project org.apache.maven:apache-maven:pom:3
Hello,
Only lurking those days, but chiming in quickly here :-).
2017-09-10 20:54 GMT+02:00 Robert Scholte :
> On Sun, 10 Sep 2017 20:21:11 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> On Sun 10 Sep 2017 at 19:04, Tibor Digana wrote:
>>
>> Hi All,
>>>
>>> Are we facin
You think it has to do you the commit fixing Class Loader issue or the
previous commits as well?
On Sun, Sep 10, 2017 at 11:23 PM, Michael Osipov
wrote:
> Am 2017-09-10 um 23:19 schrieb Tibor Digana:
>
>> Definitely I agree!
>> Let's see if it is JDK issue or platform issue. Let's exclude Oracle
Am 2017-09-10 um 23:19 schrieb Tibor Digana:
Definitely I agree!
Let's see if it is JDK issue or platform issue. Let's exclude Oracle Java
suspicion and then it's serious issue.
Not a platform one. Reproduced on Windows 10 with Zulu 7 Update 154. I
will download Oracla Java 7 from MOSC and tes
Definitely I agree!
Let's see if it is JDK issue or platform issue. Let's exclude Oracle Java
suspicion and then it's serious issue.
On Sun, Sep 10, 2017 at 11:17 PM, Michael Osipov
wrote:
> Am 2017-09-10 um 23:15 schrieb Tibor Digana:
>
>> This one 1.7.0_80 which is 7u80:
>> http://www.oracle.c
Am 2017-09-10 um 23:15 schrieb Tibor Digana:
This one 1.7.0_80 which is 7u80:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html
No one will seriously run this one. So if we say that our stuff runs off
7 then we have to test OpenJDK and Zulu too.
This one 1.7.0_80 which is 7u80:
http://www.oracle.com/technetwork/java/javase/downloads/java-archive-downloads-javase7-521261.html
On Sun, Sep 10, 2017 at 11:12 PM, Michael Osipov wrote:
> Am 2017-09-10 um 23:07 schrieb Tibor Digana:
>
>> Michael, now try with Oracle Java 7.
>>
>
> Last public
Am 2017-09-10 um 23:07 schrieb Tibor Digana:
Michael, now try with Oracle Java 7.
Last public version or up-to-date paid version?
On Sun, Sep 10, 2017 at 11:02 PM, Michael Osipov
wrote:
Am 2017-09-10 um 22:27 schrieb Stephen Connolly:
Well I ran the release with 1.7.0_80 which iirc is th
Michael, now try with Oracle Java 7.
On Sun, Sep 10, 2017 at 11:02 PM, Michael Osipov
wrote:
> Am 2017-09-10 um 22:27 schrieb Stephen Connolly:
>
>> Well I ran the release with 1.7.0_80 which iirc is the last public release
>> of Oracle Java 7...
>>
>
> Fails also on Windows with Zulu 7:
> $ mvn
Am 2017-09-10 um 22:27 schrieb Stephen Connolly:
Well I ran the release with 1.7.0_80 which iirc is the last public release
of Oracle Java 7...
Fails also on Windows with Zulu 7:
$ mvn -v
Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T21:39:06+02:00)
Maven home: D:\E
Well I ran the release with 1.7.0_80 which iirc is the last public release
of Oracle Java 7...
On Sun 10 Sep 2017 at 21:08, Michael Osipov wrote:
> Folks,
>
> tried running master on
> Maven home: /usr/local/share/java/maven
> Java version: 1.7.0_151, vendor: Oracle Corporation
> Java home: /us
Folks,
tried running master on
Maven home: /usr/local/share/java/maven
Java version: 1.7.0_151, vendor: Oracle Corporation
Java home: /usr/local/openjdk7/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "freebsd", version: "11.1-release-p1", arch: "i386", family: "unix"
and I get thi
Tested on several projects
+1
On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12338964&styleName=Text&projectId=12316922
>
> There are 350 issues left in
Robert,
>>And if we're focusing on the latter, shouldn't the twitter question be
Good remark! I am not against such question on Twitter but I would be
interested in one more in comparison to Gradle.
*What the Maven should improve to make Maven more attractive against
Gradle?*
Because I don't th
On Sun, 10 Sep 2017 20:21:11 +0200, Stephen Connolly
wrote:
On Sun 10 Sep 2017 at 19:04, Tibor Digana wrote:
Hi All,
Are we facing new API regarding networking and security useful in Java
8?
When I first saw these options I asked myself what benefit would have
the
User and Jenkins
Stephen,
I was pragmatic and did not want to push users to use Maven&Java8 only
because JDK 7 is weak.
First the interest should go from inside, this means API and then users.
I agree with Michael whether we should better focus on Maven 4 and POM
structure.
For instance today everybody could no
Am 2017-09-10 um 19:07 schrieb Stephen Connolly:
Hervé and I discussed on irc earlier today.
My suggestion - I was going to write up tomorrow - is that we drop 7 for
3.6.x
We should focus 3.6.x on making the codebase Java 8 (lambdas, replace
FileStream with the non-file handle leak version,
On Sun 10 Sep 2017 at 19:04, Tibor Digana wrote:
> Hi All,
>
> Are we facing new API regarding networking and security useful in Java 8?
>
> When I first saw these options I asked myself what benefit would have the
> User and Jenkins from Java 8.
> And second question was whether we would be so f
Hi All,
Are we facing new API regarding networking and security useful in Java 8?
When I first saw these options I asked myself what benefit would have the
User and Jenkins from Java 8.
And second question was whether we would be so flexible to rewrite the code
and use Lambda fully anywhere in th
+1
Thanks!
On Sat, Sep 9, 2017 at 2:34 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317227&version=12341254
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=p
Hervé and I discussed on irc earlier today.
My suggestion - I was going to write up tomorrow - is that we drop 7 for
3.6.x
We should focus 3.6.x on making the codebase Java 8 (lambdas, replace
FileStream with the non-file handle leak version, adopt Path, etc) with
a view to encourage contribu
But on twitter thus probably far from being a good representation of our
users ...
Le dim. 10 sept. 2017 à 18:45, Gary Gregory a
écrit :
> On Sep 10, 2017 10:33, "Robert Scholte" wrote:
>
> So what would be the conclusion?
>
> 35% want to keep Java7 as JRE for Maven for a shorter or longer peri
On Sep 10, 2017 10:33, "Robert Scholte" wrote:
So what would be the conclusion?
35% want to keep Java7 as JRE for Maven for a shorter or longer period?
IMHO that's a lot
but less than the 65% who do not, an overwhelming majority.
Gary
Robert
On Sun, 10 Sep 2017 11:55:20 +0200, Stephen Co
So what would be the conclusion?
35% want to keep Java7 as JRE for Maven for a shorter or longer period?
IMHO that's a lot
Robert
On Sun, 10 Sep 2017 11:55:20 +0200, Stephen Connolly
wrote:
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven 3.6.x
65% want Java 8&9 for Maven
Analyzer...
stagingUrl: https://repository.apache.org/content/repositories/maven-1364
groupId: org.apache.maven
artifactId: apache-maven
version: 3.5.1
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1364/org/apache/maven/apache-maven/3.5.1/apache-maven-3.5.1-src.z
Hi,
We solved 25 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338964&styleName=Text&projectId=12316922
There are 350 issues left in JIRA for Maven core:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20
So poll results:
493 votes cast
25% want Java 7,8&9 for Maven 3.6.x
65% want Java 8&9 for Maven 3.6.x
10% want Java 8&9 for Maven 3.6.x and 6 months of backporting to 3.5.x
On Sat 9 Sep 2017 at 11:50, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://twitter.com/asfmavenproje
38 matches
Mail list logo
