On Wed, Mar 4, 2020 at 9:50 AM Bob Harner wrote:
> Maybe call it tapestry-components instead of tapestry-corelib, to be
> clearer?
>
Good point. I just thought of corelib since it's the package name. Maybe
tapestry-pages, to be clearer that everything concerning pages and
components are there? t
Hi Thiago!
On Tue, Mar 3, 2020 at 6:37 PM Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Hello!
>
> On Sat, Feb 29, 2020 at 6:31 AM Ilya Obshadko wrote:
>
> > My application still runs on 5.4-beta-6 due to various breaking component
> > changes introduced in later versions.
>
>
> T
Maybe call it tapestry-components instead of tapestry-corelib, to be
clearer?
On Tue, Mar 3, 2020, 11:37 AM Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Hello!
>
> On Sat, Feb 29, 2020 at 6:31 AM Ilya Obshadko wrote:
>
> > My application still runs on 5.4-beta-6 due to various br
Hello!
On Sat, Feb 29, 2020 at 6:31 AM Ilya Obshadko wrote:
> My application still runs on 5.4-beta-6 due to various breaking component
> changes introduced in later versions.
The ones in the other thread? If not, please post them here so we can
discuss them.
> I'm quite happy with it, but I
My application still runs on 5.4-beta-6 due to various breaking component
changes introduced in later versions. I'm quite happy with it, but I'm
getting concerned about outdated upstream dependencies (like Hibernate).
So I did the following:
- upgraded everything to 5.4.5, adding tapestry-core