On Wed, Jan 27, 2010 at 3:27 AM, ant elder <[email protected]> wrote: > On Wed, Jan 27, 2010 at 10:57 AM, Simon Laws <[email protected]> > wrote: >> I wasn't advocating removing the separate property file! This is >> generated stuff so it's not like we have to do work to keep it in >> sync. >> >> Simon >> > > Ah ok sorry i misunderstood, alright I've just tried to do that but i > can't actually see how to easily get it done. The problem is with the > way we have the separate META-INF\MANIFEST.MF file in the module > top-level folder which is copied into the final jar by the Tuscany > plugin and I can't yet find a way to get the updated manifest to be > put in the jar without actually updating the top-level > META-INF\MANIFEST.MF file which would mean it would always be flagged > as updated in svn after a build which isn't very good. Using the jar > plugin as the webpage shows doesn't work as that uses the wrong > manifest, and so does using the manifest in target/classes during the > build. > > ...ant >
I configured the plugin to be more tolerant to fails when discovering the svn revision (see r904595) . This should avoid issues when building from a git copy of the svn repo. -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
