Re: [jboss-as7-dev] How to verify a patches for non-public AS
Yes of course. I'm talking about a patch that applies to the 7.1 code base only.
A commit that cannot be made in jboss-as, but only in jboos-eap.
A fix to the R4V42 OSGi Framework.
In AS8 we have the R5 Framework.
On Apr 17, 2013, at 1:23 PM, Darran Lofthouse <darran.lofthouse(a)jboss.com> wrote:
The overall upstream is the master branch of jboss-as
On 17/04/13 12:09, Thomas Diesler wrote:
> … and where is upstream for EAP-6.x ?
>
> I think it is jboss-eap/6.x <https://github.com/jbossas/jboss-eap>;, and
> not jboss-as/7.1 <https://github.com/jbossas/jboss-as/tree/7.1>
>
> On Apr 17, 2013, at 1:04 PM, Heiko Braun <hbraun(a)redhat.com
> <mailto:hbraun@redhat.com>> wrote:
>
>>
>>
>> If the patch needs to be upstream first, the upstream build can be
>> used to verified it, no?
>>
>>
>>
>> On Apr 17, 2013, at 1:02 PM, Thomas Diesler <thomas.diesler(a)jboss.com
>> <mailto:thomas.diesler@jboss.com>> wrote:
>>
>>> All would be good if the reporter can verify the patch before it goes
>>> in the next EAP release, can he?
>>
>
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thomas Diesler
> JBoss OSGi Lead
> JBoss, a division of Red Hat
> xxxxxxxxxxxxxxxxxxxxxxxxxxxx
>
>
>
>
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx