I have a similar situation, I have native and java in 2 separate project trees and make java projects to depends on the native artifacts.
The native will be released first, and then fix up java's dependency management to pickup the released native artifact, and then release the java tree For the native release process, it becomes multiple steps process 1. do release:prepare on native tree first 2. go to each platform and run mvn scm:bootstrap to build the just released native tag. Note you can use maven profile to detect the running platform and set up appropriate build properties for you platform specific build a CI server can reduce the manual sub steps in 2 -Dan On Mon, Sep 7, 2009 at 8:42 AM, Antonio Petrelli<antonio.petre...@gmail.com> wrote: > 2009/9/7 Mark Howard <m...@tildemh.com>: >> We're using maven for most of our java development projects but need to >> integrate with some native code. We have a build system that can build >> dlls and shared objects and have integrated this into a maven build so >> that it creates a jar containing the dlls or shared objects. > > Is it simply a case of packaging? I mean, do you need to build every > single DLL, so, etc. and then package them together to create a > distribution for each supported platform? > If yes, it seems a job for the assembly plugin (using the "attach" goal). > > Antonio > > --------------------------------------------------------------------- > 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
