Gilles Dodinet wrote: > ive tried to build from trunk but encountered some problems with > bootstrap : i had to build core-it-verifier by hand (using alpha-2), > but then all it-tests failed because of file not found (however the > files were actually present). i remember having encountered such issue > a while back when bootstrapping (as far as i can recall that was a > basedir issue). i havent investigated this very far and downloaded the > last snapshot instead.
This is a bit weird. I'd like to work this through with you if possible (as you can see, our clean build is working on the integration machine - so I'd need to see what in your environment is causing it). > > but yet im still not sure how to register an artifact handler. maven-artifact/src/main/resources/META-INF/plexus/components.xml lists them > i also wonder how i can specify non defualt artifact name mapping. > indeed even though it is to handle assembly name like any other > artifact, assemblies generally don't include version in the name (no > judgement nor appreciation here). on the other hand m2 default > repository layout has a folder per version so i guess it should be > possible to locate a dependency even if its name doesn't make the > version explicit, not ? (although i understand this make it not > backward compatible) In the repository, the naming format is quite strict - the handler only has control over the extension used (And the subdirectory in the old style repo). I don't quite understand the use case - you can bundle/save without versions locally, but the repository artifacts should still have a version. Can you explain more about this? > > concerning the lifecycle i'm not sure how to map it to a specific > packaging type. it's tempting though to use the artifact handler for > this. but handlers seem to only define packageGoal(). so how to > instruct m2 that a project that has a 'foo' packaging type should be > compiled with foo-compiler. This would be the responsibility of the compiler mojo. However, you may need to alter the lifecycle more - there has been a thread of discussion about how to do this recently, but is not yet implemented. > i'm not sure either to understand the directory() method. is this > method present to support m1 repository-style ? correct. > what i have so far is pretty simplistic as you can see at > http://codehaus.org/~gdodinet/csharp.png. ok, I was thinking that you should be able to use the same compiler mojo, and have an alternate configuration element for csharp (and we could possibly put the java compiler options into a separate nested element too). I'm not sure about this - maybe it is better to have a separate mojo. How much do they differ? I agree we could rename classpath elements to dependencyFiles, however. > concerning the ant task i would have been happier without it (not > mentionning that it needs an ant project - however i use 1.5.4, > perhaps that changed in 1.6+) but for now i didn't wnat to rewrite > something similar. That's fine to get started. I think a good goal is to get some of the ant compiler code into commons-jci, without the ant project/types/listener bindings if that's possible. I'm going to try and kickstart that soon. - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
