search

nikgoodley-ibboost / jstd-maven-plugin

Automatically exported from code.google.com/p/jstd-maven-plugin
0 stars 0 forks source link

Plugin attempts to start server even when server is already running #19

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start a JSTD server via command prompt and capture a browser on that server. 
2. Install jstd-maven-plugin and run it using the command mvn jstd:test.
3. Observe: Build fails, because the server is already running.

What is the expected output? What do you see instead?
Expected: Tests run against the persistent server specified in the 
<configuration><server> node. 
Actual: Tests fail to run because the server is already running:

WARNING: Attempt to start a started server
Dec 28, 2012 2:57:14 PM com.google.jstestdriver.JsTestDriverServerImpl$JettyLife
CycleLogger lifeCycleStarting
FINE: Server starting
Dec 28, 2012 2:57:14 PM com.google.jstestdriver.JsTestDriverServerImpl$JettyLife
CycleLogger lifeCycleFailure
WARNING: Server failed
java.net.BindException: Address already in use: JVM_Bind

What version of the product are you using? On what operating system?
JSTD 1.3.5, maven 2, Windows 7.

Please provide any additional information below.
This occurs when the persistent server is running on localhost. I haven't 
tested it against an external server yet. I tested this using localhost and 
127.0.0.1, both fail with the same error noted above.

Original issue reported on code.google.com by dylanbut...@gmail.com on 28 Dec 2012 at 11:01

GoogleCodeExporter commented 9 years ago 
Here's the rest of the error message:

[ERROR] Failed to execute goal com.googlecode.jstd-maven-plugin:jstd-maven-plugi
n:1.3.2.5:test (default-cli) on project [project-name]: Failed to pa
rse results -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal c
om.googlecode.jstd-maven-plugin:jstd-maven-plugin:1.3.2.5:test (default-cli) on
project [project-name]: Failed to parse results
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:217)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)...

Original comment by dylanbut...@gmail.com on 28 Dec 2012 at 11:02

GoogleCodeExporter commented 9 years ago 
I am unable to recreate this issue with the latest version of the plugin, 
1.3.5.1. When using a server that is already running, please make sure that no 
port is specified in your POM or Maven command line properties. Specifying a 
port tells JSTD to start up a server on that port.

Original comment by nateredd...@gmail.com on 18 Mar 2013 at 2:09