Re: svn commit: r1083903 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/resources/ src/main/resources/org/ src/main/resources/org/apache/ src/main/resources/org/apache/maven/ src/main/resourc

[Dennis Lundberg]

On 2011-03-22 11:37, Benjamin Bentmann wrote:
> Hi Dennis,
> 
>> Author: dennisl
>> Date: Mon Mar 21 19:08:08 2011
>> New Revision: 1083903
>>
>> URL: http://svn.apache.org/viewvc?rev=1083903&view=rev
>> Log:
>> o Add an experimental way of sending the release announcement, so that
>> I can
>> test it on a real release. If all goes well I will move this into
>> maven-plugins-parent and add the relevant documentation to our release
>> documents.
>>
>> Added:
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/
>>
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/
>>
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/plugins/
>>
>>
>> maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/plugins/announcement.vm
>>
> 
> Wouldn't something like "src/release/announcement.vm" be a more
> appropriate place for this file? It looks odd to place build-time config
> files into the directory that is meant to host runtime-time classpath
> resources.

Yes, you are right. I didn't read the plugin docs thoroughly enough and
thought that was the only place one could put them. If the experiment
goes well I'll make sure to move them to a non classpath location.

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


-- 
Dennis Lundberg

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

Re: How do you get aether to traverse the entire dependency tree?

[Benjamin Bentmann]

David Jencks wrote:


Is there some way to  require minimum plugin versions in a custom packaging or 
its LifecycleMapping?


No, lifecycle mappings can only provide default plugin versions, the 
versions from the POMs win.



Benjamin

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

Re: How do you get aether to traverse the entire dependency tree?

[David Jencks]

This ended up being good advice.  The problem was an antique 
maven-install-plugin specified in a parent pom.

Is there some way to  require minimum plugin versions in a custom packaging or 
its LifecycleMapping?  

thanks
david jencks

On Mar 21, 2011, at 3:06 AM, Benjamin Bentmann wrote:

> David Jencks wrote:
> 
>> Any advice?
> 
> Provide a standalone example project that allows others to reproduce/analyze 
> the problem.
> 
> 
> Benjamin
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 


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

Re: Defining common localRepository that will work on both Windows and linux

[Wayne Fay]

> My settings file in the .m2 folder begins like this-
> C:\maven-repo\
>
> I want to make this generic and define a common localRepository which will
> work both on Windows and on Linux. Please help.

If you drop the C:\ and just specify a path, it will be common to both
Windows and Linux. I am pretty sure Windows uses the SystemDrive
property (type "set" in MSDOS to see the value) to decide which drive
the path is located on, so hopefully all your Windows users have that
value the same.

For example:
/maven-repo/

Wayne

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

Defining common localRepository that will work on both Windows and linux

[Ritika.Goel]

Hi,

My settings file in the .m2 folder begins like this-
C:\maven-repo\

I want to make this generic and define a common localRepository which will work 
both on Windows and on Linux. Please help.

Thanks,

Ritika Goel
Equities Connectivity and Futures
Barclays Capital
(212) 320-7356




___

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
___

Re: [VOTE] Release Maven GPG Plugin version 1.2

[Evgeny Mandrikov]

+1

On Tue, Mar 22, 2011 at 17:08, Lukas Theussl  wrote:

>
> +1
>
> -Lukas
>
>
>
> Dennis Lundberg wrote:
>
>> Hi,
>>
>> We solved 2 issues:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431&styleName=Html&version=16529
>>
>> There are still a couple of issues left in JIRA:
>>
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11431&status=1
>>
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-021/
>>
>> Staging site:
>> http://maven.apache.org/plugins/maven-gpg-plugin-1.2/
>>
>> 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
>
>


-- 
Best regards,
Evgeny Mandrikov aka Godin 
http://twitter.com/_godin_

Re: [VOTE] Release Maven GPG Plugin version 1.2

[Lukas Theussl]

+1

-Lukas


Dennis Lundberg wrote:

Hi,

We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11431&styleName=Html&version=16529

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11431&status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-021/

Staging site:
http://maven.apache.org/plugins/maven-gpg-plugin-1.2/

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

Re: Include maven-car-plugin to the official maven plugins

[Stephen Connolly]

FYI Ben has granted Arnaud & I jira admin access also. so we should have a
bit more redundancy now

-Stephen

2011/3/20 Stephen Connolly 

> Yeah, I'll pester ben on tuesday and see if we can get a couple more PMCs
> with admin rights (AFAIK Brett is the only one)
>
>
> 2011/3/19 Arnaud Héritier 
>
>> I lost my admin rights a long time ago and I'm not sure there are
>> always codehaus jira admins here ?
>> The best is to contact ben on IRC or by opening a HAUS issue
>>
>> Cheers
>>
>> Arnaud
>>
>> On Sat, Mar 19, 2011 at 9:19 PM, Stephane Nicoll
>>  wrote:
>> > okay I have a candidate implementation based on the initial plugin on
>> google
>> > code.
>> >
>> > Can someone with Jira admin right create the maven project for the
>> plugin
>> > please?
>> > http://jira.codehaus.org/browse/MPA-116
>> >
>> > Thanks,
>> > Stéphane
>> >
>> > On Sat, Mar 19, 2011 at 10:04 AM, Kristian Rosenvold <
>> > kristian.rosenv...@gmail.com> wrote:
>> >
>> >> Sorry, my misunderstanding.
>> >>
>> >> Looks good to me ;)
>> >>
>> >> Kristian
>> >>
>> >>
>> >>
>> >> lø., 19.03.2011 kl. 09.51 +0100, skrev Stephane Nicoll:
>> >> > What other code are you talking about? The plugin on google code? The
>> >> idea
>> >> > here is to deprecate it in favor of this "official" maven plugin
>> >> >
>> >> > S.
>> >> >
>> >> > On Sat, Mar 19, 2011 at 9:49 AM, Kristian Rosenvold <
>> >> > kristian.rosenv...@gmail.com> wrote:
>> >> >
>> >> > > Just out of curiosity, how does this code relate to the other code
>> that
>> >> > > does similar stuff? Is it a copy paste fork?
>> >> > >
>> >> > > Kristian
>> >> > >
>> >> > > lø., 19.03.2011 kl. 09.42 +0100, skrev Olivier Lamy:
>> >> > > > Hi,
>> >> > > > No problem for me if you want to add this new packaging support
>> and
>> >> > > > add in maven core.
>> >> > > >
>> >> > > > acr ?
>> >> > > >
>> >> > > > --
>> >> > > > Olivier
>> >> > > >
>> >> > > > 2011/3/19 Stephane Nicoll :
>> >> > > > > No Maven committers/PMCs replied to this.
>> >> > > > >
>> >> > > > > Any insight?
>> >> > > > >
>> >> > > > > S.
>> >> > > > >
>> >> > > > > On Mon, Mar 14, 2011 at 9:22 AM, Stephane Nicoll
>> >> > > > > wrote:
>> >> > > > >
>> >> > > > >> Hi,
>> >> > > > >>
>> >> > > > >> I am currently working on supporting the "application-client"
>> >> artifact
>> >> > > > >> type properly in the EAR plugin. Pablo (in CC) wrote a
>> >> > > > >> maven-car-plugin[1] which is very similar to the EJB plugin
>> but
>> >> for
>> >> > > > >> application-client type. Do we think it would be reasonable to
>> add
>> >> > > > >> this plugin to the portfolio of standard plugins? (if Pablo
>> >> accepts to
>> >> > > > >> contribute it to the ASF but I don't think it would be an
>> issue).
>> >> > > > >>
>> >> > > > >> I am bit puzzled about the type 'car' since car is already
>> used by
>> >> > > > >> Geronimo for their deployment plans;
>> >> application-client
>> >> > > > >> would better fit I'd say (with a .jar extension)
>> >> > > > >>
>> >> > > > >> The problems I am having is that since we don't have an
>> "official"
>> >> > > > >> maven type for that thing and nothing to build it with Maven,
>> I
>> >> can't
>> >> > > > >> detect these artifacts other than scanning every single jar
>> file
>> >> added
>> >> > > > >> to a project to see if there is a
>> META-INF/application-client.xml
>> >> > > > >> file. Frankly, I am not going to implement a feature that will
>> >> scan
>> >> > > > >> every single jar file before building an EAR
>> >> > > > >>
>> >> > > > >> The plugin needs a bit of cleanup (namely the jEE version
>> check)
>> >> and I
>> >> > > > >> don't know if the community uses this a lot but we don't cover
>> the
>> >> > > > >> whole spectrum of the JavaEE spec and it wouldn't cost us much
>> to
>> >> do
>> >> > > > >> it.
>> >> > > > >>
>> >> > > > >> Can someone remind me how these "official" types gets added
>> and
>> >> > > > >> detected by Maven? Do we absolutely need to touch the core
>> type
>> >> > > > >> definition files or is there another way?
>> >> > > > >>
>> >> > > > >> Please let me know what you think.
>> >> > > > >>
>> >> > > > >> Thanks,
>> >> > > > >> S.
>> >> > > > >>
>> >> > > > >> [1] http://code.google.com/p/maven-car-plugin
>> >> > > > >>
>> >> > > > >
>> >> > > >
>> >> > > >
>> -
>> >> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> > > > For additional commands, e-mail: dev-h...@maven.apache.org
>> >> > > >
>> >> > >
>> >> > >
>> >> > >
>> >> > >
>> -
>> >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> > > For additional commands, e-mail: dev-h...@maven.apache.org
>> >> > >
>> >> > >
>> >>
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: dev-h...@maven.apache.org
>> >>
>> >>
>> >
>

Re: svn commit: r1083903 - in /maven/plugins/trunk/maven-gpg-plugin: ./ src/main/resources/ src/main/resources/org/ src/main/resources/org/apache/ src/main/resources/org/apache/maven/ src/main/resourc

[Benjamin Bentmann]

Hi Dennis,


Author: dennisl
Date: Mon Mar 21 19:08:08 2011
New Revision: 1083903

URL: http://svn.apache.org/viewvc?rev=1083903&view=rev
Log:
o Add an experimental way of sending the release announcement, so that I can
test it on a real release. If all goes well I will move this into
maven-plugins-parent and add the relevant documentation to our release
documents.

Added:
maven/plugins/trunk/maven-gpg-plugin/src/main/resources/
maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/
maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/
maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/

maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/plugins/

maven/plugins/trunk/maven-gpg-plugin/src/main/resources/org/apache/maven/plugins/announcement.vm


Wouldn't something like "src/release/announcement.vm" be a more 
appropriate place for this file? It looks odd to place build-time config 
files into the directory that is meant to host runtime-time classpath 
resources.



Benjamin

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