this is typical as the profile is not considered part of the build unless
activated.
However, it seems reasonable to adjust profile dependencies in the way you
indicated, so I'd say it's a bug you can file.
To workaround it, I suggest putting the value in a property outside the
profile so that it
hi there
while executing release:prepare the versions of dependencies to
submodules are adjusted correct. but they're just adapted to the new
version if they are not defined within a profile section.
the profile 'jboss' was activated correct. i've checked that with
help:active-profiles.
---
