Re: [wildfly-dev] Maven 3.3.1+ coming to wildfly and wildfly-core
Hi *,
I have just sent the PR to wildfly:
https://github.com/wildfly/wildfly/pull/9577
As agreed here on wildfly-dev, the PR adapts the build.* and
integration-tests.* scripts to use mvnw and keeps those old scripts for
backwards compatibility.
The README was changed to recommend plain mvn or mvnw rather than the
old build.* scripts.
Scott, James, Petr and others please review and eventually test in your
scenarios.
Thanks,
Peter
On 2017-01-12 09:53, Peter Palaga wrote:
The PR https://github.com/wildfly/wildfly-core/pull/2017 got merged
in
WF Core (thanks Brian!) and I am going to prepare a similar PR for WF. -- P
On 2016-12-14 09:36, Peter Palaga wrote:
> Hi Scott, OK, let's keep the build.(sh|bat) scripts for now. I'll change
> them (1) to wrap mvnw and (2) to print a warning that they are
> deprecated in favor of mvnw. -- P
>
> On 2016-12-14 01:04, Scott Marlow wrote:
>> Hi Peter,
>>
>> On Tue, Dec 13, 2016 at 5:26 PM, Peter Palaga <ppalaga(a)redhat.com> wrote:
>>> Hi James,
>>>
>>> On 2016-12-13 22:51, James Perkins wrote:
>>>> Hi Peter,
>>>> It may not be a big deal because it's just for builds, but instead
of
>>>> deleting the build.(sh|bat) maybe we just make those invoke the
>>>> appropriate mvnw command instead.
>>>
>>> That would be easy to do, but can you name a situation where it would
>>> actually matter?
>>
>> We have a few (compliance) test scripts that invoke build.sh to build
>> the app server from source. I'm not sure how widespread use of
>> build.sh is in other test environments but we probably could ask that
>> question via a separate topic.
>>
>> Scott
>>
>
> _______________________________________________
> 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