Hi,
We solved N issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=18533
There are still a couple of 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
Hi Robert Kristian,
Early Access build for JDK 9 b31 https://jdk9.java.net/download/ is
available on java.net, summary of changes are listed here
http://www.java.net/download/jdk9/changes/jdk9-b31.html
Early Access build for JDK 8u40 b06 http://jdk8.java.net/download.html
is available on
Hi Mark,
Please file an issue in JIRA about this. If you attach a small Maven
project that highlights your problems we have something to work with,
and can hopefully convert that into an integration test.
On Mon, Sep 22, 2014 at 12:55 AM, Mark Derricutt m...@talios.com wrote:
Hrm, just tried
Hi,
sorry
Hi,
We solved N issues:
This should be written as:
We solved 2 issues...
Kind regards
Karl-Heinz Marbaise
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128version=18533
There are still a couple of issues left in JIRA:
On 21 Sep 2014, at 22:54, animator l.gadaw...@gmail.com wrote:
Thanks for answers!
I removed reporting section and unfortunately it doesn't work.. (*1)(btw.
before that I added reporting api and declared InstrumentMojo extends
AbstractMavenReport but this doesn't work too).
I suppose
GitHub user Batmat opened a pull request:
https://github.com/apache/maven-scm/pull/20
SCM-781: Added a recursive goal to validate scm URL.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Batmat/maven-scm SCM-781
Alternatively
Some time ago, we discussed using the JSR305 annotations. At the time we
discussed @Nonnull and @Nullable, and it turned out that those two
annotations are named based in most analysis-tools; you can make your own
org.apache.maven.annotations.Nonnull/Nullable and have a reasonable chance
of having
dependency
groupIdcom.google.code.findbugs/groupId
artifactIdjsr305/artifactId
version3.0.0/version
scopeprovided/scope
/dependency
The reason for this is that the findbugs project has been evolving
these annotations at a pace, and I would now also
Just so everyone knows, JSR 305 is in dormant status. Whatever
annotations you use aren't standard annotations since the JSR never
completed.
Cheers,
Paul
On Mon, Sep 22, 2014 at 11:14 AM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
dependency
Yeah, it seems to me like they just abandoned the JCP but kept the
name. So dormant refers to the JCP project, not the actual findbugs
module we're talking about here, which has a decent release frequency.
Kristian
2014-09-22 18:19 GMT+02:00 Paul Benedict pbened...@apache.org:
Just so everyone
And, included with a provided scope we're not forcing these
annotations on anyone. But they do give marvelous IDE support :)
Kristian
2014-09-22 18:32 GMT+02:00 Kristian Rosenvold kristian.rosenv...@gmail.com:
Yeah, it seems to me like they just abandoned the JCP but kept the
name. So dormant
And I don't really think there's much point in annotating maven core
with these values, I'm not sure there's enough guaranteed consistency
anywhere to actually make it worthwhile. it seems like annotating
shared code and libraries is the most useful.
Kristian
2014-09-22 18:33 GMT+02:00 Kristian
I haven't checked version 3.0.0, but version 1.3.9 used to have sources
with GPL headers and was rejected by Eclipse IP team. Probably worth to
double-check this has been cleaned up.
--
Regards,
Igor
On 2014-09-22, 12:14, Kristian Rosenvold wrote:
dependency
While there is a @Tainted annotation, I could not find any GPL stuff
:) Seems straight BSD to me.
(http://jsr-305.googlecode.com/svn/trunk)
Kristian
2014-09-22 18:55 GMT+02:00 Igor Fedorenko i...@ifedorenko.com:
I haven't checked version 3.0.0, but version 1.3.9 used to have sources
with
Small correction: my vote was +0
Robert
Op Sun, 21 Sep 2014 21:17:03 +0200 schreef Hervé BOUTEMY
herve.bout...@free.fr:
Hi,
The vote has passed with the following result:
+1 (binding): Karl Heinz Marbaise, Benson Margulies, Hervé Boutemy
+1 (binding): Robert Scholte
I will promote the
This vote passes with me, Karl, and Kristian. I will promote.
On Fri, Sep 19, 2014 at 5:16 PM, Benson Margulies bimargul...@gmail.com wrote:
Hi,
Here is a respin of 2.5.1. This includes one more commit that allows
builds on Maven 2.2.1 of the plugin.
We solved 4 issues:
The Apache Maven team is pleased to announce the release of the Apache
Maven Release component, version 2.5.1
maven-release provides technology for automating releases, including
the maven-release-plugin.
http://maven.apache.org/plugins/maven-release-plugin/
You should specify the version in
The index.apt already has a line for version 15. As I read
http://maven.apache.org/developers/release/parent-pom-release.html,
this is not what I expect. Did 15 get partially released or something?
-
To unsubscribe, e-mail:
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since release 14 can be seen here:
http://svn.apache.org/viewvc/maven/pom/tags/apache-15/pom.xml?r1=HEADr2=1575044diff_format=h
Staging repo:
https://repository.apache.org/content/repositories/orgapacheapache-1001
The main problem from the topic finally I managed to resolve. The problem was
wrong configuration in test-polyglot-project, the groupId of declared plugin
in pom was wrong and when the goal was executed it was used plugin from
local repository and any configuration from pom was omitted.. Anyway
The Javadoc plugin is at 2.10, is it not used because it is not considered
stable?
Gary
On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies bimargul...@gmail.com
wrote:
Hi,
Here is release 15 of the POM we maintain for the entire ASF. The
changes since release 14 can be seen here:
You need to use org.apache.maven.plugins.annotations.Component
annotation inside maven plugins, I don't believe plexus @Requirement
works.
--
Regards,
Igor
On 2014-09-22, 18:34, animator wrote:
The main problem from the topic finally I managed to resolve. The problem was
wrong configuration in
I am just trying to help some git sufferers.
On Sep 22, 2014 6:55 PM, Gary Gregory garydgreg...@gmail.com wrote:
The Javadoc plugin is at 2.10, is it not used because it is not considered
stable?
Gary
On Mon, Sep 22, 2014 at 5:27 PM, Benson Margulies bimargul...@gmail.com
wrote:
Hi,
On 22 Sep 2014, at 23:34, animator l.gadaw...@gmail.com wrote:
The main problem from the topic finally I managed to resolve. The problem was
wrong configuration in test-polyglot-project, the groupId of declared plugin
in pom was wrong and when the goal was executed it was used plugin from
24 matches
Mail list logo