On 29/05/14 11:24, Kabir Khan wrote:
On 29 May 2014, at 11:09, Darran Lofthouse <darran.lofthouse(a)jboss.com> wrote:
> +1 If we have the capability I think we should be providing the option
> for it to be used.
> An additional point, size is not the only motivation for a patch - using
> a patch means the end users don't need to start with a clean install if
> they have an existing installation.
Yes, apart from just standalone.xml, carrying over JDBC drivers (and probably other
things I forget) should be useful too
Deployments, vault instances, key and trust stores, properties files
containing their users, integration as a service on their os, tweaked
memory settings ....
And I am sure I have missed another bunch of things an end user may have
added to a clean distro ;-)
> Darran Lofthouse.
> On 29/05/14 01:12, James R. Perkins wrote:
>> If both isn't a huge deal, I say both.
>> On 05/28/2014 02:48 PM, Dimitris Andreadis wrote:
>>> IMO, if the patch is almost as big as the full distro itself, that kind of
>>> purpose. But you could provide both distros anyway and see from the download
>>> people are actually interested in, and maybe get some feedback on the patch
>>> On 28/05/2014 23:23, Jason Greene wrote:
>>>> So we noticed two problems with releasing the patch for 8.1.0.Final
>>>> 1. JBoss Tools Issues - Due to the patching mechanism in 8.0.0.Final
“disabling" jars, applying the 8.1 patch will lead to warnings, this is fixed in
their upcoming beta2 test. We have also removed the jar “disabling”, so future patches do
not have this problem.
>>>> 2. It’s Big - Due to the breadth of change in this release, the size of
the patch is only slightly smaller than the distro. We have a planned improvement to
support finer grained, per-class deltas, which would greatly reduce the size, but its not
worth holding the release over (IMO).
>>>> So the big question is assuming the above do you want a patch file for
8.1, or just a full distro only this time, and we instead ship a patch in a future 8.x
release (we are considering doing an 8.2 with the CDI update that was pulled out of 8.1
due to TCK rules)?
>>>> If there is enough demand considering 1 & 2 I would be happy to
>>>> Jason T. Greene
>>>> WildFly Lead / JBoss EAP Platform Architect
>>>> JBoss, a division of Red Hat
>>>> wildfly-dev mailing list
>>> wildfly-dev mailing list
> wildfly-dev mailing list