Interestingly, it does not fail in IDE(intellij).
It fails on mvn prompt as Tomohisa mentioned.
after running mvn clean on the prompt and fire the test on IDE, it is ok.
i did not dive into it yet.
this is my initial observation.
On Thu, May 10, 2018 at 1:16 AM, Tomohisa Igarashi
wrote:
> Yep, a
Github user WillemJiang closed the pull request at:
https://github.com/apache/camel/pull/2330
---
Not sure if we can leverage travis to do this kind of work.
As camel build is a little bit longer one by one, if we can run the
component tests in parallel that you could save us lot of time.
Willem Jiang
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
T
Yep, actually this fails for me. I noticed that I get this weird exception when
I run "mvn test -Dtest=GreaterTest"
-
WARNING - Unable to scrape for @Stateful, @Stateless, @Singleton or
@MessageDriven annotations. AnnotationFinder failed.
java.lang.RuntimeException
Hi Cameleers,
so it's not that bad[1] 77 tests failed in total. I think we need to
play with opening up some modules a bit. I'm a bit sad that it takes 9
hours for the job to run, when we add JDK 11 I would expect it to take
13 hours, would be nice if there was a way to just run the tests in
parall
On Wed, May 9, 2018 at 5:40 PM, Onder SEZGIN wrote:
> I can help with some of them by tomorrow.
Awesome, thank you. I think Tomohisa is also taking a look. Now only
the camel-ejb tests are failing[1]. Its strange I can't reproduce this
locally, other failures were pretty straightforward to fix, I
GitHub user pablomarambio opened a pull request:
https://github.com/apache/camel/pull/2330
Duplicated component name
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pablomarambio/camel patch-1
Alternatively you can review and ap
I can help with some of them by tomorrow.
On Wed, 9 May 2018 at 17:56, Pascal Schumacher
wrote:
> Hi Zoran,
>
> thank you very much for fixing this. :)
>
> -Pascal
>
> Am 09.05.2018 um 10:10 schrieb Zoran Regvart:
> > Hi Cameleers,
> > we managed to get the Ceylon example to compile without the
Hi Zoran,
thank you very much for fixing this. :)
-Pascal
Am 09.05.2018 um 10:10 schrieb Zoran Regvart:
Hi Cameleers,
we managed to get the Ceylon example to compile without the JAR
artefact being attached to the Maven reactor, this was required by the
Ceylon Maven plugin's goal to import depe
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2329
---
Hi Zoran,
it sounds good to me.
Thanks !
Regards
JB
On 09/05/2018 11:45, Zoran Regvart wrote:
Hello Cameleers,
I've created a build that will run once every day to run tests on JDK
9 and 10[1], the configuration for the build is in
`Jenkinsfile.daily`[2].
Suggestions and contributions are we
Hello Cameleers,
I've created a build that will run once every day to run tests on JDK
9 and 10[1], the configuration for the build is in
`Jenkinsfile.daily`[2].
Suggestions and contributions are welcome :)
zoran
[1] https://builds.apache.org/view/A-D/view/Camel/job/Camel.daily/
[2]
https://git
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2318
---
Hi Cameleers,
we managed to get the Ceylon example to compile without the JAR
artefact being attached to the Maven reactor, this was required by the
Ceylon Maven plugin's goal to import dependencies. You can take a look
at this commit[1] for the details of the workaround.
Now we have 21 tests that
14 matches
Mail list logo
