settings are reflected in Git, but you may
want to try rebasing your local changes to the latest changes from
svn.
BR,
Jukka Zitting
Hi,
On Mon, Apr 27, 2009 at 9:54 AM, Michael Wechner
michael.wech...@wyona.com wrote:
Jukka Zitting schrieb:
The ApacheCon planners are asking for Apache projects to self-organize
content for the upcoming ApacheCon US in November this year. It would
be cool to have a track related to content
the program for the track. The plan will then be
presented to the conference planners who make final decisions on the
conference schedule.
BR,
Jukka Zitting
...@hudson.zones.apache.org to
post to sling-comm...@.
BR,
Jukka Zitting
Hi,
On Wed, Apr 29, 2009 at 9:38 AM, Jukka Zitting jukka.zitt...@gmail.com wrote:
I'll see if I can explicitly allow hud...@hudson.zones.apache.org to
post to sling-comm...@.
OK, done. Not sure if it works though, it could be that the
@apache.org filter is applied before the normal moderation
also to sling-...@.
BR,
Jukka Zitting
Hi,
Ping. Anyone interested in pushing out a new release?
BR,
Jukka Zitting
Hi,
On Wed, Apr 29, 2009 at 2:53 PM, Felix Meschberger fmesc...@gmail.com wrote:
Jukka Zitting schrieb:
Ping. Anyone interested in pushing out a new release?
I am not sure how interested he really is ;-) But IIRC Carsten agreed to
stand in as the RM for it.
Yeah, I saw that. Just pinging
last summer, but now that I look
back to it, it happened on sling-priv...@. It would be good to get
feedback and consensus also from the larger community (who are most
affected by the policy change!) before nailing it down.
BR,
Jukka Zitting
should only be used to lower the barrier
for committership, not to raise the barrier for (P)PMC membership.
BR,
Jukka Zitting
2.0 is officially out before upgrading to JCR
2.0.
At current rate of things I would expect Jackrabbit 2.0 to be out
sometime within the second half of this year.
BR,
Jukka Zitting
to upgrade to Jackrabbit 2.x once it's available.
BR,
Jukka Zitting
be good to fix the build breakage.
BR,
Jukka Zitting
an issue reported for this
(https://issues.apache.org/jira/browse/JCR-1991), but so far nobody
has had the time or know-how to make this happen. I'd love to have
OSGi metadata included already in Jackrabbit 1.6.
BR,
Jukka Zitting
it's bound to actual changes that people commit.
BR,
Jukka Zitting
Hi,
One more change:
* The sling-trunk-1.6 job is now only build after a successful
sling-trunk-1.5. This way we won't get duplicate warnings (separately
for 1.5 and 1.6) about broken builds.
BR,
Jukka Zitting
the
build will be broken as the it will reference artifacts which are not
available in a public repo - but on my machine :)
Branch?
BR,
Jukka Zitting
Hi,
On Tue, May 5, 2009 at 5:09 PM, Carsten Ziegeler cziege...@apache.org wrote:
Jukka Zitting wrote:
Branch?
We're not branching for a release; we only branch if really necessary.
Why? Doing the release preparation in a branch would allow others to
continue using trunk for normal development
not cover the licensing information of all
the code included in those packages. The embedded bundles in those
packages seem to contain all the required licensing metadata (which is
why I don't vote -1), but the top level files should at least point to
this more detailed information.
BR,
Jukka
,
Jukka Zitting
is solved.
Release often!
BR,
Jukka Zitting
and launch any runnable jar (and the full set of
dependencies) in the Maven repository.
Of course this doesn't do any of the OSGi stuff, but as you mention,
the OSGi startup could well be handled as a second stage.
BR,
Jukka Zitting
tika.xml
project xmlns=http://maven.apache.org/POM/4.0.0
graduation criteria have been met and I
don't think there's anything more that the Incubator can give to
Sling.
Thanks to everyone who's been participating so far, and good luck to
Apache Sling as a standalone TLP!
/mentor hat on
BR,
Jukka Zitting
,
Jukka Zitting
Hi,
On Tue, May 26, 2009 at 5:15 PM, John Crawford craw...@gmail.com wrote:
Is there a better way to handle this?
Access control.
BR,
Jukka Zitting
Hi,
On Fri, Apr 24, 2009 at 8:57 AM, conflue...@apache.org wrote:
Reviewed 2009-09-24, this page's information is in sync with the current
Sling codebase.
As noted by Tako Schotanus in a chat, this does seem to prove that
Sling's really the future!
BR,
Jukka Zitting
Hi,
Jackrabbit is using Google Analytics to track usage of the
jackrabbit.apache.org web site, and I was wondering if Sling would be
interested in similar data. See [1] for an example report.
[1] http://markmail.org/download.xqy?id=7xwz2anfrp4tfikonumber=1
BR,
Jukka Zitting
where it's truly needed (though at the cost
of the cache not being global).
BR,
Jukka Zitting
an order of magnitude more performance. With a
simple high-level cache I was able to achieve this.
BR,
Jukka Zitting
.
BR,
Jukka Zitting
of the same
artifacts with different checksums and signatures.
We could ask the people at reposit...@apache.org to copy the existing
artifacts from p.a.o to r.a.o.
BR,
Jukka Zitting
of the background for this, so I'm probably
missing something essential here... Be gentle. :-)
BR,
Jukka Zitting
be the holder of the cache and provide the user-specific subset of the
cache to the per-request-ResourceResolver.
I explored this idea a bit, and came up with a patch I submitted in SLING-1010.
BR,
Jukka Zitting
Hi,
On Fri, Jun 26, 2009 at 10:58 AM, Ian Bostoni...@tfd.co.uk wrote:
Now that the svn repo has moved,
has the git mirror been updated ?
I have now updated the Git mirror to use the new svn location for new commits.
BR,
Jukka Zitting
[
https://issues.apache.org/jira/browse/SLING-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569818#action_12569818
]
Jukka Zitting commented on SLING-251:
-
Is this a form of vanity URLs or an answer
[
https://issues.apache.org/jira/browse/SLING-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569879#action_12569879
]
Jukka Zitting commented on SLING-251:
-
Couldn't we solve the same needs much more
[
https://issues.apache.org/jira/browse/SLING-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12570341#action_12570341
]
Jukka Zitting commented on SLING-251:
-
Ah, I see what you mean.
Is there a use case
[
https://issues.apache.org/jira/browse/SLING-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576983#action_12576983
]
Jukka Zitting commented on SLING-315:
-
The problem regarding licensing I have
Reporter: Jukka Zitting
Assignee: Jukka Zitting
Fix For: 2.0.0
As discussed on the mailing list, we should merge third party license
information from LICENSE.* files to the LICENSE files.
--
This message is automatically generated by JIRA.
-
You can reply to this email
Clarify scripting/ruby licensing
Key: SLING-541
URL: https://issues.apache.org/jira/browse/SLING-541
Project: Sling
Issue Type: Improvement
Components: Scripting
Reporter: Jukka Zitting
Clarify launchpad/jcrapp licensing
--
Key: SLING-542
URL: https://issues.apache.org/jira/browse/SLING-542
Project: Sling
Issue Type: Improvement
Components: Launchpad
Reporter: Jukka
[
https://issues.apache.org/jira/browse/SLING-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved SLING-539.
-
Resolution: Fixed
Resolving as Fixed with these followup issues:
SLING-540: Clarify extensions
[
https://issues.apache.org/jira/browse/SLING-540?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12605530#action_12605530
]
Jukka Zitting commented on SLING-540:
-
AFAIK all the code in Dojo should be OK for us
: Bug
Components: General
Reporter: Jukka Zitting
Carsten recently (revision 670566) added the incubating repository to the
parent POM in svn. But since many components refer to version 3-incubator
(instead of 4-incubator-SNAPSHOT) as the parent POM, this repository reference
[
https://issues.apache.org/jira/browse/SLING-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607255#action_12607255
]
Jukka Zitting commented on SLING-555:
-
As noted by Bertrand on the mailing list, we
Components: Engine
Environment: org.apache.sling.engine from revision 685501
Reporter: Jukka Zitting
Priority: Minor
As discussed on the mailing list (see
http://markmail.org/message/fphyjdeb2oecjqdn), there is an issue when using the
RequestDispatcher to include other
[
https://issues.apache.org/jira/browse/SLING-877?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12678709#action_12678709
]
Jukka Zitting commented on SLING-877:
-
I would even question the need
: Jukka Zitting
The Sling trunk has lots of files with missing svn:eol-style settings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SLING-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting resolved SLING-941.
-
Resolution: Fixed
Assignee: Jukka Zitting
I fixed all the missing svn:eol-styles I could
[
https://issues.apache.org/jira/browse/SLING-920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12705520#action_12705520
]
Jukka Zitting commented on SLING-920:
-
One more change
* The sling-trunk-1.6 job is now
Components: JCR Resource
Reporter: Jukka Zitting
Priority: Minor
As recently discussed [1], I'm trying to speed up resolution of resources that
don't exist. The resource resolution algorithm in Sling is very powerful, but
it also needs to look at many different paths when
[
https://issues.apache.org/jira/browse/SLING-1010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jukka Zitting updated SLING-1010:
-
Attachment: MissingPathCache.patch
Attached the proposed patch (against bundles/jcr/resource
101 - 152 of 152 matches
Mail list logo
