IMO the problems are dealing with Nexus, a web site, and a 'dist' directory; that THREE things to get just right, none are 100% automated. With Nexus you have to do some manual steps. If you look at all the instructions for any commons component, it is long, a combo of manual and Maven+Nexus magic and error prone. It is not fun and a barrier.
Gary On Tue, Oct 8, 2013 at 12:46 PM, Benedikt Ritter <brit...@apache.org> wrote: > Hi, > > one of the points that seem to always come up once in a while is the > process of releasing components. I've never done it myself so I'm asking > people who have done it: > > What are the problems and how can we make releasing easier? > Is the complexity of the parent pom a problem? (Do we really need all the > stuff that is declared there?) > Is there a way to automate all the stuff that needs to be done in a > portable way? > Would it be possible to automate release for example on a Jenkins instance? > > Benedikt > > > -- > http://people.apache.org/~britter/ > http://www.systemoutprintln.de/ > http://twitter.com/BenediktRitter > http://github.com/britter > -- 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
