[wildfly-dev] Finally Released wildfly-maven-plugin

[Bill Burke]

Ok, awesome.

On 2/14/2014 12:03 PM, James R. Perkins wrote:
> Maybe I'm misunderstanding. The default configuration for the plugin
> works. At least in all the tests I've done. The port was changed to a
> default of 9990 which the ModelControllerClient will use the
> http-remoting protocol for. I did add an option to override the protocol
> if desired.
>
> I was wrong yesterday when I said it used the management interface. I
> made a bad assumption that it was doing that without really looking at
> how the ModelControllerClient connects. It looks like by default the
> http-remoting protocol is used unless the port is 9999 which then
> defaults to remoting. Of course that can be overridden, but if the
> protocol is left null that's the path it takes.
>
> If I'm missing something please let me know. It definitely wouldn't
> surprise me if I'm missing something obvious here :)
>
> On 02/14/2014 07:53 AM, Bill Burke wrote:
>> I'm saying anybody that is using, or wants to use it may think "It
>> doesn't work!" because the native mgmt interface is off in the Wildfly
>> distro.  And thus, the 1000 questions....
>>
>> On 2/14/2014 10:51 AM, James R. Perkins wrote:
>>> Ha, indeed. In the case it doesn't work I'm just using GitHub issues for
>>> it at this point. Pinging me directly is fine too or this ML.
>>>
>>> On 02/14/2014 05:08 AM, Bill Burke wrote:
>>>> Expect 1000 questions of "Why doesn't this work?"
>>>>
>>>> On 2/14/2014 1:51 AM, James R. Perkins wrote:
>>>>> It's late, but the wildfly-maven-plugin 1.0.0.Final was released.
>>>>>
>>>>> Not much has changed since the 7.5.Final of the jboss-as-maven-plugin.
>>>>> It's mainly a repackage and change of the goal prefix.
>>>>>
>>>>> See the docs https://docs.jboss.org/wildfly/plugins/maven/latest/.
>>>>>
>

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com