Maarten,
> AFAIK wicketstuff-core trunk is compatible with wicket 1.4.0
Yes, I know. But my client is not really happy about using trunk/snapshots
in a production system. And frankly, neither am I. I love snapshot
releases, but if I can prevent the extra steps needed to use them in
production I would.
> Side note: I don't see the version of wicket-stuff has to match exactly
> with version of wicket ?
> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
> until wicket 1.4.1 is out ?
I agree. Its just that right now there is no release at all.
As soon as there are more releases of the wicketstuff-core projects and/or
wicket, it makes sense to start a compatibility matrix.
BTW, I don't really care if wicketstuff-core is completely 100% stable, it
will never be. Promoting every first snapshot of the month to a release is
good enough for me.
Regards,
Erik.
On Wed, 12 Aug 2009 10:24:07 +0200, Maarten Bosteels
<[email protected]> wrote:
> Hello,
>
> On Wed, Aug 12, 2009 at 10:16 AM, Erik van Oosten
> <[email protected]>wrote:
>
>>
>> Hello,
>>
>> Now that Wicket 1.4.0 is out, I wonder which wicketstuff core version is
>> compatible. There is no 1.4.0 version of wicketstuff core (yet?). Should
>> I
>> use 1.4-rc8-SNAPSHOT?
>
>
> AFAIK wicketstuff-core trunk is compatible with wicket 1.4.0
>
> Side note: I don't see the version of wicket-stuff has to match exactly
> with version of wicket ?
> Suppose someone releases wicketstuff-core-1.4.0 today, and tomorrow some
> bugs are fixed in wicketstuff-core, then we can't release these bug-fixes
> until wicket 1.4.1 is out ?
>
> IMO, wicket is just a dependency of wicketstuff-code (as defoined in the
> pom) and both projects should use their own unrelated version numbers.
>
> wdyt ?
>
> Maarten
>
>
>>
>>
>> I guess http://sourceforge.net/projects/wicket-stuff/files/ is no longer
>> in
>> use.
>>
>> Regards,
>> Erik.
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
