Contribution to maven dependency plugin

2016-05-04 Thread Abhishek Sinha (abhsinh2) 
Hi,

I want to contribute to maven dependency plugin. Can you please point me to 
steps I need to follow for contribution?

Thanks
Abhishek
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Roadmap for MJAR-193 (lifecycle definition in jar plugin)

2016-05-04 Thread Karl Heinz Marbaise 

Hi,

On 5/4/16 10:38 PM, Karl Heinz Marbaise wrote:

Hi Mirko,

just for the record the issue is:

https://issues.apache.org/jira/browse/MJAR-183

and not MJAR-193 ;-)..

On 5/4/16 9:21 PM, Mirko Friedenhagen wrote:

Hello,

I think I understand why it is more appropriate to put life cycles for
package types into the corresponding plugin.

So is the plan to update referenced mojos between minor plugin releases?


I think there problem with that approach, cause if you define your
plugin versions via pluginManagement in your projects (corporate pom
etc.) there will be no change...only if you just omit the definitions
this will influence one...as it does today with changing Maven version...


This should meant:

I think there is no problem with that approach...






Will maven-core 3000 drop life cycle definitions and everyone will
have to
include the type plugin in the pom and remember to switch on extensions?


From the current state yes...

The most important at the moment is we need a mapping from packaging to
plugin which must be extendable...

But we might enhance Maven so there is no need to define extensions=true
...etc.. would make handling simpler...

This is the first step to have the chance for changing Maven core...



Just curious :-)

Regards
Mirko




Some further informations:
http://www.mail-archive.com/dev@maven.apache.org/msg108951.html


Also information about the subject:

https://issues.apache.org/jira/browse/MNG-5697

Kind regards
Karl Heinz

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Roadmap for MJAR-193 (lifecycle definition in jar plugin)

2016-05-04 Thread Karl Heinz Marbaise 

Hi Mirko,

just for the record the issue is:

https://issues.apache.org/jira/browse/MJAR-183

and not MJAR-193 ;-)..

On 5/4/16 9:21 PM, Mirko Friedenhagen wrote:

Hello,

I think I understand why it is more appropriate to put life cycles for
package types into the corresponding plugin.

So is the plan to update referenced mojos between minor plugin releases?


I think there problem with that approach, cause if you define your 
plugin versions via pluginManagement in your projects (corporate pom 
etc.) there will be no change...only if you just omit the definitions 
this will influence one...as it does today with changing Maven version...




Will maven-core 3000 drop life cycle definitions and everyone will have to
include the type plugin in the pom and remember to switch on extensions?


From the current state yes...

The most important at the moment is we need a mapping from packaging to 
plugin which must be extendable...


But we might enhance Maven so there is no need to define extensions=true 
...etc.. would make handling simpler...


This is the first step to have the chance for changing Maven core...



Just curious :-)

Regards
Mirko




Some further informations:
http://www.mail-archive.com/dev@maven.apache.org/msg108951.html


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Apache Source Release Assembly Descriptor version 1.0.6

2016-05-04 Thread Christopher 
+1 (non-binding)

On Mon, May 2, 2016 at 7:50 PM Hervé BOUTEMY  wrote:

> Hi,
>
> In preparation to Apache parent pom version 18, we need a little bugfix on
> Apache Source Release Assembly Descriptor to fix MPOM-106
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314621=12329542=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1006/
>
> https://repository.apache.org/content/repositories/orgapacheapache-1006/org/apache/apache/resources/apache-source-release-assembly-descriptor/1.0.6/apache-source-release-assembly-descriptor-1.0.6-source-release.zip
>
> Source release checksum(s):
> apache-source-release-assembly-descriptor-1.0.6-source-release.zip sha1:
> d2f887c6af52f78927819914a60680aef2ce01c2
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Roadmap for MJAR-193 (lifecycle definition in jar plugin)

2016-05-04 Thread Mirko Friedenhagen 
Hello,

I think I understand why it is more appropriate to put life cycles for
package types into the corresponding plugin.

So is the plan to update referenced mojos between minor plugin releases?

Will maven-core 3000 drop life cycle definitions and everyone will have to
include the type plugin in the pom and remember to switch on extensions?

Just curious :-)

Regards
Mirko
-- 
Sent from my mobile

Re: plexus-utils

2016-05-04 Thread Christian Schulte 
It's working. Thanks.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: plexus-utils

2016-05-04 Thread Christian Schulte 
Am 05/04/16 um 20:27 schrieb Karl Heinz Marbaise:
> Hi Christian,
> 
> On 5/4/16 8:25 PM, Christian Schulte wrote:
>> Thanks. Joined @Github and filed an issue @Sonatype JIRA.
> 
> Can you give the issue reference ?
> 



It's already done but deployment is still failing with

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy
(default-deploy) on project plexus-utils: Failed to deploy artifacts:
Could not transfer artifact org.codehaus.plexus:plexus-utils:jar:3.0.23
from/to plexus-releases
(https://oss.sonatype.org/service/local/staging/deploy/maven2/): Failed
to transfer file:
https://oss.sonatype.org/service/local/staging/deploy/maven2/org/codehaus/plexus/plexus-utils/3.0.23/plexus-utils-3.0.23.jar.
Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

I have setup 'plexus-releases' and 'plexus-snapshots' server definitions
in my settings. Do I need to do anything else?

Regards,
-- 
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: plexus-utils

2016-05-04 Thread Karl Heinz Marbaise 

Hi Christian,

On 5/4/16 8:25 PM, Christian Schulte wrote:

Thanks. Joined @Github and filed an issue @Sonatype JIRA.


Can you give the issue reference ?


Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: plexus-utils

2016-05-04 Thread Christian Schulte 
Thanks. Joined @Github and filed an issue @Sonatype JIRA.


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[VOTE] Release Apache Maven JAR Plugin version 3.0.0 (Take 3)

2016-05-04 Thread Karl Heinz Marbaise 

Hi,

We solved 21 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12334171

There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MJAR%20AND%20status%20%3D%20Open%20ORDER%20BY%20priority%20DESC

Staging repo:
https://repository.apache.org/content/repositories/maven-1265
https://repository.apache.org/content/repositories/maven-1265/org/apache/maven/plugins/maven-jar-plugin/3.0.0/maven-jar-plugin-3.0.0-source-release.zip

Source release checksum(s):
maven-jar-plugin-3.0.0-source-release.zip sha1: 
b749bfd9e76b92102f372fd807b17779c4d03c7e


Staging site:
http://maven.apache.org/plugins-archives/maven-jar-plugin-LATEST/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1

Kind regards
Karl Heinz Marbaise

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: plexus-utils

2016-05-04 Thread Karl Heinz Marbaise 

Hi,

On 5/4/16 6:25 AM, Olivier Lamy wrote:

Hi,
I just invited you as a member. So you can merge your pr.
Not sure how it works to cut release. You probably need some karma setup in
sonatype oss.
If it's a pain let me know and I will do it for you.


You need to open a jira request here:

https://issues.sonatype.org/

and ask for permission to release to the groupId...

This needed to be acknowledged by some members..

Kind regards
Karl Heinz



Olivier

On 4 May 2016 at 09:54, Christian Schulte  wrote:


Hi,

is [https://github.com/codehaus-plexus/plexus-utils] the correct
repository to open pull requests at? I would like to merge a pull
request and create a 'plexus-utils-3.0.23' release. How is that done?
Which issue tracker to use? Whome/where to ask? etc.

Regards,
--
Christian


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Release Plugin And A BOM

2016-05-04 Thread Petar Tahchiev 
Yeah,

I guess I feel the same and that's why I wanted to consult the dev list
first before raising a JIRA.

2016-05-03 23:21 GMT+02:00 Jörg Schaible :

> Hi Petar,
>
> Petar Tahchiev wrote:
>
> > Hi all,
> >
> > @Uwe - the enforcer rules are great, but I don't think I need them.
> > @Jorg - Resolving the parent during release:prepare is fine. What I don't
> > like is that it also asks me to resolve the platform version.
>
> The point is, that Maven does not recreate the effective POM to build again
> the list of versions to resolve. It's simply a corner case. Some might
> argue
> it is undefined behavior, others might say it's a bug ;-)
>
> Cheers,
> Jörg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


-- 
Regards, Petar!
Karlovo, Bulgaria.
---
Public PGP Key at:
http://pgp.mit.edu:11371/pks/lookup?op=get=0x19658550C3110611
Key Fingerprint: A369 A7EE 61BC 93A3 CDFF  55A5 1965 8550 C311 0611