@ Vincent: Great to hear that you can provide the patches.
Just for my understanding: Is is not possible to use Nexus because of the dynamic artifactID and Nexus being not eable to understand it? Or is it a general issue with the NAR plugin? @ Jörg: Could you please also post an excerpt of the "demo-dll"-project POM and how you specify different classifiers in the first place? Thanks! Jan -----Ursprüngliche Nachricht----- Von: Vincent Hardion [mailto:vincent.hard...@gmail.com] Gesendet: Dienstag, 18. August 2009 01:00 An: Maven Users List Betreff: Re: RE : AW: RE: AW: Re: AW: Re: Maven for Non-Java Projects Hi, > - Are your patches applied in the trunk of the nar plugin ? I'm not commiter on the CVS of Freehep. But as suggest Jan, I'll send you the patch from the last known version once I come back to my office. > - Is the nar plugin works well also for other phase than compile > (for > instance, test phase) ? We didn't try yet the unit test with Cpp project maybe we'll use CppUnit. It's planned for Q4. I know there are specials goals like nar-testCompile and nar-test but I can't tell you more. > Agree and it's quite pain with platform dependent languages such > C/C++ > How do you cope with this problem ? In fact, there are more than one variable in this problem. In C++, we have to think also with release/debug mode et static/shared linking for library. We tried several solutions. The most integrated to maven should be to set the classifier field of pom used to distinguish jdk. But It doesn't work for 2 reasons : Nar plugin doesn't support it all (I had more than patch it) It breaks snapshot feature. The binaries are in the same deployment path with different timestamps. So the workaround we choose contists to use a "dynamic" artifactId name with the OS name inner with a property. We save lot of time of work but with the experience shows that this is not the best solution. We can't longer use proxy manager like Nexus, the BOM (import of version) is difficult and this won't be support longer by maven. I think we could use the 1st solution by deploy artifacts after all compilation. Best regards, Vincent Le 14 août 09 à 16:53, Rémy Sanlaville a écrit : > Hi Vincent, > > Thanks for your interesting feedback. > > I have some more questions : > - Are your patches applied in the trunk of the nar plugin ? > > - Is the nar plugin works well also for other phase than compile > (for > instance, test phase) ? If yes, which unit test framework are you > using > (CppUnit, CxxTest, googletest...) ? > > - >In C++ with the same code, you need to build one binary for each > platform. Worst, you need to build on each platform to generate the > good > binary. > Agree and it's quite pain with platform dependent languages such > C/C++ > How do you cope with this problem ? > > Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org