When I build the code base, I'm able to get a change list before the build. My developers are asking me to include a special entry in the MANIFEST.MF files for our JAR's that tracks the version of the JAR, but is not the build number. For example, the first time I run a build, the MANIFEST.MF would have two custom fields like so:
Build-Number: 1.0.1 Version-Number: 1 Now, if I change a single Java file and perform a build, I would expect that the Build-Number would change in all JAR's (passed in by Anthill Pro), but Version-Number would only increment for the JAR's that hold the file. So, if the file is in module1/src/foo.java and I have another module named modules2, both would have the same Build-Number, but only module1's JAR would have Version-Number: 2. module1.jar's MANFIEST.MF: Build-Number: 1.0.2 Version-Number: 2 module2.jar's MANIFEST.MF: Build-Number: 1.0.2 Version-Number: 1 Given that my change log has only one line (module1/src/foo.java), what would be the best way of taking my jar basedir value and checking to see if any of the contents are listed in my change log? My only inputs for this is a list of changes, line by line, and the value of jar basedir. I can construct my change log to look however I need it to (convert it to a fileset if needed). BTW, I really want to avoid a custom task. Thanks! Robert
