[WFLY-12377] Document usage of JAXWS Client BOM in jaws-* quickstarts

[emmartins]

Issue: https://issues.jboss.org/browse/WFLY-12377

[fabiobrz]

LGTM, I'd wait for a last ack from @snelluli1

[emmartins]

I believe compatible is proper in this case, compliant usually implies there is something like a spec to follow and here it's just a matter of dependency version compatibility.

…

On Wed, 2 Oct 2019 at 09:05, fabiobrz ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In jaxws-addressing/client/pom.xml <#363 (comment)>: > @@ -44,6 +44,11 @@ <artifactId>jaxws-addressing-service</artifactId> <classifier>classes</classifier> </dependency> + <!-- The JAXWS Client BOM provides management dependencies compatible with the app server, + useful for building, testing or debugging JAXWS client applications. Import it to the app's pom.xml + dependencyManagement and then set dependencies on specific artifacts, or alternatively simply set + a single dependency on it, for the app to depend on all the artifacts it manages, as done here. + --> @emmartins <https://github.com/emmartins>, @snelluli1 <https://github.com/snelluli1>, just a second thought on the above mentioned last sentence. Maybe "compliant" would be more appropriate than "compatible"? Just checking here, WDYT? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#363?email_source=notifications&email_token=AAEDY6DJ6SUFYDPLM3CXVRLQMRI4VA5CNFSM4I22GQM2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCGS27JI#discussion_r330416985>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAEDY6AXSYXKVNT2JMWAESTQMRI4VANCNFSM4I22GQMQ> .

[fabiobrz]

Right @emmartins, last reply makes sense to me.

[emmartins]

thanks both