O.K. the cause of the problem was that I forgot to add the camel-quickfix
module back to the module list again (Thanks Dan) which's done now:
http://svn.apache.org/viewvc?view=revision&revision=1347418
I triggered a manual build for "Camel.trunk.fulltest.java7" to see how it
will go now.
@Claus
Hi
Sorry for the inconvenience!
I've got no idea why it can't download the artifacts as it did perfectly
build for me both on OS X and WIN. It's all here:
http://repo.marketcetera.org/maven/quickfixj/quickfixj-all/1.5.2-bd/
Anyway, I've just deleted my m2 cache and run a full build right now to
Oh and that was in the assembly part, eg at the end
Or if you do a
cd apache-camel
mvn clean install
then it should build the assembly, and thus you should be able to
trigger this issue as well.
On Thu, Jun 7, 2012 at 5:53 AM, Claus Ibsen wrote:
> Hi
>
> This breaks the build as the JAR canno
Hi
This breaks the build as the JAR cannot be downloaded.
I just did a
mvn clean install -Dtest=false
from the root of the project dir.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.3:process
(default) on project apache-camel: Failed to resolve depende
The Apache Jenkins build system has built Camel.trunk.notest (build #1560)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1560/
to view the results.
On Wednesday, June 06, 2012 05:14:01 PM Babak Vahdat wrote:
> Hi Christian
>
> according to what I've read many times by this thread I assumed we do
> always skip running the OSGi tests on CI-Servers so why I did already
> check-in the update for QuickFIX/J but apparently I did misunderstand
> som
Hi Christian
according to what I've read many times by this thread I assumed we do always
skip running the OSGi tests on CI-Servers so why I did already check-in the
update for QuickFIX/J but apparently I did misunderstand something here.
I'm also puzzled about the last JDK7 build:
https://build
We have to wait for a few SMX bundle releases (at present, we have SNAPSHOT
dependencies in our features definitions)...
Best,
Christian
On Wed, Jun 6, 2012 at 3:39 PM, Babak Vahdat wrote:
> Hi
>
> Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
> camel-quickfix module is n
The issues@ list was created in November 2011.
Don't let it trouble you, it may mean we understand each other without the
need of words... ;-)
It's good to see the user@ list still grows.
Best,
Christian
On Wed, Jun 6, 2012 at 10:51 AM, Claus Ibsen wrote:
> Hi
>
> Maybe the decline in posts on
Hi
Upgrade to QuickFIX/J 1.5.2 is already done (CAMEL-5334). As well the
camel-quickfix module is now enabled again on the Jenkins
(Camel.trunk.fulltest.java7).
I did test both on OS X as well as WIN (JDK 6 & JDK 7). So let's see how it
will go through the next build...
Babak
Claus Ibsen-2 wro
I'll be doing release dry runs today.
Hadrian
On 05/07/2012 10:27 AM, Claus Ibsen wrote:
Hi
I think its time we start close down on a Camel 2.10 release. The
2.9.0 release was on January 1sy 2012, so its been 4.5 months since
that release. Yes in between there has been 2 patch releases, eg
2.9.
Hi Bilgin,
Thanks a lot for your feedback!
Makes me happy to see others arguing the same thing as me :-)
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/About-what-to-do-with-the-Response-retrieved-through-a-Producer-when-the-Exchange-is-NOT-out-capable-tp5713946p57140
Hi
I don't see anything strange on this as there was no Hokuspokus I did by the
following revision :-)
http://svn.apache.org/viewvc?view=revision&revision=1300914
Through introducing a dedicated by camel-msv POM we instruct
Maven to pick from here:
[1]
http://svn.apache.org/repos/asf/servicemi
Hi Babak,
I think your example makes perfect sense and if the exchange pattern
is InOnly one should not be able to set the body of the OUT.
If the API is less friendly, then the users will be able to figure out
easily what Christian said "the component should check the MEP and put
the response in
Hi,
I've fixed a link in Spring Integration wiki.
I supposed that "spring integration endpoints" link in "The
spring-integration: component provides a bridge for Camel components
to talk to spring integration endpoints" should point to the Spring
Integration project page [1], not the the Camel's
Hi
Maybe the decline in posts on @dev is because we created the @issues
list for all the JIRA notifications?
I cant remember though how far back we did that.
On Tue, Jun 5, 2012 at 12:22 AM, Christian Müller
wrote:
> Hello all!
>
> I prepared the Apache board report for June 2012 [1]. Please, t
On Tue, Jun 5, 2012 at 5:36 PM, Claus Ibsen wrote:
> Hi
>
> The Apache CI server on Camel trunk with java7, had an issue at the end.
> I think its related to that Maven 3.0.4 issue with that camel-msv
> component (I think it was that one).
> So I configured it to use Maven 3.0.3 instead, just to s
17 matches
Mail list logo
