Damn project was renamed to wildfly-maven-plugin but I totally forgot to put that in the release notes. Egg -> My face https://github.com/wildfly/wildfly-maven-plugin Sent from my iPhone > On Feb 12, 2014, at 8:21 PM, Bill Burke <bburke(a)redhat.com&gt; wrote: > > FYI: Because native mgmt interface is no longer on by default > jboss-as-maven-plugin no longer works OTB. Any tests, demos, > quickstarts, tutorials that rely on this will also not work anymore. > > -- > Bill Burke > JBoss, a division of Red Hat > http://bill.burkecentral.com > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev _______________________________________________ wildfly-dev mailing list wildfly-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/wildfly-dev

I knew it existed, but I didn't try it as its been in beta for a LOOONNNNGGGG time and I figured it had the same problems. It still sucks I can't use jboss-as-maven-plugin OTB. I'll try it out. Am I supposed to have the native mgmt interface set up to be able to use it? I couldn't see any switches that allows you to use the HTTP interface. On 2/13/2014 4:14 AM, Eduardo Martins wrote: > Should also be noted that the jboss-as.port property changed to wildfly.port, and that since the default port is now 9090, targeting another node that was started with a port offset needs that property updated to the correct value, for instance a port offset of 100, as used by several quickstarts, now needs -Dwildfly.port=10090 instead of -Djboss-as.port=10099 > > So an egg in my face too, since I have been changing this in wildfly/quickstarts and didn’t remember that when you asked contributions to the release notes... > > —E > > On 13 Feb 2014, at 03:22, Jason T. Greene <jgreene(a)redhat.com&gt; wrote: > >> Damn project was renamed to wildfly-maven-plugin but I totally forgot to put that in the release notes. >> >> Egg -> My face >> >> https://github.com/wildfly/wildfly-maven-plugin >> >> Sent from my iPhone >> >>> On Feb 12, 2014, at 8:21 PM, Bill Burke <bburke(a)redhat.com&gt; wrote: >>> >>> FYI: Because native mgmt interface is no longer on by default >>> jboss-as-maven-plugin no longer works OTB. Any tests, demos, >>> quickstarts, tutorials that rely on this will also not work anymore. >>> >>> -- >>> Bill Burke >>> JBoss, a division of Red Hat >>> http://bill.burkecentral.com >>> _______________________________________________ >>> wildfly-dev mailing list >>> wildfly-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/wildfly-dev >> _______________________________________________ >> wildfly-dev mailing list >> wildfly-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/wildfly-dev

On 2/13/2014 12:13 PM, James R. Perkins wrote: > Yeah, sorry. I'm planning on doing a release of the wildfly-maven-plugin > today. I was going to do it yesterday, but I was waiting to hear > something back from a contributor. > > Yes, it uses the native management interface. I do have a plan to look > at the HTTP interface, but I just haven't had a chance. At this point > it's essentially the same as the jboss-as-maven-plugin only renamed and > repackaged. > > FWIW too you can still use the jboss-as-maven-plugin you just need to > pass the jboss-as.port, e.g. -Djboss-as.port=9990, or set it in the > plugin configuration, <port>9990</port>. > No you can't use 9990. HTTP interface runs on port 9990. Plus, you have to edit standalone.xml to add the now missing native management interface.

Is there any reason other than port reduction for removing the native mgmt interface? Can we put it back please?