Hi Gregor
Sorry for adding that CS error this morning. I guess the extra text in
that exception message may have caused the line to be too long?
I noticed some Maven WARNs about some examples was a bit wrong with
bundle vs jar. So I aligned them and just pushed.
I will step away from the computer
The Apache Jenkins build system has built Camel.trunk.notest (build #3171)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3171/
to view the results.
Hi Claus,
I am still working on the release, just found some CS issues.
I am using a different box now, because the OOME problems were
definitely caused by some issues with the machine I was using
previously.
Will keep you posted.
Thanks,
Gregor
On Sat, Apr 22, 2017 at 11:02 AM, Claus Ibsen
The Apache Jenkins build system has built Camel.trunk.notest (build #3170)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3170/
to view the results.
Hi
Yeah that can be an idea. I assume this is for developers from the command line?
CI servers etc will still use the maven version they have been
instructed in their jobs.
We may also consider bumping up the lowest Maven version number that
we have in the root pom as the pre-requisite. Its 3.2.5
Hi Claus,
On Sat, Apr 22, 2017 at 10:03 AM, Claus Ibsen wrote:
> Thanks for sharing this. I think when the vote is open we should post
> this on the Camel front page, eg on May 1st.
this works for me, I was just thinking that we should put an
announcement in the interim if someone is wondering w
Hi Claus,
On Sat, Apr 22, 2017 at 10:14 AM, Claus Ibsen wrote:
> Anyone tried using the new Maven 3.5.0 and build the Camel source code
> with that. And if so any feedback?
I've used it when testing Java 9 issues (using
docker.io/maven:3.5.0-jdk-9), worked without issues.
Perhaps we should cons
The Apache Jenkins build system has built Camel.trunk.notest (build #3169)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3169/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3168)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3168/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3167)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3167/
to view the results.
Hi
Building the release candidate takes up a lot of memory and Gregor has
hit a OOME with 6gb.
We are cleaning up a bit in the project to upgrade some of the maven
plugins to use newer versions and reduce some cruft in the assembly.
On Sat, Apr 22, 2017 at 9:20 AM, Claus Ibsen wrote:
> Hi
>
>
The Apache Jenkins build system has built Camel.trunk.notest (build #3166)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3166/
to view the results.
Hi,
I've started using Maven 3.5.0 recently and so far I haven't found any
issues with it on Camel development (I'm using macOS). Once you switch to
it you should be amazed that Maven output gets colorful :-)
On Sat, Apr 22, 2017 at 5:14 PM, Claus Ibsen wrote:
> Hi
>
> I have been using the old
The Apache Jenkins build system has built Camel.trunk.notest (build #3165)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3165/
to view the results.
Hi
I have been using the old/stable Maven 3.2.5 for a rather long time.
And Maven 3.3.3 should be good as well since that is what the CI
servers are using.
Anyone tried using the new Maven 3.5.0 and build the Camel source code
with that. And if so any feedback?
--
Claus Ibsen
Hi
Thanks for sharing this. I think when the vote is open we should post
this on the Camel front page, eg on May 1st.
On Fri, Apr 21, 2017 at 12:32 PM, Zoran Regvart wrote:
> Hi Cameleers,
>
> I would like to post this to the news section of the site and to the
> users mailing list:
> "
> The Ca
Hi
As a side note I listened to a podcast 424 about open source
conferences and it was a good show.
I personally likely wont have time in June as my life take a turn as I
am moving to a new house (and back to Denmark) in the summer.
If the show is about Camel 10 years it would be good to see if
The Apache Jenkins build system has built Camel.trunk.notest (build #3164)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3164/
to view the results.
Hi
Looking at the CI tests then they all look good (blue/green)
https://builds.apache.org/view/A-D/view/Camel/
.. except for the spring-boot tests which had two tests for
camel-core-xml and camel-spring-dm which does not make sense at all so
I have removed them. This should make this job blue as
Hi Gregor
I can see you committed some fixed last evening.
Do you think that you found all the "bugs" in terms of building a
release candidate, or do we have more problems?
On Fri, Apr 21, 2017 at 9:22 PM, Gregor Zurowski
wrote:
> Hi Claus,
>
> Thanks for taking care of this. I will start bui
Hello all.
I need some help with the enrich EIP.
When im using it i have seen an error like this
org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
33 in XML document from URL
[bundle://296.49:0/META-INF/spring/camel-context.x
21 matches
Mail list logo
