[
https://issues.apache.org/activemq/browse/CAMEL-3325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Ford updated CAMEL-3325:
-
Component/s: camel-jmx
Affects Version/s: 2.6.0
> camel-jmx: Auto creation of a monitor bea
Agree on all counts.
Hadrian
On Nov 10, 2010, at 5:06 PM, Guillaume Nodet wrote:
> AAFAIK, most projects use the default settings, i.e. edit for
> committers, comments for everyone with an ICLA on file.
> If non-committers with a ICLA on file want to edit, permissions is
> granted case by case us
Then this is a problem. I added you to the asf-cla group and you should have
the karma to edit the wiki.
By the way you have two confluence accounts, which one did you use? Can you
ping me on #camel tomorrow and resolve this interactively?
Thanks,
Hadrian
On Nov 10, 2010, at 4:16 PM, Eric John
AAFAIK, most projects use the default settings, i.e. edit for
committers, comments for everyone with an ICLA on file.
If non-committers with a ICLA on file want to edit, permissions is
granted case by case usually (at least, that's what i've done since a
few years).
So the bar is lower than for cod
Hadrian,
As it turns out, not anyone with a signed CLA can edit the Camel wiki.
The Apache Confluence wiki allows each community to determine who can
edit the pages in their space.
I went create a page listing the ideas/issues around a site update and
was confronted with a "Permission Denied" page.
I have created the camel-jmx category
On Wed, Nov 10, 2010 at 7:07 PM, Mark Ford wrote:
> There should be a component category in JIRA for camel-jmx
>
> As for this issue, I have some code that's mostly working. I'll be
> putting the finishing touches on over the course of the next couple of
> we
On Wednesday 10 November 2010 2:07:48 pm Guillaume Nodet wrote:
> On Wed, Nov 10, 2010 at 16:15, Daniel Kulp wrote:
> > On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
> >> On 10 November 2010 14:51, Daniel Kulp wrote:
> >> > For most of the people on this list, it ISN'T a big deal
On Wed, Nov 10, 2010 at 16:15, Daniel Kulp wrote:
> On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
>> On 10 November 2010 14:51, Daniel Kulp wrote:
>> >
>> > For most of the people on this list, it ISN'T a big deal. We deal with
>> > svn and mvn every day. For others, it could
There should be a component category in JIRA for camel-jmx
As for this issue, I have some code that's mostly working. I'll be
putting the finishing touches on over the course of the next couple of
weeks as time permits. Any input on the feature is appreciated.
On Wed, Nov 10, 2010 at 11:47 AM, Ma
camel-jmx: Auto creation of a monitor bean via endpoint properties
--
Key: CAMEL-3325
URL: https://issues.apache.org/activemq/browse/CAMEL-3325
Project: Apache Camel
Issue Type:
Just for the record. I like scalate too, it's f*** awesome s*** :).
Hadrian
On Nov 10, 2010, at 11:04 AM, Johan Edstrom wrote:
> I actually really liked the scalate project and writing the docs in IDEA,
> making a patch and tossing it in github.
>
> Offline editing also seems really nice for wh
Now, that's not entirely true either.
Not all projects include the wiki documentation in the distro. That is the
issue!
Since we do, everything in the distro must be AL2 and the IP tracked to
original contributions.
A non committer must either submit a patch (which does not currently work for
d
I actually really liked the scalate project and writing the docs in IDEA,
making a patch and tossing it in github.
Offline editing also seems really nice for when you are on planes, in airports
or hotels.
Not to mention if you actually fix a bug and submit a patch you could fix
documentation in
On Nov 10, 2010, at 10:28 AM, James Strachan wrote:
> On 10 November 2010 15:15, Daniel Kulp wrote:
>> On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
>>> On 10 November 2010 14:51, Daniel Kulp wrote:
For most of the people on this list, it ISN'T a big deal. We deal
> And then for people to actually be able to edit the wiki page they
> have to sign up for the ICLA which takes a fair bit of time and for
> some people just scare them off.
This is a mandatory part as long as we include the manual in the distro.
Hadrian
On Nov 10, 2010, at 10:07 AM, Claus Ibsen
On Wed, Nov 10, 2010 at 16:29, Eric Johnson wrote:
> I want to make sure I understand a few of the issues here:
>
> We want to make it as easy as possible for people to make changes to
> the documentation.
> Before a person can edit the wiki they need to sign an icla.
> We don't let anyone change
On 10 November 2010 15:00, Hadrian Zbarcea wrote:
> That is true, but you can see your changes in the wiki right away.
>
> I love the idea of having the docs version controlled, I understand all the
> benefits. I am also convinced losing the ability to edit in place is a major
> community issue.
I want to make sure I understand a few of the issues here:
We want to make it as easy as possible for people to make changes to
the documentation.
Before a person can edit the wiki they need to sign an icla.
We don't let anyone change the code who hasn't been vetted by the
community and made a com
On 10 November 2010 15:15, Daniel Kulp wrote:
> On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
>> On 10 November 2010 14:51, Daniel Kulp wrote:
>> >
>> > For most of the people on this list, it ISN'T a big deal. We deal with
>> > svn and mvn every day. For others, it could be.
On 10 November 2010 15:00, Hadrian Zbarcea wrote:
> That is true, but you can see your changes in the wiki right away.
>
> I love the idea of having the docs version controlled, I understand all the
> benefits. I am also convinced losing the ability to edit in place is a major
> community issue.
On Wednesday 10 November 2010 9:59:11 am James Strachan wrote:
> On 10 November 2010 14:51, Daniel Kulp wrote:
> >
> > For most of the people on this list, it ISN'T a big deal. We deal with
> > svn and mvn every day. For others, it could be.
>
> Given 99% of all our documentation and web con
On Wed, Nov 10, 2010 at 4:00 PM, Hadrian Zbarcea wrote:
> That is true, but you can see your changes in the wiki right away.
>
> I love the idea of having the docs version controlled, I understand all the
> benefits. I am also convinced losing the ability to edit in place is a major
> community
That is true, but you can see your changes in the wiki right away.
I love the idea of having the docs version controlled, I understand all the
benefits. I am also convinced losing the ability to edit in place is a major
community issue. Can we have both? We want to make it as easy as possible fo
On 10 November 2010 14:51, Daniel Kulp wrote:
> On Wednesday 10 November 2010 9:43:13 am Guillaume Nodet wrote:
>> On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea wrote:
>> > Thanks James,
>> >
>> > You have to comment out the dependency on scalate-test in the pom for
>> > this to work (otherwise
On 10 November 2010 14:43, Guillaume Nodet wrote:
> On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea wrote:
>> Thanks James,
>>
>> You have to comment out the dependency on scalate-test in the pom for this
>> to work (otherwise you get a "Failed to resolve artifact").
>>
>> That aside, one of the
Yeah, that's what I mean and what I believe was discussed in Aug. Hosting it at
the ASF (or somewhere) I don't think would be a problem.
Guillaume, I assume we'd deploy the webapp in Karaf, correct? ;)
On a second thought, since a few projects plan on using it, what about
incubating it at the AS
[
https://issues.apache.org/activemq/browse/CAMEL-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63240#action_63240
]
Claus Ibsen commented on CAMEL-3324:
trunk: 1033501.
OSGi will prepend the bundle id in
On Wednesday 10 November 2010 9:43:13 am Guillaume Nodet wrote:
> On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea wrote:
> > Thanks James,
> >
> > You have to comment out the dependency on scalate-test in the pom for
> > this to work (otherwise you get a "Failed to resolve artifact").
> >
> > Tha
On 10 November 2010 13:40, Hadrian Zbarcea wrote:
> Thanks James,
>
> You have to comment out the dependency on scalate-test in the pom for this to
> work (otherwise you get a "Failed to resolve artifact").
>
> That aside, one of the important requirements I believe is not to raise the
> barrier
On Wed, Nov 10, 2010 at 14:40, Hadrian Zbarcea wrote:
> Thanks James,
>
> You have to comment out the dependency on scalate-test in the pom for this to
> work (otherwise you get a "Failed to resolve artifact").
>
> That aside, one of the important requirements I believe is not to raise the
> bar
Thanks James,
You have to comment out the dependency on scalate-test in the pom for this to
work (otherwise you get a "Failed to resolve artifact").
That aside, one of the important requirements I believe is not to raise the
barrier to entry for those who want to contribute documentation. Today
FWIW I started an experimental spike to try recreate the Camel website
using wiki files from source control - exported from Confluence -
(rather than the Confluence / AutoExport icky stuff) like Karaf &
ServiceMix are doing. More as a test of Scalate than any attempt to
actually change any document
[
https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63235#action_63235
]
Bengt Rodehav commented on CAMEL-3309:
--
Yes, of course Claus. Sorry for taking your time
[
https://issues.apache.org/activemq/browse/CAMEL-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3288.
Resolution: Won't Fix
CAMEL-3324 resolves the problem.
> Allow option to let end user set a cu
[
https://issues.apache.org/activemq/browse/CAMEL-3324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-3324.
Resolution: Fixed
trunk: 1033440.
> Camel should auto find free CamelContext MBean name when r
Camel should auto find free CamelContext MBean name when registering Camel in
JMX to avoid failing on startup due existing mbean name
-
Key: CAMEL-3
Hi,
We working on SMX/Karaf so we basically stuck a bit in current stuff. But
don't worries, we going to continue working with Camel community too. We
just need to finish one task to avoid designer overload.
Best regards,
Lukasz
-Original Message-
From: Hadrian Zbarcea [mailto:hzbar...@gm
[
https://issues.apache.org/activemq/browse/CAMEL-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63231#action_63231
]
Claus Ibsen commented on CAMEL-3309:
You have to use {{file:onlyname.noext}}
{code}
fro
38 matches
Mail list logo
