Re: [jdf-dev] BOM to JBDS
Hi,
I don't think it's unfriendly. It simply adds SwitchYard
dependencies to the user's pom. It's up to the user to have their repositories
configured correctly so the dependencies can be resolved. In this case, it looks like a
transitive dependency is missing from the configured repositories.
Right. This was why I asked the question - I assumed that the tooling wasn't
automatically adding a BOM.
That was how it looked to me. Something in the dependency chain
requires that GAV, but it isn't available from any of the repositories, which is why I
redirected the issue to the build guys.
EAP transitive dependencies aren't necessarily correct in the POM's - the
artifacts referenced might be missing from the public repository . You
*must* use the IP and EAP BOM's to override POM transitive dependencies.
Also, from FSW 6.1.0 onward, dependencies in our POM's won't necessarily
be available either.
So, the fix is to make sure that a BOM is configured in the project. How
do we get this into the current versions, and how do we synchronise this
for the next versions (where I assume that we'll have the -with-switchyard
and -with-s-ramp, etc. developer BOM's.)?
Thanks,
J
--
Red Hat
Newcastle upon Tyne