mv wicket15-tree -> wicketstuff core?

[Martijn Dashorst <ma...@gmail.com>]

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

Re: mv wicket15-tree -> wicketstuff core?

[Martin Grigorov <mg...@apache.org>]

+1 !

But before making any changes we should check Joachim's work on simplifying
the folder tree for WicketStuff projects!

Martin Grigorov
Freelancer. Available for hire!
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Mon, Aug 3, 2015 at 12:43 PM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:

> 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 <mg...@apache.org>
> 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 <
> > martijn.dashorst@gmail.com> 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
>

Re: mv wicket15-tree -> wicketstuff core?

[Martin Grigorov <mg...@apache.org>]

According to
http://central.sonatype.org/pages/requirements.html#supply-javadoc-and-sources
we need to supply -javadoc and -sources to be able to deploy to
Central/Sonatype.

So I'll just disable javadoc and deployment for "xyz-examples" modules.

Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov

On Mon, Aug 3, 2015 at 11:43 AM, Martijn Dashorst <
martijn.dashorst@gmail.com> wrote:

> 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 <mg...@apache.org>
> 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 <
> > martijn.dashorst@gmail.com> 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
>

Re: mv wicket15-tree -> wicketstuff core?

[Martijn Dashorst <ma...@gmail.com>]

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 <mg...@apache.org> 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 <
> martijn.dashorst@gmail.com> 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

Re: mv wicket15-tree -> wicketstuff core?

[Martijn Dashorst <ma...@gmail.com>]

On Mon, Aug 3, 2015 at 11:34 AM, Martin Grigorov <mg...@apache.org> wrote:
> 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.

Well, the code is done, complete, finished. I don't see a future where
the tree/treetable will become a javascript client side component,
however the code itself has value for existing projects that already
use it. The component itself doesn't have many bugs if any, so I don't
see a problem with it staying in wicketstuff. Swarm/Wasp have the same
status.

Wicket proper has some unmaintained modules and/or components as well:
Wicket Velocity comes to mind,  the Rating component, YUI DatePicker?

> The code is deprecated because it won't be maintained too.

I'm actually thinking about removing the deprecation warnings. It is
my intention to keep the code compiling and working, but not improving
it (we have better components for that).

> It is available just to make migration to Wicket 7 easier.

And to not throw away valuable code for our users. At least at my day
job we use these components in 2 places, where there's no business
case to rewrite those pages at this moment. Given the nature of these
tables and custom column implementations, the investment would be
prohibitive. Of course we can move the code internally, but I guess we
are not the only company using these components.

Martijn

Re: mv wicket15-tree -> wicketstuff core?

[Martin Grigorov <mg...@apache.org>]

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 <
martijn.dashorst@gmail.com> 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
>