Unfortunately, yui is not updated with the same care as the core.

I hope to get around to yui soon to lend a hand to all those who have
contributed.


Cheers,
David



> -----Original Message-----
> From: Gwyn Evans [mailto:[EMAIL PROTECTED]
> Sent: 24 September 2007 19:03
> To: [email protected]
> Subject: Re: yui examples
>
>
> On Monday, September 24, 2007, 10:51:30 AM, Mattijs
> <[EMAIL PROTECTED]> wrote:
>
> > i just checked out  wicket-contrib-yui and wicket-contrib-yui-examples
> > to do some testing.
> > When i ran maven on it, the projects wouldn't build because of some
> > wrong dependencies in the pom.xml.
> > In a lot of places references are made to wicket 1.3.0-SNAPSHOT. But
> > this doesn't exist in the maven repository.
>
> Looks to be there[1] to me, or are you meaning the main IBiblio repo,
> in which case, no, it's not there as it's a snapshot and we only
> publish full releases there. It's available at the WicketStuff repo,
> as documented at the bottom of the page here[2], though.
>
> You need to be aware that code in trunk will typically have SNAPSHOT
> dependencies, which only get fixed to released dependencies at a
> release point, so may well required you to do additional hunting
> around in order to set things up for trunk working
>
> > Can anyone tell me if the yui examples are updated frequently or still
> > running on an old version of wicket-contrib-yui. When i checked it out,
> > the yui examples project wouldn't build either.
>
> No idea, I'm afraid
>
> > PS: is this the right mailing list to ask these questions?
>
> There's an overlap, but [EMAIL PROTECTED]'s probably the better one.
>
> /Gwyn
>
> [1]
http://wicketstuff.org/maven/repository/org/apache/wicket/wicket/1.3.0-SNAPS
HOT/
[2] http://wicket.apache.org/getting-wicket.html


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to