Le mardi 14 octobre 2014 09:28:21 Olivier Lamy a écrit :
> On 14 October 2014 05:01, Hervé BOUTEMY wrote:
> > 2. if we configured Checkstyle to report an error, this means check should
> > fail: if you find that it should not fail, please help improve Checkstyle
> > configuration by setting severi
I figured I might make something like maven-shared-testcase to contain a
replacement for PlexusTestCase, or do we already have one ?
(PlexusTestCase is the leading source of plexus-container-default
dependencies...)
WDYT ?
Kristian
NIO delete handles various unicode-releated issues where regular
File.delete does not work, and for some reason they decided to make a
different method rather than fix it, probably because they then can
throw exceptions instead of the silly boolean value.
Kristian
2014-10-13 22:54 GMT+02:00 D
I am cancelling this vote because of 2 different test failures that
make this release hard to build.
The irony is of course that one of the failures the release zip does
not contain real, symlinks, and this release is a precondition to
assembly-plugin 2.5, which will be able to make zips with syml
On 10/13/2014 10:34 PM, Kristian Rosenvold wrote:
> Maven-shared-utils:
>
> http://repository.apache.org/content/repositories/maven-1076/org/apache/maven/shared/maven-shared-utils/0.7/maven-shared-utils-0.7-source-release.zip
> Source checksum: 8b2a6f31505a158d295d5b06c800d61f821a15c2 (sha1)
Ther
Members of this PMC are not shy about demanding that code style
conform. I would rather fail a build because I forgot the stupid
spaces around the stupid parameters than have to scramble and fix
something when someone complains. Let's get checkstyle to enforce what
seems we enforce anyway, and then
On 14 October 2014 10:43, Stephen Connolly
wrote:
> On Monday, October 13, 2014, Olivier Lamy wrote:
>
>> On 14 October 2014 05:01, Hervé BOUTEMY > > wrote:
>> > Le lundi 13 octobre 2014 09:25:17 Olivier Lamy a écrit :
>> >> Hi,
>> >> You mean with the new setup the build will fail because of a c
On Monday, October 13, 2014, Olivier Lamy wrote:
> On 14 October 2014 05:01, Hervé BOUTEMY > wrote:
> > Le lundi 13 octobre 2014 09:25:17 Olivier Lamy a écrit :
> >> Hi,
> >> You mean with the new setup the build will fail because of a checkstyle
> >> issue?
> > yes, it will fail because of an i
On 14 October 2014 05:01, Hervé BOUTEMY wrote:
> Le lundi 13 octobre 2014 09:25:17 Olivier Lamy a écrit :
>> Hi,
>> You mean with the new setup the build will fail because of a checkstyle
>> issue?
> yes, it will fail because of an issue reported by Checkstyle, as we configured
> its checking rule
Le dimanche 12 octobre 2014 10:10:47 Benson Margulies a écrit :
> On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise
wrote:
> If, in
> fact, no one is willing to make even a 3.0.x release, we should
> 'unsupport' 3.0.x in the same way we unsupported 2.2.x.
I'm willing to do a 3.0.6 release wit
I like it!
:)
Regards,
Hervé
Le dimanche 12 octobre 2014 20:12:56 Karl Heinz Marbaise a écrit :
> Hi,
>
>
> based on the work i did i enhanced the dist-tool to produce some parts
> of the report which i manually created...
>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prer
The Maven team is pleased to announce the release of the Apache Maven
Compiler Plugin, version 3.2
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 configuration:
+1 ( none binding) tested with my internal build on windows. Does it mean
the clean task is faster due to NIO. My apology if i happen to hijack this
thread.
-D
On Mon, Oct 13, 2014 at 1:34 PM, Kristian Rosenvold
wrote:
> Hi,
>
> Maven-shared-utils:
>
> We solved N=3 issues:
>
> http://jira.cod
Hi,
Maven-shared-utils:
We solved N=3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20207&styleName=Text&projectId=11761
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11761&status=1&component=15606
http://r
If eclipse usage survey is any indication, users tend to move to the latest
eclipse version quite fast. I think it is okay to expect m2e 1.5 or better at
this point. For actively developed codebases anyways.
On October 13, 2014 3:03:21 PM EDT, Anders Hammar wrote:
>>
>> this is the only change
>
> this is the only change for 3.0.5: http://maven.apache.org/security.html
> bottom line: certificates are not checked.
> It's a serious security issue and for that reason I'd prefer 3.0.5 over
> 3.0.4
Security issue or not, there are commercial IDEs out there (used by larger
companies) that in
Op Sun, 12 Oct 2014 16:10:47 +0200 schreef Benson Margulies
:
On Sun, Oct 12, 2014 at 9:25 AM, Karl Heinz Marbaise
wrote:
Hi Robert,
from my point of view minimum to 3.0.5 ...nothing below...afterwards
3.1.1.and then 3.2.1...the latest releases from the appropriate
release
lines 3.0
Anders,
this is the only change for 3.0.5: http://maven.apache.org/security.html
bottom line: certificates are not checked.
It's a serious security issue and for that reason I'd prefer 3.0.5 over
3.0.4
thanks,
Robert
Op Mon, 13 Oct 2014 07:48:11 +0200 schreef Anders Hammar
:
Personally
The Maven team is pleased to announce the release of the Apache Maven
Compiler Plugin, version 3.2
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 configuration:
The vote has passed with the following result:
+1 (binding): Karl, Robert, Herve, Olivier, John
I'll promote the release.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
Le lundi 13 octobre 2014 09:25:17 Olivier Lamy a écrit :
> Hi,
> You mean with the new setup the build will fail because of a checkstyle
> issue?
yes, it will fail because of an issue reported by Checkstyle, as we configured
its checking rules
> I personally find really hard for a "style" problem
Robert Scholte wrote:
> Hi,
>
> Right now we change the Maven prerequisite to 2.2.1 and I noticed some new
> issues which already want to move it forward to 3.0.4. I wonder why to
> move to this version.
>
> Most (API-)changes have been introduced with the 3.0 alpha and beta
> releases. I don't
22 matches
Mail list logo
