Markus
plugin-management section with a plugin config that allows you to specify
LD_LIBRARY_PATH
e.g maven-nar-plugin
artifactIdparent-plugin/artifactId build
pluginManagement
plugins plugin
artifactIdmaven-nar-plugin/artifactIdconfiguration linker lib
name/
type/
Maybe you like to vote or comment: http://jira.codehaus.org/browse/MNG-5448 ?
:-)
Regards
-Markus
-Ursprüngliche Nachricht-
Von: Dan Tran [mailto:dant...@gmail.com]
Gesendet: Montag, 25. März 2013 17:04
An: Maven Users List
Betreff: Re: How to tell Maven to put DLL dependency into
Dan,
thank you for this tip. I is working very well. But one question I still do
have: If I have a second project which needs the same native dependency,
obviously I have to tell configure maven-surefire-plugin again. This is a bit
strange, as obviously the fact that the configuration is
dont think maven can do that ( surefire understand jars but not dll/so
). I am facing the same issue and the best I can come up ATM is to
configure every single project
-D
On Mon, Mar 25, 2013 at 12:58 AM, Markus Karg k...@quipsy.de wrote:
Dan,
thank you for this tip. I is working very well.
The bad thing is that just I noticed that m2e actually *clears* already
manually configured native library paths from Eclipse's build path config!
So while it is unable to *set* that information, it is checky enough to
*remove* correct, existing, wanted settings. :-(
-Ursprüngliche
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
Ok. I just assumed that the EclEmma Eclipse plugin would handle all of this
in Eclipse. I haven't used it myself.
Any CI problems are not related to this; I was just focusing on the Eclipse
part of the problem.
/Anders
On Thu, Feb 28, 2013 at 11:08 AM, Markus Karg k...@quipsy.de wrote:
Who
EclEmma simply runs code coverage. AFAIK it does not care about
java.library.path at all. My actual need is one POM-centric declaration of a
DLL dependency that works in *any* tools able to deal with POMs. :-)
-Ursprüngliche Nachricht-
Von: anders.g.ham...@gmail.com
My POM declared a dependency to a DLL:
dependency
groupIdnet.sf.jacob-project/groupId
artifactIdjacob-runtime/artifactId
typedll/type
classifierx64/classifier
version1.17-M2/version
- Use maven profile to detect OS arch and set it into a maven property
- Use maven-dependcy-plugin to down all requires dll. Make sure to
take advantage of the property set in step 1
- Configure maven-surefire-plugin to set PATH env variable into the
download directory
Good luck
-D
On Wed,
Hi Marcus,
Markus Karg wrote:
My POM declared a dependency to a DLL:
dependency
groupIdnet.sf.jacob-project/groupId
artifactIdjacob-runtime/artifactId
typedll/type
classifierx64/classifier
Dan,
sounds reasonable. I think I'll do that! :-)
Thanks a lot!
-Markus
-Original Message-
From: Dan Tran [mailto:dant...@gmail.com]
Sent: Mittwoch, 27. Februar 2013 17:41
To: Maven Users List
Subject: Re: How to tell Maven to put DLL dependency into
java.library.path?
- Use
Jörg,
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?
Thanks! :-)
Markus
-Original Message-
From: Jörg Schaible
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.
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
Possibly. Because in fact, I need other tools to understand the need for
java.library.path, too, mosty the m2e Eclipse plugin, which I doubt will
understand any manual PATH changes in the surefire config (does it?).
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
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
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:
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
19 matches
Mail list logo
