Sebb, Please modify the POMs and whatever else as you see fit.
It sure would be nice to release 2.1. Gary On Thu, Jan 16, 2014 at 7:22 PM, sebb <seb...@gmail.com> wrote: > At present, the VFS poms use the "apache-release" profile from the > Apache pom, and override some bits of it that don't suit Commons. > > However, this is also done by the Commons parent pom which provides > its own "release" profile. > > This is not ideal as VFS uses a different process for releasing code > from all other Commons components. > > VFS is a multi-module project, which makes it a bit trickier to deal > with assemblies etc. > > However as far as I can tell, it is relatively simple to fix VFS. > > Change VFS parent pom to disable the assembly plugin for itself and > all inheriting poms > > Change VFS distribution pom to re-enable the assembly plugin and > change the profile "apache-release" to "release" > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/> Spring Batch in Action <http://www.manning.com/templier/> Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
