TeamCity is still unable to connect to the SVN server, so there are no
artifacts for 1.4.7-SNAPSHOT. You need to build the artifacts for yourself..
Regards,
Peter
2010-04-18 20:39 keltezéssel, Nikita Tovstoles írta:
> Could someone pls point me to 1.4.7-SNAPSHOT maven repo location? It's not
> h
Could someone pls point me to 1.4.7-SNAPSHOT maven repo location? It's not here:
http://wicketstuff.org/maven/repository/org/wicketstuff/wicketstuff-core/
thanks
-nikita
On Wed, Mar 24, 2010 at 2:26 PM, nino martinez wael
wrote:
> artifacts should find their way into the repo once team city buil
is that when running a test or?
2010/4/2 新希望软件 -- 俞宏伟 :
> i found thant push component has some problem. after update push compenet to
> 1.4.7-snapshot, the application throws some error message:
>
> 04-02 09:34:55.546[ RequestCycle.java:1521:ERROR] There is no
> application attached to curr
i found thant push component has some problem. after update push compenet to
1.4.7-snapshot, the application throws some error message:
04-02 09:34:55.546[ RequestCycle.java:1521:ERROR] There is no
application attached to current thread http-8081-4
org.apache.wicket.WicketRuntimeException: T
Well, one could see that in version x.x.x of wicketstuff core project
x was excluded.. It was just a proposition. As with everything else it
has pro's and con's.
2010/4/1 Jeremy Thomerson :
> there's already an attic - why create a new one? it will just generate more
> emails to the list whining
there's already an attic - why create a new one? it will just generate more
emails to the list whining about "i can't find such and such" - by those who
can't use the search function well. there's nothing special about an
ex-core project that means it needs its own attic
--
Jeremy Thomerson
http
I guess we could start a branch, called wicketstuff-core-attic. Then
upgrade them to latest wicket version and see if they work and if not,
then remove them. Unless someone wants to fix the errors.
2010/3/28 Major Péter :
> JavaEE-Inject is tested, and OK.
>
> It looks like there are projects, whi
JavaEE-Inject is tested, and OK.
It looks like there are projects, which are depending to a specific
wicket version (1.4-rc*, 1.4.5):
* multi-text-input-parent
* flot-parent/flot
* flot-parent/flot-examples
* wicket-html5-parent
* ddcalendar-parent/ddcalendar
* ddcalendar-parent/ddcalendar-example
Hi Boris,
thank you for doing the job. I have tested jWicket again and everything looks
fine.
Stefan
-Ursprüngliche Nachricht-
Von: Boris Goldowsky [mailto:bgoldow...@cast.org]
Gesendet: Mittwoch, 24. März 2010 22:14
An: users@wicket.apache.org
Betreff: Wicketstuff updated!
As
artifacts should find their way into the repo once team city builds..
2010/3/24 Boris Goldowsky :
> As discussed, and not hearing any objections, I've updated the
> wicketstuff-core project to depend on Wicket 1.4.7. wicketstuff-core's
> version number is now 1.4.7-SNAPSHOT, and the idea is that
As discussed, and not hearing any objections, I've updated the
wicketstuff-core project to depend on Wicket 1.4.7. wicketstuff-core's
version number is now 1.4.7-SNAPSHOT, and the idea is that people can
test it, and barring any major problems it can be released as a stable
version 1.4.7 .
N
11 matches
Mail list logo
