Yeah, I think this is a better name.
Best,
Christian
On Thu, Sep 27, 2012 at 7:53 AM, Claus Ibsen wrote:
> Hi
>
> Why not call the package org.apachextras.camel.examples.esper
>
>
> On Wed, Sep 26, 2012 at 9:09 PM, Henryk Konsek wrote:
> > Hi,
> >
> > Since we distribute Camel-Extra artifacts
Hi
Why not call the package org.apachextras.camel.examples.esper
On Wed, Sep 26, 2012 at 9:09 PM, Henryk Konsek wrote:
> Hi,
>
> Since we distribute Camel-Extra artifacts via OSS sonatype, we cannot
> use groupId like 'com.iona.ps.demos' for 'camel-esper-demo'. I changed
> it then to 'org.apach
I fail to follow the reasoning. There are plenty of camel components
hosted by other open source projects, various individual github users
and even by commercial companies.
What does project governance have to do with anything? Bonus question:
is your expectation that Apache Camel would be a o
You can read more about how to run the maven release plugin here [1]
[1] http://camel.apache.org/release-guide.html
Best,
Christian
--
If you want to follow the discussion, here is the pointer [1].
[1]
http://mail-archives.apache.org/mod_mbox/community-dev/201209.mbox/%3CCALvzYd-h4Q=cteggqcneeninhvose8uigt2gtk22n9cmr_k...@mail.gmail.com%3E
Best,
Christian
On Mon, Sep 24, 2012 at 11:38 PM, Daniel Shahaf wrote:
> Luciano Resende
You can follow the discussion here [1].
[1]
http://mail-archives.apache.org/mod_mbox/community-dev/201209.mbox/%3CCALvzYd-h4Q=cteggqcneeninhvose8uigt2gtk22n9cmr_k...@mail.gmail.com%3E
Best,
Christian
On Wed, Sep 26, 2012 at 1:29 PM, James Carman wrote:
> There is some discussion about this, tho
You can do this. I'm busy with some admin stuff...
Best,
Christian
On Wed, Sep 26, 2012 at 10:48 PM, Henryk Konsek wrote:
> > Because Camel 2.10.0 is already released, we should use this as parent
> > version of the Camel extra root pom.
>
> I agree. 2.10.1 was too high, but 2.10.0 will be fine
> Because Camel 2.10.0 is already released, we should use this as parent
> version of the Camel extra root pom.
I agree. 2.10.1 was too high, but 2.10.0 will be fine as 2.10-SNAPSHOT
should not change after the release.
Will you apply this change?
--
Henryk Konsek
http://henryk-konsek.blogspot.
Because Camel 2.10.0 is already released, we should use this as parent
version of the Camel extra root pom.
Best,
Christian
On Wed, Sep 26, 2012 at 9:39 PM, Henryk Konsek wrote:
> > Why not 2.10.0?
>
> Because there is no version 2.10.0-SNAPSHOT in the Apache Snapshot
> repository.
>
> Now we s
> I will do a dry run today or tomorrow...
+1
--
Henryk Konsek
http://henryk-konsek.blogspot.com
I will do a dry run today or tomorrow...
Best,
Christian
On Wed, Sep 26, 2012 at 9:31 PM, Henryk Konsek wrote:
> Hi,
>
> I would like to release Camel Extra 2.10.0 at Friday.
>
> Anybody wants to raise some blocking issues? From my point of view the
> Camel Extra codebase is ready to go.
>
> BT
planners@ wrote yesterday:
The conference is taking place from Monday 5th to Thursday 8th November. On
the Monday we have hackathons, coding sprints etc, to which you are very
much encouraged to come. We're also aiming to have a drinks reception on
Monday evening, for speakers and committers, which
> Why not 2.10.0?
Because there is no version 2.10.0-SNAPSHOT in the Apache Snapshot repository.
Now we set version to 2.10-SNAPSHOT and during the release, we will
tell Maven Release plugin to set release version to 2.10.0.
This way we will be as compatible as possible with Apache Camel
release
> Did you try the maven release plugin? It make sure we do not have any
> SNAPSHOT dependencies and so on...
I'll release version later this week. Then we will use Maven Release
plugin. Until then, I want to be sure that Snapshots deployed to
Sonatype are as good as they should be.
--
Henryk Kon
Hi,
I would like to release Camel Extra 2.10.0 at Friday.
Anybody wants to raise some blocking issues? From my point of view the
Camel Extra codebase is ready to go.
BTW From Camel Extra 2.11 I would like to introduce more formal way of
releasing the version. We could start with PMC voting for t
+1
On Wed, Sep 26, 2012 at 9:19 PM, Henryk Konsek wrote:
> Hi,
>
> I though I have already done it but apparently I was wrong. I renamed
> JGroups package from 'org.apache.camel' to 'org.apachextras.camel'.
>
> Regards.
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.com
>
--
+1
On Wed, Sep 26, 2012 at 9:09 PM, Henryk Konsek wrote:
> Hi,
>
> Since we distribute Camel-Extra artifacts via OSS sonatype, we cannot
> use groupId like 'com.iona.ps.demos' for 'camel-esper-demo'. I changed
> it then to 'org.apache-extras.camel-extra.examples.iona'. I also
> changed Java pack
Why not 2.10.0?
Best,
Christian
On Wed, Sep 26, 2012 at 8:36 PM, Henryk Konsek wrote:
> In rev932 I set parent version to 2.10-SNAPSHOT as we do not want to
> be dependent on the "future" version of Camel (it was 2.10.1 release
> version).
>
> --
> Henryk Konsek
> http://henryk-konsek.blogspot.
Did you try the maven release plugin? It make sure we do not have any
SNAPSHOT dependencies and so on...
Best,
Christian
On Wed, Sep 26, 2012 at 7:56 PM, Henryk Konsek wrote:
> Hi,
>
> In rev931 I've fixed snapshot repository configuration. I also
> deployed 2.10 artifacts to the Sonatype OSS s
In rev932 I set parent version to 2.10-SNAPSHOT as we do not want to
be dependent on the "future" version of Camel (it was 2.10.1 release
version).
--
Henryk Konsek
http://henryk-konsek.blogspot.com
Hi,
In rev931 I've fixed snapshot repository configuration. I also
deployed 2.10 artifacts to the Sonatype OSS snapshot repository.
However I think that we need to change the snapshot versions to the
2.10.0 to be compatible with Camel 2.10.0 versioning. I'll do it and
proceed with the release.
R
Hi again,
Just sending a quick question to ask if there is a problem with this patch
at all?
I understand that there will be a problem with the current checkstyle
requirements, as I haven't been able to successfully make it run yet! I'll
have to look into this and see why.
Are there any other p
There is some discussion about this, though. We aren't sure if it's
the "hosting" or the "management" of the code that is the sticking
point. The hosting is definitely out, but merely using an external
source control system and all the other infrastructure/management
services here at the ASF migh
+1 if we can unify the wiki and issue for Camel and Camel-Extra.
The reason which we setup the Camel-Extra project is we cannot host the code of
GPL license in Apache.
I don't think we cannot add the document or issues into Apache Camel due to
that kind of issue.
Any thoughts?
On Wednesday, S
Hi Christian and @All,
As many Camel committers will be there at ApacheConference, it could be
interesting that we organise a round table with all committers and drink a
beer after camel sessions day ...
Regards,
Charles
On Wed, Sep 26, 2012 at 8:48 AM, Christian Müller <
christian.muel...@gmai
> - Using Apache JIRA for Camel extra
For now, I'll keep Camel Extra issues in Google Issue tracker. We
shouldn't have Camel Extra issues spread around two places. However it
will be nice if eventually we could use Jira for that.
> (- Using Issue notifications on iss...@camel.apache.org for issue
26 matches
Mail list logo
