[jira] [Commented] (SLING-1778) Symlinks

[ https://issues.apache.org/jira/browse/SLING-1778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793984#comment-13793984 ] Bertrand Delacretaz commented on SLING-1778: The shared components might go un

[jira] [Commented] (SLING-3162) Sling virtual resource tree only appears in project when in Java EE perspective, not Java perspective

[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793986#comment-13793986 ] Stefan Egli commented on SLING-3162: [~justinedelson], the 'content browser' appears i

Re: [jira] [Commented] (SLING-1778) Symlinks

Hi Bertrand on where to potentially add such a resource provider... Am 14.10.2013 um 10:06 schrieb Bertrand Delacretaz (JIRA): > Bertrand Delacretaz commented on SLING-1778: > > > The shared components might go under bundles/commons/resourceprovider

Re: [jira] [Commented] (SLING-1778) Symlinks

Hi Felix, On Mon, Oct 14, 2013 at 10:27 AM, Felix Meschberger wrote: >> Bertrand Delacretaz commented on SLING-1778: ... >> The shared components might go under bundles/commons/resourceprovider > ---Currently we have two non-JCR resource providers: Filesystem and Bundle > Resource Provider; bot

[jira] [Assigned] (SLING-3164) Clarify and deprecate ClusterView.getId

[ https://issues.apache.org/jira/browse/SLING-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli reassigned SLING-3164: -- Assignee: Stefan Egli > Clarify and deprecate ClusterView.getId > -

[jira] [Resolved] (SLING-3164) Clarify and deprecate ClusterView.getId

[ https://issues.apache.org/jira/browse/SLING-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli resolved SLING-3164. Resolution: Fixed deprecated ClusterView.getId() and adjusted javadoc accordingly > Clarify and de

[jira] [Updated] (SLING-3164) Clarify and deprecate ClusterView.getId

[ https://issues.apache.org/jira/browse/SLING-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli updated SLING-3164: --- Fix Version/s: Discovery API 1.0.2 > Clarify and deprecate ClusterView.getId > --

[jira] [Commented] (SLING-3165) Cannot remove Bundle or Content Package Module from Server

[ https://issues.apache.org/jira/browse/SLING-3165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794059#comment-13794059 ] Robert Munteanu commented on SLING-3165: As a workaround, you can right-click on t

[jira] [Commented] (SLING-3162) Sling virtual resource tree only appears in project when in Java EE perspective, not Java perspective

[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794060#comment-13794060 ] Robert Munteanu commented on SLING-3162: I don't think the package explorer uses t

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling JCR Installer #1969

See

Jenkins build is back to normal : sling-trunk-1.6 #1969

See

[jira] [Updated] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3162: -- Summary: Sling virtual resource tree only appears in the Project Explorer, not the Package Expl

[jira] [Commented] (SLING-3162) Sling virtual resource tree only appears in project when in Java EE perspective, not Java perspective

[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794102#comment-13794102 ] Justin Edelson commented on SLING-3162: --- [~egli] Ah... good point. I didn't notice t

[jira] [Updated] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[ https://issues.apache.org/jira/browse/SLING-3162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3162: -- Description: In the Java EE perspective, the default navigator view is the Project Explorer.

[jira] [Resolved] (SLING-3168) Deprecating JobUtil class?

[ https://issues.apache.org/jira/browse/SLING-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3168. - Resolution: Fixed I've dropped the priority completely and therefore simply deprecated it

[jira] [Created] (SLING-3171) Deprecate job name handling

Carsten Ziegeler created SLING-3171: --- Summary: Deprecate job name handling Key: SLING-3171 URL: https://issues.apache.org/jira/browse/SLING-3171 Project: Sling Issue Type: Task Co

[jira] [Resolved] (SLING-3171) Deprecate job name handling

[ https://issues.apache.org/jira/browse/SLING-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3171. - Resolution: Fixed > Deprecate job name handling > --- > >

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing #1970

See

Jenkins build became unstable: sling-trunk-1.6 #1970

See

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing #1971

See

Jenkins build is back to stable : sling-trunk-1.6 #1971

See

[jira] [Resolved] (SLING-3166) Job Scheduling Possibilities

[ https://issues.apache.org/jira/browse/SLING-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3166. - Resolution: Fixed I've added monthly and yearly and also support for a cron expression -

[jira] [Comment Edited] (SLING-3028) Support for progress tracking of jobs and keeping jobs

[ https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793608#comment-13793608 ] Carsten Ziegeler edited comment on SLING-3028 at 10/14/13 4:43 PM: -

Build failed in Jenkins: sling-trunk-1.7 #337

See Changes: [cziegeler] SLING-3168 : Deprecating JobUtil class? -- [...truncated 14839 lines...] 14.10.2013 15:13:22.513 *INFO* [main] org.apache.sling.event Service [org.apache.sling.event.impl

Jenkins build is back to normal : sling-trunk-1.7 #338

See

[jira] [Commented] (SLING-3169) Naming of Job related enumerations

[ https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794375#comment-13794375 ] Carsten Ziegeler commented on SLING-3169: - Or maybe we don't need the FAILED state

[jira] [Commented] (SLING-3166) Job Scheduling Possibilities

[ https://issues.apache.org/jira/browse/SLING-3166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794447#comment-13794447 ] Stefan Seifert commented on SLING-3166: --- thanks, looks perfect and the api is much c

[jira] [Commented] (SLING-3168) Deprecating JobUtil class?

[ https://issues.apache.org/jira/browse/SLING-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794494#comment-13794494 ] Stefan Seifert commented on SLING-3168: --- ok, good why was job priority completely d

[jira] [Commented] (SLING-3170) Complex Job Result Structures

[ https://issues.apache.org/jira/browse/SLING-3170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794518#comment-13794518 ] Stefan Seifert commented on SLING-3170: --- option A): job engine provides a resource p

[jira] [Commented] (SLING-3167) Job Logging

[ https://issues.apache.org/jira/browse/SLING-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794523#comment-13794523 ] Stefan Seifert commented on SLING-3167: --- perhaps this is somewhat related to SLING-3

[jira] [Commented] (SLING-3171) Deprecate job name handling

[ https://issues.apache.org/jira/browse/SLING-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794528#comment-13794528 ] Stefan Seifert commented on SLING-3171: --- +1 for removing/deprecating the current uni

[jira] [Commented] (SLING-3169) Naming of Job related enumerations

[ https://issues.apache.org/jira/browse/SLING-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794536#comment-13794536 ] Stefan Seifert commented on SLING-3169: --- ok, lets have a look on the current impleme

[jira] [Created] (SLING-3172) Job schedule name handling

Stefan Seifert created SLING-3172: - Summary: Job schedule name handling Key: SLING-3172 URL: https://issues.apache.org/jira/browse/SLING-3172 Project: Sling Issue Type: Improvement

[jira] [Commented] (SLING-3028) Support for progress tracking of jobs and keeping jobs

[ https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794543#comment-13794543 ] Stefan Seifert commented on SLING-3028: --- i commented on the seperate ticktes. for th

[jira] [Created] (SLING-3173) Job Engine: Support custome queue implementations

Stefan Seifert created SLING-3173: - Summary: Job Engine: Support custome queue implementations Key: SLING-3173 URL: https://issues.apache.org/jira/browse/SLING-3173 Project: Sling Issue Type:

[jira] [Commented] (SLING-3172) Job schedule name handling

[ https://issues.apache.org/jira/browse/SLING-3172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794548#comment-13794548 ] Stefan Seifert commented on SLING-3172: --- as with the (now deprecated) job name i fin

[jira] [Commented] (SLING-3173) Job Engine: Support custome queue implementations

[ https://issues.apache.org/jira/browse/SLING-3173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13794554#comment-13794554 ] Stefan Seifert commented on SLING-3173: --- we should not bother on this for the first/