I dont mind the checkstyle stuff, but we have /not/ had a vote that
mandates this to be a requirement. Until we do so I think we should
safely just add skip to checkstyle where it's inappropriate, or
ignore more stuff.
Kristian
2014-10-25 20:36 GMT+02:00 Andreas Gudian andreas.gud...@gmail.com:
Hi,
My personal preference is to have all annotations first, i.e. before the
visibility modifier.
I checked the JLS, but couldn't find any recommendation. The examples in
chapter 9.7 use the order that Checkstyle suggests.
--
Dennis Lundberg
Den 25 okt 2014 20:38 skrev Andreas Gudian
I agree, and believe that it was Hervè's intention for this to be a soft
rule, at least to start with.
--
Dennis Lundberg
Den 26 okt 2014 07:47 skrev Kristian Rosenvold
kristian.rosenv...@gmail.com:
I dont mind the checkstyle stuff, but we have /not/ had a vote that
mandates this to be a
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/61
Updated documentation in SUREFIRE-1047 and SUREFIRE-1097
Documentation for argLine and includes/excludes section.
You can merge this pull request into a Git repository by running:
$ git
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/61
---
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
Hi All,
Let's discuss the release of SUREFIRE 2.18.
Initially we wanted to release surefire 2.18 by the EO October.
(Previously I wanted to wait and make more bugfixes but nowadays it does not
make sense to postpone the release date and wait for next weeks.)
Current situation is quite good.
All
I would like to commit one more improvement in 2.18 which does not block us
at all.
-
BR, tibor17
--
View this message in context:
http://maven.40175.n5.nabble.com/Release-Plan-for-SUREFIRE-2-18-tp5810740p5810744.html
Sent from the Maven Developers mailing list archive at Nabble.com.
Hi Tibor,
That sounds great! Then I'd go over the open PRs on GitHub once again (I
promised some of them to be merged in time for 2.18).
Perhaps we can attempt a release later this week then.
Andreas
Am Sonntag, 26. Oktober 2014 schrieb tibor17 :
I would like to commit one more improvement
Great work, guys ! I am currently busy roaming freely around in the
maven universe fixing all sorts of random stuff, I'm happy you two are
taking care of surefire :)
K
2014-10-26 12:58 GMT+01:00 Andreas Gudian andreas.gud...@gmail.com:
Hi Tibor,
That sounds great! Then I'd go over the open
+1
K
2014-10-23 21:48 GMT+02:00 Kristian Rosenvold kristian.rosenv...@zenior.no:
Hi,
We solved 33 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18952styleName=TextprojectId=11126
There are still a couple of issues left in JIRA:
Hi,
really good work...
Kind regards
Karl Heinz Marbaise
On 10/26/14 12:58 PM, Andreas Gudian wrote:
Hi Tibor,
That sounds great! Then I'd go over the open PRs on GitHub once again (I
promised some of them to be merged in time for 2.18).
Perhaps we can attempt a release later this week
Hi,
i have a question for this topic:
checkstyle reported that the license header is not correct...
[INFO] There are 5 checkstyle errors.
[ERROR] JavaCodeTransform.java[4] (header) RegexpHeader: Line does not
match expected header line of '^ \* Licensed to the Apache Software
Foundation
Hi folks,
do we have a policy for Maven dependencies for non-plugins after Karl
Heinz has raised the baseline to 2.2.1?
I'd like to release Maven Archiver and raise dependency versions,
especially Maven to 2.2.1.
Michael
Hi,
In my opinion the new minimum level of Maven (2.2.1) should cover all of
our projects, not just plugins. Standardizing on a single base version will
also mean less artifacts to download for new Maven installations.
This reminds me of something I've been meaning to do for a while now. We
have
Am 2014-10-26 um 17:32 schrieb Dennis Lundberg:
Hi,
In my opinion the new minimum level of Maven (2.2.1) should cover all of
our projects, not just plugins. Standardizing on a single base version will
also mean less artifacts to download for new Maven installations.
This reminds me of
Hi,
we have already a very simple report which shows which plugins are at
2.2.1 and which not...
https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-prerequisites.html
But what Dennis has suggested sounds like lightyears better
kind regards
Karl Heinz Marbaise
On 10/26/14
+1
Op Thu, 23 Oct 2014 21:48:25 +0200 schreef Kristian Rosenvold
kristian.rosenv...@zenior.no:
Hi,
We solved 33 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18952styleName=TextprojectId=11126
There are still a couple of issues left in JIRA:
Hi,
The vote has passed with the following result:
+1 (binding): Karl, Robert, Kristian
I will promote the artifacts to the central repo and generally fiddle
with the docs.
Kristian
-
To unsubscribe, e-mail:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=20685
There are still 2 issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MCLEAN%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging repo:
+1
2014-10-26 20:48 GMT+01:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=20685
There are still 2 issues left in JIRA:
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18325projectId=11761
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/browse/MSHARED-168?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC
in general, annotations on a method are about the method: actual recomendation
is ok for that
but JSR 305 annotations are about the return type: IMHO, these annotations are
best like proposed by Andreas
this would require Checkstyle new feature
and consensus in the Maven team to use it
let's
Hi again,
I've uploaded some reports for plugins and shared, which should keep
people busy for a while. The reports are in text format, and should be
easy to grasp. The one you want in this case is the
dependency-graf.txt
http://people.apache.org/~dennisl/dependency-reports/
Feedback is very
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085version=19853
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20JXR%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
Staging
GitHub user mcculls opened a pull request:
https://github.com/apache/maven/pull/26
Update Guava dependency to 18.0
With the update of Guice to 3.2.3, the limitation on the Guava dependency
no longer applies.
You can merge this pull request into a Git repository by running:
$
I am going to fix the following in surefire 2.18
SUREFIRE-649 and SUREFIRE-1053
Thus we will have same nullable/empty-string behavior with environment
variables.
Then I will open improvement in JIRA and improve text in printed warnings
with shutdown after elapsed timeout in parallel execution.
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/62
[SUREFIRE-649] empty strings in systemPropertyVariables element
The fix for
https://jira.codehaus.org/browse/SUREFIRE-649
You can merge this pull request into a Git repository by
The Apache Maven team is pleased to announce the release of the
long-awaited Apache Maven Assembly Plugin, version 2.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
28 matches
Mail list logo
