Re: Beginning the process of updating maven-pmd-plugin

Create an account on Xircles [1] and then file a JIRA ticket [2] with your patch. Please include integration tests or similar to verify the new functionality. [1] https://xircles.codehaus.org/ [2] http://jira.codehaus.org/browse/MPMD /Anders On Mon, Jan 19, 2015 at 2:15 AM, wrote: > I've devel

Re: Surefire Plugin does not handle workingDirectory in fork mode properly

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

Re: Releasing the Checkstyle Plugin

Thanks, will do. On Sun, Jan 18, 2015 at 8:12 AM, Dennis Lundberg wrote: > Henning, > > Please try the latest 2.14-SNAPSHOT version from the ASF repository. > You should be able to just override the Checkstyle version by adding a > dependency on Checkstyle 6.2 to the Maven Checkstyle Plugin in yo

Beginning the process of updating maven-pmd-plugin

I've developed an update to the maven-pmd-plugin 3.3 project which allows it to check JSP files - I'd like to begin the process of getting the plugin updated, but I'm not sure what the next step is. Is there someone who can guide me on this process or direct me to the documentation? Thanks -

Surefire Plugin does not handle workingDirectory in fork mode properly

Hi All, Not sure whether this is a proper place however Surefire webpage redirects to this mailing group. Recently we found two issues in Surefire plugin related to surefire.forkNumber variable and ability to define separate working directory per forked JVM. First issue is that the same directory i

Re: [VOTE] Release Apache Maven GPG Plugin version 1.6 - Take 2

+1 Regards, Hervé Le jeudi 15 janvier 2015 20:26:50 Dan Tran a écrit : > Hi, > > We solved 4 issues: > http://jira.codehaus.org/secure/ReleaseNote.jspa? > projectId=11431&version=20125 > > There are still a couple of issues left in JIRA: > http://jira.codehaus.org/issues/?jql=project%20%3D% >

Re: [VOTE] Release Apache Maven Shared Component: Maven Dependency Analyzer Version 1.6

+1 (non-binding) Verified with m-dependency-p ITs. /Anders On Sun, Jan 18, 2015 at 3:34 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 3 issues: > https://jira.codehaus.org/secure/ReleaseNote.jspa? > projectId=11761&version=20721 > > There are still a couple of issues left in JIRA: > https

Re: [VOTE] Release Apache Maven GPG Plugin version 1.6 - Take 2

+1 On Jan 16, 2015, at 9:33 AM, Karl Heinz Marbaise wrote: > Hi Dan, > > checked SHA1 Ok. > > Checked with Maven 3.2.5, 3.1.1, 3.0.5, 2.2.1 via: > > mvn -Prun-its clean verify > > without any issue.. > > +1 from me. > > Kind regards > Karl Heinz Marbaise > > On 1/16/15 5:26 AM, Dan Tran w

Re: [VOTE] Release Apache Maven GPG Plugin version 1.6 - Take 2

Hi We need a couple more PMC votes Thanks -D On Fri, Jan 16, 2015 at 9:59 AM, Dan Tran wrote: > +1 ( none binding). > > -D > > On Fri, Jan 16, 2015 at 6:33 AM, Karl Heinz Marbaise > wrote: > >> Hi Dan, >> >> checked SHA1 Ok. >> >> Checked with Maven 3.2.5, 3.1.1, 3.0.5, 2.2.1 via: >> >> mv

Re: [VOTE] Release Apache Maven Shared Component: Maven Dependency Analyzer Version 1.6

+1 On Jan 18, 2015, at 9:34 AM, Karl Heinz Marbaise wrote: > Hi, > > We solved 3 issues: > https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=20721 > > There are still a couple of issues left in JIRA: > https://jira.codehaus.org/browse/MSHARED/component/13265 > > Stagin

Re: Releasing the Checkstyle Plugin

Henning, Please try the latest 2.14-SNAPSHOT version from the ASF repository. You should be able to just override the Checkstyle version by adding a dependency on Checkstyle 6.2 to the Maven Checkstyle Plugin in your project's POM. On Sat, Jan 17, 2015 at 6:39 PM, Henning Schmiedehausen wrote: >

Re: Releasing the Checkstyle Plugin

There are now 3 issues left for the 2.14 version in JIRA. I've commented on two of them. Unless someone wants to include them (and are willing to do the work shortly) I will move them to the backlog. After that I will start the release of 2.14. Then I plan to do 2.15 (Java 6) and 2.16 (Java 7) in

Re: Plugin exposing API - best practise?

Hello Igor, Well - there is certainly a point of requiring the plugin API to require same dependencies (including versions) as are mandatory for correct execution of the plugin itself. A common parent defining maven GAVs and standard dependency management can probably solve that without too much h

[VOTE] Release Apache Maven Shared Component: Maven Dependency Analyzer Version 1.6

Hi, We solved 3 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=20721 There are still a couple of issues left in JIRA: https://jira.codehaus.org/browse/MSHARED/component/13265 Staging repo: https://repository.apache.org/content/repositories/maven-1127 https://

Re: Releasing the dependency plugin?

Hi, On 1/18/15 2:42 PM, Anders Hammar wrote: MDEP-466 [1] is the regression I was talking about. The issue has been fixed in source but it requires a new release of maven-dependency-analyzer. Ok...Than i will start VOTE for maven-dependency-analyzer... First ... [1] https://jira.codehaus.

Re: Releasing the dependency plugin?

MDEP-466 [1] is the regression I was talking about. The issue has been fixed in source but it requires a new release of maven-dependency-analyzer. [1] https://jira.codehaus.org/browse/MDEP-466 /Anders On Sun, Jan 18, 2015 at 10:22 AM, Anders Hammar wrote: > There's a regression in the last rel

Re: Plugin exposing API - best practise?

2015-01-18 12:17 GMT+01:00 Lennart Jörelid : > Hello folks, > > I need a best practise here - hope you can assist me with some ideas and > suggestions. > > *APIs for extensible-configuration plugins* > > I believe that plugins that exposes extensible configuration options should > publish the APIs

Re: Plugin exposing API - best practise?

I probably wouldn't use this for my plugins Today, plugin extensions are loaded in the same classloader as the rest of plugin dependencies. Hiding plugin dependencies from extensions during compile-time does not reflect runtime and can do more harm than good. If, for example, a plugin depends on

Plugin exposing API - best practise?

Hello folks, I need a best practise here - hope you can assist me with some ideas and suggestions. *APIs for extensible-configuration plugins* I believe that plugins that exposes extensible configuration options should publish the APIs of those options as a separate project, to keep the set of t

[VOTE] Release Apache Maven Shared Component: Maven JarSigner Version 1.4

Hi, We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=19864 There are still a couple of issues left in JIRA: http://jira.codehaus.org/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC Staging

Re: Releasing the dependency plugin?

There's a regression in the last release that would be great to have fixed as well. I'm not by a computer right now though to dig up the jira. /Anders (mobile) Den 17 jan 2015 09:41 skrev "Karl Heinz Marbaise" : > Hi, > > On 1/17/15 6:16 AM, Henning Schmiedehausen wrote: > >> Hi, >> >> any chance