Thanks Shelan, I updated the "How to build Roller" page to explain that you run Roller via Maven like so:
cd roller_trunk/weblogger-webapp mvn jetty:run - Dave On Tue, Jan 25, 2011 at 1:03 AM, shelan Perera <[email protected]> wrote: > Hi Dave, > > When i was going through the mailing list i found the same problem and as it > stated i issued "mvn jetty:run" command instead of "mvn jetty:run-war" goal > and it was a success. > > I observed that when i issue the "mvn jetty:run-war" command derby instance > start and then stop in the middle of starting which causes the previous > error. > > Thanks > > On Tue, Jan 25, 2011 at 10:14 AM, shelan Perera <[email protected]> wrote: > >> Hi Dave, >> >> Thanks for the quick reply in my previous mail latter part, i have tried >> the weblogger-webapp directory. I am getting the following error.I think in >> the development test run the database suppose to start on its own. (and also >> i there is no any other service running on the port 3223). >> >> Thanks >> >> >> - SUCCESS: loaded JDBC driver class >> [org.apache.derby.jdbc.ClientDriver] >> - ERROR: unable to obtain database connection. Likely problem: bad >> connection parameters or database unavailable. >> >> >> [org.apache.derby.client.am.DisconnectException: >> java.net.ConnectException : Error opening socket to server localhost on port >> 3223 with message : Connection refused >> at org.apache.derby.client.net.NetAgent.<init>(Unknown Source) >> at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source) >> at org.apache.derby.client.am.Connection.<init>(Unknown Source) >> at org.apache.derby.client.net.NetConnection.<init>(Unknown Source) >> >> >> >> >> >> >> On Tue, Jan 25, 2011 at 10:07 AM, Dave <[email protected]> wrote: >> >>> It sounds like you may be reading some out of the documentation (probably >>> my >>> fault). Try running mvn jetty:run in the weblogger-webapp directory >>> instead. >>> >>> - Dave >>> On Jan 24, 2011 11:23 PM, "shelan Perera" <[email protected]> wrote: >>> > Hi devs, >>> > >>> > I am interested in Apache Roller project and willing to contribute to >>> the >>> > success of the project.I checked out the sources from svn and try to >>> build >>> > roller from the sources.I could build the sources successfully. >>> > >>> > As in the Web help guide for users i was trying to run from embedded >>> jetty >>> > using mvn jetty:run-war and got the following exception. >>> > (inside weblogger-web). >>> > >>> > and also i noted that in the pom.xml there is no plugin description for >>> the >>> > jetty. >>> > >>> > Downloading: >>> > http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml >>> ^Cshelan@shelan-laptop:~/gsoc/roller/weblogger-web$ >>> > mvn -e jetty:run-war [INFO] Error stacktraces are turned on. [INFO] >>> Scanning >>> > for projects... Downloading: >>> > >>> >>> http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xmlDownloading >>> : >>> > >>> >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xmlDownloaded >>> : >>> > >>> http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadata.xml(9 >>> > KB at 0.8 KB/sec) Downloaded: >>> > http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml (17 >>> KB >>> at >>> > 1.2 KB/sec) [INFO] >>> > ------------------------------------------------------------------------ >>> > [INFO] BUILD FAILURE [INFO] >>> > ------------------------------------------------------------------------ >>> > [INFO] Total time: 13.815s [INFO] Finished at: Mon Jan 24 23:11:54 IST >>> 2011 >>> > [INFO] Final Memory: 6M/74M [INFO] >>> > ------------------------------------------------------------------------ >>> > [ERROR] No plugin found for prefix 'jetty' in the current project and in >>> the >>> > plugin groups [org.apache.maven.plugins, org.codehaus.mojo] available >>> from >>> > the repositories [local (/home/shelan/.m2/repository), central ( >>> > http://repo1.maven.org/maven2)] -> [Help 1] >>> > org.apache.maven.plugin.prefix.NoPluginFoundForPrefixException: No >>> plugin >>> > found for prefix 'jetty' in the current project and in the plugin groups >>> > [org.apache.maven.plugins, org.codehaus.mojo] available from the >>> > repositories [local (/home/shelan/.m2/repository), central ( >>> > http://repo1.maven.org/maven2)] at >>> > >>> >>> org.apache.maven.plugin.prefix.internal.DefaultPluginPrefixResolver.resolve(DefaultPluginPrefixResolver.java:92) >>> > at >>> > >>> >>> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.findPluginForPrefix(MojoDescriptorCreator.java:262) >>> > at >>> > >>> >>> org.apache.maven.lifecycle.internal.MojoDescriptorCreator.getMojoDescriptor(MojoDescriptorCreator.java:222) >>> > at >>> > >>> >>> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:106) >>> > at >>> > >>> >>> org.apache.maven.lifecycle.internal.DefaultLifecycleTaskSegmentCalculator.calculateTaskSegments(DefaultLifecycleTaskSegmentCalculator.java:86) >>> > at >>> > >>> >>> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:98) >>> > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319) at >>> > org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at >>> > org.apache.maven.cli.MavenCli.execute(MavenCli.java:534) at >>> > org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at >>> > org.apache.maven.cli.MavenCli.main(MavenCli.java:141) 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.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) >>> > at >>> > >>> >>> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) >>> > at >>> > >>> >>> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) >>> > at >>> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) >>> > >>> > Since documentation for the 4.x are not exactly same as the current >>> folder >>> > structure i tried the same command inside trunk/weblogger-webapp >>> > But i got ( this time tomcat started.) >>> > >>> > >>> > [org.apache.derby.client.am.DisconnectException: >>> > java.net.ConnectException : Error opening socket to server localhost >>> > on port 3223 with message : Connection refused >>> > at org.apache.derby.client.net.NetAgent.<init>(Unknown Source) >>> > at org.apache.derby.client.net.NetConnection.newAgent_(Unknown Source) >>> > at org.apache.derby.client.am.Connection.<init>(Unknown Source) >>> > at org.apache.derby.client.net.NetConnection.<init>(Unknown Source) >>> > >>> > >>> > So what is the correct folder to issue the command to run development >>> > testing? Have i missed anything.? >>> > >>> > And also i would like to thank for the documentation provided in such >>> > a comprehensive manner. >>> > >>> > >>> > -- >>> > Shelan Perera >>> > >>> > Blog : http://www.shelanlk.com >>> > Twitter: shelan >>> > skype :shelan.perera >>> > gtalk :shelanrc >>> > >>> > I am the master of my fate: >>> > I am the captain of my soul. >>> > *invictus* >>> >> >> >> >> -- >> Shelan Perera >> >> Blog : http://www.shelanlk.com >> Twitter: shelan >> skype :shelan.perera >> gtalk :shelanrc >> >> I am the master of my fate: >> I am the captain of my soul. >> *invictus* >> >> >> >> >> >> >> >> > > > -- > Shelan Perera > > Blog : http://www.shelanlk.com > Twitter: shelan > skype :shelan.perera > gtalk :shelanrc > > I am the master of my fate: > I am the captain of my soul. > *invictus* >
