You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All of these dependencies should be in the runtime scope, but it appears that the default maven plugin doesn't include the dependencies in the compile configuration by default in the runtime scope, see this thread
The behavior is expected. Parent configurations won't be considered when mapping configurations to scopes (doing so wouldn't work for 'compile' and 'runtime', for example). I recommend to change the way you share common dependencies, but I'd have to know/see more about your current solution to give concrete recommendations.
Experimenting locally with the maven-publish plugin gives promising results
The text was updated successfully, but these errors were encountered:
for this pom looks OK. compile scope is the default and most common scope
in maven. runtime is rarely used and the only thing I might make different
it the runtime slf4j-siimple dependency - leaving it out completely. but it
is not a big deal as it is.
missing dependencies is diffferent topic
I added this last night to make sure I didn't forget it. I may be misattributing the classloader errors I was seeing to the difference in what I expected from the pom. Part of why I assumed the compile scope was wrong is due to the jruby-gradle-plugin not having anything in that scope.
The currently released pom:
All of these dependencies should be in the runtime scope, but it appears that the default
maven
plugin doesn't include the dependencies in thecompile
configuration by default in theruntime
scope, see this threadExperimenting locally with the
maven-publish
plugin gives promising resultsThe text was updated successfully, but these errors were encountered: