CODEWITHSUNDEEP
mavenjakarta-eepluginswildfly
Cooper
Cooper

Reputation: 226

Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.0.Final:deploy (default-cli) on project

I am working on a maven multi-module project Java EE 7 having the following folder structure.

+---parent-module
    +---module-domain
    +---module-service
    +---module-web

I want to configure the Wildfly maven plugin to deploy/undeploy aps to Wildfly app server 8.0.0 and this is the pom.xml ( in the parent module's pom):

    <plugin>
                    <groupId>org.wildfly.plugins</groupId>
                    <artifactId>wildfly-maven-plugin</artifactId>
                    <version>1.0.0.Final</version>

                    <configuration>
                        <hostname>127.0.0.1</hostname>
                        <port>9990</port>
                        <username>admin</username>
                        <password>admin</password>
                        <!-- <jbossHome>C:/tools/wildfly-8.0.0.Final</jbossHome> -->
                    </configuration>
</plugin>

this is the log :

Failed to execute goal org.wildfly.plugins:wildfly-maven-plugin:1.0.0.Final:deploy (default-cli) on project .....Reason: I/O Error could not execute operation '{
[ERROR] "operation" => "read-attribute",
[ERROR] "address" => [],
[ERROR] "name" => "launch-type"
[ERROR] }': java.net.ConnectException: JBAS012144: Could not connect to http-remoting://127.0.0.1:9990. The connection timed out

====>Any clue please?

Thanks

Upvotes: 4

Views: 14096

Answers (3)

bkomac
bkomac

Reputation: 1200

There could be some dependency problems. Try to deploy your app manually via admin console, to see if some problems exist during deploy.

enter image description here

In my case I left some libraries as provided.

Upvotes: 1

James R. Perkins
James R. Perkins

Reputation: 17780

With the information provided in the comments I think you're misunderstanding the goals a bit. The wildfly-maven-plugin is really used to fully manage a container. When you execute mvn wildfly:start the server process that was created is shutdown when maven exits. This is likely why you can't connect as there is no server running.

Not part of the answer, but feel free to file an issue indicating you'd like to have the start goal not exit after maven exits. I'm likely not opposed to adding a boolean property which can be set to true that will leave the process running.

Upvotes: 1

Harald Wellmann
Harald Wellmann

Reputation: 12865

Looks like the WildFly server is not running. Did you start it manually, or do you also use wildfly:start in your POM?

Upvotes: 2

Related Questions