[wildfly-dev] jboss-as-maven-plugin no longer works OTB

[James R. Perkins]

On 02/13/2014 09:24 AM, Bill Burke wrote:
>
> 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.
You're correct, I should have thought of that :) I will be releasing a 
final version of the plugin today if that helps at all.
>
> Is there any reason other than port reduction for removing the native
> mgmt interface?  Can we put it back please?
That I can't answer. I'm fairly ignorant in that area.

-- 
James R. Perkins
Red Hat JBoss Middleware