Re: maven archetype

2012-08-26 Thread Martin Grigorov
Hi,

Check
- https://github.com/Bessonov/wicket-example
- jWeekend LegUp
- Wicketopia

On Fri, Aug 24, 2012 at 8:33 PM, Bruce McGuire brlmcgu...@gmail.com wrote:
 PS: I forgot to mention that I would like to use testNG.

 Thanks again.

 Bruce.

 On Fri, Aug 24, 2012 at 10:31 AM, Bruce McGuire brlmcgu...@gmail.comwrote:

 Hi There.

 It has been a while and a new company since I did a project with Wicket,
 and I would like to start out with a properly set up project.

 I am looking for an archetype that uses new versions of
   Wicket
   Spring
   Hibernate

 Any ideas would be greatly appreciated.

 Thanks,

 Bruce.




-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



maven archetype

2012-08-25 Thread Bruce McGuire
Hi There.

It has been a while and a new company since I did a project with Wicket,
and I would like to start out with a properly set up project.

I am looking for an archetype that uses new versions of
  Wicket
  Spring
  Hibernate

Any ideas would be greatly appreciated.

Thanks,

Bruce.


Re: maven archetype

2012-08-25 Thread Bruce McGuire
PS: I forgot to mention that I would like to use testNG.

Thanks again.

Bruce.

On Fri, Aug 24, 2012 at 10:31 AM, Bruce McGuire brlmcgu...@gmail.comwrote:

 Hi There.

 It has been a while and a new company since I did a project with Wicket,
 and I would like to start out with a properly set up project.

 I am looking for an archetype that uses new versions of
   Wicket
   Spring
   Hibernate

 Any ideas would be greatly appreciated.

 Thanks,

 Bruce.



Re: Maven archetype and tomcat:run

2010-07-19 Thread Mansour Al Akeel
Martin,
thank you. But I don't have servlet.jar in the lib folder. There's no
lib folder, since I am using maven archetype.
If I have to exclude it from POM.XML then how ?
tomcat plugin depends on it !

can you please kindly give me more details ?

On Sun, Jul 18, 2010 at 11:16 AM, Martin Grigorov
martin.grigo...@gmail.com wrote:
 Remove servlet.jar from yourApplication.war#WEB-INF/lib/ folder


 2010/7/18 Mansour Al Akeel mansour.alak...@gmail.com

 Hello all:
 I am trying to run tomcat from maven and including openEJB. The
 command I am using to run tomcat:

 mvn tomcat:run

 The error I am getting :

 Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
 INFO: Starting tomcat server
 Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
 INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
 Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext
 filterStart
 SEVERE: Exception starting filter wicket.site
 java.lang.ClassCastException:
 org.apache.wicket.protocol.http.WicketFilter cannot be cast to
 javax.servlet.Filter
        at
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
        at
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
        at
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
        at
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
        at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
        at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
        at
 org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
        at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
        at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
        at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
        at
 org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
        at
 org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
        at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
        at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
        at
 org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
        at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:616)
        at
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
        at
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext start
 SEVERE: Error filterStart

 So I created a webapp project from maven archetype, and added openEjb
 dependency:

                dependency
                        groupIdorg.apache.openejb/groupId
                        artifactIdopenejb-core/artifactId
                        version3.1.2/version
                /dependency

 The error I am getting now is:

 Jul 18, 2010 7:02:37 AM org.apache.catalina.core.StandardWrapperValve
 invoke
 SEVERE: Servlet.service() for servlet jsp threw exception
 java.lang.LinkageError: loader constraint violation: loader (instance
 of org/apache/jasper/servlet/JasperLoader) previously initiated
 loading for a different type with name
 javax/servlet/http/HttpServletRequest
        at java.lang.Class.getDeclaredMethods0(Native Method)
        at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
        at java.lang.Class.getDeclaredMethods(Class.java:1808)
        at
 org.apache.catalina.util.DefaultAnnotationProcessor.processAnnotations(DefaultAnnotationProcessor.java:226

Re: Maven archetype and tomcat:run

2010-07-19 Thread Martin Grigorov
In your pom.xml find the dependency for javax.servlet:servlet-api and add
scopeprovided/scope

2010/7/19 Mansour Al Akeel mansour.alak...@gmail.com

 Martin,
 thank you. But I don't have servlet.jar in the lib folder. There's no
 lib folder, since I am using maven archetype.
 If I have to exclude it from POM.XML then how ?
 tomcat plugin depends on it !

 can you please kindly give me more details ?

 On Sun, Jul 18, 2010 at 11:16 AM, Martin Grigorov
 martin.grigo...@gmail.com wrote:
  Remove servlet.jar from yourApplication.war#WEB-INF/lib/ folder
 
 
  2010/7/18 Mansour Al Akeel mansour.alak...@gmail.com
 
  Hello all:
  I am trying to run tomcat from maven and including openEJB. The
  command I am using to run tomcat:
 
  mvn tomcat:run
 
  The error I am getting :
 
  Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
  INFO: Starting tomcat server
  Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
  INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
  Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext
  filterStart
  SEVERE: Exception starting filter wicket.site
  java.lang.ClassCastException:
  org.apache.wicket.protocol.http.WicketFilter cannot be cast to
  javax.servlet.Filter
 at
 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
 at
 
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
 at
 
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
 at
 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
 at
 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
 at
  org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
 at
  org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
 at
  org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
 at
  org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
 at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
 at
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
 at
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
 at
 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
 at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
 at
  org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at
 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 at
 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:616)
 at
  org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at
  org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
  Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext start
  SEVERE: Error filterStart
 
  So I created a webapp project from maven archetype, and added openEjb
  dependency:
 
 dependency
 groupIdorg.apache.openejb/groupId
 artifactIdopenejb-core/artifactId
 version3.1.2/version
 /dependency
 
  The error I am getting now is:
 
  Jul 18, 2010 7:02:37 AM org.apache.catalina.core.StandardWrapperValve
  invoke
  SEVERE: Servlet.service() for servlet jsp threw exception
  java.lang.LinkageError: loader constraint violation: loader (instance
  of org/apache/jasper/servlet/JasperLoader) previously initiated
  loading for a different type with name
  javax/servlet/http/HttpServletRequest
 at java.lang.Class.getDeclaredMethods0(Native Method

Re: Maven archetype and tomcat:run

2010-07-19 Thread Mansour Al Akeel
Martin, I don't have this depndency in my pom, and it's not in the
list of resolved dependencies:

here's what I have

dependencies
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket/artifactId
version${wicket.version}/version
/dependency

dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-extensions/artifactId
version${wicket.version}/version
/dependency

dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.6/version
scopetest/scope
/dependency

dependency
groupIdorg.wicketstuff/groupId
artifactIdjavaee-inject/artifactId
version${wicketstuff.version}/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version3.1.2/version
/dependency

dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-log4j12/artifactId
version${slf4j.version}/version
/dependency




On Mon, Jul 19, 2010 at 3:07 PM, Martin Grigorov mgrigo...@apache.org wrote:
 In your pom.xml find the dependency for javax.servlet:servlet-api and add
 scopeprovided/scope

 2010/7/19 Mansour Al Akeel mansour.alak...@gmail.com

 Martin,
 thank you. But I don't have servlet.jar in the lib folder. There's no
 lib folder, since I am using maven archetype.
 If I have to exclude it from POM.XML then how ?
 tomcat plugin depends on it !

 can you please kindly give me more details ?

 On Sun, Jul 18, 2010 at 11:16 AM, Martin Grigorov
 martin.grigo...@gmail.com wrote:
  Remove servlet.jar from yourApplication.war#WEB-INF/lib/ folder
 
 
  2010/7/18 Mansour Al Akeel mansour.alak...@gmail.com
 
  Hello all:
  I am trying to run tomcat from maven and including openEJB. The
  command I am using to run tomcat:
 
  mvn tomcat:run
 
  The error I am getting :
 
  Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
  INFO: Starting tomcat server
  Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
  INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
  Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext
  filterStart
  SEVERE: Exception starting filter wicket.site
  java.lang.ClassCastException:
  org.apache.wicket.protocol.http.WicketFilter cannot be cast to
  javax.servlet.Filter
         at
 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
         at
 
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
         at
 
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
         at
 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
         at
 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
         at
  org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
         at
  org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
         at
  org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
         at
  org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
         at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
         at
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
         at
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
         at
 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
         at
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
         at org.apache.maven.cli.MavenCli.main(MavenCli.java:362

Re: Maven archetype and tomcat:run

2010-07-19 Thread Martin Grigorov
Try to run the application with maven-jetty-plugin or even better in a
standalone web container without Maven involved and see what is the outcome.

2010/7/19 Mansour Al Akeel mansour.alak...@gmail.com

 Martin, I don't have this depndency in my pom, and it's not in the
 list of resolved dependencies:

 here's what I have

dependencies
dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket/artifactId
version${wicket.version}/version
/dependency

dependency
groupIdorg.apache.wicket/groupId
artifactIdwicket-extensions/artifactId
version${wicket.version}/version
/dependency

dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version4.6/version
scopetest/scope
/dependency

dependency
groupIdorg.wicketstuff/groupId
artifactIdjavaee-inject/artifactId
version${wicketstuff.version}/version
/dependency

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version3.1.2/version
/dependency

 dependency
groupIdorg.slf4j/groupId
artifactIdslf4j-log4j12/artifactId
version${slf4j.version}/version
/dependency




 On Mon, Jul 19, 2010 at 3:07 PM, Martin Grigorov mgrigo...@apache.org
 wrote:
  In your pom.xml find the dependency for javax.servlet:servlet-api and
 add
  scopeprovided/scope
 
  2010/7/19 Mansour Al Akeel mansour.alak...@gmail.com
 
  Martin,
  thank you. But I don't have servlet.jar in the lib folder. There's no
  lib folder, since I am using maven archetype.
  If I have to exclude it from POM.XML then how ?
  tomcat plugin depends on it !
 
  can you please kindly give me more details ?
 
  On Sun, Jul 18, 2010 at 11:16 AM, Martin Grigorov
  martin.grigo...@gmail.com wrote:
   Remove servlet.jar from yourApplication.war#WEB-INF/lib/ folder
  
  
   2010/7/18 Mansour Al Akeel mansour.alak...@gmail.com
  
   Hello all:
   I am trying to run tomcat from maven and including openEJB. The
   command I am using to run tomcat:
  
   mvn tomcat:run
  
   The error I am getting :
  
   Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
   INFO: Starting tomcat server
   Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
   INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
   Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext
   filterStart
   SEVERE: Exception starting filter wicket.site
   java.lang.ClassCastException:
   org.apache.wicket.protocol.http.WicketFilter cannot be cast to
   javax.servlet.Filter
  at
  
 
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
  at
  
 
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
  at
  
 
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
  at
  
 
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
  at
  
 
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
  at
   org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
  at
   org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
  at
   org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
  at
  
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
  at
 org.apache.catalina.startup.Embedded.start(Embedded.java:825)
  at
  
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
  at
  
 
 org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
  at
  
 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
  at
  
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
  at
  
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
  at
  
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
  at
  
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
  at
  
 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348

Re: Maven archetype and tomcat:run

2010-07-19 Thread Mansour Al Akeel
It runs ok  under a standard tomcat installation, and I can do remote
debugging. However, it's not as convenient as if it's running from
maven, where I can view changes easily.
In my case, changes has to be deployed to tomcat installation after
re-packaging the war file.

When dealing with maven-jetty-plugin (from
http://javaadventure.blogspot.com/2010/03/openejb-jetty-and-maven-transaction.html
) I get an exception:

Listening for transport dt_socket at address: 4000
[INFO] Scanning for projects...
[INFO] 
[INFO] Building quickstart
[INFO]task-segment: [jetty:run]
[INFO] 
[INFO] Preparing jetty:run
[INFO] [resources:resources {execution: default-resources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy
filtered resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO] Copying 1 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy
filtered resources, i.e. build is platform dependent!
[INFO] Copying 0 resource
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [jetty:run {execution: default-cli}]
[INFO] Configuring Jetty for project: quickstart
[INFO] Webapp source directory =
/home/mansour/workspace/Rentals/wicket/src/main/webapp
[INFO] Reload Mechanic: automatic
[INFO] Classes = /home/mansour/workspace/Rentals/wicket/target/classes
[INFO] Configuring Jetty from xml configuration file =
/home/mansour/workspace/Rentals/wicket/src/main/jetty/jetty.xml
2010-07-19 16:34:21.916:INFO::Logging to STDERR via org.mortbay.log.StdErrLog
Apache OpenEJB 3.1.2build: 20091010-03:11
http://openejb.apache.org/
INFO - openejb.home = /home/mansour/workspace/Rentals/wicket
INFO - openejb.base = /home/mansour/workspace/Rentals/wicket
INFO - Configuring Service(id=Default Security Service,
type=SecurityService, provider-id=Default Security Service)
INFO - Configuring Service(id=Default Transaction Manager,
type=TransactionManager, provider-id=Default Transaction Manager)
INFO - Found ClientModule in classpath:
/home/mansour/.m2/repository/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar
INFO - Found ClientModule in classpath:
/home/mansour/.m2/repository/org/mortbay/jetty/start/6.1.22/start-6.1.22.jar
INFO - Beginning load:
/home/mansour/.m2/repository/org/eclipse/jdt/core/3.1.1/core-3.1.1.jar
ERROR - Unable to clear Sun JarFileFactory cache
java.lang.ClassCastException: java.lang.String cannot be cast to java.net.URL
at 
org.apache.openejb.ClassLoaderUtil.clearSunJarFileFactoryCache(ClassLoaderUtil.java:173)
at 
org.apache.openejb.ClassLoaderUtil.destroyClassLoader(ClassLoaderUtil.java:130)
at 
org.apache.openejb.ClassLoaderUtil.destroyClassLoader(ClassLoaderUtil.java:97)
at 
org.apache.openejb.config.DeploymentLoader.load(DeploymentLoader.java:185)
at 
org.apache.openejb.config.ConfigurationFactory.configureApplication(ConfigurationFactory.java:509)
at 
org.apache.openejb.config.ConfigurationFactory.getOpenEjbConfiguration(ConfigurationFactory.java:380)
at 
org.apache.openejb.assembler.classic.Assembler.getOpenEjbConfiguration(Assembler.java:299)
at 
org.apache.openejb.assembler.classic.Assembler.build(Assembler.java:278)
at org.apache.openejb.OpenEJB$Instance.init(OpenEJB.java:137)
at org.apache.openejb.OpenEJB.init(OpenEJB.java:286)
at org.apache.openejb.OpenEJB.init(OpenEJB.java:265)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.apache.openejb.loader.OpenEJBInstance.init(OpenEJBInstance.java:36)
at 
org.apache.openejb.client.LocalInitialContextFactory.init(LocalInitialContextFactory.java:71)
at 
org.apache.openejb.client.LocalInitialContextFactory.init(LocalInitialContextFactory.java:53)
at 
org.apache.openejb.client.LocalInitialContextFactory.getInitialContext(LocalInitialContextFactory.java:42)
at 
javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at 
javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.init(InitialContext.java:197)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 

Re: Maven archetype and tomcat:run

2010-07-18 Thread Martin Grigorov
Remove servlet.jar from yourApplication.war#WEB-INF/lib/ folder


2010/7/18 Mansour Al Akeel mansour.alak...@gmail.com

 Hello all:
 I am trying to run tomcat from maven and including openEJB. The
 command I am using to run tomcat:

 mvn tomcat:run

 The error I am getting :

 Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
 INFO: Starting tomcat server
 Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
 INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
 Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext
 filterStart
 SEVERE: Exception starting filter wicket.site
 java.lang.ClassCastException:
 org.apache.wicket.protocol.http.WicketFilter cannot be cast to
 javax.servlet.Filter
at
 org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at
 org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
at
 org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
at
 org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
at
 org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
 org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at
 org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
 org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
at
 org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
at
 org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
at
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
 org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
 org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
 Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext start
 SEVERE: Error filterStart

 So I created a webapp project from maven archetype, and added openEjb
 dependency:

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version3.1.2/version
/dependency

 The error I am getting now is:

 Jul 18, 2010 7:02:37 AM org.apache.catalina.core.StandardWrapperValve
 invoke
 SEVERE: Servlet.service() for servlet jsp threw exception
 java.lang.LinkageError: loader constraint violation: loader (instance
 of org/apache/jasper/servlet/JasperLoader) previously initiated
 loading for a different type with name
 javax/servlet/http/HttpServletRequest
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
at java.lang.Class.getDeclaredMethods(Class.java:1808)
at
 org.apache.catalina.util.DefaultAnnotationProcessor.processAnnotations(DefaultAnnotationProcessor.java:226)
at
 org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:148)
at
 org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
at
 org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260

Maven archetype and tomcat:run

2010-07-17 Thread Mansour Al Akeel
Hello all:
I am trying to run tomcat from maven and including openEJB. The
command I am using to run tomcat:

mvn tomcat:run

The error I am getting :

Jul 18, 2010 6:53:29 AM org.apache.catalina.startup.Embedded start
INFO: Starting tomcat server
Jul 18, 2010 6:53:29 AM org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/6.0.26
Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext filterStart
SEVERE: Exception starting filter wicket.site
java.lang.ClassCastException:
org.apache.wicket.protocol.http.WicketFilter cannot be cast to
javax.servlet.Filter
at 
org.apache.catalina.core.ApplicationFilterConfig.getFilter(ApplicationFilterConfig.java:275)
at 
org.apache.catalina.core.ApplicationFilterConfig.setFilterDef(ApplicationFilterConfig.java:422)
at 
org.apache.catalina.core.ApplicationFilterConfig.init(ApplicationFilterConfig.java:115)
at 
org.apache.catalina.core.StandardContext.filterStart(StandardContext.java:3838)
at 
org.apache.catalina.core.StandardContext.start(StandardContext.java:4488)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:785)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at 
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.startup.Embedded.start(Embedded.java:825)
at 
org.codehaus.mojo.tomcat.AbstractRunMojo.startContainer(AbstractRunMojo.java:533)
at 
org.codehaus.mojo.tomcat.AbstractRunMojo.execute(AbstractRunMojo.java:239)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Jul 18, 2010 6:53:30 AM org.apache.catalina.core.StandardContext start
SEVERE: Error filterStart

So I created a webapp project from maven archetype, and added openEjb
dependency:

dependency
groupIdorg.apache.openejb/groupId
artifactIdopenejb-core/artifactId
version3.1.2/version
/dependency

The error I am getting now is:

Jul 18, 2010 7:02:37 AM org.apache.catalina.core.StandardWrapperValve invoke
SEVERE: Servlet.service() for servlet jsp threw exception
java.lang.LinkageError: loader constraint violation: loader (instance
of org/apache/jasper/servlet/JasperLoader) previously initiated
loading for a different type with name
javax/servlet/http/HttpServletRequest
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java:2444)
at java.lang.Class.getDeclaredMethods(Class.java:1808)
at 
org.apache.catalina.util.DefaultAnnotationProcessor.processAnnotations(DefaultAnnotationProcessor.java:226)
at 
org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:148)
at 
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:329)
at 
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:313)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:260)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter

Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
Hi,

when creating a fresh Wicket project with the following line as
generated by the quickstart page on wicket.apache.org:

mvn archetype:create -DarchetypeGroupId=org.apache.wicket
-DarchetypeArtifactId=wicket-archetype-quickstart
-DarchetypeVersion=1.4-rc4 -DgroupId=com.mycompany
-DartifactId=myproject

...I run into a number of (easily fixable, but somewhat annoying and
non-obvious) problems.

- The classpath file generated by 'mvn eclipse:eclipse' has an
  include-pattern of '**/*.java' for both src/test/java and
  src/main/java. This means that by default none of the HTML files or
  other resources will be copied to the classpath when for example
  using the 'Start' class.
   This can of course be fixed by manually removing these restrictions
  from the classpath, but on regenerating with eclipse:eclipse they
  will be added again. Also, this is probably non-obvious to new users.
  I think this is more of a Maven problem than one with Wicket, but it
  shows up as more of a problem here because not many other projects
  have their resources directly in the packages. I have not found an
  option in eclipse:eclipse to set these include patterns. Does anybody
  know whether any such options exist? If yes, I propose adding an
  appropriate setting to the Wicket archetype. If not, I think there
  should be a notice about this quirk on the quickstart page.
   I realize this is probably due to the fact that Maven wants to copy
  the resources itself, so it can do its filtering. However, I don't
  really see that as an issue for a typical Wicket project, or am I
  missing something?

The second problem is due to the way I set up my project -- it may be
odd (is it?), but I think this is rather sensible for standalone
component development.

- I am developing a standalone component for use in other projects, so
  under src/main/ I'd like to have only the classes and resources that
  belong to the component. On the other hand, for testing and debugging
  purposes, a simple Wicket application and page are very handy, so I
  moved those from src/main to src/test, since these shouldn't show up
  in the generated jar file.
   This works in Eclipse when I remove the restrictions mentioned above
  from both src/main and src/test. When I try to use 'mvn jetty:run',
  it breaks down, complaining that it can't find the Application class
  (and by extension also the other classes in src/test). This is
  fixable by adding
configuration
 useTestClasspathtrue/useTestClasspath
/configuration
  to the jetty-plugin part of the generated pom.xml. I don't see any
  negative side-effects of this, so I'd like to propose adding this to
  the archetype.

As an aside: Is this practice of keeping a debug Application under
src/test considered good or bad practice? If bad, why?

Best regards, and thanks for a great framework!
Carl-Eric

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Juan Carlos Garcia M.

The first problem you mention is due to a change in how the maven eclipse
plugins works, documented as a bug in: 
http://www.mail-archive.com/d...@maven.apache.org/msg80176.html
http://www.mail-archive.com/d...@maven.apache.org/msg80176.html 

Known Issues:
* [MECLIPSE-443] - Only include **/*.java in Java source directories
may affect you if you use ajdt or have non-java sources in your
directories that you expect to be compiled
Release 2.6.1 (which may get renamed to 2.7) has fixed this issue and will
be released shortly.

However in order to get it works and better don't need to worry about fixing
this in eclipse every time you generate the Eclipse project through mvn
eclipse:eclipse, you can specify to use version 2.5 of maven-eclipse-plugin
in your POM.xml

 build
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-eclipse-plugin/artifactId
  version2.5/version
/plugin
  /plugins
  /build

Hope this help.


igor.vaynberg wrote:
 
 On Tue, May 26, 2009 at 3:25 AM, Carl-Eric Menzel
 cm.wic...@users.bitforce.com wrote:
 - The classpath file generated by 'mvn eclipse:eclipse' has an
  include-pattern of '**/*.java' for both src/test/java and
  src/main/java. This means that by default none of the HTML files or
  other resources will be copied to the classpath when for example
  using the 'Start' class.
 
 go to preferences/compiler/building/output folder and remove *.html
 from Filtered Resources list.
 
 The second problem is due to the way I set up my project -- it may be
 odd (is it?), but I think this is rather sensible for standalone
 component development.

 - I am developing a standalone component for use in other projects, so
  under src/main/ I'd like to have only the classes and resources that
  belong to the component. On the other hand, for testing and debugging
  purposes, a simple Wicket application and page are very handy, so I
  moved those from src/main to src/test, since these shouldn't show up
  in the generated jar file.
 
 test is for tests :)
 
 the proper way to do this is to create a multimodule project - one
 module containing the component and another containing a demo which
 you can also use for testing.
 
 -igor
 
 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org
 
 
 

-- 
View this message in context: 
http://www.nabble.com/Problem-with-Maven-archetype%2C-Eclipse-Classpath-and-jetty%3Arun-tp23720481p23725755.html
Sent from the Wicket - User mailing list archive at Nabble.com.


-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Igor Vaynberg
On Tue, May 26, 2009 at 3:25 AM, Carl-Eric Menzel
cm.wic...@users.bitforce.com wrote:
 - The classpath file generated by 'mvn eclipse:eclipse' has an
  include-pattern of '**/*.java' for both src/test/java and
  src/main/java. This means that by default none of the HTML files or
  other resources will be copied to the classpath when for example
  using the 'Start' class.

go to preferences/compiler/building/output folder and remove *.html
from Filtered Resources list.

 The second problem is due to the way I set up my project -- it may be
 odd (is it?), but I think this is rather sensible for standalone
 component development.

 - I am developing a standalone component for use in other projects, so
  under src/main/ I'd like to have only the classes and resources that
  belong to the component. On the other hand, for testing and debugging
  purposes, a simple Wicket application and page are very handy, so I
  moved those from src/main to src/test, since these shouldn't show up
  in the generated jar file.

test is for tests :)

the proper way to do this is to create a multimodule project - one
module containing the component and another containing a demo which
you can also use for testing.

-igor

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
On Tue, 26 May 2009 08:31:04 -0700
Igor Vaynberg igor.vaynb...@gmail.com wrote:

 go to preferences/compiler/building/output folder and remove *.html
 from Filtered Resources list.

I know that :-) I was proposing making this the default in
the archetype.  

 test is for tests :)
 the proper way to do this is to create a multimodule project - one
 module containing the component and another containing a demo which
 you can also use for testing.

Interesting idea, I'll try that.

But I need a page if I want to test a form (and thus testing how my
component acts within the form), don't I? WicketTester.newFormTester
seems to want to have a page started first. That's why I wanted to have
the page in the test directory, because I only need it as a test
fixture.

Thanks for the reply
Carl-Eric

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Fw: Problem with Maven archetype, Eclipse Classpath and jetty:run

2009-05-26 Thread Carl-Eric Menzel
On Tue, 26 May 2009 08:39:36 -0700 (PDT)
Juan Carlos Garcia M. jcgarc...@gmail.com wrote:

 [MECLIPSE ticket and workaround]

 Hope this help.

Yes it does, thank you.

Carl-Eric

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Wicket Quickstart maven archetype - Archetype repository missing

2008-02-14 Thread OliZilla

Currently when I run the mvn quickstart command provided by the quickstart
web page, maven complains:


...
[INFO] [archetype:create]
[INFO] Archetype repository missing. Using the one from
[org.apache.wicket:wicket-archetype-quickstart:1.3.0-beta3 -
http://repo1.maven.org/maven2] found in catalog internal
Define value for version: :


Where it then waits for user input. 
I wasn't sure what was going on, as this had never happened before, so i
just blindly hit return a couple of times. Of course the build then failed
with the following message:


[ERROR] BUILD ERROR
[INFO]

[INFO] The archetype generation must be configured here


I found that if i entered 1.3.1 where it asked for a value of version:
and then com.yournamehere where it asks for value for package: then my
quickstart project was created successfully with the following log:


Define value for version: : 1.3.1
Define value for package: : com.myfrikinpackage
Confirm properties configuration:
groupId: com.mycompany
artifactId: myproject3
version: 1.3.1
package: com.myfrikinpackage
 Y: : y
[INFO]

[INFO] Using following parameters for creating OldArchetype:
wicket-archetype-quickstart:1.3.1
[INFO]

[INFO] Parameter: groupId, Value: com.mycompany
[INFO] Parameter: packageName, Value: com.myfrikinpackage
[INFO] Parameter: basedir, Value: /Users/oli/temp
[INFO] Parameter: package, Value: com.myfrikinpackage
[INFO] Parameter: version, Value: 1.3.1
[INFO] Parameter: artifactId, Value: myproject3
[INFO] * End of debug info from resources from generated
POM ***
[INFO] OldArchetype created in dir: /Users/oli/temp/myproject3
[INFO]

[INFO] BUILD SUCCESSFUL
[INFO]



A bit of googling would suggest this is a maven issue, see: 
http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html
http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html
 


on the appfuse mailing list, someone is having the same problem. I have
tried clearing the offending part of my local repos, but I still can't run
the command without some user input.


The solution is very simple, but its not immediately obvious, so may put off
new users (I discovered it trying to convince a collegue how easy it was to
get up and running on Wicket, which was slightly embarrassing). Is any one
else experiencing this, or know what is going on?


Oli 
-- 
View this message in context: 
http://www.nabble.com/Wicket-Quickstart-maven-archetype---%22Archetype-repository-missing%22-tp15481228p15481228.html
Sent from the Wicket - User mailing list archive at Nabble.com.


Re: Wicket Quickstart maven archetype - Archetype repository missing

2008-02-14 Thread Raphaël Piéroni
This is because of the recent release of maven archetype 2.0-alpha-1 release.

Please consider calling the old plugin version the time for the maven
team to fix the problem.

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create ...


Cheers.

Raphaël

2008/2/14, OliZilla [EMAIL PROTECTED]:

  Currently when I run the mvn quickstart command provided by the quickstart
  web page, maven complains:


  ...
  [INFO] [archetype:create]
  [INFO] Archetype repository missing. Using the one from
  [org.apache.wicket:wicket-archetype-quickstart:1.3.0-beta3 -
  http://repo1.maven.org/maven2] found in catalog internal
  Define value for version: :


  Where it then waits for user input.
  I wasn't sure what was going on, as this had never happened before, so i
  just blindly hit return a couple of times. Of course the build then failed
  with the following message:


  [ERROR] BUILD ERROR
  [INFO]
  
  [INFO] The archetype generation must be configured here


  I found that if i entered 1.3.1 where it asked for a value of version:
  and then com.yournamehere where it asks for value for package: then my
  quickstart project was created successfully with the following log:


  Define value for version: : 1.3.1
  Define value for package: : com.myfrikinpackage
  Confirm properties configuration:
  groupId: com.mycompany
  artifactId: myproject3
  version: 1.3.1
  package: com.myfrikinpackage
   Y: : y
  [INFO]
  
  [INFO] Using following parameters for creating OldArchetype:
  wicket-archetype-quickstart:1.3.1
  [INFO]
  
  [INFO] Parameter: groupId, Value: com.mycompany
  [INFO] Parameter: packageName, Value: com.myfrikinpackage
  [INFO] Parameter: basedir, Value: /Users/oli/temp
  [INFO] Parameter: package, Value: com.myfrikinpackage
  [INFO] Parameter: version, Value: 1.3.1
  [INFO] Parameter: artifactId, Value: myproject3
  [INFO] * End of debug info from resources from generated
  POM ***
  [INFO] OldArchetype created in dir: /Users/oli/temp/myproject3
  [INFO]
  
  [INFO] BUILD SUCCESSFUL
  [INFO]
  


  A bit of googling would suggest this is a maven issue, see:
  
 http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html
  
 http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html


  on the appfuse mailing list, someone is having the same problem. I have
  tried clearing the offending part of my local repos, but I still can't run
  the command without some user input.


  The solution is very simple, but its not immediately obvious, so may put off
  new users (I discovered it trying to convince a collegue how easy it was to
  get up and running on Wicket, which was slightly embarrassing). Is any one
  else experiencing this, or know what is going on?


  Oli

 --
  View this message in context: 
 http://www.nabble.com/Wicket-Quickstart-maven-archetype---%22Archetype-repository-missing%22-tp15481228p15481228.html
  Sent from the Wicket - User mailing list archive at Nabble.com.



Re: Wicket Quickstart maven archetype - Archetype repository missing

2008-02-14 Thread Nino Saturnino Martinez Vazquez Wael
Thanks. Had a million problems yesterday, thought it was because I ran 
on a windoze box.


Raphaël Piéroni wrote:

This is because of the recent release of maven archetype 2.0-alpha-1 release.

Please consider calling the old plugin version the time for the maven
team to fix the problem.

mvn org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create ...


Cheers.

Raphaël

2008/2/14, OliZilla [EMAIL PROTECTED]:
  

 Currently when I run the mvn quickstart command provided by the quickstart
 web page, maven complains:


 ...
 [INFO] [archetype:create]
 [INFO] Archetype repository missing. Using the one from
 [org.apache.wicket:wicket-archetype-quickstart:1.3.0-beta3 -
 http://repo1.maven.org/maven2] found in catalog internal
 Define value for version: :


 Where it then waits for user input.
 I wasn't sure what was going on, as this had never happened before, so i
 just blindly hit return a couple of times. Of course the build then failed
 with the following message:


 [ERROR] BUILD ERROR
 [INFO]
 
 [INFO] The archetype generation must be configured here


 I found that if i entered 1.3.1 where it asked for a value of version:
 and then com.yournamehere where it asks for value for package: then my
 quickstart project was created successfully with the following log:


 Define value for version: : 1.3.1
 Define value for package: : com.myfrikinpackage
 Confirm properties configuration:
 groupId: com.mycompany
 artifactId: myproject3
 version: 1.3.1
 package: com.myfrikinpackage
  Y: : y
 [INFO]
 
 [INFO] Using following parameters for creating OldArchetype:
 wicket-archetype-quickstart:1.3.1
 [INFO]
 
 [INFO] Parameter: groupId, Value: com.mycompany
 [INFO] Parameter: packageName, Value: com.myfrikinpackage
 [INFO] Parameter: basedir, Value: /Users/oli/temp
 [INFO] Parameter: package, Value: com.myfrikinpackage
 [INFO] Parameter: version, Value: 1.3.1
 [INFO] Parameter: artifactId, Value: myproject3
 [INFO] * End of debug info from resources from generated
 POM ***
 [INFO] OldArchetype created in dir: /Users/oli/temp/myproject3
 [INFO]
 
 [INFO] BUILD SUCCESSFUL
 [INFO]
 


 A bit of googling would suggest this is a maven issue, see:
 
http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html
 
http://www.nabble.com/Archetype-repository-missing-and-asking-for-a-version-and-package-td15446552s2369.html


 on the appfuse mailing list, someone is having the same problem. I have
 tried clearing the offending part of my local repos, but I still can't run
 the command without some user input.


 The solution is very simple, but its not immediately obvious, so may put off
 new users (I discovered it trying to convince a collegue how easy it was to
 get up and running on Wicket, which was slightly embarrassing). Is any one
 else experiencing this, or know what is going on?


 Oli

--
 View this message in context: 
http://www.nabble.com/Wicket-Quickstart-maven-archetype---%22Archetype-repository-missing%22-tp15481228p15481228.html
 Sent from the Wicket - User mailing list archive at Nabble.com.




--
Nino Martinez Wael
Java Specialist @ Jayway DK
http://www.jayway.dk
+45 2936 7684


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Wicket maven archetype

2007-09-07 Thread Gwyn Evans
On Friday, September 7, 2007, 9:38:53 AM, Al [EMAIL PROTECTED] wrote:

 Gwyn Evans wrote:
 It's a bug in the Maven Surefire plugin V2.3 that shows up if there's
 a src/test/java tree but neither JUnit or TestNG in the dependencies.
 
 Simplest fix is to add
 
 dependency
 groupIdjunit/groupId
 artifactIdjunit/artifactId
 version3.8.2/version
 scopeprovided/scope
 /dependency
 
  to the generated pom.xml's dependencies section.  I've added it to
  the code for the archetype in SVN, but can't do anything about the
  one already published in beta3.

 That should surely be scopetest/scope?

 Regards,

 Al

Well caught - must be more careful when I cut  paste!


/Gwyn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Re: Wicket maven archetype

2007-09-07 Thread Robo
Works,

Thanks


- Originálna Správa -
Od: Gwyn Evans  
Komu:  
Poslaná: 07.09.2007 11:00 
Predmet: Re: Wicket maven archetype

 On Friday, September 7, 2007, 9:38:53 AM, Al  wrote:
 
  Gwyn Evans wrote:
  It\'s a bug in the Maven Surefire plugin V2.3 that shows up if there\'s
  a src/test/java tree but neither JUnit or TestNG in the dependencies.
  
  Simplest fix is to add
  
  
  junit
  junit
  3.8.2
  provided
  
  
   to the generated pom.xml\'s  section.  I\'ve added it to
   the code for the archetype in SVN, but can\'t do anything about the
   one already published in beta3.
 
  That should surely be test?
 
  Regards,
 
  Al
 
 Well caught - must be more careful when I cut  paste!
 
 
 /Gwyn
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 


__
http://www.tahaj.sk - Stiahnite si najnovsie verzie vasich oblubenych programov



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Wicket maven archetype

2007-09-07 Thread Gwyn Evans
On Friday, September 7, 2007, 7:24:36 AM, Robo [EMAIL PROTECTED] wrote:

 Hello,

 Any idea?

 [INFO] Trace
 java.lang.NullPointerException
 at
 org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.ja
 va:594)

It's a bug in the Maven Surefire plugin V2.3 that shows up if there's
a src/test/java tree but neither JUnit or TestNG in the dependencies.

Simplest fix is to add

dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.2/version
scopeprovided/scope
/dependency

 to the generated pom.xml's dependencies section.  I've added it to
 the code for the archetype in SVN, but can't do anything about the
 one already published in beta3.

/Gwyn


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]