I'd prefer to include that kind of information in the user guide (which already does contain some such info) because it is more likely to be kept current that way. Commented out configurations will tend to go out of date without breaking anything.
You mean to create a tutorial how to modify Virgo's kernel? We have to be careful here since that might cause more issues than expected if everyone starts modifying and making incompatible for the kernel changes just because they saw a tutorial - all these issues will bounce back. Maybe a better and more safe approach would be to leave people contact us when they need something. Wdyt?
Sent from my HTC
----- Reply message -----
From: "Hristo Iliev" <hsiliev@xxxxxxxxx>
Date: Tue, Jan 11, 2011 12:43
Subject: [virgo-dev] Janino
To: "Virgo Project" <virgo-dev@xxxxxxxxxxx>
Hi,
Since Janino is not big I also vote for packing it with Virgo.
We can also create sample configurations (as comments) to demonstrate how
the users can add other libraries. I find this quite useful. Wdyt?
Regards,
Hristo Iliev
On 11 January 2011 12:17, Glyn Normington <gnormington@xxxxxxxxxx> wrote:
> I agree, but I didn't want to put words in people's mouths.
>
> Anyone think differently?
>
> Regards,
> Glyn
> PS. Nice to see your name in Cyrillic.
>
> On 11 Jan 2011, at 10:13, Борислав Капукаранов wrote:
>
> Hi Glyn,
>
> While it doesn't sound so good to make the kernel heavier, it seems that
> Janino won't bring that much overhead. Indeed the commons-compiler.jar is
> required - i just checked that, but its very lightweight. Janino seems like
> a library, so it should not require much time to start up and i guess it
> won't slow the start of the medic bundles(which will start to depend on
> it) notably, however the benefit to have support out-of-the-box and improve
> the UX is more valuable. So i think the benefits of having Janino support
> out-of-the-box are greater than the losses
>
> Best Regards
> Borislav
>
> 2011/1/11 Glyn Normington <gnormington@xxxxxxxxxx>
>
>> A user has raised an enhancement bug [1] to enable Java boolean
>> expressions to be used in logback filter configuration - a fairly basic
>> requirement which I think we should address. The question is how we should
>> implement the enhancement and I'd value people's opinions on the
>> alternatives I've written up in the bug.
>>
>> Regards,
>> Glyn
>> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=333920
>>
>>
>> _______________________________________________
>> virgo-dev mailing list
>> virgo-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/virgo-dev
>>
>>
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev
>
>
>
> _______________________________________________
> virgo-dev mailing list
> virgo-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/virgo-dev
>
>
_______________________________________________
virgo-dev mailing list
virgo-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/virgo-dev
