Are we moving away from ant to maven, or is this just. An alternative
build process. If the latter is true, how do we ensure that we don't
break one of them?
Cheers
Trons
Sent from my iPhone
On 29. juni 2010, at 11.41, Jørgen Austvik <[email protected]> wrote:
Yesterday I pushed the maven build scripts.
You should be able to "build" with "mvn -Dmaven.test.skip=true" now.
Known issues:
- Some tests fail
- Solaris packages not created
- Documentation updates (README, wiki page)
- Manifest must be changed
- .war file does not contain classes
- jrcs dependency to jar file
- jmx_remote dependency to jar file
- JFlex saves the file in the src directory
This is how I intend to deal with these issues:
Tests: Fix one after another. Help is appreciated.
Solaris packages: Create a shell script (like the ipkg packages). Help
is appreciated.
Documentation: Write it :)
Manifest: Fix with plugin in .pom
war file content: pom fix
jrcs: check out the .zip file with the source that we have in our
repository (several times to get the change history), and create a
maven project and build for that. opengrok-indexer will depend on it.
jflex: fix after vi delete the ant builds by moving files to maven
directory structure (opengrok-indexer/src/{java, test, generated})
Other issues people have found that I have forgotten?
-J
_______________________________________________
opengrok-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
_______________________________________________
opengrok-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opengrok-dev
