All,
We were thinking of just releasing with jboss-as.version set to the SNAPSHOT of the target
AS7 release and then overriding this property if/when the tests are ran against the final
release, by passing -Djboss-as.version=<final version> to the build command line.
Unless anyone can point out a problem with this approach, or suggest an improvement,
we'll just go with that.
Paul.
On 18 Sep 2012, at 09:55, Paul Robinson <paul.robinson(a)redhat.com> wrote:
Brian,
I don't think forwards compatibility can be guaranteed. We've had a few problems
in the past where the the jboss-as-arquillian-container-managed dependency was set to a
different version of AS7 to that which we were testing against.
Here's a specific example:
https://issues.jboss.org/browse/JBTM-1243 and
https://github.com/jbosstm/quickstart/pull/18/files for the fix. In this example we were
using the jboss-javaee-6.0-with-tools bom to get the jboss-as-arquillian-container-managed
dependency version. This bom set the version to 7.1.1.Final, which failed to work with
7.2.0.Alpha1-SNAPSHOT. So, in this case we would need to match up the releases.
I don't recall the specifics of other occasions, but it's certainly happened to
us a few times.
Paul.
On 17 Sep 2012, at 16:24, Brian Stansberry <brian.stansberry(a)redhat.com> wrote:
> Does JBossTS need to use the same arquillian container version as is
> included with the latest AS? I'm no Arquillian expert, but it seems like
> if that's required something has gone wrong with our Arquillian
> integration. Seems like the idea would be to make these containers
> forward compatible.
>
> Apologies if I'm all wet here.
>
> On 9/17/12 10:12 AM, Paul Robinson wrote:
>> All,
>>
>> JBoss transactions uses Arquillian for some of the project tests.
>> Therefore JBossTS has a dependency on AS7 (for the Arquillian container
>> dependency), but as AS7 consumes JBossTS, the target AS7 version is not
>> available when we do the release of JBossTS. We get around this at the
>> moment by referencing a SNAPSHOT version of AS7 in the Arquillian
>> container dependency. However, this does mean that our release will
>> reference the SNAPSHOT dependency.
>>
>> This must be a common issue that other projects have. I was wondering
>> what the accepted pattern was to solve this issue?
>>
>> Paul.
>>
>> --
>> Paul Robinson
>> Web service transactions lead
>> paul.robinson(a)redhat.com <mailto:paul.robinson@redhat.com>
>>
>> JBoss, a Division of Red Hat
>> Registered in England and Wales under Company Registration No. 03798903
>> Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
>> (USA), Charlie Peters (USA)
>>
>>
>>
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>>
>
>
> --
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Paul Robinson
Web service transactions lead
paul.robinson(a)redhat.com
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)
_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
--
Paul Robinson
Web service transactions lead
paul.robinson(a)redhat.com
JBoss, a Division of Red Hat
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham (USA), Brendan Lane (Ireland), Matt Parson
(USA), Charlie Peters (USA)