See
https://builds.apache.org/job/sling-oak-it-1.6/org.apache.sling$org.apache.sling.launchpad.testing/31/
[
https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-3529.
-
Resolution: Won't Fix
I realized that this is not really possible from within a bundle
[
https://issues.apache.org/jira/browse/SLING-3117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3117.
Resolution: Fixed
* http://svn.apache.org/viewvc?view=revisionrevision=1594002 added
Tommaso Teofili created SLING-3553:
--
Summary: Run FindBugs (and fix accordingly) on Sling Replication
code
Key: SLING-3553
URL: https://issues.apache.org/jira/browse/SLING-3553
Project: Sling
Chetan,
for the long-term this would be an option. But atm I don't see an option to
adapt our code to such a changed structure for various project-related
reasons.
But nevertheless an idea, we should think about.
Jörg
2014-05-13 8:34 GMT+02:00 Chetan Mehrotra (JIRA) j...@apache.org:
[
[
https://issues.apache.org/jira/browse/SLING-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reopened SLING-3529:
-
Move startup handling to a separate bundle
--
See https://builds.apache.org/job/sling-trunk-1.7/492/changes
Hugh Mc Guinness created SLING-3554:
---
Summary: createDataStoreGarbageCollector returns null
Key: SLING-3554
URL: https://issues.apache.org/jira/browse/SLING-3554
Project: Sling
Issue Type:
[
https://issues.apache.org/jira/browse/SLING-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996268#comment-13996268
]
Carsten Ziegeler commented on SLING-3525:
-
The startup behaviour can't be made
[
https://issues.apache.org/jira/browse/SLING-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996215#comment-13996215
]
Tommaso Teofili commented on SLING-3553:
thanks [~rombert], hopefully we'll get it
[
https://issues.apache.org/jira/browse/SLING-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu resolved SLING-3552.
Resolution: Fixed
Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1594203
Robert Munteanu created SLING-3555:
--
Summary: Simpler target platform management with the target
platform generator DSL
Key: SLING-3555
URL: https://issues.apache.org/jira/browse/SLING-3555
Project:
[
https://issues.apache.org/jira/browse/SLING-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996135#comment-13996135
]
Chetan Mehrotra commented on SLING-3525:
Looks like you are trying to access the
[
https://issues.apache.org/jira/browse/SLING-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996409#comment-13996409
]
Jörg Hoh commented on SLING-3525:
-
Well, that's probably more work than expected then.
Robert Munteanu created SLING-3556:
--
Summary: The Filter API should work on resources, not on
filesystem-based paths
Key: SLING-3556
URL: https://issues.apache.org/jira/browse/SLING-3556
Project:
[
https://issues.apache.org/jira/browse/SLING-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996445#comment-13996445
]
Igor Sechyn commented on SLING-3547:
we are currently experiencing the same issues in
[
https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2651:
---
Description: We should have the ability to update just a section of the
local checkout,
Hello list
When processing events and jobs, the corresponding subject triggering
the event usually gets lost. This lead to event handlers / job consumers
often operating with administrative sessions/resolvers to do their work,
which in turn can lead to privilege escalations.
A possible solution
Hi,
FYI I have created https://issues.apache.org/jira/browse/INFRA-7715
about this - if someone here knows how to fix the issue please let me
know, I'm not too familiar with buildbot.
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2651:
---
Summary: Manually trigger sync on files/directories (was: Manually trigger
import on
[
https://issues.apache.org/jira/browse/SLING-3552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996482#comment-13996482
]
Robert Munteanu commented on SLING-3552:
Follow-up fix in
[
https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2651:
---
Summary: Manually trigger import on files/directories (was: [Tooling]
manually trigger sync
[
https://issues.apache.org/jira/browse/SLING-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tommaso Teofili updated SLING-3548:
---
Priority: Trivial (was: Major)
Replication queue servlet doesn't use the queue parameter
[
https://issues.apache.org/jira/browse/SLING-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-2651:
---
Description: We should be able to manually publish a subtree of content, as
opposed to the
I have processed a few pull requests from
https://github.com/apache/sling/pulls, but I don't see how to close
them. Does anyone know?
Thanks,
Justin
[
https://issues.apache.org/jira/browse/SLING-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson resolved SLING-3547.
---
Resolution: Fixed
I have applied a slightly modified version of this patch in r1594343; the
[
https://issues.apache.org/jira/browse/SLING-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Edelson updated SLING-3547:
--
Fix Version/s: Sling Models Implementation 1.0.6
Default handling for numerical types on
Hi Lars,
I see your point, I don't see right now how a general approach could look
like. However, the creator of a job could add the subject as a property to
the job and the consumer can use this value to create a resource resolver
based on that value. But I think this has to be done on a job by
On Wednesday 07 May 2014 07:59:26 Carsten Ziegeler wrote:
Hi,
with the recent changes, the jsp scripting now uses the commons compiler
(the java scripting we have already does so). This avoids embedding the
eclipse compiler twice and now we have a single bundle dealing with java
compilation
+1
Sounds sensible and is certainly a good separation of concerns.
Regards
Julian
On Wed, May 7, 2014 at 7:59 AM, Carsten Ziegeler cziege...@apache.org wrote:
Hi,
with the recent changes, the jsp scripting now uses the commons compiler
(the java scripting we have already does so). This
Thanks everyone - I've moved the bundle
Carsten
2014-05-13 17:56 GMT+02:00 Oliver Lietz apa...@oliverlietz.de:
On Wednesday 07 May 2014 07:59:26 Carsten Ziegeler wrote:
Hi,
with the recent changes, the jsp scripting now uses the commons compiler
(the java scripting we have already
[
https://issues.apache.org/jira/browse/SLING-3553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996206#comment-13996206
]
Tommaso Teofili commented on SLING-3553:
added FindBugs to pom.xml and fixed first
[
https://issues.apache.org/jira/browse/SLING-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13996465#comment-13996465
]
Robert Munteanu commented on SLING-3556:
Attached [^SLING-3556-wip-1.patch], which
[
https://issues.apache.org/jira/browse/SLING-3525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13995155#comment-13995155
]
Jörg Hoh commented on SLING-3525:
-
Hi Carsten,
I attached the complete FFDC file and just
[
https://issues.apache.org/jira/browse/SLING-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Klco updated SLING-3485:
Attachment: SLING-3485.diff
Sorry for taking so long to follow up with this. I marked the Sling API as
35 matches
Mail list logo