Hi Daniel, This sounds like a reasonable request. There are two things I can think of: - create an assembly type that is just the directory - pass a flag to the assembly plugin to not create the archive
The second would be preferable if at some point you intend to use the archive to distribute. You could then pass it on the command line (or place a small profile in the directory to always do it under development), and use the intermediate directory under target. Could you please file this as a JIRA request? Also, if that is what you want to do, it would be a fairly simple change so if you want to make that change locally and submit a patch, we'd greatly appreciate it :) Thanks, Brett On 8/15/05, Daniel Krisher <[EMAIL PROTECTED]> wrote: > I recently made the jump from Ant to Maven (2.0-beta snapshot), and I must > say that I am very impressed. Having never used Maven before, it only took a > couple of hours to set up a fairly complex multi-module build process. We > had spent a significant amount of time attempting to engineer a generic > ant-based build process by specifying inter-module dependancies, the result > was a very messy practically unmaintainable set of build files (although > they worked...). With maven, the setup was a breeze and we have gained > better maintainability and extensibility. My only gripe is the lack of > documentation for Maven 2.0, which is completely understandable being a > pre-release application. > > The one thing I have not been able to figure out with Maven is how to build > our application in a manner suitable for immediate use on the system it is > being built on. I have been using the assembly plugin to specify the > structure of the application, including dependancies, an executable jar, and > configuration/data files, which works just fine: > > assembly.tar.bz2: > Application.jar (the executable jar) > lib/ (directory containing all dependencies) > config/ (directory containing runtime configuration) > data/ (directory containing data files) > > Our application is an OpenGL-based visualization tool, and unfortunately, > much of the testing can not be easily automated (we need to analyze the > appearance of OpenGL scenes). This means that during development, we > frequently and repeatedly run the application after a build. Using the > assembly plugin is the only way I have found to create the correct directory > structure for the application, however I would like to do this without > actually archiving the components (i.e. create the file structure but don't > tar/zip/etc it). Building the archive takes a significant amount of time, > and more often than not, we don't ever use the archive (except to extract > the contents to the filesystem, run the application, and repeat the > process). > > So my question is... Is there a way to specify an assembly-like structure ( > e.g. using bin.xml) to create a non-archived assembly? > > > -- > Daniel Krisher > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
