I find the arguments by Plamen very convincing. As a user I would look for
that configuration where I previously did the same thing when it ended up
in the Manifest: in the config of the jar plugin.
I wouldn't expect to suddenly switch to the shade plugin to be able to
define the main class or the
Yupp, I'm afraid neither version ranges nor information from any
dependencyManagement sections are considered.
Only the plain versions or properties work, and transitive dependencies are
pulled in.
And I agree that a special scope would have been a nice alternative
solution, but that would have o
What ever you do, make sure you never try to put unbounded sysout/syserr of
a test case into memory, ever. Not even for a short time, as there may be
users with a ton of output that is currently buffered in the
overflow-files. Changing this can cause serious performance issues (gc
pauses, swapping)
+1
Tested on a couple of projects, with Maven 3.3.9 and 3.5.0, on Win
(binaries) and macOS (source build).
Great job, Tibor!
2017-04-08 14:26 GMT+02:00 Petr Široký :
> +1 (non-binding)
>
> Tested on Fedora 25 + JDK 8u121 + Maven 3.5.0 with several large projects.
> No issue found.
>
> @Tibor,
+1
Really awesome stuff, everyone!
(I tested with a good range of projects, some of them having different
versions of some karaf-maven-plugins that tend to break with Maven updates
-- everything was smooth, though.)
2017-02-23 17:10 GMT+01:00 Stephen Connolly :
> Hi,
>
> We solved 65 issues:
>
+1
Anders Hammar schrieb am Mi. 4. Jan. 2017 um 13:22:
> +1
>
>
>
> /Anders
>
>
>
> On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly <
>
> stephen.alan.conno...@gmail.com> wrote:
>
>
>
> > Hi,
>
> >
>
> > We have collectively managed to mess up our ability to follow the
> original
>
> > release
2016-08-31 22:02 GMT+02:00 Tibor Digana :
> >>So, we can try to have different source folders for different runtimes.
> No. If you are developers you would not say this.
> No developer would develop and merge the same code multiple times!!!
> Look, now let the maven-compiler-plugin to download jar
+1
Am Montag, 16. Mai 2016 schrieb Jason van Zyl :
> +1
>
> > On May 16, 2016, at 7:35 AM, Igor Fedorenko > wrote:
> >
> > +1
> >
> > --
> > Regards,
> > Igor
> >
> > On Mon, May 16, 2016, at 01:43 AM, Anders Hammar wrote:
> >> +1
> >>
> >> /Anders (mobile)
> >> On May 15, 2016 23:24, "Michael O
Hi Thomas,
One way to learn how things roll is to find an existing plugin that does
something related to what you are trying to do and check the sources there.
Many of the plugins developed here in the Apache Maven project are not too
complex and might help you finding what you look for. Same goes
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.5.1.
The Compiler Plugin is used to compile the sources of your project.
http://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configur
Hi,
The vote has passed with the following result:
+1 : Andreas Gudian, Michael Osipov, Anders Hammar, Karl Heinz Marbaise
PMC quorum: reached.
I will promote the artifacts to the central repo.
Thanks!
@Michael: I'll still count your vote only once :-D. But thanks for the
spirit!
Am Dienstag, 9. Februar 2016 schrieb Michael Osipov :
> Am 2016-02-06 um 20:25 schrieb Andreas Gudian:
>
>> Hi,
>>
>> We solved 3 issues (well, two of them deal with the same error):
&g
Two hours to go - anyone else care for a vote? PMC quorum is not reached,
yet. ;-)
Am Samstag, 6. Februar 2016 schrieb Andreas Gudian :
> Hi,
>
> We solved 3 issues (well, two of them deal with the same error):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?v
self +1
2016-02-06 20:25 GMT+01:00 Andreas Gudian :
> Hi,
>
> We solved 3 issues (well, two of them deal with the same error):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334747&styleName=Text&projectId=12317225
>
> There are still a
+1 from me, although I had to remove the DEPENDENCIES file form the
source-zip in order to build it (the rat-config doesn't have an exclusion
for the file).
2016-02-06 0:10 GMT+01:00 Hervé BOUTEMY :
> Hi,
>
> We solved 17 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectI
Hi,
We solved 3 issues (well, two of them deal with the same error):
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334747&styleName=Text&projectId=12317225
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317225%20AND
No idea if I've done it the way it is supposed to be done, but
check AbstractCompilerMojo#resolveProcessorPathEntries in the
maven-compiler-plugin.
In case it helps... :-)
Am Samstag, 6. Februar 2016 schrieb Karl Heinz Marbaise :
> Hi,
>
> If i'm in a plugin can i manually trigger the resolutio
Welcome Andreas,
Great to have you on bord!
Andreas (the other one, but not Anders. Getting complicated.)
Am Freitag, 5. Februar 2016 schrieb :
> Author: adangel
> Date: Fri Feb 5 10:55:17 2016
> New Revision: 1728634
>
> URL: http://svn.apache.org/viewvc?rev=1728634&view=rev
> Log:
> Updated
inue that discussion in
https://issues.apache.org/jira/browse/MCOMPILER-235
Thanks,
Andreas
2016-01-21 20:44 GMT+01:00 Andreas Gudian :
> To be honest, I wasn't even aware of that bug, as I only checked the
> summaries of the x latest bugs shortly before the release. And yes, when on
&g
27;ll look into it.
Andreas
2016-01-21 15:44 GMT+01:00 Thomas Broyer :
> On Wed, Jan 20, 2016 at 8:43 PM Andreas Gudian wrote:
>
> > ** New Feature
> > * [MCOMPILER-203] - Allow compiler-plugin to specify annotation
> > processor dependencies
> >
>
> Gr
The Apache Maven team is pleased to announce the release of the Apache
Maven Compiler Plugin, version 3.5.
The Compiler Plugin is used to compile the sources of your project.
http://maven.apache.org/plugins/maven-compiler-plugin/
You should specify the version in your project's plugin configurat
Hi,
The vote has passed with the following result:
+1 : Andreas Gudian, Tibor Digana, Karl Heinz Marbaise
PMC quorum: reached.
I will promote the artifacts to the central repo.
Thanks!
My +1:
- checked SHA-1 sum
- checked building from source with ITs
- tested binaries with some smaller projects.
2016-01-17 0:03 GMT+01:00 Andreas Gudian :
> Hi,
>
> We solved 5 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330435&style
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12330435&styleName=Text&projectId=12317225
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317225%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20D
Hey there,
I'd like to start with the release process for the maven-compiler-plugin
3.5. It's on Maven 3 now, but the adjustments and cleanups in that area are
only minor until now.
Other than that, it contains one small bugfix and one new feature (support
for specifying an annotation processor c
de&node=5858379&i=0>>:
> >
> > > Hi Andreas,
> > >
> > > See Robert's change. This maybe helps
> > >
> > >
> >
> https://github.com/apache/maven-surefire/commit/9cb143414134a2c8f0bfec5b84f01571875a26fe
> > >
> > &
Hey,
funny, I ran into the very same problem when working on MCOMIPLER-203 and
after updating to Maven 3.0 dependencies: I'm getting the very same
exception when running the CompilerMojoTestCase.
I'm all ears on how to solve that, so if anyone has a hint... :)
I pushed a branch on github, and, f
Santa says it's alright, so here's my +1. :)
2015-12-23 13:17 GMT+01:00 Karl Heinz Marbaise :
> Hi,
>
> i need one more PMC vote...;-)...
>
> On 12/20/15 2:05 PM, Karl Heinz Marbaise wrote:
>
>> Hi,
>>
>> We solved 5 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1
+1
2015-12-13 22:20 GMT+01:00 Dennis Lundberg :
> Hi,
>
> We solved 4 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621&version=12332973
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317621
> JUnit 4 End Of Life
>
> I have a strong reason to use Java 8 in Surefire project.
> For more information read this
> https://github.com/junit-team/junit-lambda/issues/31
Hi Tibor,
Wouldn't it be enough to only build the new Junit-5 provider with
source/target level 8 (if that would even be nec
2015-12-13 19:04 GMT+01:00 Benson Margulies :
> On Sun, Dec 13, 2015 at 9:40 AM, Benson Margulies
> wrote:
> > On Dec 13, 2015 3:25 AM, "Stephen Connolly"
> > wrote:
> >>
> >> pom?
> >
> >
> > 1. The feature descriptor is xml
> >
> > 2. I believe that this still adds transitive dependencies to t
2015-12-13 12:05 GMT+01:00 Robert Scholte :
> The first time I heard about JDK9s Jigsaw having a classpath and a
> modulepath, which can be used at the same time AND both containing jars, I
> had a big "OH NO!". We can't change the pom, so the first thing that
> came to my mind was indeed usin
Hi Kristian,
can you please give me push-access to the plexus-compiler repository?
I'm working on an old MCOMPILER issue and need to change stuff over there
as well...
Thanks,
Andreas
2015-02-09 18:13 GMT+01:00 Kristian Rosenvold :
> They are now all at https://github.com/codehaus-plexus
>
>
Welcome, Christian! Great to have you with us!
Am Donnerstag, 10. Dezember 2015 schrieb Karl Heinz Marbaise :
> Hi Christian,
>
> also a welcome from my side..
>
> Kind regards
> Karl Heinz Marbaise
>
> On 12/10/15 11:08 PM, Hervé BOUTEMY wrote:
>
>> yeah, welcome to the team, Christian!
>>
>> L
Great, it's that time of year again :-).
I'm all for bumping the Java version, although I have no apparent need for
it. But Java 8 opens so many doors, as Stephen listed... And who knows how
long we'll live with 3.4.x.
In the end, usually users who are stuck with an old JDK for their code
either
AFAIR, such constants (primitives and Strings) are inlined by the compiler
- and the dependeny analyzer works on the bytecode and not the sources,
right?
Am Mittwoch, 25. November 2015 schrieb Jochen Wiedmann :
> What exactly is it, you'd like to detect?
>
>
> On Wed, Nov 25, 2015 at 8:11 AM, K
Forwarding to dev@
-- Forwarded Message --
From: *Johannes Link*
Date: 18/11/2015
Subject: Open Test Alliance
Hi you all,
I'm writing to you in your roles as committers to the maven sure-fire
plugin. Since we couldn't figure out the "main contributors" (in case
you have such a
+1 from me.
2015-11-10 18:16 GMT+01:00 Jason van Zyl :
> Hi,
>
> Time to release Maven 3.3.9!
>
> Here is a link to the issues resolved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074
>
> Staging repo:
> https://repository.apache.org/content/reposit
2015-11-06 18:42 GMT+01:00 Uwe Barthel :
> -1
>
> Many commercial projects still require Java 1.6.
>
The question asked by Attila is if the *default *values for the
source/target parameters in the compiler-plugin could use some attention
(and I think it should, as the default value 1.5 is just us
I think it's actually a good idea to do something about that.
Users who don't specify a source/target version would fall on their bottoms
with a change to 1.7 as default as well. So why using 1.7 as a default,
which is EOL (or at least nearly) anyway?
Keeping the default on 1.5 might bite users a
It's a smooth ride. Here's my +1 ... not legally, but morally binding ;)
2015-10-28 14:30 GMT+01:00 Jason van Zyl :
> Hi,
>
> Time to release Maven 3.3.7!
>
> Here is a link to the issues resolved:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12333074
>
>
+1 :)
2015-10-29 15:19 GMT+01:00 Tamás Cservenák :
> +1
>
> On Wed, Oct 28, 2015 at 5:28 PM Robert Scholte
> wrote:
>
> > +1
> > Robert Scholte
>
Benson, is there a full stack trace in the XML test report? I would have
expected that we shorten out most of the stack traces on the console
output...
2015-10-16 16:35 GMT+02:00 Benson Margulies :
> On Fri, Oct 16, 2015 at 10:31 AM, Tibor Digana
> wrote:
> > Can you give me the link?
>
>
> http
Am Donnerstag, 15. Oktober 2015 schrieb Michael Osipov :
> Am 2015-10-15 um 02:26 schrieb Tibor Digana:
>
>> Hi,
>>
>> It takes 4 to 5 hour to complete the commit of surefire site on SVN.
>> The site is about 4,200 files and 820 folders.
>>
>> I am doing it on people.apache.org machine; otherwise
Good idea!
Funny enough, I've seen multi-module projects that wouldn't work with this
- they have an aggregator pom on the top-level, with:
componentA/common
componentA/server
componentB/common
..
So they skip a level of aggregator poms (in the componentX-directories).
I'd consider that an edg
What a release! 50 issues solved? Tibor, you're the man! Kudos for all the
work you've put into this one (again).
I've just built it from the source including all integration tests (JDK 7
only, sorry). In just 41 minutes, the build showed full success. I've
executed the test that Karl-Heinz wrote
I was the last one doing a release there, primarily fixing some issues that
blocked it from being much of use for Java 8 projects that share the
.project / .classpath files in SCM. I still stand by the reasoning that I
had the last time, of why there is still the need for it - despite the
great len
2015-06-27 14:40 GMT+02:00 robert.patr...@oracle.com <
robert.patr...@oracle.com>:
>
> The second time, I tried to interact around someone else's problem with
> mvnDebug.cmd. No one ever responded.
>
That's not really true - people did respond, it's just that no one stood up
and put your suggest
Hi Milos,
Try your asf username (without @apache.org) and the corresponding password.
That should get you in.
Hth,
Andreas
Am Mittwoch, 17. Juni 2015 schrieb Milos Kleint :
> Hey,
>
> this is the first time round I'm trying to edit a MNG issue after migration
> from codehaus and while my usern
Hi,
You can check the build-helper-maven-plugin, which has a tiny goal to add a
source directory to the project:
https://github.com/mojohaus/build-helper-maven-plugin/blob/master/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java
The maven-eclipse-plugin picks up all source directorie
How about running the git-svn import on people.a.o? Would we be allowed to
do that (in terms of load/storage)? Svn-operations there are blazing fast
in comparison to the remote https access. Or should we ask infra for some
access to a server in the vicinity of one of the svn-mirrors?
Am Montag, 1
The Apache Maven team is pleased to announce the release of the Apache
Maven Eclipse Plugin, version 2.10
This plugin is used to generate Eclipse IDE files (*.classpath, *.project,
*.wtpmodules and the .settings folder) for use with a project - if the M2E
Eclipse-Plugin does not fit you.
This rel
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Jason van Zyl, Hervé Boutemy
+1 (non binding): Andreas Gudian
Thank you guys for the votes!
I will promote the artifacts to the central repo.
2015-05-27 21:44 GMT+02:00 Andreas Gudian :
> Here's m
Here's my own +1.
2015-05-26 23:10 GMT+02:00 Hervé BOUTEMY :
> +1
>
> Regards,
>
> Hervé
>
> Le dimanche 24 mai 2015 22:04:52 Andreas Gudian a écrit :
> > Hi,
> >
> > this will be the last Maven 2 compatible release of this plugin.
> >
> >
expected seemed to be not part of the
> release package...
>
>
> If i start the tests in the
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin
> directory the above tests will run successfully...and don't produce
> errors...
>
>
>
>
&g
Hi,
this will be the last Maven 2 compatible release of this plugin.
We solved 9 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317423&version=12330751
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MECLIPSE
+1, I also always like what I'm reading from Manfred.
(don't these votes usually take place in private@?)
2015-05-13 13:12 GMT+02:00 Jason van Zyl :
> +1
>
> On May 13, 2015, at 2:55 AM, Hervé BOUTEMY wrote:
>
> > Hi,
> >
> > I'd like to introduce Manfred Moser as committer for the Apache Mave
Nice! +1
Am Donnerstag, 7. Mai 2015 schrieb Stephen Connolly :
> +1
>
> On 7 May 2015 at 18:59, Karl Heinz Marbaise > wrote:
>
> > Hi,
> >
> > i would like to update our main page http://maven.apache.org/ to the new
> > Maven Fluido Skin 1.4 including new logo which will look like this:
> >
> >
Hi Tibor,
wow, that's a lot of work you put in there! Great!
As you also changed stuff in surefire-booter and I always wondered, I'm
cc-ing dev@ with this question:
Do we have any documentation on which JDKs we officially support to be used
in a toolchain configuration?
For quite a while now, s
Done. Created issue MSHARED-415 and set it to resolved.
@Tibor: if there isn't anything else in the release anyway, you can also
combine both into one release-process/vote.
2015-05-04 18:47 GMT+02:00 Karl Heinz Marbaise :
> Hi,
>
>
> On 5/3/15 11:13 PM, Tibor Digana wrote:
>
>> Currently surefir
GMT+02:00 Hervé BOUTEMY :
> Le vendredi 1 mai 2015 15:14:05 Andreas Gudian a écrit :
> > Anyone who has ever done a release of a large plugin like surefire from a
> > european location knows what a pain it is to svn-commit a couple of
> > thousand files. It takes hours, but
Anyone who has ever done a release of a large plugin like surefire from a
european location knows what a pain it is to svn-commit a couple of
thousand files. It takes hours, but only if you're lucky and the process is
not interrupted by the server.
I had to dance around that by zipping up the local
Hi Karl,
I still have half of an issue to fix before the release - I was just
immensly lazy regarding my maven activities the last months.
So it's good you bring it up, Karl! I'll see that I get my ass up over this
weekend.
I also promised to add some lines in the relation of this plugin vs m2e
In the windows script, I introduced a new variable for the debug settings -
perhaps we can do the same for the shell scripts.
Am Freitag, 24. April 2015 schrieb Francisco Collao Gárate :
> Yep the behavior is different, in my case I was using a .mavenrc, so
> when I use the mvnDebug add all optio
Can you check what actions this lets you do and if somthing is still
> missing,
> please?
>
> Regards
>
> Hervé
>
>
> Le vendredi 10 avril 2015 23:34:49 Andreas Gudian a écrit :
> > Hi,
> >
> > I already am in the group "maven-developers",
Hi,
I already am in the group "maven-developers", but I don't seem to be able
to do anything meaningfull, like managing versions or assigning issues to
myself... I checked in SUREFIRE and in MECLIPSE.
Is there some part missing in the config?
Thanks,
Andreas
2015-04-10 23:23 GMT+02:00 Dan Tran
Great, Thanks!
I'll do the 2.10 release in a not too distant future.
Am Donnerstag, 9. April 2015 schrieb Joseph Walton :
> I've taken a look at two cleanup tasks for maven-eclipse-plugin.
>
> One is a clearout of long-deprecated classes:
>
> https://issues.apache.org/jira/browse/MECLIPSE-6
2015-04-07 21:53 GMT+02:00 Robert Scholte :
> Hi,
>
> I'd like to do a release of the maven-release-plugin soon, especially for
> the Windows+M3.3.1 users.
>
I still don't get why I didn't think of that when renaming mvn.bat to
mvn.cmd... :-/
If I read that right, there is a problem in the shell scripts, not the
windows cmd script, right? Because mvnDebug.cmd works for me as expected.
Am Sonntag, 5. April 2015 schrieb Karl Heinz Marbaise :
> Hi,
>
> based on some comments (http://blog.soebes.de/blog/
> 2015/03/17/apache-maven-3-dot-
+1 from me.
I've tested under Windows with some projects that also contain Maven
Verifier based integration tests.
Thanks for doing this release, Jason!
2015-03-13 23:46 GMT+01:00 Karl Heinz Marbaise :
> Hi Jason,
>
> checked several projects of my own projects,
>
> checked with:
> * takari
In the last two releases of surefire, we included the jira-report in the
site, listing all resolved issues with the appropriate fix-version:
http://maven.apache.org/surefire/maven-surefire-plugin/jira-report.html
Am Dienstag, 10. März 2015 schrieb Karl Heinz Marbaise :
> Hi Stephan,
>
> On 3/10
he VM-argument name.
2015-02-26 18:07 GMT+01:00 Jason van Zyl :
>
> On Feb 26, 2015, at 3:49 AM, Andreas Gudian
> wrote:
>
> > I can handle that, but not before the weekend.
> >
> > Jason, does that conflict with your schedule for the release?
> >
>
> No dire
t; > > IBM J9 JDK 6 seems to require a minimum of Windows XP SP3 [2].
> > >
> > > [1] http://www.oracle.com/technetwork/java/javase/config-417990.html
> > > [2]
> > >
> > >
> >
> http://www-01.ibm.com/support/knowledgecenter/#!/SSYKE2_6.0.0/com.ibm.java.doc.60
nized.
One thing we could do to make stuff easier around these .bat scripts is to
drop support for this 4NT shell and Windows versions that are not based on
NT (i.e. Windows 9x / ME).
2015-02-25 19:38 GMT+01:00 Jason van Zyl :
> Awesome, thanks!
>
> On Feb 25, 2015, at 10:32 AM, Andreas G
Hi guys,
I'm stuck with a windows box and I can give it a try...
.bat-scripting is not really a joy, but what's in the patch should be
translatable.
Andreas
2015-02-25 17:01 GMT+01:00 Igor Fedorenko :
> You can see actual diff to mvn shell script in [1], but the changes was
> basically two-fo
compiler from tyco-compiler-jdt
package... Looking at their code, that's to be expected.
2015-02-06 18:51 GMT+01:00 Andreas Gudian :
> Hi,
>
> With one of the previous builds, I've noticed that the mvn compiler
> plugin running on JDK 9 is unable to use a different JDK from
Hi,
With one of the previous builds, I've noticed that the mvn compiler
plugin running on JDK 9 is unable to use a different JDK from a toolchain.
Before I start digging into this: has anyone else noticed /
investigated that already?
On a different note: using JDK 9 to do some compiling / annot
Great, Daniel, I thought I'm the only one thinking that way... ;-)
2015-02-02 19:38 GMT+01:00 Daniel Kulp :
>
> I’m -1 to retiring the maven-eclipse-plugin until the m2e stuff is at a
> state where it can be as flexible and useful as the maven-eclipse-plugin.
> Trying to bring a large complex pr
I'm pretty sure I might be bashed for writing this, but what the heck... ;-)
I do still see some need for the maven-eclipse-plugin.
To be perfectly clear, I agree that m2e is by far superior in many ways,
not only tech-wise, but also conceptionally.
Still, at work we had to migrate from m2e to m
Thanks, Norbert!
Could you also create a new Pull-Request for it? Then I can fetch it more
easily :-)
Am Mittwoch, 28. Januar 2015 schrieb Norbert Wnuk :
> Link after pushing amended commit -
>
> https://github.com/norbertwnuk/maven-surefire/commit/d6a8af593fc03e12ecf2dc8047669472f7ca263b
>
> O
Hi Norbert,
yesterday I ran the whole build locally (Windows) with JDK 5 and everything
worked for me.
For the linux case, I guess it's hard to create an directory with an
invalid name. In case you don't find an alternative approach, I wouldn't be
devastated if we just removed that test case agai
Hi Norbert,
Oh, I misses that one as well - our animal sniffer seems to put its nose
only into the main classes.
A new pull-request would be great.
Am Dienstag, 20. Januar 2015 schrieb Norbert Wnuk :
> Hi Andreas,
> The JDK API level is not enforced during build so that my accidental usage
> of
Hi Norbert,
sounds great! To create a Jira-Issue for surefire [1], you just need to
sign-up on xircles [2].
You can attach your path to the Jira issue, if you like. The most fluent
way to suggest patches is by making a pull-request on GitHub where we can
directly discuss the patch.
In the end, f
I think that we don't need to fully open up our plugins so that anyone can
customize each aspect "on the fly". We would too much hide the fact that
the execution is highly customized because some special stuff is hidden on
the classpath somewhere.
Likewise, if we allowed that sort of customization
Did we already cover what we want to keep supporting via Toolchains?
We would have to take some care in Surefire if we wanted to keep some
support for <1.6 when using toolchains or when allowing users to configure
a different JVM.
2014-12-25 15:57 GMT+01:00 Karl Heinz Marbaise :
> Hi,
>
> let
+1
2014-12-24 17:03 GMT+01:00 :
> Hi,
>
> We solved 13 issues:
> https://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=10541&version=20814
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&jqlQuery=project+
H, H, or otherwise H.
Am Dienstag, 9. Dezember 2014 schrieb Stephen Connolly :
> This is a run-off vote to select the top two options for our new mascot's
> name.
>
> The entries with the highest number of votes will be selected for the final
> round. If there is only one entry with the highest
I suggest Darth Mowl. But not seriously ;-).
Am Dienstag, 25. November 2014 schrieb Stephen Connolly :
>
> http://people.apache.org/~stephenc/maven-logo-contest/maven-owl-final-large.png
>
> When I created this owl, I gave it the name "Couché Tard" which is a french
> nickname for an owl (litera
+1
Am Dienstag, 25. November 2014 schrieb Stephen Connolly :
> For anyone who has been living under a rock, here is the background
>
> Background
> =
>
> I think everyone can agree that the site needs a reorganisation and a
> rewrite. Users cannot find what they need, and the end result i
I like it. Cute but resolute birdy, and the font looks fresh and modern.
But wait - did someone shoot a hole right through the owl? You can even see
the shadow behind it. ;-) Maybe the patch in the middle could be a little
darker, perhaps with a hint/tint of the surrounding colour?
2014-11-19 18
Hi Marek,
interesting... For Surefire 3.0 we have some stuff in mind to allow users
hooking in the surefire logic at several points, one of them being the
determination of tests to run and their execution order. I didn't think
about that particular case of yours, yet. But good to know.
As for the
I would just respin the release with version 3.3. With Subversion it's not
that big a deal to delete a tag (with a proper comment) and recreate it for
the re-spin.
With git it would be a big no-no to replace an already pushed tag, that's
why I create the final tag only after the vote completed and
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 2.18
The release contains a number of bug fixes, and introduces an option to
automatically rerun failing tests, including proper reporting on the
console and in the XML reports for the individual
Hi,
The vote has passed with the following result:
+1 (binding):
Karl Heinz Marbaise, Hervé Boutemy, Kristian Rosenvold
+1 (non binding):
Tibor Digana, Andreas Gudian
I will promote the artifacts to the central repo.
Could on of the PMC members please copy the source release to the
s something looking funny about that. I'll create a Jira
issue and fix it for the next version.
>
> Kristian
>
>
> 2014-11-03 23:12 GMT+01:00 Hervé BOUTEMY >:
> > +1
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 1 nove
My own +1.
Am Sonntag, 2. November 2014 schrieb Karl Heinz Marbaise :
> Hi,
>
> first to say trying to build surefire with Maven 2.2.1 will fail with a
> circular dependency...problem (as Kristian mentioned)...so best would be to
> require such things not by a README better by prerequisites/enfo
Hmm, I would find it a bit embarrassing to release a source zip that I know
does not build without either deleting a file or skipping the rat-check,
which, as of only recently, is otherwise part of the build. That was not
the case for the previous releases... :-/
Am Sonntag, 2. November 2014 sch
Hi,
We solved 31 issues:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=20175
There are still lots of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+upda
vote for Maven JXR based on this problem...
>
> Filed in an issue https://issues.apache.org/jira/browse/RAT-184
>
>
> Kind regards
> Karl Heinz Marbaise
>
>
> On 11/1/14 7:05 PM, Andreas Gudian wrote:
>
>> Looks like this source-zip can't be built due to the fai
Looks like this source-zip can't be built due to the failing rat-check on
the generated DEPENDENCIES file as well.
I'm supposed to cancel the vote now, right? I would do a respin with an
exclusion for that file in the rat-config.
What about the other votes in progress?
2014-10-31 20:10 GMT+01:
1 - 100 of 162 matches
Mail list logo
