Hi
You are welcome to log a JIRA / provide a patch / github PR to correct this
http://camel.apache.org/contributing
On Thu, Aug 18, 2016 at 9:15 PM, Moon, John wrote:
> Found the issue, you assume the parent folder is named "camel" in
> SpringBootHelper.java (line 53).
>
> public static File c
The Apache Jenkins build system has built Camel.trunk.notest (build #2847)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2847/
to view the results.
Hi Claus,
Any further thoughts?
This is becoming an ongoing problem in my projects and I'd appreciate your
views before making any changes.
Cheers!
On 17 Aug 2016 15:22, "Raul Kripalani" wrote:
> Also Claus, I found a mixture of per-release-line SNAPSHOTS and
> per-release SNAPSHOTs in our re
Found the issue, you assume the parent folder is named "camel" in
SpringBootHelper.java (line 53).
public static File camelProjectRoot(File baseDir) {
try {
File root = baseDir.getCanonicalFile();
while (root != null && !root.getName().equals("camel")) {
Trying to do a full build in the master branch but getting this error. My
commandline looks like this:
mvn clean install -Pfastinstall -pl '!etc' -Dmaven.test.skip=true
[ERROR] Failed to execute goal
org.apache.camel:camel-package-maven-plugin:2.18-SNAPSHOT:prepare-spring-boot-starter
(valida
https://issues.apache.org/jira/browse/LOG4J2-905
This looks relevant.
On 18 August 2016 at 10:51, Luca Burgazzoli wrote:
> I'll ask the log4j guys, thx for spotting this.
>
> ---
> Luca Burgazzoli
>
>
> On Thu, Aug 18, 2016 at 5:37 PM, Antonin Stefanutti
> wrote:
> > Hi Luca,
> >
> > I’ve just
Github user trobert closed the pull request at:
https://github.com/apache/camel/pull/1127
---
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 ena
I'll ask the log4j guys, thx for spotting this.
---
Luca Burgazzoli
On Thu, Aug 18, 2016 at 5:37 PM, Antonin Stefanutti
wrote:
> Hi Luca,
>
> I’ve just encountered an issue when using the date function that gets
> substituted by Log4j 2 and causes the exception below to be thrown.
>
> It happe
GitHub user trobert opened a pull request:
https://github.com/apache/camel/pull/1127
fix moduleClassNames attribute wiring in JSonDataFormat
`moduleClassNames` is not taken into account in ``
This commit fix this.
Please can you backport to 2.17 too ? thanks
You ca
Hi Luca,
I’ve just encountered an issue when using the date function that gets
substituted by Log4j 2 and causes the exception below to be thrown.
It happens in a number of situations:
- when a route definition containing the date function get logged (in DEBUG
level)
- when an advice is being a
10 matches
Mail list logo
