Hey,
org.apache.maven.lifecycle.LifecycleExecutionException: Mojo error occurred:
Connection refused: connect
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:56
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecuto
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycle
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:282)
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.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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Mojo error
occurred: Connection refused: connect
at
org.codehaus.mojo.jboss.AbstractDeployerMojo.doURL(AbstractDeployerMojo.java:101)
at org.codehaus.mojo.jboss.DeployMojo.execute(DeployMojo.java:40)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:53
... 16 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at
java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.Socket.connect(Socket.java:518)
at java.net.Socket.connect(Socket.java:468)
Rick
On Thu, Aug 14, 2008 at 7:58 AM, Martin Gainty <[EMAIL PROTECTED]> wrote:
>
> Rick-
> please display stacktrace from your logMartin
> ______________________________________________ Disclaimer and
> confidentiality note Everything in this e-mail and any attachments relates
> to the official business of Sender. This transmission is of a confidential
> nature and Sender does not endorse distribution to any party other than
> intended recipient. Sender does not necessarily endorse content contained
> within this transmission. > Date: Thu, 14 Aug 2008 07:45:03 -0400> From:
> [EMAIL PROTECTED]> To: [email protected]> Subject: Re: Deploying war
> to JBOSS using maven> > could be. I am going to dig and just as an FYI let
> you know. Thanks and> appreciate your response!> > Rick> > On Wed, Aug 13,
> 2008 at 6:34 PM, Siarhei Dudzin <[EMAIL PROTECTED]>wrote:> > > On
> Thu, Aug 14, 2008 at 12:18 AM, Ricky <[EMAIL PROTECTED]> wrote:> >> > >
> Hi,> > >> > > Thanks for your reply. I used jboss:harddeploy and it worked
> for me.> > > However> > > i see that jboss:start doesnt actually start the
> server. Am i missing> > > something?> >> >> > I never used jboss plugin so I
> can't tell why it doesn't start.> >> >> > > and also jboss:deploy vs hard
> deploy whats the difference?> >> >> > No idea, but I can imagine is that
> jboss:deploy is deployment via jmx> > deployer and hard deploy is just
> dropping the artifact to the hot> > deployment> > directory of jboss.> >> >
> Siarhei> >
> _________________________________________________________________
> Your PC, mobile phone, and online services work together like never before.
> http://clk.atdmt.com/MRT/go/108587394/direct/01/
