2006/2/14, Stevenson, Chris <[EMAIL PROTECTED]>:
Seems correct
Seems correct but may you add one upper level 'maven-csharp' in which all your plugins and common code will be placed. (like maven-native)
the org.codehaus.mojo project has only one trunk/tags/branches dir.
But you can tag any part (tree) by copying your csharp module into a well named directory inside the tags directory (see the subversino manuel)
It goes the same way for branches. you can branch only a part of the modules in mojo. by example your csharp module.
May that helps (and i'm not too wrong)
Regards
Raphaël
Hello All,So I think I've convinced myself for now that the best place for the CSharp stuff is the mojo project. I think being in m2 core may be too constrictive to development.Just to check, I'm moving all my code to be in the mojos package but as I have multiple plugins inside my project I'm hoping to have code in this manner:packages:org.codehaus.mojo.csharp (root mojo package)org.codehaus.mojo.csharp.studio (plugin)org.codehaus.mojo.csharp.dotnetassembly (plugin)org.codehaus.mojo.csharp.nunit (plugin)
Seems correct
etc...and the plugin names should be the opposite of the m2 core convention:studio-maven-plugindotnetassembly-maven-pluginnunit-maven-pluginIs this correct?
Seems correct but may you add one upper level 'maven-csharp' in which all your plugins and common code will be placed. (like maven-native)
Anything else I should know before submitting source? Also are we able to branch and tag mojos independently of the wider project? ie does each mojo have a svn trunk/tag/branches dir?
the org.codehaus.mojo project has only one trunk/tags/branches dir.
But you can tag any part (tree) by copying your csharp module into a well named directory inside the tags directory (see the subversino manuel)
It goes the same way for branches. you can branch only a part of the modules in mojo. by example your csharp module.
May that helps (and i'm not too wrong)
Regards
Raphaël
