See comments

On 12/21/05, Stevenson, Chris <[EMAIL PROTECTED]> wrote:
> I will try and put together an apt doc over the next week which details all
> (*most*) of the dotnet stuff.
>
> The things that would be excellent to get into ibiblio first off would be:
>
> - My Nunit build (is on javaforge too). This is obviously pretty key as
> can't do any of the unit testing for projects without it. This is a dll.

We can upload the original dll from nunit to the org.nunit groupId if
you provide the pom


> - The updated plexus csharp compiler (perhaps I could submit a patch as this
> is already hosted at maven but I have altered it a bit to get it working).
> Jar.

This has to go through the plexus project, please submit the patch


> - The two archetypes (dotnet exe and lib) that I've written so far. Jar.
> - The dotnet-assembly-plugin (contains general dotnet tools). Jar.

For now we can upload them to the com.javaforge.maven-csharp groupId,
please follow the instructions at
http://maven.apache.org/guides/mini/guide-ibiblio-upload.html


>
> Nice to haves would be:
>
> - Log4net (though I need to email the developers to make sure they have no
> objections to me releasing a mavenised version). Dll

If it's something released by the log4net project it can go to the
org.apache.logging.log4net groupId, if it's something you customized,
it has to go to com.javaforge.maven-csharp groupId


> - The Visual Studio plugin ( this allows you to create a visual studio
> project off the pom). Jar.

This can go also to com.javaforge.maven-csharp groupId


>
> Its likely that the plugins will go through a fairly regular release
> schedule as people start to play with them and find the bits I've missed.
> :-)
>
> Thanks for the link I will add a csharp bit too the language support page.
>
> Regs,
>
> Chris

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to