Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 699690 Details for
Bug 912786
Need to release note that some quickstarts ship with the beta version of Shrinkwrap resolver which is not supported
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Email discussion around this issue.
ShrinkwrapResolver.txt (text/plain), 16.40 KB, created by
sgilda
on 2013-02-19 21:51:31 UTC
(
hide
)
Description:
Email discussion around this issue.
Filename:
MIME Type:
Creator:
sgilda
Created:
2013-02-19 21:51:31 UTC
Size:
16.40 KB
patch
obsolete
>Return-Path: pmuir@redhat.com >Received: from zmta05.collab.prod.int.phx2.redhat.com (LHLO > zmta05.collab.prod.int.phx2.redhat.com) (10.5.81.12) by > zmail12.collab.prod.int.phx2.redhat.com with LMTP; Tue, 19 Feb 2013 > 11:06:39 -0500 (EST) >Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) > by zmta05.collab.prod.int.phx2.redhat.com (Postfix) with ESMTP id 728EFF2658; > Tue, 19 Feb 2013 11:06:39 -0500 (EST) >Received: from [10.3.231.107] (vpn-231-107.phx2.redhat.com [10.3.231.107]) > by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id r1JG5i0q006420 > (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); > Tue, 19 Feb 2013 11:06:37 -0500 >Content-Type: text/plain; charset=us-ascii >Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) >Subject: Re: [wfk] Shrinkwrap resolver >From: Pete Muir <pmuir@redhat.com> >In-Reply-To: <8A834AA6-865E-43B0-A351-32CB2105D033@redhat.com> >Date: Tue, 19 Feb 2013 16:06:38 +0000 >Cc: Mustafa Musaji <mmusaji@redhat.com>, Sande Gilda <sgilda@redhat.com>, > wfk-pm-list <wfk-pm-list@redhat.com>, > Andrew Lee Rubinger <arubinge@redhat.com> >Content-Transfer-Encoding: quoted-printable >Message-Id: <3DC74205-E384-4F20-972C-4AF713E862FF@redhat.com> >References: <1634199967.26985987.1361284623787.JavaMail.root@redhat.com> <8A834AA6-865E-43B0-A351-32CB2105D033@redhat.com> >To: Burr Sutter <bsutter@redhat.com> >X-Scanned-By: MIMEDefang 2.67 on 10.5.11.12 > >Sande, will you do this or should I? > >On 19 Feb 2013, at 15:30, Burr Sutter <bsutter@redhat.com> wrote: > >> Release notes at a minimum - Sande, Pete - can one of you create the = >BZ listing the impacted quickstarts by name and appropriate text as to = >the value of the resolver and why it is tech preview for now? >>=20 >> We could put that text in every impacted readme.md (each quickstart) = >but that becomes a maintenance burden. At least in the release notes it = >gives GSS something to point to if the customer asks a question about = >the technology. >>=20 >> On Feb 19, 2013, at 9:37 AM, Mustafa Musaji wrote: >>=20 >>> Thanks for the solution Burr. This seems the best way forward given = >the circumstances. >>>=20 >>> Where would this be labelled as a tech preview? Release Notes? >>>=20 >>> Thanks >>> Mus >>>=20 >>> ----- Original Message ----- >>>> From: "Burr Sutter" <bsutter@redhat.com> >>>> To: "Pete Muir" <pmuir@redhat.com> >>>> Cc: "Sande Gilda" <sgilda@redhat.com>, "wfk-pm-list" = ><wfk-pm-list@redhat.com>, "Andrew Lee Rubinger" >>>> <arubinge@redhat.com> >>>> Sent: Tuesday, 19 February, 2013 1:35:59 PM >>>> Subject: Re: [wfk] Shrinkwrap resolver >>>>=20 >>>>=20 >>>> On Feb 19, 2013, at 7:41 AM, Pete Muir wrote: >>>>=20 >>>>>=20 >>>>> On 19 Feb 2013, at 12:40, Burr Sutter <bsutter@redhat.com> wrote: >>>>>=20 >>>>>>=20 >>>>>> On Feb 18, 2013, at 12:08 PM, Karel Piwko wrote: >>>>>>=20 >>>>>>> It can go Final when we have documentation and guides. There are >>>>>>> two factors blocking us: >>>>>>> 1/ I don't have any spare resources at this moment to write those >>>>>>> 2/ Arquillian guides are migrated to Asciidoc right now, which >>>>>>> even complicates 1/ >>>>>>>=20 >>>>>>> That said, I don't think we can release Final in such time to be >>>>>>> able to make it TP for WFK 2.2 unless somebody else will write >>>>>>> the guides/docs. >>>>>>>=20 >>>>>>> On Feb 18, 2013, at 5:54 PM, Mustafa Musaji <mmusaji@redhat.com> >>>>>>> wrote: >>>>>>>=20 >>>>>>>> Even if it's marked as Final I'd prefer it if we can mark this >>>>>>>> as a private component in some way. =46rom what Karel says, it's >>>>>>>> only used to run tests we ship, so we would say it's not part >>>>>>>> of the tests themselves but only used to build the test. >>>>>>>=20 >>>>>>> Sorry, I did not use correct wording here. It as used to build >>>>>>> test archives, and as such, it is a part of Java code for every >>>>>>> test class. >>>>>>>=20 >>>>>>>>=20 >>>>>>>> Do we want to support this or is it just because we are shipping >>>>>>>> it? >>>>>>>>=20 >>>>>>> I think the problem is that we do not support it, but we ship it >>>>>>> in the test code and pom.xml of every DeltaSpike example. >>>>>>=20 >>>>>> Only the Deltaspike quickstarts? >>>>>>=20 >>>>>> Or all EAP & WFK quickstarts? >>>>>=20 >>>>> Anything that needs to bundle a lib in it's war/ear, and wants to >>>>> use arquillian tests to test functionality in that lib. >>>>>=20 >>>>> This has mostly come up for DS quickstarts, but it's used for a few >>>>> EAP quickstarts as well. >>>>=20 >>>> OK - so we need to get this Shrinkwrap resolver to Final instantly. >>>> :-) >>>>=20 >>>> The community can make it final, without docs. >>>> The product can label it as Tech Preview, without docs. >>>> We can close the loop on this hole in time for WFK 2.2 and EAP >>>> 6.1.Alpha? >>>>=20 >>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>>>=20 >>>>>>>> Regards >>>>>>>> Mus >>>>>>>>=20 >>>>>>>> -------------- >>>>>>>> Mustafa Musaji >>>>>>>> Software Maintenance Engineer >>>>>>>> Red Hat UK Ltd >>>>>>>> 200 Fowler Avenue, Farnborough Business Park, Farnborough, Hants >>>>>>>> GU14 7JP >>>>>>>>=20 >>>>>>>> Registered in England and Wales under Company Registration No. >>>>>>>> 03798903 >>>>>>>> Directors: Michael Cunningham (USA), Brendan Lane (Ireland), >>>>>>>> Matt Parson (USA), Charlie Peters (USA) >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> ----- Original Message ----- >>>>>>>>> From: "Pete Muir" <pmuir@redhat.com> >>>>>>>>> To: "Mustafa Musaji" <mmusaji@redhat.com> >>>>>>>>> Cc: "Sande Gilda" <sgilda@redhat.com>, "Andrew Lee Rubinger" >>>>>>>>> <arubinge@redhat.com>, "wfk-pm-list" >>>>>>>>> <wfk-pm-list@redhat.com> >>>>>>>>> Sent: Monday, 18 February, 2013 4:39:04 PM >>>>>>>>> Subject: Re: [wfk] Shrinkwrap resolver >>>>>>>>>=20 >>>>>>>>> Err, Final >>>>>>>>>=20 >>>>>>>>> On 18 Feb 2013, at 16:38, Pete Muir <pmuir@redhat.com> wrote: >>>>>>>>>=20 >>>>>>>>>> Andrew, Karel, when can this get to FINAL? >>>>>>>>>>=20 >>>>>>>>>> This is developer tooling, so it would be fine to include as >>>>>>>>>> Tech >>>>>>>>>> Preview if that makes the support load easier. >>>>>>>>>>=20 >>>>>>>>>> On 18 Feb 2013, at 09:11, Mustafa Musaji <mmusaji@redhat.com> >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>>>> 1) Is ShrinkWrap Resolver out as a FINAL yet or is it still >>>>>>>>>>>> in >>>>>>>>>>>> Beta? >>>>>>>>>>>=20 >>>>>>>>>>> The reason I ask this is because if it's a BETA, we can't >>>>>>>>>>> claim to >>>>>>>>>>> support it. We need the documentation and guides to be ready >>>>>>>>>>> as >>>>>>>>>>> supporting something means it's part of a paid subscription >>>>>>>>>>> and >>>>>>>>>>> customer expect this. >>>>>>>>>>>=20 >>>>>>>>>>> Regards >>>>>>>>>>> Mus >>>>>>>>>>>=20 >>>>>>>>>>> -------------- >>>>>>>>>>> Mustafa Musaji >>>>>>>>>>> Software Maintenance Engineer >>>>>>>>>>> Red Hat UK Ltd >>>>>>>>>>> 200 Fowler Avenue, Farnborough Business Park, Farnborough, >>>>>>>>>>> Hants >>>>>>>>>>> GU14 7JP >>>>>>>>>>>=20 >>>>>>>>>>> Registered in England and Wales under Company Registration >>>>>>>>>>> No. >>>>>>>>>>> 03798903 >>>>>>>>>>> Directors: Michael Cunningham (USA), Brendan Lane (Ireland), >>>>>>>>>>> Matt >>>>>>>>>>> Parson (USA), Charlie Peters (USA) >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> ----- Original Message ----- >>>>>>>>>>>> From: "Mustafa Musaji" <mmusaji@redhat.com> >>>>>>>>>>>> To: "Andrew Lee Rubinger" <arubinge@redhat.com> >>>>>>>>>>>> Cc: "Sande Gilda" <sgilda@redhat.com>, "wfk-pm-list" >>>>>>>>>>>> <wfk-pm-list@redhat.com>, "Karel Piwko" <kpiwko@redhat.com> >>>>>>>>>>>> Sent: Monday, 18 February, 2013 9:06:19 AM >>>>>>>>>>>> Subject: Re: [wfk] Shrinkwrap resolver >>>>>>>>>>>>=20 >>>>>>>>>>>> Sorry I'm late to the party... >>>>>>>>>>>>=20 >>>>>>>>>>>> 1) Is ShrinkWrap Resolver out as a FINAL yet or is it still >>>>>>>>>>>> in >>>>>>>>>>>> Beta? >>>>>>>>>>>>=20 >>>>>>>>>>>> 2) If it's used to only build our examples/quickstarts and >>>>>>>>>>>> not >>>>>>>>>>>> run >>>>>>>>>>>> them (correct?) can we mark it as "internal/private" in the >>>>>>>>>>>> docs >>>>>>>>>>>> (i.e. unsupported)? >>>>>>>>>>>>=20 >>>>>>>>>>>> We can discuss this in more detail on the PM call this >>>>>>>>>>>> afternoon. >>>>>>>>>>>>=20 >>>>>>>>>>>> Regards >>>>>>>>>>>> Mus >>>>>>>>>>>>=20 >>>>>>>>>>>> -------------- >>>>>>>>>>>> Mustafa Musaji >>>>>>>>>>>> Software Maintenance Engineer >>>>>>>>>>>> Red Hat UK Ltd >>>>>>>>>>>> 200 Fowler Avenue, Farnborough Business Park, Farnborough, >>>>>>>>>>>> Hants >>>>>>>>>>>> GU14 >>>>>>>>>>>> 7JP >>>>>>>>>>>>=20 >>>>>>>>>>>> Registered in England and Wales under Company Registration >>>>>>>>>>>> No. >>>>>>>>>>>> 03798903 >>>>>>>>>>>> Directors: Michael Cunningham (USA), Brendan Lane (Ireland), >>>>>>>>>>>> Matt >>>>>>>>>>>> Parson (USA), Charlie Peters (USA) >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> ----- Original Message ----- >>>>>>>>>>>>> From: "Andrew Lee Rubinger" <arubinge@redhat.com> >>>>>>>>>>>>> To: "Karel Piwko" <kpiwko@redhat.com> >>>>>>>>>>>>> Cc: "Sande Gilda" <sgilda@redhat.com>, "wfk-pm-list" >>>>>>>>>>>>> <wfk-pm-list@redhat.com> >>>>>>>>>>>>> Sent: Thursday, 14 February, 2013 4:03:56 PM >>>>>>>>>>>>> Subject: Re: [wfk] Shrinkwrap resolver >>>>>>>>>>>>>=20 >>>>>>>>>>>>> To be clear from a tech/support perspective, SWR is now >>>>>>>>>>>>> 2.0.0-beta-2, >>>>>>>>>>>>> API locked and thus supportable. Documentation and some >>>>>>>>>>>>> guides >>>>>>>>>>>>> are >>>>>>>>>>>>> the only thing left before progressing this to CR and then >>>>>>>>>>>>> Final. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> S, >>>>>>>>>>>>> ALR >>>>>>>>>>>>>=20 >>>>>>>>>>>>> ----- Original Message ----- >>>>>>>>>>>>> From: "Karel Piwko" <kpiwko@redhat.com> >>>>>>>>>>>>> To: "Pete Muir" <pmuir@redhat.com> >>>>>>>>>>>>> Cc: "Marek Schmidt" <maschmid@redhat.com>, "Andrew Lee >>>>>>>>>>>>> Rubinger" >>>>>>>>>>>>> <arubinge@redhat.com>, "Sande Gilda" <sgilda@redhat.com>, >>>>>>>>>>>>> "Rafael >>>>>>>>>>>>> Benevides" <benevides@redhat.com>, "wfk-pm-list" >>>>>>>>>>>>> <wfk-pm-list@redhat.com> >>>>>>>>>>>>> Sent: Thursday, February 14, 2013 8:27:04 AM >>>>>>>>>>>>> Subject: Re: Shrinkwrap resolver >>>>>>>>>>>>>=20 >>>>>>>>>>>>> On Thu, 14 Feb 2013 14:45:20 +0000 >>>>>>>>>>>>> Pete Muir <pmuir@redhat.com> wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On 14 Feb 2013, at 14:23, Marek Schmidt wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> (adding wfk-pm-list to CC) >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Do we have a fat enough warning sign for this kind of >>>>>>>>>>>>>>> stuff? >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Given that we are trying to push for "support defined by >>>>>>>>>>>>>>> examples" I >>>>>>>>>>>>>>> suggest we be very careful about letting unsupported >>>>>>>>>>>>>>> features >>>>>>>>>>>>>>> slip into >>>>>>>>>>>>>>> the examples. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> We generally are. Unfortunately, shrinkwrap resolver is >>>>>>>>>>>>>> something >>>>>>>>>>>>>> it's >>>>>>>>>>>>>> basically impossible to not use :-( I'm not aware of >>>>>>>>>>>>>> anything >>>>>>>>>>>>>> else >>>>>>>>>>>>>> like this. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> We have quite strict restrictions on how we deal with >>>>>>>>>>>>>>> tech >>>>>>>>>>>>>>> preview >>>>>>>>>>>>>>> features (e.g. the need to have them in a separate file >>>>>>>>>>>>>>> in the >>>>>>>>>>>>>>> customer >>>>>>>>>>>>>>> portal, etc.) and marking something as "not supported" >>>>>>>>>>>>>>> feels >>>>>>>>>>>>>>> like >>>>>>>>>>>>>>> something that should be even more strict... >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> I admit that I am not quite sure how exactly the >>>>>>>>>>>>>>> "example-based >>>>>>>>>>>>>>> support" >>>>>>>>>>>>>>> applies to the quickstarts' test suites, but since we do >>>>>>>>>>>>>>> certify >>>>>>>>>>>>>>> arquillian, I'd expect that a customer would expect the >>>>>>>>>>>>>>> arquillian/shrinkwrap features present in the >>>>>>>>>>>>>>> quickstarts' >>>>>>>>>>>>>>> tests >>>>>>>>>>>>>>> to be >>>>>>>>>>>>>>> supported as well. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Proposals welcome. It's definitely something we need to >>>>>>>>>>>>>> address. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> We need opinion from GSS. >>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Marek S. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> On 02/14/2013 03:09 PM, Karel Piwko wrote: >>>>>>>>>>>>>>>> Hi, >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> resurrecting the thread. There is already 2.0.0-beta-2 >>>>>>>>>>>>>>>> out. I >>>>>>>>>>>>>>>> think we can >>>>>>>>>>>>>>>> leave it in (JDF/DeltaSpike) quickstarts and put a big >>>>>>>>>>>>>>>> fat >>>>>>>>>>>>>>>> warning we do >>>>>>>>>>>>>>>> not support that in WFK, because we have no other tool >>>>>>>>>>>>>>>> to be >>>>>>>>>>>>>>>> used anyway. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> We will need to upgrade quickstarts and boms to use this, >>>>>>>>>>>>>> currently >>>>>>>>>>>>>> we are on >>>>>>>>>>>>>> version 1. Can you file a JDF issue. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> https://issues.jboss.org/browse/JDF-205 >>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> We would add support in next WFK 2.3 release. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> This would help *a lot*. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> How does it sound? >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Karel >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> On Wed, 16 Jan 2013 05:03:03 -0500 (EST) >>>>>>>>>>>>>>>> Andrew Lee Rubinger <arubinge@redhat.com> wrote: >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> Path to product for ShrinkWrap Resolvers should be the >>>>>>>>>>>>>>>>> next >>>>>>>>>>>>>>>>> available wave >>>>>>>>>>>>>>>>> after we go to Beta shortly. Our alpha cycle is long >>>>>>>>>>>>>>>>> to >>>>>>>>>>>>>>>>> prove >>>>>>>>>>>>>>>>> the API, >>>>>>>>>>>>>>>>> and the implementation has been fairly stable and >>>>>>>>>>>>>>>>> well-tested >>>>>>>>>>>>>>>>> throughout. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> SWR 2.0.0-alpha-7 out today, and Karel and I will be >>>>>>>>>>>>>>>>> discussing >>>>>>>>>>>>>>>>> the move >>>>>>>>>>>>>>>>> to Beta and API lock over the next few weeks. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> S, >>>>>>>>>>>>>>>>> ALR >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> ----- Original Message ----- >>>>>>>>>>>>>>>>> From: "Pete Muir" <pmuir@redhat.com> >>>>>>>>>>>>>>>>> To: "Karel Piwko" <kpiwko@redhat.com> >>>>>>>>>>>>>>>>> Cc: "Marek Schmidt" <maschmid@redhat.com>, "Andy >>>>>>>>>>>>>>>>> Rubinger" >>>>>>>>>>>>>>>>> <arubinge@redhat.com>, "Sande Gilda" >>>>>>>>>>>>>>>>> <sgilda@redhat.com>, >>>>>>>>>>>>>>>>> "Rafael >>>>>>>>>>>>>>>>> Benevides" <benevides@redhat.com> Sent: Tuesday, >>>>>>>>>>>>>>>>> January 15, >>>>>>>>>>>>>>>>> 2013 >>>>>>>>>>>>>>>>> 11:45:48 AM Subject: Re: Shrinkwrap resolver >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> Got it. We have been using this a bit in JDF >>>>>>>>>>>>>>>>> quickstarts. >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> There is no other way to sanely do what the resolver >>>>>>>>>>>>>>>>> does, >>>>>>>>>>>>>>>>> so >>>>>>>>>>>>>>>>> I'm not sure >>>>>>>>>>>>>>>>> how to replace it in the quickstarts... >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>> On 3 Jan 2013, at 07:10, Karel Piwko wrote: >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> Hey Pete, >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> ShrinkWrap resolver is currently not a part of any WFK >>>>>>>>>>>>>>>>>> certification. I'd >>>>>>>>>>>>>>>>>> personally recommend customers to use 2.0.0-X stream >>>>>>>>>>>>>>>>>> though, >>>>>>>>>>>>>>>>>> if they >>>>>>>>>>>>>>>>>> want to experiment with it. >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> We are very close to have a beta release in January >>>>>>>>>>>>>>>>>> and I'm >>>>>>>>>>>>>>>>>> personally >>>>>>>>>>>>>>>>>> aiming getting code and documentation ready to a be a >>>>>>>>>>>>>>>>>> part >>>>>>>>>>>>>>>>>> of >>>>>>>>>>>>>>>>>> WFK 2.3 >>>>>>>>>>>>>>>>>> release. >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> Karel >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>> On Fri, 21 Dec 2012 10:44:24 +0000 >>>>>>>>>>>>>>>>>> Pete Muir <pmuir@redhat.com> wrote: >>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> Hey Karel >>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> Marek said you are the man for this. Should we be >>>>>>>>>>>>>>>>>>> recommending >>>>>>>>>>>>>>>>>>> customers to use this? Is it part of Arquillian in >>>>>>>>>>>>>>>>>>> WFK? If >>>>>>>>>>>>>>>>>>> so, what >>>>>>>>>>>>>>>>>>> version? >>>>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>>>> Pete >>>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Marek Schmidt >>>>>>>>>>>>>>> Seam/Weld QE Lead >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>=20 >>>>=20 >>>>=20 >>>>=20 >>=20 >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 912786
: 699690