Hide Forgot
Description of problem: For quite some time I've been using Ant rather than Maven to build the topic tool. We do however still have a number of entries in the Makefile that I use for building and pushing RPMs which have co-existed with both build systems. Ideally I'd like to move these into the build.xml file and remove the Makefile from the tree completely as I think it's confusing to have intermingling build systems like this. There are task types in ant which will support this, I just haven't gotten around to it. --- For the record the reasons I switched out maven are: 1) I'm familiar with ant already. 2) It was proving difficult to generate builds on RHEL which some users required as maven is not in the standard repos for it. This was also seen as a potential blocker if I ever try to get this into brew.
Made some good progress on this in working copy, pending tidy up of the readme before commit. I have added the 'package' target to the build.xml file which successfully builds the RPM. I haven't added a target for package signing (which was in the makefile but has not been used in some time) or updating the repository (which was out of date). SO would like to look into these further.
Committed revision 75851.
Committed revision 75854. [sgordon@zugzug trunk]$ ant -projecthelp Buildfile: /home/sgordon/Source/topic/trunk/build.xml Build file for Topic Tool. Builds both JAR and RPM output formats. Main targets: all Build all, builds both JAR and RPM formats. build Build JAR file. clean Clean up pre-existing build(s). init Initialize build directory structure. jar Build JAR file, pseudonym for build target. rpm Build RPM file. Default target: all
This isn't really delivered to end users in the RPMs, it's already in SVN where developers (read: me) run the builds from . Thus no RPM build is required so I am closing this as current release.