Re: Wicketstuff updated!
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 nino.martinez.w...@gmail.com wrote: artifacts should find their way into the repo once team city builds.. 2010/3/24 Boris Goldowsky bgoldow...@cast.org: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
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 here: http://wicketstuff.org/maven/repository/org/wicketstuff/wicketstuff-core/ thanks -nikita On Wed, Mar 24, 2010 at 2:26 PM, nino martinez wael nino.martinez.w...@gmail.com wrote: artifacts should find their way into the repo once team city builds.. 2010/3/24 Boris Goldowsky bgoldow...@cast.org: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
is that when running a test or? 2010/4/2 新希望软件 -- 俞宏伟 nhsoft@gmail.com: 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: There is no application attached to current thread http-8081-4 at org.apache.wicket.Application.get(Application.java:179) at org.apache.wicket.Component.getMarkupId(Component.java:1542) at org.apache.wicket.Component.getMarkupId(Component.java:1578) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getPreconditionScript(AbstractAjaxTimerBehavior.java:140) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.generateCallbackScript(AbstractDefaultAjaxBehavior.java:170) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getCallbackScript(AbstractAjaxTimerBehavior.java:127) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getJsTimeoutCall(AbstractAjaxTimerBehavior.java:120) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.respond(AbstractAjaxTimerBehavior.java:163) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:286) at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119) at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428) at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:312) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:359) at org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) at org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:174) at org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) my wicket version is 1.4.7. On Thu, Apr 1, 2010 at 20:50, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 jer...@wickettraining.com: 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://www.wickettraining.com On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 majorpe...@sch.bme.hu: JavaEE-Inject is tested, and OK.
Re: Wicketstuff updated!
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 jer...@wickettraining.com: 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://www.wickettraining.com On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 majorpe...@sch.bme.hu: 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-examples What's going to happen with them? Regards, Peter 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
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: There is no application attached to current thread http-8081-4 at org.apache.wicket.Application.get(Application.java:179) at org.apache.wicket.Component.getMarkupId(Component.java:1542) at org.apache.wicket.Component.getMarkupId(Component.java:1578) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getPreconditionScript(AbstractAjaxTimerBehavior.java:140) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.generateCallbackScript(AbstractDefaultAjaxBehavior.java:170) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getCallbackScript(AbstractAjaxTimerBehavior.java:127) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.getJsTimeoutCall(AbstractAjaxTimerBehavior.java:120) at org.apache.wicket.ajax.AbstractAjaxTimerBehavior.respond(AbstractAjaxTimerBehavior.java:163) at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:286) at org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119) at org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92) at org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250) at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at org.apache.wicket.RequestCycle.steps(RequestCycle.java:1428) at org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:479) at org.apache.wicket.protocol.http.WicketFilter.doFilter(WicketFilter.java:312) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:359) at org.springframework.security.context.HttpSessionContextIntegrationFilter.doFilterHttp(HttpSessionContextIntegrationFilter.java:235) at org.springframework.security.ui.SpringSecurityFilter.doFilter(SpringSecurityFilter.java:53) at org.springframework.security.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:371) at org.springframework.security.util.FilterChainProxy.doFilter(FilterChainProxy.java:174) at org.springframework.security.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:99) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:619) my wicket version is 1.4.7. On Thu, Apr 1, 2010 at 20:50, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 jer...@wickettraining.com: 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://www.wickettraining.com On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 majorpe...@sch.bme.hu: 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): *
Re: Wicketstuff updated!
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 majorpe...@sch.bme.hu: 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-examples What's going to happen with them? Regards, Peter 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
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://www.wickettraining.com On Wed, Mar 31, 2010 at 11:57 AM, nino martinez wael nino.martinez.w...@gmail.com wrote: 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 majorpe...@sch.bme.hu: 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-examples What's going to happen with them? Regards, Peter 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
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-examples What's going to happen with them? Regards, Peter 2010-03-24 22:14 keltezéssel, Boris Goldowsky írta: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
RE: Wicketstuff updated!
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 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Wicketstuff updated!
artifacts should find their way into the repo once team city builds.. 2010/3/24 Boris Goldowsky bgoldow...@cast.org: 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 . Now, before people can easily test this, the artifacts need to get into the wicket snapshots maven repository, right? Can someone with the requisite permissions make this happen? In the meantime of course people are encouraged to download the projects and build and test them locally. In addition to wicket, the following dependencies were also updated to the latest stable version within the same major version of the project. I did not attempt to move Lucene from version 2.4.1 to 3.0.1, for instance, since more significant changes might be required for this (if any subproject is actually using it). Jetty: 6.1.22 Lucene: 2.4.1 slf4j: 1.5.11 JUnit: 4.8.1 I had to make a couple of changes to get everything to build with the new dependencies (commented out wagon-ssh-external extension from inmethod-grid; added new required constructor argument to two instances of SpringComponentInjector). People should test the build and make sure these changes are ok. But at least for me, I can do a mvn install at the top level and it works. Bng - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
