Hi,
On Jan 8, 2008 10:13 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
Paddy, welcome to the team!
+1!
BR,
Jukka Zitting
I'm wondering if it would make sense to change the default setting for
the sling plugin regarding the installation of the bundle into a running
sling application.
Currently the default is to install it, if the plugin is added to the
build. The url of the running sling app is also
Hi,
Am Montag, den 07.01.2008, 17:45 +0100 schrieb Carsten Ziegeler:
I'm wondering when we follow the supposed version guide if our current
versions are correct: 2.0.0-incubator-snapshot uses an even micro
version, but it should be an odd one (as it is a snapshot) :)
So it seems that we
Hi,
Am Sonntag, den 06.01.2008, 20:46 +0200 schrieb Jukka Zitting:
Hi,
On Jan 6, 2008 8:26 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Version comparison is in terms of comparing each version part to each
other. The numeric parts are compared as would be expected. The
qualifier part
On Jan 8, 2008 9:13 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Paddy, welcome to the team!...
Welcome, it's good to see the Sling community growing!
-Bertrand
On Jan 8, 2008 10:07 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...D'oh - sometimes the solution is too simple :)...
Still, will you change the default to *not* install the bundles?
Installing them automatically by default is bad bad bad IMHO,
according to the Principle Of Least Surprise
Hi Carsten,
Am Dienstag, den 08.01.2008, 10:07 +0100 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Hi,
Am Dienstag, den 08.01.2008, 09:51 +0100 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Hi,
I am at unease with both solutions ;-)
:)
But I think clearing the URL
Felix Meschberger wrote:
Yes, the initial release breaks the rules in two aspects: The SNAPSHOT
is even and it will encompass almost everything :-)
Of course we could turn back the current release numbers to
1.9.9-incubtator-SNAPSHOT and then comply with the concept... But I am
not sure,
Felix Meschberger wrote:
Hi,
Am Dienstag, den 08.01.2008, 09:51 +0100 schrieb Carsten Ziegeler:
Felix Meschberger wrote:
Hi,
I am at unease with both solutions ;-)
:)
But I think clearing the URL and not doing anything if the url is
missing is probably the better solution. Otherwise we
On Jan 8, 2008 9:38 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I think clearing the URL and not doing anything if the url is
missing is probably the better solution
Agreed, and it' be good for the plugin to output a message like
bundle not installed as sling.url is empty, to let the
Felix Meschberger wrote:
Hi,
Am Dienstag, den 08.01.2008, 10:25 +0100 schrieb Bertrand Delacretaz:
On Jan 8, 2008 10:07 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...D'oh - sometimes the solution is too simple :)...
Still, will you change the default to *not* install the bundles?
On Jan 8, 2008 10:49 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...As we will not configure this plugin for our sling bundles everything
works as expected
Ok - I seemed to remember the plugin being active in some Sling modules.
But if it's not, then I'm fine with the current defaults.
Cool. Thanks.
Regards
Felix
Am Dienstag, den 08.01.2008, 10:51 +0100 schrieb Bertrand Delacretaz:
Hi Felix,
On Jan 8, 2008 8:48 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I think, if the osgiProp is missing, the StringBuffer should just be
initialized empty. This IMHO is not a
Hi,
Am Dienstag, den 08.01.2008, 10:40 +0100 schrieb Bertrand Delacretaz:
On Jan 8, 2008 10:28 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
... * If the sling plugin IS configured in the project, the installation
happens in the install phase - and of course fails if there is
On Jan 8, 2008 10:28 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
... * If the sling plugin IS configured in the project, the installation
happens in the install phase - and of course fails if there is
no local install
Here's my failure scenario:
-Beginner runs some Sling
Bertrand Delacretaz wrote:
On Jan 8, 2008 10:28 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
... * If the sling plugin IS configured in the project, the installation
happens in the install phase - and of course fails if there is
no local install
Here's my failure scenario:
Hi Felix,
On Jan 8, 2008 8:48 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I think, if the osgiProp is missing, the StringBuffer should just be
initialized empty. This IMHO is not a failure situation and thus not
warrant an Exception...
Ok, so in revision 609916 I have changed that code
Bertrand Delacretaz wrote:
On Jan 8, 2008 10:49 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...As we will not configure this plugin for our sling bundles everything
works as expected
Ok - I seemed to remember the plugin being active in some Sling modules.
Really? No, no - that's not
[
https://issues.apache.org/jira/browse/SLING-149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12556896#action_12556896
]
Bertrand Delacretaz commented on SLING-149:
---
I have created
Hi,
I experienced the same problem. That's probably Alex and I use the
same environment: MacOSX and starting sling with the launcher/app/
target/-full.jar
One problem is the HTTP Service bundle that is used which did include
a Servlet API 1.3 implementation (Jetty) although Sling
Hi,
I get errors for not finding org.apache.felix.framework.Logger class
in the sling-webapp project when loaded inside Eclipse and could fix
that by adding the dependency org.apache.felix.framework to the sling-
webapp pom (no JIRA issue as it seems too simple ;-):
Index: pom.xml
Thanks Felix, for those that don't know me, I currently run the
website development team at Edmunds.com in Santa Monica, California
(rough place to work ;-). I've been doing web site development for
about twelve years or so and have focused mainly on the middle and
back-end tiers. However,
I'd like to update the various ScriptEngineFactories so that they
provide their services via osgi. This way the registration of
factories can be done via standard osgi bundle activation. This would
allow the default script resolver to access Freemarker and the other
engines, and could be
I guess the current bundles are accessible to the DefaultSlingScript
resolver (assuming they are active and an entry for META-INF/services/
javax.script.ScriptEngineFactory), I was thinking that it might be
nice to have their packages exported rather than remain private. I
guess, though,
Am Dienstag, den 08.01.2008, 12:02 -0800 schrieb Padraic Hannon:
I'd like to update the various ScriptEngineFactories so that they
provide their services via osgi. This way the registration of
factories can be done via standard osgi bundle activation. This would
allow the default script
Ah ! Had the same issue when building the everything is a resource
prototype: I solved this by having the activate method initialize all
pending servlets. This works as the ServletContext is a static mandatory
reference and those are bound BEFORE the component gets activated.
That is, as soon as
Hi Alexander,
Am Dienstag, den 08.01.2008, 17:26 +0100 schrieb Alexander Klimetschek:
One problem is the HTTP Service bundle that is used which did include
a Servlet API 1.3 implementation (Jetty) although Sling expects a 2.4
API. That caused runtime errors of the JSPs in the sample app.
So I've worked on various aspects of sling and written a component
here and there, however, I'd like to work on a more complete example
(perhaps this would go towards some of the documentation we have said
is needed) and am stumbling. So far we have a pretty strong link
between Content and
Felix Meschberger wrote:
Hi Carsten,
Am Dienstag, den 08.01.2008, 07:55 +0100 schrieb Carsten Ziegeler:
It's difficult to tell what is going wrong from here, but one possible
problem could be the startup order of the bundles. I've put most of the
org.apache.felix.* bundles into the
Felix Meschberger schrieb:
Ah ! Had the same issue when building the everything is a resource
prototype: I solved this by having the activate method initialize all
pending servlets. This works as the ServletContext is a static mandatory
reference and those are bound BEFORE the component gets
30 matches
Mail list logo
