when dependencies are missing, can we report to the user exactly what kinds of
jars are typically required?
-----------------------------------------------------------------------------------------------------------
Key: CAMEL-1311
URL: https://issues.apache.org/activemq/browse/CAMEL-1311
Project: Apache Camel
Issue Type: Improvement
Reporter: James Strachan
Fix For: 2.0.0
See this tweet ...
http://twitter.com/casron/statuses/1172707316
not exactly sure how we can do it though :) I wonder if when we know there is a
class missing, we can deduce some groupId + artifact Id that is typically
missing, then we can report on the jars (and the dependencies) missing for that
group ID and artifact ID? e.g. if we know that (say) XStream jar is missing,
can we report the camel-xstream dependencies that are missing?
This typically occurs when we use the apache-camel uber-jar and then the
converters can't be registered due to the dependencies not being there. So how
about adding (say) camel-xstream knows that jars it requires and has some kinda
way (through Maven / OSGi tooling) to auto-generate a list of missing jars?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
