Java Reference
In-Depth Information
<version>2.3</version>
<configuration>
<ejbVersion>3.2</ejbVersion>
<!-- Generate ejb-client for client project
-->
<generateClient>true</generateClient>
</configuration>
</plugin>
</plugins>
</build>
In the first part of the XML fragment, we specified the project's
finalName
attribute,
which will dictate the name of the packaged artifact (in our example, the project's name
corresponds to our project's artifact ID, so it will be named
ticket-agency-
ejb.jar
).
The artifact ID named
wildfly-maven-plugin
will actually trigger the WildFly
Maven plugin that will be used to deploy our project.
So, once you have configured the WildFly plugin, your application can be deployed auto-
matically by entering from your project root. This can be done by typing the following
command in the console:
mvn wildfly:deploy
Since deployment is a repetitive task for a developer, it would be convenient to execute
this operation from within the Eclipse environment. All you need is to create a new
Run
Configurations
setting from the upper menu by navigating to
Run
|
Run Configura-
tions
.
Enter the project's base directory (hint: the
Browse Workspace...
utility will help you
pick up the project from your project list) and type your Maven goal into the
Goals
text-
box, as shown in the following screenshot:
