On 4/22/06, Tommy Svensson <[EMAIL PROTECTED]> wrote: > When I used Ant to build my project I made the 2 generators executable > with java -jar by supplying a Main-Class and Class-path entries in the > MANIFEST.MF file of the jar files.
Put MANIFEST.MF in src/main/resources/META-INF and it will appear in the jar. Also: http://maven.apache.org/guides/mini/guide-manifest.html > Problem 2: > In the end I also want to package these 4 parts into a release zip (also > including documentation) that can be installed and used by simply > unzipping somewhere. Maven Assembly Plugin http://maven.apache.org/plugins/maven-assembly-plugin/ (I suggest using the latest snapshot, some features have been added since the last release.) > Problem 3: > I want to be able to checkout clean sources from CVS and then simply > build the whole project with one build command. With maven I seem to be > required to manually initiate the build for each part and to do it in > the correct order so that dependencies are resolved correctly. I want a > dependency on the source also, not only the compiled binaries. I want to > be able to have a top project with dependencies on the other 4 and when > I build that all projects are build in the order required to support > compile dependencies. Now that you've split your project into modules, create a 'top level' pom.xml file which lists them: <modules> <module>myproj-core</module> <module>myproj-gen1</module> ... (Optionally, each of these modules can have a <parent> element pointing at this top-level pom, and then they will inherit from the parent.) Now Maven will resolve the dependencies and build the projects in the correct order, for example with: $ mvn install HTH, -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
