Who said that I do not use the EclEmma Eclipse plugin? Actually I do. :-) But that does neither solve the problem that each new guy in the team needs to set up his java.library.path in Eclipse again, nor the problem that a CI server like Jenkins / Hudson needs to know about all native libraries for running unit tests. *And* m2e clears the manual native lib settings in Eclipse each time it updates from the POM.xml! ;-(
-----Ursprüngliche Nachricht----- Von: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] Im Auftrag von Anders Hammar Gesendet: Donnerstag, 28. Februar 2013 08:54 An: Maven Users List Betreff: Re: How to tell Maven to put DLL dependency into java.library.path? Why not just use the EclEmma Eclipse plugin? It uses Jacoco from what I read on their web site, despite the "emma" in the name of the plugin. /Anders On Thu, Feb 28, 2013 at 8:48 AM, Dan Tran <dant...@gmail.com> wrote: > I think that would work if you invoke 'maven install' using m2e. > However, if you use eclispe's unit test, that may not possible since I > too could not working. I basically configure eclispe or put the dlls > in my system path > > -D > > On Wed, Feb 27, 2013 at 11:21 PM, Markus Karg <k...@quipsy.de> wrote: > > I fact these are not "my " DLLs but are ready-to-use artifacts of > > the > JACOCO project on SourceForge. So I will *never* build them on my own. > But I need to have it working m2e. Do you think your solution will > convince m2e to add lib to java.library.path? > > > > -----Ursprüngliche Nachricht----- > > Von: Dan Tran [mailto:dant...@gmail.com] > > Gesendet: Mittwoch, 27. Februar 2013 22:29 > > An: Maven Users List > > Betreff: Re: How to tell Maven to put DLL dependency into > java.library.path? > > > > if you already have all you DLL loaded at your maven repo, Then it > > make > sense to do so at this moment > > > > if you are required to build dll with maven, better look into NAR > > > > -D > > > > On Wed, Feb 27, 2013 at 12:35 PM, Wayne Fay <wayne...@gmail.com> wrote: > >>> thank you for this interesting idea. I think this would be the > >>> most sophisticated ("most mavenic") solution, but I have the > >>> feeling that Dan's to be simpler to set up in the short term for a Maven > >>> novice? > >> > >> Go with Dan's solution for now, but I think you'll change to the > >> Nar plugin eventually. > >> > >> Wayne > >> > >> ------------------------------------------------------------------- > >> -- 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 > > > > -------------------------------------------------------------------- > > - 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 > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
