This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 252387 - Generate maven plugin for WildFly application server
Summary: Generate maven plugin for WildFly application server
Status: NEW
Alias: None
Product: serverplugins
Classification: Unclassified
Component: WildFly (show other bugs)
Version: 8.1
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: ehsavoie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-13 16:38 UTC by arungupta
Modified: 2015-05-15 17:18 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description arungupta 2015-05-13 16:38:32 UTC 
If WildFly is chosen as an application server for a Java EE maven project, then WildFly maven plugin should be included in the generated pom.xml. The fragment would look like:

<project>
    ...
    <build>
        ...
        <plugins>
            ...
            <plugin>
                <groupId>org.wildfly.plugins</groupId>
                <artifactId>wildfly-maven-plugin</artifactId>
                <version>1.1.0.Alpha1</version>
            </plugin>
            ...
        </plugins>
        ...
    </build>
...
</project>

Its explained at: http://docs.jboss.org/wildfly/plugins/maven/latest/examples/deployment-example.html
Comment 1 ehsavoie 2015-05-15 16:43:26 UTC 
I'm not sure about that as :
 1/ Getting the "right" version of the maven plugin is error prone
 2/ What's the use of the Maven plugin as it may mess things with the current netbeans plugin
Comment 2 arungupta 2015-05-15 17:18:08 UTC 
Pick the latest version of WildFLy plugin at the time of NetBeans plugin release.

Adding to NetBeans project will allow me to run the project outside NetBeans easily as well.