Debugging options
I have some code that's not working like it should, and like it does in other projects. I made a quickstart, but it works there. What other debugging options do I have besides plain Java debugging (short of sharing my repo with a maintainer / expert, which I'm 100% open to)? I have a DropDownChoice with a PropertyModel. The dropdown is set up initially just fine. But any changes to the selection result in the property object being null and I can't for the life of me figure out why. I've included the wicket sources in my debugger and have poked around in there, but can't see anything obvious to my untrained eye. I use this same pattern in lots of other files in different projects, but for some reason it's just not working here, so I'm obviously missing something, but can't figure out what. Wicket 7.11. -- Sent from: http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
FINAL REMINDER: Apache EU Roadshow 2018 in Berlin next week!
Hello Apache Supporters and Enthusiasts This is a final reminder that our Apache EU Roadshow will be held in Berlin next week on 13th and 14th June 2018. We will have 28 different sessions running over 2 days that cover some great topics. So if you are interested in Microservices, Internet of Things (IoT), Cloud, Apache Tomcat or Apache Http Server then we have something for you. https://foss-backstage.de/sessions/apache-roadshow We will be co-located with FOSS Backstage, so if you are interested in topics such as incubator, the Apache Way, open source governance, legal, trademarks or simply open source communities then there will be something there for you too. You can attend any of talks, presentations and workshops from the Apache EU Roadshow or FOSS Backstage. You can find details of the combined Apache EU Roadshow and FOSS Backstage conference schedule below: https://foss-backstage.de/schedule?day=2018-06-13 Ticket prices go up on 8th June 2018 and we have a last minute discount code that anyone can use before the deadline: 15% discount code: ASF15_discount valid until June 7, 23:55 CET You can register at the following link: https://foss-backstage.de/tickets Our Apache booth and lounge will be open from 11th - 14th June for meetups, hacking or to simply relax between sessions. And we will be posting regular updates on social media throughout next week so please follow us on Twitter @ApacheCon Thank you for your continued support and we look forward to seeing you in Berlin! Thanks Sharan Foga, VP Apache Community Development http://apachecon.com/ PLEASE NOTE: You are receiving this message because you are subscribed to a user@ or dev@ list of one or more Apache Software Foundation projects. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: FormTester, FinishButton and Wicket 8.0
I'll take a look. Have fun Sven Am 06.06.2018 um 17:16 schrieb Francesco Chicchiriccò: Hi all, I am migrating the Syncope master branch from Wicket 7 to 8. It seems all is working fine when dealing via browser, but the integration tests are mostly failing. As Syncope heavily uses Wizards, the reason seems that FormTester fails somehow to submit the Finish button (though no error is reported); the failing statement is (for example): https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64 but I can see that no submit was effectively performed by https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62 hence no feedback message was generated. Strange is that I am also sure that the Next button is effectively submitted by https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56 Is there anything relevant that was changed in WicketTester with Wicket 8? The code above works fine with Wicket 7, and performing the same actions via browser works fine too. TIA. Regards. - 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
FormTester, FinishButton and Wicket 8.0
Hi all, I am migrating the Syncope master branch from Wicket 7 to 8. It seems all is working fine when dealing via browser, but the integration tests are mostly failing. As Syncope heavily uses Wizards, the reason seems that FormTester fails somehow to submit the Finish button (though no error is reported); the failing statement is (for example): https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L64 but I can see that no submit was effectively performed by https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L62 hence no feedback message was generated. Strange is that I am also sure that the Next button is effectively submitted by https://github.com/apache/syncope/blob/master/fit/core-reference/src/test/java/org/apache/syncope/fit/console/ParametersITCase.java#L56 Is there anything relevant that was changed in WicketTester with Wicket 8? The code above works fine with Wicket 7, and performing the same actions via browser works fine too. TIA. Regards. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: Release WiQuery for Wicket 8
I've fixed the problem. The setup currently used is discouraged and broken in m2e, but I don't feel like restructuring the whole thing to get rid of this test-jar. Emond On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > The culprit is: > > https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868 > b940d9be3a > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl wrote: > > `mvn clean install` fails for me because no test-jar is built for the core > > module: > > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ > > > >> 0.353 s] > >> > >> [INFO] WiQuery Core Project ... SUCCESS [ > >> > >> 2.673 s] > >> > >> [INFO] WiQuery jQuery UI Project .. FAILURE [ > >> > >> 0.023 s] > >> > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED > >> [INFO] > >> > >> [INFO] BUILD FAILURE > >> [INFO] > >> > >> [INFO] Total time: 3.720 s > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > >> [INFO] > >> > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not > >> resolve dependencies for project org.wicketstuff.wiquery: > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > >> https://oss.sonatype.org/content/repositories/snapshots was cached in > >> the local repository, resolution will not be reattempted until the update > >> interval of sonatype-nexus-snapshots has elapsed or updates are forced -> > >> [Help 1] > >> [ERROR] > > > > Did you change something about test-jar configuration? I do not see > > `test-jar` generation enabled in the POM file. > > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > > > > emond.papega...@topicus.nl> wrote: > >> Hi Thomas, > >> > >> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. > >> I did > >> not do a release, as I cannot push to central. If you want to run your > >> tests > >> on some CI server, you probably have to push the artifacts to a local > >> repo > >> also. > >> > >> Best regards, > >> Emond > >> > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > >> > Hi Emond, > >> > > >> > How can I test this? Did you do a milestone release or do I have to > >> > >> build > >> > >> > from source and push to my local artifact repo? > >> > > >> > Best, > >> > > >> > Thomas > >> > > >> > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > >> > >> emond.papega...@topicus.nl> > >> > >> > wrote: > >> > > I've just pushed a massive upgrade of all components. Removed all > >> > > deprecated > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > >> > > refactoring. > >> > > Please test the changes in your project. The tests pass and the demo > >> > >> runs > >> > >> > > fine, but my project only uses a limited set of the UI components. > >> > > > >> > > Best regards, > >> > > Emond > >> > > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > >> > > > I'm planning to upgrade jQuery UI to the latest version next week. > >> > >> We > >> > >> > > > are > >> > > > currently migrating all our applications to wicket 8 and also > >> > >> depend on > >> > >> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly > >> > >> dead. > >> > >> > > > The rest of the world probably switched to yet another fancy > >> > >> JavaScript > >> > >> > > ui > >> > > > >> > > > library. At least the will make it easy to stay up to date with the > >> > > > >> > > latest > >> > > > >> > > > version :) > >> > > > > >> > > > I can't push a release to central, but perhaps Martin can do that > >> > >> when > >> > >> > > I'm > >> > > > >> > > > done? For now you can use a snapshot build. It works, but the UI > >> > > > API > >> > > > >> > > might > >> > > > >> > > > change a bit before the 8.0 release. > >> > > > > >> > > > Best regards, > >> > > > Emond Papegaaij > >> > > > > >> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : > >> > > > > Hi Ernesto, > >> > > > > > >> > > > > I'm not sure how many people are still using it. But as I said, > >> > > > > my > >> > > > >> > > project > >> > > > >> > > > > heavily depends on it. > >> > > > > > >> > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( > >> > > > > https://github.com/wicketstuff/wiquery) and a simple release of > >> > >> 8.0.0 > >> > >> > > > > would > >> > > > > be enough for me. > >> > > > > > >> > > > > Best, > >> > > > > > >> > > > > Thomas > >> > > > > > >> > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < > >> > > > > > >> > > > > reier...@gmail.com> wrote: > >> > > > > > Hi, > >> > > > > > > >> > > > > > I do not know who is actually using
Re: Release WiQuery for Wicket 8
You are right, I still had the artifacts in my local repo. The old configuration did not build anymore due to changes in the jar-plugin. I'll look into it. Emond On woensdag 6 juni 2018 11:57:43 CEST Thomas Heigl wrote: > The culprit is: > > https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868 > b940d9be3a > On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl wrote: > > `mvn clean install` fails for me because no test-jar is built for the core > > module: > > > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ > > > >> 0.353 s] > >> > >> [INFO] WiQuery Core Project ... SUCCESS [ > >> > >> 2.673 s] > >> > >> [INFO] WiQuery jQuery UI Project .. FAILURE [ > >> > >> 0.023 s] > >> > >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED > >> [INFO] > >> > >> [INFO] BUILD FAILURE > >> [INFO] > >> > >> [INFO] Total time: 3.720 s > >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 > >> [INFO] > >> > >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not > >> resolve dependencies for project org.wicketstuff.wiquery: > >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > >> https://oss.sonatype.org/content/repositories/snapshots was cached in > >> the local repository, resolution will not be reattempted until the update > >> interval of sonatype-nexus-snapshots has elapsed or updates are forced -> > >> [Help 1] > >> [ERROR] > > > > Did you change something about test-jar configuration? I do not see > > `test-jar` generation enabled in the POM file. > > > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > > > > emond.papega...@topicus.nl> wrote: > >> Hi Thomas, > >> > >> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. > >> I did > >> not do a release, as I cannot push to central. If you want to run your > >> tests > >> on some CI server, you probably have to push the artifacts to a local > >> repo > >> also. > >> > >> Best regards, > >> Emond > >> > >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > >> > Hi Emond, > >> > > >> > How can I test this? Did you do a milestone release or do I have to > >> > >> build > >> > >> > from source and push to my local artifact repo? > >> > > >> > Best, > >> > > >> > Thomas > >> > > >> > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > >> > >> emond.papega...@topicus.nl> > >> > >> > wrote: > >> > > I've just pushed a massive upgrade of all components. Removed all > >> > > deprecated > >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > >> > > refactoring. > >> > > Please test the changes in your project. The tests pass and the demo > >> > >> runs > >> > >> > > fine, but my project only uses a limited set of the UI components. > >> > > > >> > > Best regards, > >> > > Emond > >> > > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > >> > > > I'm planning to upgrade jQuery UI to the latest version next week. > >> > >> We > >> > >> > > > are > >> > > > currently migrating all our applications to wicket 8 and also > >> > >> depend on > >> > >> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly > >> > >> dead. > >> > >> > > > The rest of the world probably switched to yet another fancy > >> > >> JavaScript > >> > >> > > ui > >> > > > >> > > > library. At least the will make it easy to stay up to date with the > >> > > > >> > > latest > >> > > > >> > > > version :) > >> > > > > >> > > > I can't push a release to central, but perhaps Martin can do that > >> > >> when > >> > >> > > I'm > >> > > > >> > > > done? For now you can use a snapshot build. It works, but the UI > >> > > > API > >> > > > >> > > might > >> > > > >> > > > change a bit before the 8.0 release. > >> > > > > >> > > > Best regards, > >> > > > Emond Papegaaij > >> > > > > >> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : > >> > > > > Hi Ernesto, > >> > > > > > >> > > > > I'm not sure how many people are still using it. But as I said, > >> > > > > my > >> > > > >> > > project > >> > > > >> > > > > heavily depends on it. > >> > > > > > >> > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( > >> > > > > https://github.com/wicketstuff/wiquery) and a simple release of > >> > >> 8.0.0 > >> > >> > > > > would > >> > > > > be enough for me. > >> > > > > > >> > > > > Best, > >> > > > > > >> > > > > Thomas > >> > > > > > >> > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < > >> > > > > > >> > > > > reier...@gmail.com> wrote: > >> > > > > > Hi, > >> > > > > > > >> > > > > > I do not know who is actually using this
Re: Release WiQuery for Wicket 8
The culprit is: https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868b940d9be3a On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl wrote: > `mvn clean install` fails for me because no test-jar is built for the core > module: > > [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ >> 0.353 s] >> [INFO] WiQuery Core Project ... SUCCESS [ >> 2.673 s] >> [INFO] WiQuery jQuery UI Project .. FAILURE [ >> 0.023 s] >> [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED >> [INFO] >> >> [INFO] BUILD FAILURE >> [INFO] >> >> [INFO] Total time: 3.720 s >> [INFO] Finished at: 2018-06-06T11:48:16+02:00 >> [INFO] >> >> [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not >> resolve dependencies for project org.wicketstuff.wiquery: >> wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find >> org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in >> https://oss.sonatype.org/content/repositories/snapshots was cached in >> the local repository, resolution will not be reattempted until the update >> interval of sonatype-nexus-snapshots has elapsed or updates are forced -> >> [Help 1] >> [ERROR] > > > Did you change something about test-jar configuration? I do not see > `test-jar` generation enabled in the POM file. > > On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij < > emond.papega...@topicus.nl> wrote: > >> Hi Thomas, >> >> The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. >> I did >> not do a release, as I cannot push to central. If you want to run your >> tests >> on some CI server, you probably have to push the artifacts to a local >> repo >> also. >> >> Best regards, >> Emond >> >> On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: >> > Hi Emond, >> > >> > How can I test this? Did you do a milestone release or do I have to >> build >> > from source and push to my local artifact repo? >> > >> > Best, >> > >> > Thomas >> > >> > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < >> emond.papega...@topicus.nl> >> > wrote: >> > > I've just pushed a massive upgrade of all components. Removed all >> > > deprecated >> > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and >> > > refactoring. >> > > Please test the changes in your project. The tests pass and the demo >> runs >> > > fine, but my project only uses a limited set of the UI components. >> > > >> > > Best regards, >> > > Emond >> > > >> > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: >> > > > I'm planning to upgrade jQuery UI to the latest version next week. >> We >> > > > are >> > > > currently migrating all our applications to wicket 8 and also >> depend on >> > > > wiquery quite a lot. It does however seem that jQuery UI is mostly >> dead. >> > > > The rest of the world probably switched to yet another fancy >> JavaScript >> > > >> > > ui >> > > >> > > > library. At least the will make it easy to stay up to date with the >> > > >> > > latest >> > > >> > > > version :) >> > > > >> > > > I can't push a release to central, but perhaps Martin can do that >> when >> > > >> > > I'm >> > > >> > > > done? For now you can use a snapshot build. It works, but the UI API >> > > >> > > might >> > > >> > > > change a bit before the 8.0 release. >> > > > >> > > > Best regards, >> > > > Emond Papegaaij >> > > > >> > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : >> > > > > Hi Ernesto, >> > > > > >> > > > > I'm not sure how many people are still using it. But as I said, my >> > > >> > > project >> > > >> > > > > heavily depends on it. >> > > > > >> > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( >> > > > > https://github.com/wicketstuff/wiquery) and a simple release of >> 8.0.0 >> > > > > would >> > > > > be enough for me. >> > > > > >> > > > > Best, >> > > > > >> > > > > Thomas >> > > > > >> > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < >> > > > > >> > > > > reier...@gmail.com> wrote: >> > > > > > Hi, >> > > > > > >> > > > > > I do not know who is actually using this project. I use to >> > > >> > > contribute to >> > > >> > > > > it >> > > > > >> > > > > > a few years ago. I haven't used it for ages.. >> > > > > > >> > > > > > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl < >> tho...@umschalt.com> >> > > > > >> > > > > wrote: >> > > > > > > Hi, >> > > > > > > >> > > > > > > Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, >> could >> > > > > > >> > > > > > somebody >> > > > > > >> > > > > > > please cut a release of WiQuery compatible with the new >> version? >> > > > > > > >> > > > > > > Our application still heavily relies on WiQuery and we can't >> move >> > > >> > > to >> > > >> > > > > > Wicket >> > > > > > >> > > >
Re: Release WiQuery for Wicket 8
`mvn clean install` fails for me because no test-jar is built for the core module: [INFO] WiQuery Parent 8.0-SNAPSHOT SUCCESS [ > 0.353 s] > [INFO] WiQuery Core Project ... SUCCESS [ > 2.673 s] > [INFO] WiQuery jQuery UI Project .. FAILURE [ > 0.023 s] > [INFO] WiQuery Demo Project 8.0-SNAPSHOT .. SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 3.720 s > [INFO] Finished at: 2018-06-06T11:48:16+02:00 > [INFO] > > [ERROR] Failed to execute goal on project wiquery-jquery-ui: Could not > resolve dependencies for project > org.wicketstuff.wiquery:wiquery-jquery-ui:jar:8.0-SNAPSHOT: Failure to find > org.wicketstuff.wiquery:wiquery-core:jar:tests:8.0-SNAPSHOT in > https://oss.sonatype.org/content/repositories/snapshots was cached in the > local repository, resolution will not be reattempted until the update > interval of sonatype-nexus-snapshots has elapsed or updates are forced -> > [Help 1] > [ERROR] Did you change something about test-jar configuration? I do not see `test-jar` generation enabled in the POM file. On Wed, Jun 6, 2018 at 11:43 AM, Emond Papegaaij wrote: > Hi Thomas, > > The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. I > did > not do a release, as I cannot push to central. If you want to run your > tests > on some CI server, you probably have to push the artifacts to a local repo > also. > > Best regards, > Emond > > On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > > Hi Emond, > > > > How can I test this? Did you do a milestone release or do I have to build > > from source and push to my local artifact repo? > > > > Best, > > > > Thomas > > > > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij < > emond.papega...@topicus.nl> > > wrote: > > > I've just pushed a massive upgrade of all components. Removed all > > > deprecated > > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > > > refactoring. > > > Please test the changes in your project. The tests pass and the demo > runs > > > fine, but my project only uses a limited set of the UI components. > > > > > > Best regards, > > > Emond > > > > > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > > > > I'm planning to upgrade jQuery UI to the latest version next week. We > > > > are > > > > currently migrating all our applications to wicket 8 and also depend > on > > > > wiquery quite a lot. It does however seem that jQuery UI is mostly > dead. > > > > The rest of the world probably switched to yet another fancy > JavaScript > > > > > > ui > > > > > > > library. At least the will make it easy to stay up to date with the > > > > > > latest > > > > > > > version :) > > > > > > > > I can't push a release to central, but perhaps Martin can do that > when > > > > > > I'm > > > > > > > done? For now you can use a snapshot build. It works, but the UI API > > > > > > might > > > > > > > change a bit before the 8.0 release. > > > > > > > > Best regards, > > > > Emond Papegaaij > > > > > > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : > > > > > Hi Ernesto, > > > > > > > > > > I'm not sure how many people are still using it. But as I said, my > > > > > > project > > > > > > > > heavily depends on it. > > > > > > > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( > > > > > https://github.com/wicketstuff/wiquery) and a simple release of > 8.0.0 > > > > > would > > > > > be enough for me. > > > > > > > > > > Best, > > > > > > > > > > Thomas > > > > > > > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < > > > > > > > > > > reier...@gmail.com> wrote: > > > > > > Hi, > > > > > > > > > > > > I do not know who is actually using this project. I use to > > > > > > contribute to > > > > > > > > it > > > > > > > > > > > a few years ago. I haven't used it for ages.. > > > > > > > > > > > > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl < > tho...@umschalt.com> > > > > > > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, > could > > > > > > > > > > > > somebody > > > > > > > > > > > > > please cut a release of WiQuery compatible with the new > version? > > > > > > > > > > > > > > Our application still heavily relies on WiQuery and we can't > move > > > > > > to > > > > > > > > > Wicket > > > > > > > > > > > > > 8 without it. > > > > > > > > > > > > > > Best, > > > > > > > > > > > > > > Thomas > > > > > > > > > > > > -- > > > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > > For additional commands, e-mail:
Re: Release WiQuery for Wicket 8
Hi Thomas, The easiest way is to just run 'mvn install' and depend on 8.0-SNAPSHOT. I did not do a release, as I cannot push to central. If you want to run your tests on some CI server, you probably have to push the artifacts to a local repo also. Best regards, Emond On woensdag 6 juni 2018 11:36:54 CEST Thomas Heigl wrote: > Hi Emond, > > How can I test this? Did you do a milestone release or do I have to build > from source and push to my local artifact repo? > > Best, > > Thomas > > On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij > wrote: > > I've just pushed a massive upgrade of all components. Removed all > > deprecated > > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > > refactoring. > > Please test the changes in your project. The tests pass and the demo runs > > fine, but my project only uses a limited set of the UI components. > > > > Best regards, > > Emond > > > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > > > I'm planning to upgrade jQuery UI to the latest version next week. We > > > are > > > currently migrating all our applications to wicket 8 and also depend on > > > wiquery quite a lot. It does however seem that jQuery UI is mostly dead. > > > The rest of the world probably switched to yet another fancy JavaScript > > > > ui > > > > > library. At least the will make it easy to stay up to date with the > > > > latest > > > > > version :) > > > > > > I can't push a release to central, but perhaps Martin can do that when > > > > I'm > > > > > done? For now you can use a snapshot build. It works, but the UI API > > > > might > > > > > change a bit before the 8.0 release. > > > > > > Best regards, > > > Emond Papegaaij > > > > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : > > > > Hi Ernesto, > > > > > > > > I'm not sure how many people are still using it. But as I said, my > > > > project > > > > > > heavily depends on it. > > > > > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( > > > > https://github.com/wicketstuff/wiquery) and a simple release of 8.0.0 > > > > would > > > > be enough for me. > > > > > > > > Best, > > > > > > > > Thomas > > > > > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < > > > > > > > > reier...@gmail.com> wrote: > > > > > Hi, > > > > > > > > > > I do not know who is actually using this project. I use to > > > > contribute to > > > > > > it > > > > > > > > > a few years ago. I haven't used it for ages.. > > > > > > > > > > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl > > > > > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could > > > > > > > > > > somebody > > > > > > > > > > > please cut a release of WiQuery compatible with the new version? > > > > > > > > > > > > Our application still heavily relies on WiQuery and we can't move > > > > to > > > > > > > Wicket > > > > > > > > > > > 8 without it. > > > > > > > > > > > > Best, > > > > > > > > > > > > Thomas > > > > > > > > > > -- > > > > > Regards - Ernesto Reinaldo Barreiro > > > > - > > 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: Release WiQuery for Wicket 8
Hi Emond, How can I test this? Did you do a milestone release or do I have to build from source and push to my local artifact repo? Best, Thomas On Tue, Jun 5, 2018 at 3:01 PM, Emond Papegaaij wrote: > I've just pushed a massive upgrade of all components. Removed all > deprecated > parts, upgraded jQuery UI to 1.12.1 and did some more cleanup and > refactoring. > Please test the changes in your project. The tests pass and the demo runs > fine, but my project only uses a limited set of the UI components. > > Best regards, > Emond > > On zaterdag 2 juni 2018 10:31:31 CEST you wrote: > > I'm planning to upgrade jQuery UI to the latest version next week. We are > > currently migrating all our applications to wicket 8 and also depend on > > wiquery quite a lot. It does however seem that jQuery UI is mostly dead. > > The rest of the world probably switched to yet another fancy JavaScript > ui > > library. At least the will make it easy to stay up to date with the > latest > > version :) > > > > I can't push a release to central, but perhaps Martin can do that when > I'm > > done? For now you can use a snapshot build. It works, but the UI API > might > > change a bit before the 8.0 release. > > > > Best regards, > > Emond Papegaaij > > > > Op vr 1 jun. 2018 17:36 schreef Thomas Heigl : > > > Hi Ernesto, > > > > > > I'm not sure how many people are still using it. But as I said, my > project > > > heavily depends on it. > > > > > > @papegaaij has resolved all the compile errors against 8.0.0-M9 ( > > > https://github.com/wicketstuff/wiquery) and a simple release of 8.0.0 > > > would > > > be enough for me. > > > > > > Best, > > > > > > Thomas > > > > > > On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro < > > > > > > reier...@gmail.com> wrote: > > > > Hi, > > > > > > > > I do not know who is actually using this project. I use to > contribute to > > > > > > it > > > > > > > a few years ago. I haven't used it for ages.. > > > > > > > > On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl > > > > > > wrote: > > > > > Hi, > > > > > > > > > > Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could > > > > > > > > somebody > > > > > > > > > please cut a release of WiQuery compatible with the new version? > > > > > > > > > > Our application still heavily relies on WiQuery and we can't move > to > > > > > > > > Wicket > > > > > > > > > 8 without it. > > > > > > > > > > Best, > > > > > > > > > > Thomas > > > > > > > > -- > > > > Regards - Ernesto Reinaldo Barreiro > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
