You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Peter Ertl (JIRA)" <ji...@apache.org> on 2010/08/26 17:03:53 UTC
[jira] Created: (WICKET-3014) unable to launch StartExamples from
IDEA (eventually other IDE's as well)
unable to launch StartExamples from IDEA (eventually other IDE's as well)
-------------------------------------------------------------------------
Key: WICKET-3014
URL: https://issues.apache.org/jira/browse/WICKET-3014
Project: Wicket
Issue Type: Bug
Components: wicket-examples
Affects Versions: 1.5-M1, 1.4.10
Environment: OS X, java 6, IDEA
Reporter: Peter Ertl
Attachments: wicket-1_4.patch, wicket-1_5.patch
When trying to run
org.apache.wicket.examples.StartExamples
as a Java application trough my IDE (using IntelliJ IDEA) the class loader complains that it can't find the jetty JARs.
Exception in thread "main" java.lang.NoClassDefFoundError: org/mortbay/jetty/HandlerContainer
Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HandlerContainer
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
These JARs are using maven scope 'provided' which means the container has to provide the JARs. As you might expect IDEA has no jetty JARs in the classpath when running a class. An easy fix is to move StartExamples from src/main/java to src/test/java so the dependencies are found.
Patch for 1.4 and 1.5 will follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3014) unable to launch StartExamples from
IDEA (eventually other IDE's as well)
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3014.
-----------------------------------
Assignee: Igor Vaynberg
Fix Version/s: 1.4.11
1.5-M2
Resolution: Fixed
> unable to launch StartExamples from IDEA (eventually other IDE's as well)
> -------------------------------------------------------------------------
>
> Key: WICKET-3014
> URL: https://issues.apache.org/jira/browse/WICKET-3014
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.4.10, 1.5-M1
> Environment: OS X, java 6, IDEA
> Reporter: Peter Ertl
> Assignee: Igor Vaynberg
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket-1_4.patch, wicket-1_5.patch
>
>
> When trying to run
> org.apache.wicket.examples.StartExamples
> as a Java application trough my IDE (using IntelliJ IDEA) the class loader complains that it can't find the jetty JARs.
> Exception in thread "main" java.lang.NoClassDefFoundError: org/mortbay/jetty/HandlerContainer
> Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HandlerContainer
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> These JARs are using maven scope 'provided' which means the container has to provide the JARs. As you might expect IDEA has no jetty JARs in the classpath when running a class. An easy fix is to move StartExamples from src/main/java to src/test/java so the dependencies are found.
> Patch for 1.4 and 1.5 will follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3014) unable to launch StartExamples from
IDEA (eventually other IDE's as well)
Posted by "Peter Ertl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Ertl updated WICKET-3014:
-------------------------------
Attachment: wicket-1_4.patch
wicket-1_5.patch
> unable to launch StartExamples from IDEA (eventually other IDE's as well)
> -------------------------------------------------------------------------
>
> Key: WICKET-3014
> URL: https://issues.apache.org/jira/browse/WICKET-3014
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.4.10, 1.5-M1
> Environment: OS X, java 6, IDEA
> Reporter: Peter Ertl
> Attachments: wicket-1_4.patch, wicket-1_5.patch
>
>
> When trying to run
> org.apache.wicket.examples.StartExamples
> as a Java application trough my IDE (using IntelliJ IDEA) the class loader complains that it can't find the jetty JARs.
> Exception in thread "main" java.lang.NoClassDefFoundError: org/mortbay/jetty/HandlerContainer
> Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HandlerContainer
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> These JARs are using maven scope 'provided' which means the container has to provide the JARs. As you might expect IDEA has no jetty JARs in the classpath when running a class. An easy fix is to move StartExamples from src/main/java to src/test/java so the dependencies are found.
> Patch for 1.4 and 1.5 will follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3014) unable to launch StartExamples from
IDEA (eventually other IDE's as well)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903160#action_12903160 ]
Hudson commented on WICKET-3014:
--------------------------------
Integrated in Apache Wicket 1.5.x #269 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.5.x/269/])
WICKET-3014
> unable to launch StartExamples from IDEA (eventually other IDE's as well)
> -------------------------------------------------------------------------
>
> Key: WICKET-3014
> URL: https://issues.apache.org/jira/browse/WICKET-3014
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.4.10, 1.5-M1
> Environment: OS X, java 6, IDEA
> Reporter: Peter Ertl
> Assignee: Igor Vaynberg
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket-1_4.patch, wicket-1_5.patch
>
>
> When trying to run
> org.apache.wicket.examples.StartExamples
> as a Java application trough my IDE (using IntelliJ IDEA) the class loader complains that it can't find the jetty JARs.
> Exception in thread "main" java.lang.NoClassDefFoundError: org/mortbay/jetty/HandlerContainer
> Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HandlerContainer
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> These JARs are using maven scope 'provided' which means the container has to provide the JARs. As you might expect IDEA has no jetty JARs in the classpath when running a class. An easy fix is to move StartExamples from src/main/java to src/test/java so the dependencies are found.
> Patch for 1.4 and 1.5 will follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3014) unable to launch StartExamples from
IDEA (eventually other IDE's as well)
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12903020#action_12903020 ]
Hudson commented on WICKET-3014:
--------------------------------
Integrated in Apache Wicket 1.4.x #124 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/124/])
WICKET-3014
> unable to launch StartExamples from IDEA (eventually other IDE's as well)
> -------------------------------------------------------------------------
>
> Key: WICKET-3014
> URL: https://issues.apache.org/jira/browse/WICKET-3014
> Project: Wicket
> Issue Type: Bug
> Components: wicket-examples
> Affects Versions: 1.4.10, 1.5-M1
> Environment: OS X, java 6, IDEA
> Reporter: Peter Ertl
> Assignee: Igor Vaynberg
> Fix For: 1.4.11, 1.5-M2
>
> Attachments: wicket-1_4.patch, wicket-1_5.patch
>
>
> When trying to run
> org.apache.wicket.examples.StartExamples
> as a Java application trough my IDE (using IntelliJ IDEA) the class loader complains that it can't find the jetty JARs.
> Exception in thread "main" java.lang.NoClassDefFoundError: org/mortbay/jetty/HandlerContainer
> Caused by: java.lang.ClassNotFoundException: org.mortbay.jetty.HandlerContainer
> at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
> These JARs are using maven scope 'provided' which means the container has to provide the JARs. As you might expect IDEA has no jetty JARs in the classpath when running a class. An easy fix is to move StartExamples from src/main/java to src/test/java so the dependencies are found.
> Patch for 1.4 and 1.5 will follow.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.