RE: Deploying nunit framework assembly to a public repository

2008-01-11 Thread Brian E. Fox
>NUnit includes their key for >signing within the build source, but I tend to think we should use our own >key so that people can verify the source of the assembly. I agree that if you rebuild, it should use the actual builder's key for signing. Including the key with the source seems to defeat th

Re: [VOTE] [Take 2] Release Maven Surefire version 2.4

2008-01-11 Thread Jerome Lacoste
On Jan 3, 2008 10:20 AM, Jerome Lacoste <[EMAIL PROTECTED]> wrote: > On Jan 3, 2008 9:17 AM, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > +1 > > +1 from a happy user. This vote has passed, right ? Jerome - To unsubscribe, e-mail

Re: [VOTE] Release Maven Jar plugin version 2.2

2008-01-11 Thread Olivier Lamy
Thanks. I will do that. And I will try to work on this license header removing. But currently units failed in the release project due to this (on a windows laptop but not on a solaris box). (weird) (can someone with a windows confirms this or I have a real issue on my laptop :-) ). I suspect an ind

Re: [VOTE] Release Maven Jar plugin version 2.2

2008-01-11 Thread Dennis Lundberg
Dennis Lundberg wrote: Olivier Lamy wrote: Ok (in fact license header was not here even before release). Yes it was there before the first release cycle. I caught it in the commit email: https://svn.apache.org/viewvc/maven/plugins/trunk/maven-jar-plugin/pom.xml?r1=610166&r2=610863&diff_form

Re: Deploying nunit framework assembly to a public repository

2008-01-11 Thread Shane Isbell
To provide some context on this, we are now using standard artifact resolvers for .NET assemblies and require that the filename of an assembly contain the version. This filename is also an attribute within the manifest of the library assembly and needs to match the actual filename of the artifact.

Re: Deploying nunit framework assembly to a public repository

2008-01-11 Thread Evan Worley
That depends on the answer to #1, below. If we don't need to re-sign the assembly ourself, then we can simply deploy the framework assembly that comes with their install. If we do want to re-sign, then we can re-assembly it ourself. Thanks, Evan On Jan 11, 2008 2:28 PM, Jason van Zyl <[EMAIL PR

Re: Deploying nunit framework assembly to a public repository

2008-01-11 Thread Jason van Zyl
Who created the NUnit assembly? As is from them, or something you augmented? On 11-Jan-08, at 11:34 AM, Evan Worley wrote: Hello All, If anyone can help on the questions below, it would be greatly appreciated. Thank you, Evan -- Forwarded message -- From: Evan Worley <[EM

Fwd: Deploying nunit framework assembly to a public repository

2008-01-11 Thread Evan Worley
Hello All, If anyone can help on the questions below, it would be greatly appreciated. Thank you, Evan -- Forwarded message -- From: Evan Worley <[EMAIL PROTECTED]> Date: Jan 10, 2008 7:42 PM Subject: Deploying nunit framework assembly to a public repository To: [EMAIL PROTECTED]

Re: Maven Enforcer Plugin

2008-01-11 Thread Hilco Wijbenga
On Jan 10, 2008 6:33 PM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > Hilco, I'll have to take a deeper look, it's possible that I missed some > other cases. I had to manually read and interpret the poms since I > couldn't get them unmolested from the core. Can you open a jira and > attach a sample so

Re: [vote] release maven-common-artifact-filters 1.0

2008-01-11 Thread Vincent Siveton
+1 Vincent 2008/1/10, Brian E. Fox <[EMAIL PROTECTED]>: > I'd like to release maven-common-artifact-filters 1.0 > > > > This contains some of the shared filters moved out of maven artifact and > also the filters previously contained by the dependency plugin. > > > > The release is staged at: > ht

Re: clean doesn't process additionalFileSets consistently

2008-01-11 Thread Benjamin Bentmann
Hi, Heinrich Nirschl wrote: > > Maybe the intention was to base relative file names at basedir? This > should however be done correctly of course. > I recently filled in a JIRA issue with a patch for this ( http://jira.codehaus.org/browse/MCLEAN-31 MCLEAN-31 ). You are invited to review it an