use maven-depdendency-plugin to unpack your zip file and place some where your test can understand and load
-D On Mon, Jun 1, 2009 at 11:56 AM, dkowis <[email protected]> wrote: > On Mon, 1 Jun 2009 13:58:25 -0400, Martin Gainty <[email protected]> > wrote: >> you would need to build in some manner of intelligently defining the >> (groupId,artifactId,version) for your DLL e.g. >> >> i believe the analog for groupId could be namespace //here is an example >> >> #include >> <iostream> >> >> using namespace >> std; >> >> >> namespace >> SampleOne >> >> { >> >> >> float p = 10.34; >> >> }http://www.tenouk.com/download/Module23.txt >> >> if memory serves the analog of artifactId (filename) would be system >> variable called _FILE >> __FILE >> http://gcc.gnu.org/ml/libstdc++/2000-q2/msg00381.html >> >> version would be more of a challenge ..maybe some sort of static variable >> with hardcoded version stamp? > > Hmm. I don't think I made it very clear, sorry. > > Project A and Project B are java projects that need the dll, accessed via > JNI, at runtime. Source code compilation for all the java stuff works > great. > > My problem is that the runtime dependency of rxtxSerial.dll and > rxtxParallel.dll isn't included in any way that the tests can see it or the > application upon it's completion. Especially not in Project A. It knows > it's got a runtime dependency on the zip file, but it doesn't know what to > do with it. > > Sorry for the confusion, > David > >> >> >>> Date: Mon, 1 Jun 2009 12:06:57 -0500 >>> From: [email protected] >>> To: [email protected] >>> Subject: dlls and runtime dependencies >>> >>> I've searched the mailing lists and they don't quite get far enough on >>> this >>> subject for me. >>> >>> I've got a project, incidentally it's the rxtx.org package, that uses > the >>> rxtxSerial.dll. I then have another project that uses that project: >>> >>> Project A >>> | >>> | - Project b >>> | >>> |- zipfile containing rxtxSerial.dll and rxtxParallel.dll >>> >>> So the end project needs to have the zip file somewhere in it's runtime >>> path. Project A does see that it has a runtime dependency of that zip >>> file, >>> but nothing smart happens with it. >>> >>> Basically I need an example of how to do this. If I have to break up the >>> rxtxSerial.dll and rxtxParallel.dll into two separate artifacts some > how, >>> I'd like to know how to do that too. >>> >>> I did apply the hacks to get project b to build and run it's tests. That >>> all works, but the unpacking of that dependency isn't happening anywhere >>> else up the hierarchy. >>> >>> Thanks, >>> David >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> _________________________________________________________________ >> Hotmail® has a new way to see what's up with your friends. >> > http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009 >> >> !DSPAM:2,4a2416e6102591753466293! > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
