omarsmak merged pull request #1: Change to camel bom
URL: https://github.com/apache/camel-examples/pull/1
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use
davsclaus commented on issue #1: Change to camel bom
URL: https://github.com/apache/camel-examples/pull/1#issuecomment-585210233
Yay this is very good.
Later we should add the BOM to each example so the end user only have the
pom of each example to worry about. But this is a great
omarsmak opened a new pull request #1: Change to camel bom
URL: https://github.com/apache/camel-examples/pull/1
This changes to Camel BOM instead of using Camel parent. Next is to move
specific examples building tools from main camel repo to the examples repo.
FYI @davsclaus @oscerd
ppalaga closed issue #159: Consider importing camel-bom in camel-quarkus-bom
URL: https://github.com/apache/camel-quarkus/issues/159
This is an automated message from the Apache Git Service.
To respond to the message, please
ppalaga commented on issue #159: Consider importing camel-bom in
camel-quarkus-bom
URL: https://github.com/apache/camel-quarkus/issues/159#issuecomment-527653807
Sent https://github.com/quarkusio/quarkus/pull/3836 that adds
`CreateExtensionMojo.additionalRuntimeDependencies` that can be
ppalaga commented on issue #159: Consider importing camel-bom in
camel-quarkus-bom
URL: https://github.com/apache/camel-quarkus/issues/159#issuecomment-526197649
Not a good idea, because availability of all Camel components might be
misunderstood by the end user as all those components
ppalaga opened a new issue #159: Consider importing camel-bom in
camel-quarkus-bom
URL: https://github.com/apache/camel-quarkus/issues/159
Consider importing camel-bom in camel-quarkus-bom instead of managing the
Camel components ourselves.
Pros:
* This would make the life
Github user PascalSchumacher closed the pull request at:
https://github.com/apache/camel/pull/2009
---
GitHub user PascalSchumacher opened a pull request:
https://github.com/apache/camel/pull/2009
camel-bom: fix relative path to parent pom
This should fix the build failures on build.apache.org, e.g.:
https://builds.apache.org/view/C/view/Apache%20Camel/job
other BOMs w.r.t.
> transitive dependencies.
>
> It is generated and maintained automatically by filtering out what's
> "not-our-stuff" from camel-parent.
>
> We have been asked to provide a Camel BOM like that for start.spring.io few
> months ago, but I de
s only Camel modules and
not third-party modules, so it can be included in a end-user application or
also into another library without creating conflicts with other BOMs w.r.t.
transitive dependencies.
It is generated and maintained automatically by filtering out what's
"not-our-stuff&quo
Github user tdiesler closed the pull request at:
https://github.com/apache/camel/pull/1444
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is en
GitHub user tdiesler opened a pull request:
https://github.com/apache/camel/pull/1444
[CAMEL-10787] Camel BOM does not export lucene
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tdiesler/camel CAMEL-10787
Alternatively you
13 matches
Mail list logo