Hi,
Am Dienstag, den 30.10.2007, 17:08 +0100 schrieb Lars Trieloff:
> In Sling, we already have a concept of delegation. This means, a
> resource delegates the rendering of the children to the children's
> scripts by calling
>
> Sling.include(path)
This is only one side of the medal. The oth
Add support for creating Ruby templates
---
Key: SLING-90
URL: https://issues.apache.org/jira/browse/SLING-90
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: P
Hi Betrand,
this is what we want:
...I still think having a
level of inheriance and aspect-orientation in rendering is something
we want, because it eases the development process
I agree that this might be useful in some cases - but do you think we
can achieve this efficiently and simply
Hi all,
I think we are now at a point, where the Sling API is actually, where we
wanted to go. I am currently migrating microsling to implement the Sling
API as sort of a small scale proof of concept.
After that I would like to (finally) call the vote on the Sling API and
after that start convert
On 10/30/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Done.
thanks!
-Bertrand
On 10/30/07, Lars Trieloff <[EMAIL PROTECTED]> wrote:
> ...I still think having a
> level of inheriance and aspect-orientation in rendering is something
> we want, because it eases the development process
I agree that this might be useful in some cases - but do you think we
can achieve this e
Done.
Regards
Felix
Am Dienstag, den 30.10.2007, 12:05 +0200 schrieb Bertrand Delacretaz:
> Hi,
>
> Currently the maven-sling-plugin runs sling:install by default, could
> we disable that?
>
> I find it dangerous to have stuff installed automatically by Maven,
> it's easy to oversee it when bui
This shortens the getting started guide, thus it is good.
Am 30.10.2007 um 11:05 schrieb Bertrand Delacretaz:
Hi,
Currently the maven-sling-plugin runs sling:install by default, could
we disable that?
I find it dangerous to have stuff installed automatically by Maven,
it's easy to oversee it
[
https://issues.apache.org/jira/browse/SLING-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-89.
--
Resolution: Fixed
Fixed in Rev. 590043 (actually the deploy goal was not configured so only the
Remove default setup for the bundle install and deploy goals of the sling plugin
Key: SLING-89
URL: https://issues.apache.org/jira/browse/SLING-89
Project: Sling
[
https://issues.apache.org/jira/browse/SLING-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-87.
--
Resolution: Fixed
Added an example and integration tests in revision 590035.
So we have
Hi Felix,
The first candidate is the path denoted by slingResouceType. If this
is not set, we resort to the primaryNode type.
In fact, this is overkill as the slingResourceType is intended to be
either set from a property or the primary node type if there is no
such
property. So just checki
> Currently the maven-sling-plugin runs sling:install by default, could
> we disable that?
+1
--
-< [EMAIL PROTECTED] >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
---
On 10/30/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...I would place this not in the trunk directly but in the project using
> the respective library. Just like for example I have done in the
> content-jcr project
You're right - I suggest leaving that NOTICE file where it is now, so
a
Hmm,
I would place this not in the trunk directly but in the project using
the respective library. Just like for example I have done in the
content-jcr project.
WDYT ?
Regards
Felix
Am Dienstag, den 30.10.2007, 10:55 + schrieb [EMAIL PROTECTED]:
> Author: bdelacretaz
> Date: Tue Oct 30 03:5
Hi,
Am Dienstag, den 30.10.2007, 12:05 +0200 schrieb Bertrand Delacretaz:
> Currently the maven-sling-plugin runs sling:install by default, could
> we disable that?
>
> I find it dangerous to have stuff installed automatically by Maven,
> it's easy to oversee it when building something.
I am kin
Bertrand Delacretaz wrote:
> Hi,
>
> Currently the maven-sling-plugin runs sling:install by default, could
> we disable that?
>
> I find it dangerous to have stuff installed automatically by Maven,
> it's easy to oversee it when building something.
>
+1
Carsten
--
Carsten Ziegeler
[EMAIL PROT
[
https://issues.apache.org/jira/browse/SLING-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reassigned SLING-87:
Assignee: Bertrand Delacretaz
> Add Freemarker Scripting Support
> --
Hi,
Currently the maven-sling-plugin runs sling:install by default, could
we disable that?
I find it dangerous to have stuff installed automatically by Maven,
it's easy to oversee it when building something.
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-51.
--
Resolution: Won't Fix
Setting to won't fix, people seem to agree according to sling-dev d
Use the sling-api from SLING-28 in microsling
-
Key: SLING-88
URL: https://issues.apache.org/jira/browse/SLING-88
Project: Sling
Issue Type: Improvement
Components: microsling
Hi,
With the sling-api discussions coming to a close (AFAIU), we'll be
able to "port" microsling to the new sling-api soon.
Here's my suggestion for the Maven modules to use for that:
microsling (main microsling module)
- microsling-core (depends on sling-api)
- microsling-commons (stu
On 10/30/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...If I read and understand everything
> correctly, freemarker is made available under a BSD license [1], which
> is assumed to be a class A third party license by Apache [2]
That's also my understanding.
> ...We would just have to
Hi all,
Thanks Paddy for submitting this patch. It is greatly valuated.
Before applying the patch, I would like to make sure, licensing is ok
for the freemarker library. If I read and understand everything
correctly, freemarker is made available under a BSD license [1], which
is assumed to be a c
Hi,
Am Montag, den 29.10.2007, 11:19 +0200 schrieb Bertrand Delacretaz:
> public SlingHttpServletRequestWrapper(SlingHttpServletRequest delegatee)
> I would have expected
>
> public SlingHttpServletRequestWrapper(ServletRequest delegatee)
This is just inline with the Servlet API HttpServletReque
Hi,
Am Montag, den 29.10.2007, 11:12 +0200 schrieb Bertrand Delacretaz:
> Felix, how would you suggest implementing a POST script that renders
> data when done processing? Do a request forwarding at the end of the
> POST script?
>
> That might be ok, but the programmer might want to specify exact
Hi Lars,
Thanks for elaborating and also the nice illustration, it helps alot.
Am Montag, den 29.10.2007, 11:25 +0100 schrieb Lars Trieloff:
> For script resolution, we create a weighted list of candidate paths.
> As soon as a script is found in a candidate path, we start looking for
> refine
27 matches
Mail list logo
