Hi Mark, Pure system properties can be set using <systemProperties><property>value</property>
http://maven.apache.org/maven2/plugins/maven-surefire-plugin/test-mojo.html However, surefire doesn't fork at this point, so it may not work for that particular property. I think there is already a JIRA for it under the surefire project if you want to track it. The DLL situation is a combination of documents here: http://docs.codehaus.org/display/MAVEN/Maven+2.0+Design+Documents "packaging vs type" discusses how to get the dll "build profiles" will discuss (after I finished typing it up from some scribbled notes) how to do OS specific dependencies. These are all up for review in the next week, so comments are appreciated (see my recent post to [EMAIL PROTECTED]). Cheers, Brett On 5/21/05, Mark Hobson <[EMAIL PROTECTED]> wrote: > 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]
