[
https://issues.apache.org/jira/browse/CAMEL-4125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13054509#comment-13054509
]
Hadrian Zbarcea commented on CAMEL-4125:
----------------------------------------
@Claus, I think you made some implicit assumptions that support your statement
above. I think what we need to clarify is why do we ship the full apache-camel
and how we intend users to use it. So if users download the full assembly they
have everything to do what?
If they use maven and get the source distro, building everything is one 'mvn
install' away. In an osgi environment our features use mvn: for resolving the
bundles. So I understand that you believe they not everything belongs in there
because the distro is targeting some users (I assume those who deploy
standalone or in app servers) who only need the dependencies from one package
to add them to the lib directory of their application (and hence things like
features, archetypes or camel-core-xml are useless). If that's the assumption I
understand the point, but then our binary distro is nothing more than a
convenient way of having all the camel jars in one place.
Or to put it differently, you're claiming that if you use maven, why bother
with the distro, if not doesn't matter that maven related artifacts are missing
from the distro. Did I get it right?
> Some components missing from final assemblies
> ---------------------------------------------
>
> Key: CAMEL-4125
> URL: https://issues.apache.org/jira/browse/CAMEL-4125
> Project: Camel
> Issue Type: Task
> Components: build system
> Reporter: Daniel Kulp
> Assignee: Daniel Kulp
> Fix For: 2.8.0
>
> Attachments: CAMEL-4125.txt
>
>
> The camel-dns, camel-core-xml, and camel-karaf-commands jars are not part of
> the final binary assembly. Patch forthcoming.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
