Deploy project artifacts

NMaven can now deploy dotnet libraries, and you can also deploy and resolve snapshot libraries from both remote and local repositories.

Uses AsssemblyInformationalVersion to encode the snapshot version in AssemblyInfo

Adding maven-deploy-plugin to deploy dotnet libraries, using standard maven (java) repo layout
Adding integration tests for above

Applied patch to the SI_XPT branch. It works perfectly. Thanks.

I did notice a weird thing with the patch. It handles snapshots correctly and it handles deployment correctly. But when I try to deploy snapshots, the assemblies become corrupted. I am still investigating this. Anyone else seeing the same thing?

Shane,

I haven't seen corruption but I am curious as to what could be going on. The only thing we changed in the assembly itself is the encoding of the VERSION-SNAPSHOT in the "informationalVersion" attribute of the AssemblyInfo.

Let me know if there is anything we can do to help the investigation.

-Evan

Okay, I found the problem. During a deploy the assembly, say NMaven.Logging-0.14-20070513.170342-4.dll, contained the pom.xml file, not the .NET assembly. The DeployMojo is using mavenProject.getFile() (the returned value is the pom file) as the artifact to deploy, instead of mavenProject.getArtifact().getFile() .

I will check in the change and then we should be good to go.

Feature merged into trunk.

Original patch with ASF 2.0 license added