Hi Justin,
Justin Edelson schrieb:
Up at: http://fisheye6.atlassian.com/browse/sling
Thanks alot.
It looks like the hookup is already there between Fisheye and JIRA (see
http://fisheye6.atlassian.com/changelog/sling/?cs=890897 for example),
but not between JIRA and Fisheye.
I tried
On Wed, Dec 16, 2009 at 1:36 AM, Justin Edelson justinedel...@gmail.com wrote:
Up at: http://fisheye6.atlassian.com/browse/sling
Thanks!
I have added this and similar links (ohloh, markmail) to
http://sling.apache.org/site/links.html, will be online soon.
-Bertrand
Hi all,
Felix Meschberger schrieb:
It looks like the hookup is already there between Fisheye and JIRA
(see
http://fisheye6.atlassian.com/changelog/sling/?cs=890897 for example),
but not between JIRA and Fisheye.
I tried setting up the missing link, but I get a exception from JIRA. I
[
https://issues.apache.org/jira/browse/SLING-1243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1243.
-
Resolution: Fixed
Fixed in revision 891177 by moving the tag in a separate line.
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/422/
[
https://issues.apache.org/jira/browse/SLING-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791359#action_12791359
]
Michael Dürig commented on SLING-1236:
--
There might be a solution for the first
[
https://issues.apache.org/jira/browse/SLING-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated SLING-1244:
Component/s: Commons
Fix Version/s: Commons Threads 3.0.0
Redesign thread pool
Hi zambak
In fact the map is always checked for each access, so a path matching a
map entry may even resolve faster than a patch without a match.
Hope this helps.
Regards
Felix
zambak schrieb:
Hi
I was wondering if one of the core devs would be able to comment on
performance impact of
Add pax runner support to maven-launchpad-plugin
Key: SLING-1245
URL: https://issues.apache.org/jira/browse/SLING-1245
Project: Sling
Issue Type: Improvement
Reporter: Justin
[
https://issues.apache.org/jira/browse/SLING-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791398#action_12791398
]
Felix Meschberger commented on SLING-1197:
--
Sounds good.
new prepare-package
Add version override configuration to maven-launchpad-plugin
Key: SLING-1246
URL: https://issues.apache.org/jira/browse/SLING-1246
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-1245:
--
Component/s: Maven Plugins
Add pax runner support to maven-launchpad-plugin
I'd strongly vote +1 since this could be a nice way of participation without
the overhead of
- checkout
- fixing
- creating patch
- waiting till someone downloads the patch and checks the diff
- asking for some changes in the patch
...
especially for minor bugs this can be usefull and speed up
Well, those steps would still be necessary to get changes made to trunk.
Crucible just gives you
a) a place to upload patches that is more code-friendly than JIRA
b) a place to comment upon code inline both patch submissions and existing
revisions
And I suspect we'd still want bug reports to
On Wed, Dec 16, 2009 at 8:39 PM, Justin Edelson justinedel...@gmail.com wrote:
...I suspect we'd still want bug reports to flow through JIRA,...
Yes, that's required because of the grant Apache permission to use
that code (or something like that) checkbox.
-Bertrand
Hi,
Bertrand Delacretaz schrieb:
On Wed, Dec 16, 2009 at 8:39 PM, Justin Edelson justinedel...@gmail.com
wrote:
...I suspect we'd still want bug reports to flow through JIRA,...
Yes, that's required because of the grant Apache permission to use
that code (or something like that) checkbox.
Yes I know - but the way of describing a but is a lightweight way.
Sometimes someone might see a problem without having a good solution and
copy paste of code isn't good style (and might even be unreadable for
bigger fragments of code).
So this is indeed not usefull for codesubmission but for
SlingPostServlet returns 500 error instead of 404 when attempting to delete
non-existent resource
-
Key: SLING-1247
URL:
[
https://issues.apache.org/jira/browse/SLING-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-1247:
Assignee: Felix Meschberger
SlingPostServlet returns 500 error instead of 404
[
https://issues.apache.org/jira/browse/SLING-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12791670#action_12791670
]
Felix Meschberger commented on SLING-1247:
--
Fixed in Rev. 891473: Instead of
See
http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/org.apache.sling$org.apache.sling.launchpad.testing/423/
See http://hudson.zones.apache.org/hudson/job/sling-trunk-1.5/423/changes
[
https://issues.apache.org/jira/browse/SLING-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reopened SLING-1231:
Assignee: Bertrand Delacretaz (was: Felix Meschberger)
Some integration tests
Hi,
In launchpad/testing the
org.apache.sling.launchpad.webapp.integrationtest.ResourceSuperTypeTest
fails, not sure when this started happening as in the last few days
all tests failed in Hudson due to other problems.
The failure scenario is:
Node N has sling:resourceType foo
Folder /apps/foo
24 matches
Mail list logo
