Discussion:
Release WiQuery for Wicket 8
Thomas Heigl
2018-06-01 13:39:03 UTC
Permalink
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
Ernesto Reinaldo Barreiro
2018-06-01 15:05:37 UTC
Permalink
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..
Post by Thomas Heigl
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
Thomas Heigl
2018-06-01 15:35:12 UTC
Permalink
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 <
Post by Ernesto Reinaldo Barreiro
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..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
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
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
Martin Grigorov
2018-06-01 15:44:39 UTC
Permalink
Post by 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.
I'll be able to do it Monday morning.
Post by Thomas Heigl
Best,
Thomas
On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to contribute to
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
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
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
Thomas Heigl
2018-06-01 15:49:48 UTC
Permalink
Great! Thanks Martin!
Post by Ernesto Reinaldo Barreiro
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But as I said, my
project
Post by Thomas Heigl
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.
I'll be able to do it Monday morning.
Post by Thomas Heigl
Best,
Thomas
On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to contribute
to
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
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
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
Emond Papegaaij
2018-06-02 08:31:31 UTC
Permalink
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
Post by 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 <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to contribute to
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
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
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
Emond Papegaaij
2018-06-05 13:01:20 UTC
Permalink
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
Post by Emond Papegaaij
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
Post by 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 <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to contribute to
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
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
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Thomas Heigl
2018-06-06 09:36:54 UTC
Permalink
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
Post by Emond Papegaaij
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
Post by Emond Papegaaij
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
Post by Emond Papegaaij
library. At least the will make it easy to stay up to date with the
latest
Post by Emond Papegaaij
version :)
I can't push a release to central, but perhaps Martin can do that when
I'm
Post by Emond Papegaaij
done? For now you can use a snapshot build. It works, but the UI API
might
Post by Emond Papegaaij
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But as I said, my
project
Post by Emond Papegaaij
Post by Thomas Heigl
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 <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to
contribute to
Post by Emond Papegaaij
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
please cut a release of WiQuery compatible with the new version?
Our application still heavily relies on WiQuery and we can't move
to
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Wicket
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
Emond Papegaaij
2018-06-06 09:43:52 UTC
Permalink
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
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
Post by Emond Papegaaij
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
Post by Emond Papegaaij
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
Post by Emond Papegaaij
library. At least the will make it easy to stay up to date with the
latest
Post by Emond Papegaaij
version :)
I can't push a release to central, but perhaps Martin can do that when
I'm
Post by Emond Papegaaij
done? For now you can use a snapshot build. It works, but the UI API
might
Post by Emond Papegaaij
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But as I said, my
project
Post by Emond Papegaaij
Post by Thomas Heigl
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 <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to
contribute to
Post by Emond Papegaaij
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0, could
somebody
Post by Thomas Heigl
please cut a release of WiQuery compatible with the new version?
Our application still heavily relies on WiQuery and we can't move
to
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Wicket
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Martin Grigorov
2018-06-07 15:10:16 UTC
Permalink
8.0 is on its way to Maven Central!
I did not build the javadoc, but I actually don't know why. But as I don't
care about these javadoc errors, I've disabled lint. You should be able to
build now.
Emond
There are many javadoc related errors in this project. mvn install fails
[WARNING] The requested profile "frontend" could not be activated because
it does not exist.
[WARNING] The requested profile "buildbot" could not be activated because
it does not exist.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.7:jar (attach-javadocs)
on
[ERROR] Exit code: 1 -
/home/martin/git/wiquery/wiquery-core/src/main/java/
org/wicketstuff/wiquery/
[ERROR] public static ResourceReference getJQueryResourceReference()
[ERROR] ^
[ERROR]
/home/martin/git/wiquery/wiquery-core/src/main/java/
org/wicketstuff/wiquery/
[ERROR] public abstract JsScope callback();
[ERROR] ^
[ERROR]
/home/martin/git/wiquery/wiquery-core/src/main/java/
org/wicketstuff/wiquery/
[ERROR] public Event(EventLabel... eventLabels)
[ERROR] ^
[ERROR]
/home/martin/git/wiquery/wiquery-core/src/main/java/
org/wicketstuff/wiquery/
for
label
[ERROR] public DefaultChainableStatement(String label, CharSequence...
args)
....
How did you build it with Java 8 ?
OK. I will make a release!
Hi Emond,
I did some exploratory testing against the current build. I checked
Dialog,
Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem
to be
working at first glance.
All my tests pass as well.
Best,
Thomas
On Wed, Jun 6, 2018 at 1:07 PM, Emond Papegaaij <
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
https://github.com/wicketstuff/wiquery/commit/
0235691174ceeede22b588d2f67868
b940d9be3a
On Wed, Jun 6, 2018 at 11:51 AM, Thomas Heigl <
`mvn clean install` fails for me because no test-jar is built
for
the
core
[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] ------------------------------
------------------------------
------------
Could
not
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 <
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
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 <
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
Post by Emond Papegaaij
I'm planning to upgrade jQuery UI to the latest version
next
week.
We
Post by Emond Papegaaij
are
currently migrating all our applications to wicket 8 and
also
depend on
Post by Emond Papegaaij
wiquery quite a lot. It does however seem that jQuery UI
is
mostly
dead.
Post by Emond Papegaaij
The rest of the world probably switched to yet another
fancy
JavaScript
ui
Post by Emond Papegaaij
library. At least the will make it easy to stay up to
date
with
the
latest
Post by Emond Papegaaij
version :)
I can't push a release to central, but perhaps Martin
can do
that
when
I'm
Post by Emond Papegaaij
done? For now you can use a snapshot build. It works, but
the UI
Post by Emond Papegaaij
API
might
Post by Emond Papegaaij
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
Op vr 1 jun. 2018 17:36 schreef Thomas Heigl <
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But
as I
said,
Post by Emond Papegaaij
Post by Thomas Heigl
my
project
Post by Emond Papegaaij
Post by Thomas Heigl
heavily depends on it.
@papegaaij has resolved all the compile errors against
8.0.0-M9 (
Post by Emond Papegaaij
Post by Thomas Heigl
https://github.com/wicketstuff/wiquery) and a simple
release
of
8.0.0
Post by Emond Papegaaij
Post by Thomas Heigl
would
be enough for me.
Best,
Thomas
On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo
Barreiro
Post by Emond Papegaaij
Post by Thomas Heigl
<
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I
use
to
contribute to
Post by Emond Papegaaij
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl <
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and
WicketStuff
8.0.0,
could
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
somebody
Post by Thomas Heigl
please cut a release of WiQuery compatible with the
new
version?
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Post by Thomas Heigl
Our application still heavily relies on WiQuery
and we
can't
move
to
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Wicket
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
------------------------------
------------------------------
---------
apache.org
------------------------------------------------------------
---------
------------------------------------------------------------
---------
---------------------------------------------------------------------
Emond Papegaaij
2018-06-08 06:41:45 UTC
Permalink
Post by Martin Grigorov
8.0 is on its way to Maven Central!
Thanks for the help with the release Martin, and Thomas thanks for testing!

Emond



---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org
Thomas Heigl
2018-06-07 12:25:40 UTC
Permalink
Hi Emond,

I did some exploratory testing against the current build. I checked Dialog,
Autocomplete, Accordion, Slider, Sortable, and Tooltip and all seem to be
working at first glance.

All my tests pass as well.

Best,

Thomas
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
https://github.com/wicketstuff/wiquery/commit/
0235691174ceeede22b588d2f67868
b940d9be3a
`mvn clean install` fails for me because no test-jar is built for the
core
[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
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 <
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
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 <
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
Post by Emond Papegaaij
I'm planning to upgrade jQuery UI to the latest version next
week.
We
Post by Emond Papegaaij
are
currently migrating all our applications to wicket 8 and also
depend on
Post by Emond Papegaaij
wiquery quite a lot. It does however seem that jQuery UI is
mostly
dead.
Post by Emond Papegaaij
The rest of the world probably switched to yet another fancy
JavaScript
ui
Post by Emond Papegaaij
library. At least the will make it easy to stay up to date with
the
latest
Post by Emond Papegaaij
version :)
I can't push a release to central, but perhaps Martin can do
that
when
I'm
Post by Emond Papegaaij
done? For now you can use a snapshot build. It works, but the UI
API
might
Post by Emond Papegaaij
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
Op vr 1 jun. 2018 17:36 schreef Thomas Heigl <
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But as I
said,
Post by Emond Papegaaij
Post by Thomas Heigl
my
project
Post by Emond Papegaaij
Post by Thomas Heigl
heavily depends on it.
@papegaaij has resolved all the compile errors against
8.0.0-M9 (
Post by Emond Papegaaij
Post by Thomas Heigl
https://github.com/wicketstuff/wiquery) and a simple release
of
8.0.0
Post by Emond Papegaaij
Post by Thomas Heigl
would
be enough for me.
Best,
Thomas
On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to
contribute to
Post by Emond Papegaaij
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl <
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff
8.0.0,
could
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
somebody
Post by Thomas Heigl
please cut a release of WiQuery compatible with the new
version?
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Post by Thomas Heigl
Our application still heavily relies on WiQuery and we
can't
move
to
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Wicket
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
------------------------------------------------------------
---------
---------------------------------------------------------------------
---------------------------------------------------------------------
Emond Papegaaij
2018-06-06 11:00:58 UTC
Permalink
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
https://github.com/wicketstuff/wiquery/commit/0235691174ceeede22b588d2f67868
b940d9be3a
`mvn clean install` fails for me because no test-jar is built for the core
[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
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 <
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
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 <
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
Post by Emond Papegaaij
I'm planning to upgrade jQuery UI to the latest version next week.
We
Post by Emond Papegaaij
are
currently migrating all our applications to wicket 8 and also
depend on
Post by Emond Papegaaij
wiquery quite a lot. It does however seem that jQuery UI is mostly
dead.
Post by Emond Papegaaij
The rest of the world probably switched to yet another fancy
JavaScript
ui
Post by Emond Papegaaij
library. At least the will make it easy to stay up to date with the
latest
Post by Emond Papegaaij
version :)
I can't push a release to central, but perhaps Martin can do that
when
I'm
Post by Emond Papegaaij
done? For now you can use a snapshot build. It works, but the UI
API
might
Post by Emond Papegaaij
change a bit before the 8.0 release.
Best regards,
Emond Papegaaij
Post by Thomas Heigl
Hi Ernesto,
I'm not sure how many people are still using it. But as I said,
my
project
Post by Emond Papegaaij
Post by Thomas Heigl
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
Post by Emond Papegaaij
Post by Thomas Heigl
would
be enough for me.
Best,
Thomas
On Fri, Jun 1, 2018 at 5:05 PM, Ernesto Reinaldo Barreiro <
Post by Ernesto Reinaldo Barreiro
Hi,
I do not know who is actually using this project. I use to
contribute to
Post by Emond Papegaaij
Post by Thomas Heigl
it
Post by Ernesto Reinaldo Barreiro
a few years ago. I haven't used it for ages..
On Fri, Jun 1, 2018 at 3:39 PM, Thomas Heigl <
Post by Thomas Heigl
Hi,
Following the release of Wicket 8.0.0 and WicketStuff 8.0.0,
could
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
somebody
Post by Thomas Heigl
please cut a release of WiQuery compatible with the new
version?
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Post by Thomas Heigl
Our application still heavily relies on WiQuery and we can't
move
to
Post by Emond Papegaaij
Post by Thomas Heigl
Post by Ernesto Reinaldo Barreiro
Wicket
Post by Thomas Heigl
8 without it.
Best,
Thomas
--
Regards - Ernesto Reinaldo Barreiro
---------------------------------------------------------------------
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@wicket.apache.org
For additional commands, e-mail: users-***@wicket.apache.org

Loading...