Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1126
---
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 enab
The Apache Jenkins build system has built Camel.trunk.notest (build #2846)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2846/
to view the results.
The Apache Jenkins build system has built Camel.2.17.x.notest (build #109)
Status: Fixed
Check console output at https://builds.apache.org/job/Camel.2.17.x.notest/109/
to view the results.
GitHub user xldai opened a pull request:
https://github.com/apache/camel/pull/1126
fix CAMEL-10249
upgrade hawtdispatch-version to 1.22
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xldai/camel patch-2
Alternatively you can rev
The Apache Jenkins build system has built Camel.trunk.notest (build #2845)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2845/
to view the results.
I think this is pretty much the same issue as I asked for in
http://mail-archives.apache.org/mod_mbox/camel-dev/201607.mbox/%3ccago7ob0quxjfrkj+tjmkaxcqe94_dkp4-ud7m4osq-gk6d1...@mail.gmail.com%3E
- but it did not get any response.
2016-08-17 17:17 GMT+02:00 Jean-Yves BESSON (JIRA) :
>
> [ ht
Also Claus, I found a mixture of per-release-line SNAPSHOTS and per-release
SNAPSHOTs in our repo:
https://repository.apache.org/content/groups/snapshots/org/apache/camel/camel-core.
Not sure if this is intentional or not.
This is what we have for 2.17.x. I think your expectations are not met
anyw
Hi Claus,
I see your point, but the vast majority of Apache TLP projects are
publishing SNAPSHOTs per-release, not per version line.
Spark, Kafka, Zookeeper, Aries, Karaf, CXF, Maven, etc. publish per-version
SNAPSHOTs. I've only found AMQ, Flink and Tomcat doing it like us.
The maintenance/stor
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1125
---
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 enab
Hi
I want the SNAPSHOT to stay as-is on the source code, and only do the
.0 on the release builds.
Having a plethora of .0-SNAPSHOT .1-SNAPSHOT .2-SNAPSHOT is a pain to
work with, and having to prune/remove old versions becomes a
maintenance problem.
Using -SNAPSHOT then its easy to be assure it
Hey Claus,
We can change it now via the versions:set goal. That way we'll start
publishing snapshots under 2.18.0-SNAPSHOT already.
We should also prune 2.18-SNAPSHOT from the ASF Snapshots repo, to make the
build fail for those who might be using it. That'll make them investigate
and upgrade, ra
Hi
Yeah the Camel releases has always been as currently. But I do think
its better practice to have a .0 so its always 3 digits.
We can maybe start this from Camel 2.18.0 onwards.
I assume its "just" a matter when the RC is cut then the version
number typed for the Maven command should be 2.18.0
12 matches
Mail list logo
