[java-sig-commits] [Bug 825782] New version resolver doesn't work

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=825782

Stanislav Ochotnicky <sochotni at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |juan.hernandez at redhat.com,
                   |                            |mgoldman at redhat.com
          Component|maven                       |jboss-jts
           Assignee|sochotni at redhat.com         |juan.hernandez at redhat.com

--- Comment #1 from Stanislav Ochotnicky <sochotni at redhat.com> ---
So, after some investigation this failure was caused by jboss-jts pom files
specifying exact jboss-as version as a dependency. Since these pom files were
then used during the build of jboss-as itself, maven couldn't find exact
version in reactor, or local repository because it referenced older version. 

Originally it used to work, due to maven ignoring versions even in situations
where it should not, such as working with reactor or local repository. Due to
this maven fix, jboss-jts caused issues.

Various solutions exists, most clean one is probably to update/patch jboss-jts
with each upstream jboss-as release. I believe even a simple sed should do the
trick here, since version string is unique enough and so the maintenance of
this modification will be easy.

-- 
You are receiving this mail because:
You are on the CC list for the bug.