Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

Date: Wednesday, 8 January 2025 at 13:09 To: Maven Developers List Subject: Re: Contributing a Pull Request for the enforcer plugin - branch etiquette This email was sent to you by someone outside the University. You should only click on links or attachments if you are certain that the email is

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

Also note that new enforcer rules do not have to ship with the plugin. There are many that are not bundled with the core plugin such as the extra-enforcer-rules and the Java Linkage checker rule

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

IRA” thread… > > From: Andy Law > Date: Wednesday, 8 January 2025 at 09:35 > To: Maven Developers List > Subject: Re: Contributing a Pull Request for the enforcer plugin - branch > etiquette > That would be easier if there was an ‘Issues’ tab on the > apache/maven-enforcer

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

…and then I realised that this relates to the “Migration from JIRA” thread… From: Andy Law Date: Wednesday, 8 January 2025 at 09:35 To: Maven Developers List Subject: Re: Contributing a Pull Request for the enforcer plugin - branch etiquette That would be easier if there was an ‘Issues’ tab on

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

, 7 January 2025 at 22:46 To: Maven Developers List Subject: Re: Contributing a Pull Request for the enforcer plugin - branch etiquette This email was sent to you by someone outside the University. You should only click on links or attachments if you are certain that the email is genuine and the

Re: Contributing a Pull Request for the enforcer plugin - branch etiquette

Please start by filing an issue describing what the intended rule will do. It's easier to understand in prose than code. On Tue, Jan 7, 2025 at 10:02 PM Andy Law wrote: > > All, > > I’ve written some code to extend the enforcer plugin to include a “mutually > exclusive profiles” rule. I’m ready

Contributing a Pull Request for the enforcer plugin - branch etiquette

All, I’ve written some code to extend the enforcer plugin to include a “mutually exclusive profiles” rule. I’m ready to submit a Pull Request, but I’m not quite sure of the correct procedure. In my own projects, I tend to work primarily off a develop branch, folding features into that and then

Re: Contributing on the maven Checkstyle plugin

There you go: https://github.com/apache/maven-checkstyle-plugin/pull/17 I also created an improvement issue for this: https://issues.apache.org/jira/browse/MCHECKSTYLE-385 Do you need a --sign-off? Also, I haven't signed the CLA yet. Maybe the code change is insignificant enough, because it does

Re: Contributing on the maven Checkstyle plugin

Ben, Welcome aboard! Feel free to send a PR we can discuss there better for such task. Feel free to tag me @eolivelli Cheers Enrico Il mer 11 dic 2019, 17:19 Benjamin Marwell ha scritto: > Hi all, > > I'm new to this list and have contributed a single commit to CXF so far and > would like to s

Contributing on the maven Checkstyle plugin

Hi all, I'm new to this list and have contributed a single commit to CXF so far and would like to start committing on other apache maven projects as well. I'm this case: https://issues.apache.org/jira/browse/MCHECKSTYLE-356 While I think this issue is really not that important, it seems to be a

Contributing Javadoc (was Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1)

Am 03/13/17 um 23:22 schrieb Laird Nelson: > On Mon, Mar 13, 2017 at 2:26 PM Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > Gentle reminder. If you can see this thread, you are entitled to > contribute. This thread is about discovering where the Maven project can > improve how we

Re: Contributing to Apache Maven

Just to be clear about this; only actual committers on the project are allowed to assign an issue to themselves. If you want to fix an issue you will just need to attach a patch to the jira or a pull request. Kristian 2016-06-30 12:30 GMT+02:00 Stian Soiland-Reyes : > If you have registered for

Re: Contributing to Apache Maven

If you have registered for a Jira account then you should be able to add a Comment to any Jira ticket. Is there one in particular you would like to work on? Feel free! You can also just send an email here, saying "I am having a look at MAVEN-123". Nobody restricts you from working on a ticket! Yo

Re: Contributing to Apache Maven

Hi Could someone have a quick at this? I have been kindly waiting and wish to pick up a ticket. Thanks. Regards, Rajiv > On 21 Jun 2016, at 20:15, Rajiv Jain wrote: > > Hi > > I have created a JIRA account and wish to assign myself a JIRA ticket. How > can I assign a ticket to myself? It m

Re: Contributing to Apache Maven

Hi, On 6/21/16 9:15 PM, Rajiv Jain wrote: Hi I have created a JIRA account and wish to assign myself a JIRA ticket. Ok... > How can I assign a ticket to myself? Have you tried to do a "Assign to me" ? If not possible one of the DEV's could do so... > It mentions on the wiki, that I shou

Contributing to Apache Maven

Hi I have created a JIRA account and wish to assign myself a JIRA ticket. How can I assign a ticket to myself? It mentions on the wiki, that I should add a comment so that people know that you are working on this issue. Is this correct or am I looking at outdated information? Secondly, if I wo

Re: Help getting started contributing to maven

Joining this discussion... Based on my experience when I joined, Maven core and maven plugins are different beasts. Sure, if you understand the inner parts of Maven core it is easier to understand plugins, but core also depends on many different libraries which handle different aspects of the logi

Re: Help getting started contributing to maven

Hi Larry, it would be nice if you start working (or trying to sometimes it's hard i know this) on a particular issue that you might give a note here on the dev list so we know where you are working on so this will prevent duplicate work...just to prevent an other one to work on the same issue

Re: Help getting started contributing to maven

Hi Micheal, Thanks a lot for the tips. I look forward to be an active contributor in the community. Will create PR or patches soon. I am still getting to know the project (i mean the code for maven) and how it works. To become familiar with the code base i have started by studying how to build mav

Re: Help getting started contributing to maven

Am 2015-09-28 um 22:40 schrieb ivange larry: Hi all My name is Ivange Larry, am from Cameroon and new to maven community. I have followed the instructions on getting started as a developer in the Apache maven community and below are a few of the things i have done so far. First of all greeting

Re: Help getting started contributing to maven

Hello, Am Mon, 28 Sep 2015 21:40:54 +0100 schrieb ivange larry : > 1 - Is the code hosted here > https://git-wip-us.apache.org/repos/asf/maven.git, the same as the > code hosted on github with this url https://github.com/apache/maven. Yes, github receives a copy of the ASF repository. You can se

Help getting started contributing to maven

Hi all My name is Ivange Larry, am from Cameroon and new to maven community. I have followed the instructions on getting started as a developer in the Apache maven community and below are a few of the things i have done so far. I did a git clone on this url https://git-wip-us.apache.org/repos/asf

Re: Contributing to Maven

, 2014, at 1:48 PM, Karl Heinz Marbaise wrote: Hi, On 12/23/14 2:45 AM, Raghavendra Vaidya wrote: I have downloaded, built and setup maven code on intellij I am able to debug the maven build on the IDE. I want to start contributing to the project by fixing bugs. http://maven.apache.org

Re: Contributing to Maven

and setup maven code on intellij I am able to >> debug the maven build on the IDE. >> >> I want to start contributing to the project by fixing bugs. > > http://maven.apache.org/guides/development/guide-helping.html > > Furthermore there is a JIRA for Maven its

Re: Contributing to Maven

Hi, On 12/23/14 2:45 AM, Raghavendra Vaidya wrote: I have downloaded, built and setup maven code on intellij I am able to debug the maven build on the IDE. I want to start contributing to the project by fixing bugs. http://maven.apache.org/guides/development/guide-helping.html

Re: Contributing to Maven

http://javaadventure.blogspot.ca/2012/07/do-you-want-to-become-maven-committer.html Raghavendra Vaidya wrote on 22.12.2014 17:45: > I have downloaded, built and setup maven code on intellij I am able to > debug the maven build on the IDE. > > I want to start contributing to th

Contributing to Maven

I have downloaded, built and setup maven code on intellij I am able to debug the maven build on the IDE. I want to start contributing to the project by fixing bugs. Could some one point me to resources / documentation on the Maven code design - how the java components are put together .

Contributing to Maven Core

For those interested in contributing to Maven Core. http://takari.io/2014/06/02/contributing-to-maven-core.html I was also talking with Michael about hosting a hangout to demonstrate some of the pretty sophisticated tools we have for debugging Maven Core and the ITs in Eclipse. No one should

Re: Version ranges (was Re: How do I go about contributing a plugin to mojo?)

On 18-Jul-08, at 10:30 AM, Ralph Goers wrote: Jason van Zyl wrote: On 17-Jul-08, at 8:08 PM, Ralph Goers wrote: Michael McCallum wrote: why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... My builds never use versi

Version ranges (was Re: How do I go about contributing a plugin to mojo?)

Jason van Zyl wrote: On 17-Jul-08, at 8:08 PM, Ralph Goers wrote: Michael McCallum wrote: why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... My builds never use version ranges. We require that builds be reproduceab

Re: How do I go about contributing a plugin to mojo?

On 17-Jul-08, at 8:08 PM, Ralph Goers wrote: Michael McCallum wrote: why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... My builds never use version ranges. We require that builds be reproduceable at any time in th

Re: How do I go about contributing a plugin to mojo?

Thursday, July 17, 2008 10:02 AM >> To: Maven Developers List >> Subject: Re: How do I go about contributing a plugin to mojo? >> >> Anyway, my question is how do I go about contributing this? >> >> On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly >> <[EM

Re: How do I go about contributing a plugin to mojo?

Ralph Goers wrote: Michael McCallum wrote: why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... My builds never use version ranges. We require that builds be reproduceable at any time in the future. Version ranges d

Re: How do I go about contributing a plugin to mojo?

Michael McCallum wrote: why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... My builds never use version ranges. We require that builds be reproduceable at any time in the future. Version ranges don't guarantee that.

Re: How do I go about contributing a plugin to mojo?

; -Original Message- > From: Stephen Connolly [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2008 10:02 AM > To: Maven Developers List > Subject: Re: How do I go about contributing a plugin to mojo? > > Anyway, my question is how do I go about contributing this? >

RE: How do I go about contributing a plugin to mojo?

contributing a plugin to mojo? Anyway, my question is how do I go about contributing this? On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > one use case for this is when you have a suite of components and you > want to force _all_ of them to the same version.

Re: How do I go about contributing a plugin to mojo?

Anyway, my question is how do I go about contributing this? On Thu, Jul 17, 2008 at 3:01 PM, Stephen Connolly <[EMAIL PROTECTED]> wrote: > one use case for this is when you have a suite of components and you > want to force _all_ of them to the same version. > > Perhaps you have

Re: How do I go about contributing a plugin to mojo?

one use case for this is when you have a suite of components and you want to force _all_ of them to the same version. Perhaps you have several suites of components and you want to force all the components in each suite to the same versions across the suite. On Thu, Jul 17, 2008 at 2:56 PM, Stephe

Re: How do I go about contributing a plugin to mojo?

And then when you want to roll a release? Anyway, if that was the case why is it that most of the maven plugins themselves use this pattern? e.g. ${maven.version} Also you may want to force all one set of components to the same suite release... so blah-core may be only available at 1.3.5 while b

Re: How do I go about contributing a plugin to mojo?

why not just specify the dependencies with version ranges, if you do there is no need to rewrite anything it just works... On Fri, 18 Jul 2008 00:35:17 Stephen Connolly wrote: > > Oh... and if you want to prevent jumping too high in versions or too > low, it supports adding a version specificatio

Re: How do I go about contributing a plugin to mojo?

pled in sync a lot easier. > > How do I go about contributing this to mojo? > > -Stephen > > FYI here's how it works... > > In your pom you probably have a property used to define the version in > one place, for example: > > > ... >

How do I go about contributing a plugin to mojo?

I have developed a plugin that makes keeping versions of related but not quite tightly coupled in sync a lot easier. How do I go about contributing this to mojo? -Stephen FYI here's how it works... In your pom you probably have a property used to define the version in one place, for ex

Re: Configuration guide for developping / contributing to maven 2.1

> It's recent - I reported it on this list yesterday. If you take trunk back > about a week, you should find that it works a bit better. I'll wait it to be fixed. > On the other hand, if you want a slightly easier way to get started - you > might like to help correct these / vs \ issues on Window

Re: Configuration guide for developping / contributing to maven 2.1

On 01/07/2008, at 2:25 AM, Henri Gomez wrote: I'm using windows and got this error with both windows and cygwin shells ... BTW, did this problem is recent or has still been here ? It's recent - I reported it on this list yesterday. If you take trunk back about a week, you should fin

Re: Configuration guide for developping / contributing to maven 2.1

>>Tests run: 190, Failures: 4, Errors: 0, Skipped: 0 > > what are the failures you are getting in the target/surefire-reports > directory? in maven-project/target/surefire-reports : org.apache.maven.project.MavenProjectDynamismTest.txt : -

Re: Configuration guide for developping / contributing to maven 2.1

>-- Original Message -- >Reply-To: "Maven Developers List" >Date: Mon, 30 Jun 2008 17:11:09 +0200 >From: "Henri Gomez" <[EMAIL PROTECTED]> >To: "Maven Developers List" >Subject: Re: Configuration guide for developping / contri

Re: Configuration guide for developping / contributing to maven 2.1

Just grab maven 2.1 trunk to a new location (At revision: 672783) mvn clean => works mvn compile => works but I see this message : [INFO] [aspectj:compile {execution: compile-aspects}] [WARNING] bad version number found in C:\maven-repository\aspectj\aspectjrt\1.5.3\aspectjrt-1.5.3.jar expected

Re: Configuration guide for developping / contributing to maven 2.1

On 30/06/2008, at 11:55 PM, Henri Gomez wrote: It's the same problem I was working on recently, the embedder tests don't honour your settings, so they don't work with a clean local repository. I added some plugin definitions to the build itself to try and trigger it to download the right a

Re: Configuration guide for developping / contributing to maven 2.1

> It's the same problem I was working on recently, the embedder tests don't > honour your settings, so they don't work with a clean local repository. I > added some plugin definitions to the build itself to try and trigger it to > download the right artifacts (eg, resources plugin 2.2) - do you hav

Re: Configuration guide for developping / contributing to maven 2.1

On 30/06/2008, at 11:23 PM, Henri Gomez wrote: I do a mvn clean and then mvn package and attached the log (pretty long sorry). It's strange but it seems that build couldn't find may It's the same problem I was working on recently, the embedder tests don't honour your settings, so they don

Re: Configuration guide for developping / contributing to maven 2.1

On 30/06/2008, at 8:47 PM, Henri Gomez wrote: Hi to all, I'd like to works on maven 2.1 to locate and fix a problem with jaxws-mojo (http://jira.codehaus.org/browse/MNG-3586) (Eugene suggestion :) Cool, would be good to get another one off the list :) Doing a Run Maven clean works (of cou

Configuration guide for developping / contributing to maven 2.1

Hi to all, I'd like to works on maven 2.1 to locate and fix a problem with jaxws-mojo (http://jira.codehaus.org/browse/MNG-3586) (Eugene suggestion :) I grabbed the trunk from maven 2.1 into my Eclipse 3.4 workspace. I use m2eclipse 0.9.4 so I enabled Maven Dependencies Management and Enabled Ne

Re: Contributing a plug-in

It's also worth considering contributing it to installjammer itself. On 20/06/2007, at 11:55 PM, Jason van Zyl wrote: On 20 Jun 07, at 6:37 AM 20 Jun 07, Donovan, Aaron wrote: I'd like to contribute a plug-in that wraps installjammer, www.installjammer.com. We use it to

Re: Contributing a plug-in

On 20 Jun 07, at 6:37 AM 20 Jun 07, Donovan, Aaron wrote: I'd like to contribute a plug-in that wraps installjammer, www.installjammer.com. We use it to create GUI installers as part of the build process. Should I just submit a Jira issue and attach the code? I'm sure that this has been aske

Contributing a plug-in

I'd like to contribute a plug-in that wraps installjammer, www.installjammer.com. We use it to create GUI installers as part of the build process. Should I just submit a Jira issue and attach the code? I'm sure that this has been asked many times before, but I didn't see any way to search the ma

Re: Contributing several report entries from a Maven Report mojo?

No. Vincent Massol wrote: > Hi, > > Is it possible for a single report mojo to contribute several report entries > in the left menu? > > Thanks > -Vincent > > > > > > > ___ > Nouveau : téléph

Contributing several report entries from a Maven Report mojo?

Hi, Is it possible for a single report mojo to contribute several report entries in the left menu? Thanks -Vincent ___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez le

RE: Contributing

-- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 06, 2005 8:32 AM > To: Maven Developers List; [EMAIL PROTECTED] > Subject: Re: Contributing > > fixed in SVN, thanks > > James Mitchell wrote: > > > > > FYI - You g

Re: Contributing

fixed in SVN, thanks James Mitchell wrote: > > FYI - You guys probably already know, but the link for "Building > Maven 2.0" on this page: http://maven.apache.org/maven2/ > about.html#get-involved/ > > ...gets me a "Page Not Found". > > > > -- > James Mitchell > Software Engineer / Open Source

Contributing

FYI - You guys probably already know, but the link for "Building Maven 2.0" on this page: http://maven.apache.org/maven2/ about.html#get-involved/ ...gets me a "Page Not Found". -- James Mitchell Software Engineer / Open Source Evangelist Consulting / Mentoring / Freelance EdgeTech, Inc.

svn commit: r220293 - /maven/maven-1/core/trunk/xdocs/contributing/patches.xml

Author: brett Date: Fri Jul 22 04:16:09 2005 New Revision: 220293 URL: http://svn.apache.org/viewcvs?rev=220293&view=rev Log: PR: MAVEN-1647 link to issue tracking Modified: maven/maven-1/core/trunk/xdocs/contributing/patches.xml Modified: maven/maven-1/core/trunk/xdocs/contribu

svn commit: r164384 - in /maven/maven-1/core/trunk: maven.xml src/site/ src/site/developers/ src/site/developers/maven-codestyle.xml xdocs/contributing/patches.xml xdocs/developers/code-style.xml xdocs/navigation-pdf.xml xdocs/navigation.xml

aven-codestyle.xml (with props) maven/maven-1/core/trunk/xdocs/developers/code-style.xml (with props) Modified: maven/maven-1/core/trunk/maven.xml maven/maven-1/core/trunk/xdocs/contributing/patches.xml maven/maven-1/core/trunk/xdocs/navigation-pdf.xml maven/maven-1/core/trunk/x

svn commit: r155917 - in maven/maven-1/core/trunk/xdocs: contributing/ contributing/help.xml contributing/patches.xml navigation.xml reference/backwards-compatibility.xml

Author: brett Date: Wed Mar 2 05:43:38 2005 New Revision: 155917 URL: http://svn.apache.org/viewcvs?view=rev&rev=155917 Log: contributing doco and navigation tweak Added: maven/maven-1/core/trunk/xdocs/contributing/ maven/maven-1/core/trunk/xdocs/contributing/help.xml (with p

[jira] Closed: (MPEJB-4) Contributing ejb:ejbdoclet goal

http://jira.codehaus.org/browse/MPEJB-4 Here is an overview of the issue: - Key: MPEJB-4 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: Closed Priority: Major Resolution: WON'T FIX

[jira] Commented: (MAVEN-638) Contributing ejb:ejbdoclet goal

/ViewIssue.jspa?key=MAVEN-638 Here is an overview of the issue: - Key: MAVEN-638 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown

[jira] Updated: (MAVEN-638) Contributing ejb:ejbdoclet goal

View the issue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-638 Here is an overview of the issue: - Key: MAVEN-638 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: U

[jira] Commented: (MAVEN-638) Contributing ejb:ejbdoclet goal

the issue: - Key: MAVEN-638 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other

Re: [jira] Closed: (MAVEN-633) Contributing an ejb:ejb-client goal

> > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-633 > > > Here is an overview of the issue: > ----- > Key: MAVEN-633 > Summary: Contributing an ejb:ejb-client goal >Type:

[jira] Closed: (MAVEN-633) Contributing an ejb:ejb-client goal

Here is an overview of the issue: - Key: MAVEN-633 Summary: Contributing an ejb:ejb-client goal Type: New Feature Status: Closed Priority: Major Resolution: FIXED Time Spent: Unknown Remaining

[jira] Updated: (MAVEN-638) Contributing ejb:ejbdoclet goal

ssue: - Key: MAVEN-638 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other

[jira] Created: (MAVEN-638) Contributing ejb:ejbdoclet goal

: - Key: MAVEN-638 Summary: Contributing ejb:ejbdoclet goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other Fix Fors: 1.0-rc1 Assignee

[jira] Updated: (MAVEN-633) Contributing an ejb:ejb-client goal

ssue: - Key: MAVEN-633 Summary: Contributing an ejb:ejb-client goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other Fix

[jira] Updated: (MAVEN-633) Contributing an ejb:ejb-client goal

http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-633 Here is an overview of the issue: - Key: MAVEN-633 Summary: Contributing an ejb:ejb-client goal Type: New Feature Status: Unassigned Priority: Major Time S

[jira] Commented: (MAVEN-633) Contributing an ejb:ejb-client goal

Summary: Contributing an ejb:ejb-client goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other Assignee: Reporter: James CE Johnsom Created: Wed, 30 Jul 2003 1:02

[jira] Created: (MAVEN-633) Contributing an ejb:ejb-client goal

: - Key: MAVEN-633 Summary: Contributing an ejb:ejb-client goal Type: New Feature Status: Unassigned Priority: Major Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-other Assignee: Reporter: James CE Johnsom