Hi,
Maven resource filtering caused the corruption of the keystore file.
Now it should be fixed and snapshot quickstarts should run correctly.
Andrea.
On 30/03/2017 15:18, Maxim Solodovnik wrote:
sure:
Steps:
1) go to create quickstart page [1]
2) choose 8.0.0-SNAPSHOT
3) copy/create project [2]
4) cd myproject
5) mvn jetty:run
Result: Stack trace [3]
Workaround: remove all https/ssl related jetty components
*[1]* http://wicket.apache.org/start/quickstart.html
*[2]* mvn archetype:generate -DarchetypeGroupId=org.apache.wicket
-DarchetypeArtifactId=wicket-archetype-quickstart
-DarchetypeVersion=8.0.0-SNAPSHOT -DgroupId=com.mycompany
-DartifactId=myproject -DarchetypeRepository=
https://repository.apache.org/content/repositories/snapshots/
-DinteractiveMode=false
*[3] *
[ERROR] Failed to execute goal
org.eclipse.jetty:jetty-maven-plugin:9.4.3.v20170317:run (default-cli) on
project myproject: Failure: Invalid keystore format -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Exception in thread "Thread-1" java.lang.NoClassDefFoundError:
org/eclipse/jetty/io/ManagedSelector$CloseEndPoints
at org.eclipse.jetty.io.ManagedSelector.doStop(ManagedSelector.java:135)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160)
at org.eclipse.jetty.io.SelectorManager.doStop(SelectorManager.java:257)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160)
at
org.eclipse.jetty.client.AbstractHttpClientTransport.doStop(AbstractHttpClientTransport.java:87)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160)
at org.eclipse.jetty.client.HttpClient.doStop(HttpClient.java:254)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160)
at
org.eclipse.jetty.websocket.client.WebSocketClient.doStop(WebSocketClient.java:376)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.stop(ContainerLifeCycle.java:142)
at
org.eclipse.jetty.util.component.ContainerLifeCycle.doStop(ContainerLifeCycle.java:160)
at
org.eclipse.jetty.websocket.jsr356.ClientContainer.doStop(ClientContainer.java:214)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.stop(AbstractLifeCycle.java:89)
at org.eclipse.jetty.util.thread.ShutdownThread.run(ShutdownThread.java:138)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.jetty.io.ManagedSelector$CloseEndPoints
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.unsynchronizedLoadClass(ClassRealm.java:271)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:247)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:239)
... 23 more
On Thu, Mar 30, 2017 at 8:01 PM, Andrea Del Bene <an.delb...@gmail.com>
wrote:
Hi Maxim,
can you provide more details about the problem with jetty:run?
thank you.
On Thu, Mar 30, 2017 at 2:38 PM, Maxim Solodovnik <solomax...@gmail.com>
wrote:
Another report:
Latest wicket version still M4
Project created using latest 8.0.0-SNAPSHOT is not runnable using
jetty:run
On Thu, Mar 30, 2017 at 7:31 PM, Andrea Del Bene <an.delb...@gmail.com>
wrote:
It sounds like a subliminal message :-)
On Thu, Mar 30, 2017 at 11:13 AM, Martin Grigorov <
mgrigo...@apache.org>
wrote:
Hi,
Thanks for the report!
I've fixed this few months ago:
https://github.com/apache/wicket/commit/
86f7cb04020c5298e3408aea56c94e
744afed155
Maybe it is time for 7.7.0. 7.6.0 has been released 3 months ago!
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Mar 30, 2017 at 10:49 AM, Peter Henderson <
peter.hender...@starjar.com> wrote:
Hi all.
I've just created a quick start from [1] using [2]
The resulting project (pom.xml) is using
<wicket.version>7.5.0-SNAPSHOT</wicket.version>
Probably something trivial to fix in the project template?
Peter.
[1]
http://wicket.apache.org/start/quickstart.html
[2]
mvn archetype:generate -DarchetypeGroupId=org.apache.wicket
-DarchetypeArtifactId=wicket-archetype-quickstart
-DarchetypeVersion=7.6.0
-DgroupId=com.mycompany -DartifactId=redirect -DarchetypeRepository=
https://repository.apache.org/ -DinteractiveMode=false
--
Peter Henderson
--
WBR
Maxim aka solomax
---------------------------------------------------------------------
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
