Hi,
best is to create a patch which is attached to the jira issue...
And yes maven itself is in Git...and take a look if after you change all
tests are correctly working...
So somplest is to create a fork of the apache repository create a local
branch according to the issue and create an appropriate pull
request...give hint in the jira issue...
Thanks.
Kind regards
karl Heinz Marbaise
On 12/24/14 2:02 PM, Raghavendra Vaidya wrote:
I was looking at bug list and found this - MavenMNG-5721
Which is a possible null pointer exception in
org.apache.maven.repository. MetadataResolutionResult
It is a fairly easy fix where you have to assign the output of initList
function to a private variable ….
I want to fix it. Can some one tell me how do I submit a patch ? the maven site
has details on submitting patch with SVN but I guess the project has moved on
to GIT.
On Dec 23, 2014, at 1:48 PM, Karl Heinz Marbaise <[email protected]> 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/guides/development/guide-helping.html
Furthermore there is a JIRA for Maven itself:
http://jira.codehaus.org/browse/MNG
and for every plugin there are also JIRA areas available see:
http://maven.apache.org/plugins/
See the links on the right side SVN/Git and JIRA ...
You can start working on one of the issues and see if you can handle it....
If you have any questions don't hesitate to ask here on the dev list...
Could some one point me to resources / documentation on the Maven code
design - how the java components are put together .....
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
