AFAIK we can skip the javadoc generation as IDEs will download the -sources jars and use the javadoc from the source code.
We can also skip the deployment of the example war's IMO, as those are not to be dependent on (i.e. only take up diskspace at maven central). That will trim down the release process considerably. Martijn On Mon, Aug 3, 2015 at 11:34 AM, Martin Grigorov <[email protected]> wrote: > Hi, > > AFAIR several people said that we don't want to make WicketStuff a > graveyard of such code thus I put it in a separate project. > The code is deprecated because it won't be maintained too. > It is available just to make migration to Wicket 7 easier. > Adding more modules to WicketStuff makes its release a real pain. It takes > ~6 hours to release it, most of the time is spent at "deploy" and "javadoc" > phases. > I'd like to remove some old and non-maintained modules from WicketStuff for > 8.x branch. > > Martin Grigorov > Freelancer. Available for hire! > Wicket Training and Consulting > https://twitter.com/mtgrigorov > > On Mon, Aug 3, 2015 at 12:17 PM, Martijn Dashorst < > [email protected]> wrote: > >> The Wicket 15 Tree is now a separate project under the wickestuff >> organization. Is it more prudent to move it into wicketstuff core >> proper? That way, it will be released as a normal project under the >> wicketstuff umbrella, and we have to track one project less. >> >> It also removes one version property in our poms as well (we can just >> use the wicketstuff.version property) >> >> Martijn >> >> -- >> Become a Wicket expert, learn from the best: http://wicketinaction.com >> -- Become a Wicket expert, learn from the best: http://wicketinaction.com
