Motivation: Right now users need to set Maven Actions to "magic" (undocumented) values in order to get Netbeans to accept Maven-based servers. Some features, like profiling code launched by Maven-based servers is not even possible yet (see bug #200771).

Adding a full-fledged entry for Maven servers would treat such servers as first-class citizens.

PS: I use Jetty as my web server because I'm shipping a desktop application with an embedded web server. I can't use conventional web servers such as Tomcat or Glassfish. Historically Maven-based servers are used primarily for testing, but there is a need to support them as a server for the main codebase.

It's worth noting I launch Jetty in one of two ways:

1. Initially I used the jetty:run goal
2. Now I use:

      <plugin>
        <groupId>org.codehaus.mojo</groupId>
        <artifactId>exec-maven-plugin</artifactId>
        <version>1.2</version>
        <executions>
          <execution>
            <goals>
              <goal>exec</goal>
            </goals>
          </execution>
        </executions>
        <configuration>
          <executable>java</executable>
          <arguments>
            <argument>-classpath</argument>
            <classpath/>
            <argument>-Djava.library.path=${project.build.directory}/dependency/jperipheral/windows-i386-vs10-debug/lib</argument>
            <argument>-ea</argument>
            <argument>com.muxlab.vitex.database.server.Main</argument>
          </arguments>
        </configuration>
      </plugin>

because I plan on wrapping com.muxlab.vitex.database.server.Main in a native executable when I ship the product. jetty:run is well suited for getting started but I believe eventually everyone who is embedding Jetty has to replace it with a main() class.

Martin, something to think about.

*** Bug 216109 has been marked as a duplicate of this bug. ***