We are doing something very similar, building DLLs &/or Linux shared libraries then needing them copied & shipped as dependencies much as jar files are.
Also use the same maven.junit.jvmargs trick to get them in to java.library.path. I haven't tried to move any of this over to m2, but wanted to add my use-case to the discussion for m2 developers consideration Matthew > -----Original Message----- > From: Mark Hobson [mailto:[EMAIL PROTECTED] > Sent: Saturday, May 21, 2005 11:37 PM > To: Maven Users List > Subject: [m2] m2 and SWT > > Has anyone had any thoughts on how m2 could work with SWT projects? > The main problem being the OS-specific artifacts and > artifact-types, e.g. swt-win32-awt-3135.dll, and setting > java.library.path to the resolved dependency paths. > > I have a SWT project building under m1 by declaring the dll's > as dependencies with an artifact type of dll, which obviously > breaks now under m2. Also, my tests require the dll dir in > the java.library.path, which i achieved under m1 with a > maven.junit.jvmargs property expression - is there an easy > way to configure this with surefire under m2? > > Any thoughts would be appreciated. > > Cheers, > > Mark > > --------------------------------------------------------------------- > 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]
