How would we handle this wrt versions of our plugins when the requirements
for those are bumped from Java 6 to Java 7?
For example, maven-jar-plugin has plexus-archiver as a dependency. m-jar-p
v3.0.2 requires Java 6. Is a bump to v3.1.0 enough for going to Java 7?
/Anders
On Thu, May 4, 2017
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
With pure JUnit it is not possible.
You can only place @Test annotation on method => there will be at least one
test in TestClass.
---
If your project is set up for it, you can reply to
Hi Mario,
I've marked it as 3.5.1-candidate.
Patch looks complete to me.
Robert
On Fri, 05 May 2017 11:17:39 +0200, Mario Krizmanic
wrote:
Hi,
MNG-6127 is ready with included IT.
Could you include and merge it?
I need it for my maven plugins.
Best regards,
Hi Andreas,
fixed.
Unlike most other ASF projects, Maven has quite some JIRA projects. For
maintainability only pmc-member can do this.
Robert
On Fri, 05 May 2017 10:46:35 +0200, Andreas Dangel
wrote:
Hi,
I guess, I need some help with
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
Because Spock can't (do not want) generate runners at test object creation
time. Parametrized runners are generated at runtime and therefore not known at
init time.
---
If your project is set
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
@Fuud
Makes sense.
Why, what is the purpose in your f/w to schedule empty runner?
---
If your project is set up for it, you can reply to this email and have your
reply appear on
That's the big question I'd like clarify first.
Commons Compress has gone Java 7 in a minor release and people are requesting
it for Plexus Archiver...
> How would we handle this wrt versions of our plugins when the requirements
> for those are bumped from Java 6 to Java 7?
>
> For example,
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
NoTestsRemainException will be thrown in this case
---
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
On Fri, May 5, 2017 at 9:01 AM, Olivier Lamy wrote:
> well IMHO we can definitely have everything 7 mandatory...
>
I'm fine with that, but I think we should at least bump minor version of a
plugin when this happens.
/Anders
>
> On 5 May 2017 at 16:45, Anders Hammar
Hi,
MNG-6127 is ready with included IT.
Could you include and merge it?
I need it for my maven plugins.
Best regards,
Mario Krizmanic
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
well IMHO we can definitely have everything 7 mandatory...
On 5 May 2017 at 16:45, Anders Hammar wrote:
> How would we handle this wrt versions of our plugins when the requirements
> for those are bumped from Java 6 to Java 7?
>
> For example, maven-jar-plugin has
On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:
> This will also ultimately mean that these plugins will run with Maven 3.3
> only
> if someone still uses an older version and Java 6 to build their projects.
>
I don't follow.
Not to confuse anyone we should separate
Github user Fuud commented on the issue:
https://github.com/apache/maven-surefire/pull/114
@Jezorko
https://github.com/spockframework/spock/pull/558
---
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
Hi,
The vote has passed with the following result:
+1 : Karl Heinz Marbaise, Hervé Boutemy, Robert Scholte, Andreas Dangel
(non-binding)
PMC quorum: reached.
I will promote the artifacts to the central repo.
--
Andreas Dangel
https://github.com/adangel
skype: andreas_dangel
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
Question.
Could it happen that a runner has no children, as e.g. JUnit's runner
builder creates runners?
It does not make sense to allocate a thread for empty runner because this
is
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
There is one occasion when you set Filter to ParentRunner all children
could be filtered out.
On Fri, May 5, 2017 at 9:52 AM, Fedor Bobin
wrote:
Hi,
I guess, I need some help with
https://issues.apache.org/jira/browse/MPMD : I'd like to release version
3.8 and create 3.9.
I don't see the Administration link for the project... am I missing some
permissions here?
Regards,
Andreas
--
Andreas Dangel
https://github.com/adangel
skype:
The Apache Maven team is pleased to announce the release of the Apache
Maven PMD Plugin, version 3.8
A Maven plugin for the PMD toolkit, that produces a report on both code
rule violations and detected copy and paste
fragments, as well as being able to fail the build based on these metrics.
This will also ultimately mean that these plugins will run with Maven 3.3 only
if someone still uses an older version and Java 6 to build their projects.
> That's the big question I'd like clarify first.
> Commons Compress has gone Java 7 in a minor release and people are requesting
> it for
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/114
hm, I am not sure creating runners is possible and even if it is how this
could work with us because we create JUnitCore instance and put PC in to if
and intercept JUnit builder and
Github user mkrizmanic commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/21#discussion_r115063523
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/21#discussion_r115065672
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
I gave my spin for the 3.5.1-candidates. I've mentioned the issues I'd
like to add, but most are still waiting to be seconded.
Robert
On Fri, 05 May 2017 19:23:41 +0200, Stephen Connolly
wrote:
Progress seems to be being made... I'm willing to let
We should consider this batch
https://github.com/ChristianSchulte/maven/commit/3494c28426b8dd5711b730d622ba98d603caeda6#commitcomment-22009084
if we want to address the issue we talked about on IRC.
Michael
Am 2017-05-05 um 21:04 schrieb Robert Scholte:
I gave my spin for the
Great! Many thanks
Mario
> On 5 May 2017, at 12:21, Robert Scholte wrote:
>
> Hi Mario,
>
> I've marked it as 3.5.1-candidate.
> Patch looks complete to me.
>
> Robert
>
> On Fri, 05 May 2017 11:17:39 +0200, Mario Krizmanic
> wrote:
>
>>
Progress seems to be being made... I'm willing to let current progress
continue for the next 1-2 weeks before starting a whip-round to drive
towards a release... anyone want me to accelerate?
On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> I'd like people
Am 2017-05-05 um 19:23 schrieb Stephen Connolly:
Progress seems to be being made... I'm willing to let current progress
continue for the next 1-2 weeks before starting a whip-round to drive
towards a release... anyone want me to accelerate?
On Tue 25 Apr 2017 at 21:43, Stephen Connolly <
No
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/21#discussion_r115049986
--- Diff: core-it-suite/src/test/resources/mng-6127/plugin/pom.xml ---
@@ -0,0 +1,55 @@
+
+
+
+
AFAIK you, me and Stephen already agreed that MNG-5935 should be part of
3.5.1
On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov
wrote:
We should consider this batch
Hi,
On 05/05/17 21:54, Robert Scholte wrote:
AFAIK you, me and Stephen already agreed that MNG-5935 should be part
of 3.5.1
+1 From me as well for this.
Kind regards
Karl Heinz Marbaise
On Fri, 05 May 2017 21:09:02 +0200, Michael Osipov
wrote:
We should consider
That wasn't actually my point. Christian wrote that to make the entire
chain consistent several issues have to be addressed.
Am 2017-05-05 um 21:54 schrieb Robert Scholte:
AFAIK you, me and Stephen already agreed that MNG-5935 should be part
of 3.5.1
On Fri, 05 May 2017 21:09:02 +0200,
This specific issue seems quite isolated to me and is likely introduced
when switching from Sonetype Aether to Eclipse Aether, where (IIRC) the
boolean became a Boolean.
On Fri, 05 May 2017 22:18:11 +0200, Michael Osipov
wrote:
That wasn't actually my point.
Am 2017-05-05 um 10:44 schrieb Anders Hammar:
On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote:
This will also ultimately mean that these plugins will run with Maven 3.3
only
if someone still uses an older version and Java 6 to build their projects.
If someone still
33 matches
Mail list logo