Hi Gilles, Gilles Dodinet wrote:
> thanks i think i can wait for alpha-3 :) what i wanted to do was first > create a simple csharp compiler, then when i am compfortable enough > with m2 plugins development try to come with a csharp solution as far > complete as possible (compiling, running nunit, building app, creating > installers, etc. - perhaps also see if it is to update config with > auto-update section and how useful that can be). i also need to > interface with starteam. This sounds really good. It's been on our wishlist for a while, so I'd be interested to work with you to get this happening. Is there any chance you'd build the plugin tracking the m2 trunk? That way you could add in a new artifact handler now, and be an additional guinea pig for configurable handlers and the full lifecycle <-> type mapping for which we don't have a test for yet. > right now, as for the compilation step, seems i'm blocked here because > i cannot add any references to the compiler (using ant CSharp task - > 1.5.4 for that matters) - "no artifact handler for 'dll' type". What we have for compilers is in plexus-compilers. It is a generic API which was developed from a similar base as something at Apache, and I am actually going to fold that back in to Jakarta Commons JCI for the next release of the compiler plugin. So we could provide a VS.Net CSharp implementation and a Mono implementation that people could configure locally. The goal should remain compiler:compile - though we might need to look at a better way of configuring the compilers as currently it is quite java specific. WDYT? Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
