> 1. I would like to promote this plugin from the beta > state to a final release 2.0 (currently 2.0-beta-2) > > Are there any special requirements to fulfill to get into > 2.0 release or is it just a thing: do it? >
Follow the steps here: http://mojo.codehaus.org/development/performing-a-release.html#Preparing_for_the_First_Production_Release > The documentation > (http://mojo.codehaus.org/development/process.html) says > something different: > > x.y.z-alpha-n > Alpha version, not feature complete. > x.y.z-beta-n > Beta version, complete for the next release, > not tested/documented. > x.y.z > "Proper" release. Pushed to the central repositories on release. > > But in controdiction to the above the jdepend-maven-plugin > is in central available. > We push all "releases" (pre-releases as well) to central. That page should be clarified I guess. Plugins in sandbox is different though as we never make any releases of them. Thus, they can't be found in central. /Anders > > > 2. This plugin currently forks the life-cycle compile (generate): > > The question is: Why is this necessary (may be i misunderstand > a thing with those forking of the life-cycle)? > Wouldn't it be better having different goals (one which forks > an other which doesn't) to give the user the chance to decide > which to use? > > Any hints, objections, explanations? > > Thanks in advance. > > Kind regards > Karl-Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
