Hi
Now the major changes has been implemented (first 3 items from roadmap)
http://camel.apache.org/camel-27-roadmap.html
I think we should post a note on the 2.6 release notes about the
change moving forward.
Also we should consider adding a news post on the camel website as well.
eg about jdk 1
[
https://issues.apache.org/jira/browse/CAMEL-2229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-2229.
Resolution: Fixed
Fix Version/s: (was: 3.0.0)
2.7.0
Assignee:
[
https://issues.apache.org/jira/browse/CAMEL-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991740#comment-12991740
]
Stan Lewis commented on CAMEL-2853:
---
Will have a look, the test doesn't appear to show t
Yes, the package names must change, no matter what.
Yes, the camel tent at apache-extras is empty now, as it is for most other
projects. Only a few started to take advantage of it.
I will figure out this week what is the best way to move the project. That is,
can we actually move it or we shoul
[
https://issues.apache.org/jira/browse/CAMEL-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991517#comment-12991517
]
Bryan Keller commented on CAMEL-3606:
-
I ran my test using the latest 2.7 snapshot and
Fix sonar found same code for two branches issue
Key: CAMEL-3639
URL: https://issues.apache.org/jira/browse/CAMEL-3639
Project: Camel
Issue Type: Bug
Components: camel-core
Affec
[
https://issues.apache.org/jira/browse/CAMEL-3639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tracy Snell updated CAMEL-3639:
---
Attachment: sonar1.txt
> Fix sonar found same code for two branches issue
> -
If you have the karma, please!
When we got the build failures, I asked Brett about having a Camel profile and
if I could get karma on sonar, but didn't get an answer. Don't know if he
didn't notice my request, or what the reason was for him ignoring it. I chose
not to push it.
Thanks,
Hadrian
[
https://issues.apache.org/jira/browse/CAMEL-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991405#comment-12991405
]
Guillaume Nodet commented on CAMEL-3638:
We do have integration tests that use OSG
[
https://issues.apache.org/jira/browse/CAMEL-3638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991404#comment-12991404
]
Claus Ibsen commented on CAMEL-3638:
There is osgi and karaf tests in the tests direct
Upgrade maven-bundle-plugin to version 1.3.4
Key: CAMEL-3638
URL: https://issues.apache.org/jira/browse/CAMEL-3638
Project: Camel
Issue Type: Improvement
Components: osgi
Affects Ver
Hadrian,
I believe the sonar build for Camel is using the default "Sun checks with
Findbugs" setup. I could change that to use the Camel rules for Checkstyle
and PMD.
The CXF build is now using the CXF rulesets for both. It jumped the
compliance level from ~85% to ~96% as we didn't feel a
On Monday 07 February 2011 7:41:28 am Guillaume Nodet wrote:
> The bundle plugin has no knowledge of the source jar, but I think
> there are ways to configure the jar plugin to add additional manifest
> headers.
> I'm not using eclipse myself, but itsn't there any decent maven
> integration which w
Hi Guillaume,
if you work with pure maven projects then the m2eclipse plugin works
great and loads the source automatically. In this case though your
eclipse has normal maven dependencies to jars in the local maven repository.
If you work with the pde build then you are not so lucky. Then it s
The bundle plugin has no knowledge of the source jar, but I think
there are ways to configure the jar plugin to add additional manifest
headers.
I'm not using eclipse myself, but itsn't there any decent maven
integration which would download and grab the source jar from the
local repository?
On Mo
It would at least mean to add a minimal Manifest header.
In camel we do this manually:
---
org.apache.maven.plugins
maven-source-plugin
2.1.2
${project.groupId}.${project.artifactId}.source
${camel.osgi.version.clean}
${project.groupId}.${project.artifactId};version="${camel.osgi.
It seems that would require our sources jars to be packaged as osgi
bundles, which isn't the case afaik.
On Monday, February 7, 2011, Christian Schneider
wrote:
> We already have this header but I think it could perhaps be done by the
> bundle plugin automatically.
>
> The Manifest Header looks
We already have this header but I think it could perhaps be done by the
bundle plugin automatically.
The Manifest Header looks like:
Eclipse-SourceBundle:
org.eclipse.pde.core;version="3.4.0.N20071128-0010";roots:="ant_tasks/pde-antsrc,."
See: http://dev.eclipse.org/mhonarc/lists/eclipse-dev
I don't recall anything in the maven bundle plugin about that. Where
would we point to ? maven central ?
I suppose we could add that header in the root pom, though this would
also require a big of magic to get the full path I think, and that may
also fail for timestamped snapshots
On Mon, Fe
Hi Guillaume,
I am just trying a buildd with that version.
Till now it looks good.
Btw. Do you know if the source.jars now also will be generated with the
"" manifest entry so you can click them in Eclipse
if you work with a target platform? Or is this not part of the bundle
plugin?
Christi
The maven-bundle-plugin 2.3.4 has just been released, so we could try
upgrading to that one.
On Mon, Feb 7, 2011 at 10:41, Christian Schneider
wrote:
> Hi Guillaume,
>
> that´s a typical case of misreading a specification on my side. It´s good
> that I now read the spec again to proof you wrong.
Hi Guillaume,
that´s a typical case of misreading a specification on my side. It´s
good that I now read the spec again to proof you wrong. So I found that
I was wrong ;-)
The spec says.
version ::= major( '.' minor ( '.' micro ( '.' qualifier )? )? )?
I did not really be careful enough to re
[
https://issues.apache.org/jira/browse/CAMEL-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3637.
Resolution: Fixed
trunk: 1067890.
Thanks for patch.
> Mistake in camel-eventAdmin feature
> -
[
https://issues.apache.org/jira/browse/CAMEL-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated CAMEL-3637:
Attachment: CAMEL-3637.patch
> Mistake in camel-eventAdmin feature
> --
On Mon, Feb 7, 2011 at 10:05, Christian Schneider
wrote:
> Hi all,
>
> I just had mail exchange with Guillaume on the karaf list about their number
> scheme for snapshots.
> There I told him that we use an ant script to create the osgi version from
> the maven version 2.7.0-SNAPSHOT -> 2.7.0.quali
Hi all,
I just had mail exchange with Guillaume on the karaf list about their
number scheme for snapshots.
There I told him that we use an ant script to create the osgi version
from the maven version 2.7.0-SNAPSHOT -> 2.7.0.qualifier
(At least that was how I remembered we do it).
Guillaume to
[
https://issues.apache.org/jira/browse/CAMEL-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12991298#comment-12991298
]
Claus Ibsen commented on CAMEL-3626:
I just noticed in parent/pom.xml there is some os
27 matches
Mail list logo
