You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2009/02/03 19:14:00 UTC

[jira] Created: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?

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.

[jira] Commented: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?

Posted by "Carson McDonald (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/activemq/browse/CAMEL-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49109#action_49109 ] 

Carson McDonald commented on CAMEL-1311:
----------------------------------------

So I think the real issue here is that some of the optional parts log exceptions trying to find dependencies but don't fail. Looking at the logs can become confusing because of these exceptions since they aren't really meaningful. It could work just to hide those exceptions since you are already logging the fact that the part won't work without more dependencies. This led me to think that if I was told that I'm including x.jar that won't work because I don't have the dependencies needed I would just go and remove x.jar. I don't want the dependency list for x.jar, I just want to know that it needs to be removed unless I add the dependencies it needs to function. 

> 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.

[jira] Assigned: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?

Posted by "Willem Jiang (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/CAMEL-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang reassigned CAMEL-1311:
-----------------------------------

    Assignee: Willem Jiang

> 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
>            Assignee: Willem Jiang
>             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.

[jira] Commented: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?

Posted by "James Strachan (JIRA)" <ji...@apache.org>.

    [ https://issues.apache.org/activemq/browse/CAMEL-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=49105#action_49105 ] 

James Strachan commented on CAMEL-1311:
---------------------------------------

BTW a quick workaround is to just not use the uber jar.

Maybe the documentation needs to recommend folks don't use it unless they understand the dependencies?

> 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.

[jira] Updated: (CAMEL-1311) when dependencies are missing, can we report to the user exactly what kinds of jars are typically required?

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.

     [ https://issues.apache.org/activemq/browse/CAMEL-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-1311:
-------------------------------

    Fix Version/s:     (was: 2.0.0)
                   2.1.0

> 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
>            Assignee: Willem Jiang
>             Fix For: 2.1.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.