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. We are unable to directly modify the attribute to include the version in the filename since the assembly is signed by the NUnit guys.
So to support this we need to recompile the NUnit assembly with the version in the filename. There is no modification of code, just a changing on manifest attributes and the artifact filename. 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. Thanks, Shane On Jan 11, 2008 2:44 PM, Evan Worley <[EMAIL PROTECTED]> wrote: > 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 PROTECTED]> wrote: > > > 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 <[EMAIL PROTECTED]> > > > Date: Jan 10, 2008 7:42 PM > > > Subject: Deploying nunit framework assembly to a public repository > > > To: [EMAIL PROTECTED] > > > > > > > > > Hello All, > > > > > > As we are preparing for a NMaven release, there are a few questions > > > that > > > need to be answered. Most importantly, we will need to deploy NUnit's > > > framework assembly to a public repository such that NMaven consumers > > > can > > > compile and run nunit tests. There are a few questions about this, > > > I will > > > list them below. > > > > > > > > > 1. Who is to control the key used to sign the assembly? NUnit > > > provides their key along with their source, but perhaps we want to > > > own the > > > key and re-sign the assembly? > > > 2. > > > > > > http://maven.apache.org/guides/mini/guide-central-repository-upload.htmlmentions > > > a few criteria that we cannot meet for this artifact. We will not > > > have all the requires entries in the pom, such as scm url and > > > licenses. The > > > other bit is that this page says that we must " *provide proof that > > > you control the domain",* which we cannot because we don't, though > > > I've heard other artifacts have been submitted by non-owners. > > > 3. How should, if any, the process differ for uploading .net > > > artifacts > > > to a public repository? > > > > > > Thanks for any guidance, > > > Evan > > > > Thanks, > > > > Jason > > > > ---------------------------------------------------------- > > Jason van Zyl > > Founder, Apache Maven > > jason at sonatype dot com > > ---------------------------------------------------------- > > > > We know what we are, but know not what we may be. > > > > -- Shakespeare > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > >
