Github user asfgit closed the pull request at:
https://github.com/apache/maven-release/pull/6
---
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 is
yes it is exactly this one Stuart
Thanks
On Fri, Jun 10, 2016 at 10:46 PM, Stuart McCulloch
wrote:
> On Friday, 10 June 2016 at 21:33, Arnaud Héritier wrote:
>
> I need to investigate but I have a bug with findbugs and 3.4.0-SNAPSHOT
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:findbu
ok I didn't know the problem was on plugin side and I forgot that this one
wasn't in mojohaus org (but always in the codehaus groupId :( ).
I confirm that findbugs plugin 3.0.4-SNAPSHOT fixes this issue
Garvin could it be possible to release the findbugs plugin ?
thanks
On Fri, Jun 10, 2016 at 10
On Friday, 10 June 2016 at 21:33, Arnaud Héritier wrote:
> I need to investigate but I have a bug with findbugs and 3.4.0-SNAPSHOT
>
> [ERROR] Failed to execute goal
> org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs (findbugs) on project
> support-analytics: Unable to parse configuration
Am 06/10/16 um 22:33 schrieb Arnaud Héritier:
> I need to investigate but I have a bug with findbugs and 3.4.0-SNAPSHOT
It's a bug in the 'findbugs-maven-plugin' already fixed upstream but not
released yet. You just need to build a recent
https://github.com/gleclaire/findbugs-maven-plugin SNAPSHOT
I need to investigate but I have a bug with findbugs and 3.4.0-SNAPSHOT
[ERROR] Failed to execute goal
org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs (findbugs) on
project support-analytics: Unable to parse configuration of mojo
org.codehaus.mojo:findbugs-maven-plugin:3.0.1:findbugs for pa
The Apache Maven team is pleased to announce the release of the Apache
Maven Javadoc Plugin, version 2.10.4
This will be the last Maven 2 compatible version.
The Javadoc Plugin uses the Javadoc tool to generate javadocs for the
specified project.
https://maven.apache.org/plugins/maven-java
The Apache Maven team is pleased to announce the release of the
Apache Maven JAR Plugin Version 3.0.1.
https://maven.apache.org/plugins/maven-jar-plugin/
Important Note:
* Maven 3.X only
* JDK 6 minimum requirement
You should specify the version in your project's plugin configuration:
Hi,
The vote has passed with the following result:
+1 : Karl Heinz Marbaise, Hervé BOUTEMY, Robert Scholte
PMC quorum: reached
I will promote the artifacts to the central repo.
On Tue, 07 Jun 2016 20:39:52 +0200, Robert Scholte
wrote:
Hi,
We solved 12 issues:
https://issues.apache.org
Hi,
The vote has passed with the following result:
+1 : Anders Hammar, Oliver Lamy, Hervé Boutemy, Karl Heinz Marbaise
PMC quorum: reached.
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
+1
On Tue, 07 Jun 2016 20:39:52 +0200, Robert Scholte
wrote:
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317529&version=12331967&styleName=Text
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=proje
Hi Petar,
I don't think that it should be the *plugin* who decides what the loglevel
should be, but the user.
One of my big wishes is to be able to specify for which plugin or goal you
want to change the loglevel.
For example: mvn verify -X makes *everything* log on debug level. Instead
I w
Hello,
I recently got into a problem with my custom plugin. I want to filter out
some loggers, only for my plugin execution and I realized this is not
possible at the moment. I found out this issue which states exactly the
same:
https://issues.apache.org/jira/browse/MNG-5916
The bottleneck for m
\o/
On Fri, Jun 10, 2016 at 8:39 AM, Hervé BOUTEMY
wrote:
> here it is:
> I merged Christian fix
> and I managed to make ITs run as embedded (ASF Jenkins should confirm what
> works on my machine)
>
> if everything goes well, I'll merge to master tonight
>
> Regards,
>
> Hervé
>
> Le jeudi 9 jui
14 matches
Mail list logo