[jira] [Created] (SLING-4711) Syncing via a coordinate agent - conflicts resolution

[Maciej Dybek (JIRA)]

Maciej Dybek created SLING-4711:
---

 Summary: Syncing via a coordinate agent - conflicts resolution
 Key: SLING-4711
 URL: https://issues.apache.org/jira/browse/SLING-4711
 Project: Sling
  Issue Type: Bug
  Components: Distribution
Affects Versions: Content Distribution Core 0.1.1
Reporter: Maciej Dybek


Basically this issue should be treated as a question/bug.

I'm trying to synchronize two Sling instances A and B via a (third) 
coordinating instance C. This scenario is described 
[here|https://github.com/apache/sling/tree/trunk/contrib/extensions/distribution#sync-distribution].

I am using SyncDistributionAgentFactory on the syncing instance and 
QueueDistributionAgentFactory on synced instances.
On the syncing instance I'm using ScheduledDistributionTrigger which runs every 
60 seconds.

The scenario I wanted to test is conflict resolution. I made changes to the 
same resource on both "publish" instances A and B. On A instance I changed 
property X to value "A" and on B instance I changed the same property  to value 
"B" 

Currently the algorithm is as follows:
1. The syncing agent retrieves distribution packagages from both synced 
instances A and B.
2. The syncing agent have now two packagages which should be send to importers 
on synced instances.
3. The agent checks the first package and it sees that the package is from 
instance A thus it is not going to send the package to A instance. The agent 
sends the package to B instance. On B instance property X is of value "A".
4. The agent checks the second package and it sees that the package is from 
instance B thus it sends the package only to A instance. On A instance property 
X is of value B.

*Actual results:*
Instances A and B are unsynchronized because the same property is of different 
values on both of them.

*Expected results:*
Instances A and B should have the same content.

The question is if this is expected behaviour? Should I use some other 
implementations to sync my Sling instances?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-4694) Add ability to identify mime type based on file content

[Satya Deep Maheshwari (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539284#comment-14539284
 ] 

Satya Deep Maheshwari commented on SLING-4694:
--

Here's the pull request for the proposed implementation: 
https://github.com/apache/sling/pull/89
[~bdelacretaz], please review.
It includes unit tests for the newly added contentdetection bundle. I haven't 
yet add unit tests for the changes done in webdav and commons/mime bundles.

> Add ability to identify mime type based on file content
> ---
>
> Key: SLING-4694
> URL: https://issues.apache.org/jira/browse/SLING-4694
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: JCR Webdav 2.2.2
>Reporter: Satya Deep Maheshwari
>
> *Problem description:* I am facing a problem with the mime type detection of 
> a file. While debugging, I see that SlingTikaDetector.detect method is used 
> for detecting the mime type of my file. See [1]. This method just seems to 
> rely on the name of the file for detecting its mime type. Even though its 
> passed an inputstream of the file, it does not seem to use it for mime type 
> detection. So if my file name is something like xyz.tmp, it detects its mime 
> type as application/octet-stream (the default) while it may actually be a png 
> file. This is a common scenario with webdav clients wherein temporary files 
> get created with such names while being edited.
> *Suggested Solution:* 
> Quoting [~rombert]
> {quote}
> Following the discussions at SLING-1059 [1] and SLING-255 [2] I can
> infer that we more or less opted out of the 'heavy-weight' approach of
> actually parsing the input stream. Not sure if we want to revisit that
> TBH. At any rate, our MimeTypeService does not have an API for getting
> the file content based on the input stream.
> I think though there's a way around it, but only at the code level.
> The org.apache.sling.jcr.webdav.impl.helper.SlingResourceConfig class
> hardcodes the Detector implementation to be a SlingTikaDetector.
> I think it is worthwile to raise a Jira issue for this and it would
> definitely expedite the fix if you're willing to submit a patch / pull
> request. I think it can be as simple as adding a @Reference to a Tika
> Detector to the SlingWebDavServlet and then passing that to the
> SlingServletConfig.
> Cheers,
> Robert
> [1]: https://issues.apache.org/jira/browse/SLING-1059
> [2]: https://issues.apache.org/jira/browse/SLING-255
> {quote}
> Related mailing-list thread on this: 
> http://apache-sling.73963.n3.nabble.com/mime-type-detection-td4050586.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-4694) Add ability to identify mime type based on file content

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539275#comment-14539275
 ] 

ASF GitHub Bot commented on SLING-4694:
---

GitHub user sdmcraft opened a pull request:

https://github.com/apache/sling/pull/89

SLING-4694:Add ability to identify mime type based on file content

* Initial checkin. Implements the basic idea. See 
https://issues.apache.org/jira/browse/SLING-4694 for details

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sdmcraft/sling SLING-4694

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/89.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #89


commit fefeec67c83cdd6e23b70784cf732ef692082bb4
Author: Satya Deep Maheshwari 
Date:   2015-05-08T07:55:09Z

SLING-4694:Add ability to identify mime type based on file content
* Initial checkin. Implements the basic idea. See 
https://issues.apache.org/jira/browse/SLING-4694 for details




> Add ability to identify mime type based on file content
> ---
>
> Key: SLING-4694
> URL: https://issues.apache.org/jira/browse/SLING-4694
> Project: Sling
>  Issue Type: Improvement
>  Components: Servlets
>Affects Versions: JCR Webdav 2.2.2
>Reporter: Satya Deep Maheshwari
>
> *Problem description:* I am facing a problem with the mime type detection of 
> a file. While debugging, I see that SlingTikaDetector.detect method is used 
> for detecting the mime type of my file. See [1]. This method just seems to 
> rely on the name of the file for detecting its mime type. Even though its 
> passed an inputstream of the file, it does not seem to use it for mime type 
> detection. So if my file name is something like xyz.tmp, it detects its mime 
> type as application/octet-stream (the default) while it may actually be a png 
> file. This is a common scenario with webdav clients wherein temporary files 
> get created with such names while being edited.
> *Suggested Solution:* 
> Quoting [~rombert]
> {quote}
> Following the discussions at SLING-1059 [1] and SLING-255 [2] I can
> infer that we more or less opted out of the 'heavy-weight' approach of
> actually parsing the input stream. Not sure if we want to revisit that
> TBH. At any rate, our MimeTypeService does not have an API for getting
> the file content based on the input stream.
> I think though there's a way around it, but only at the code level.
> The org.apache.sling.jcr.webdav.impl.helper.SlingResourceConfig class
> hardcodes the Detector implementation to be a SlingTikaDetector.
> I think it is worthwile to raise a Jira issue for this and it would
> definitely expedite the fix if you're willing to submit a patch / pull
> request. I think it can be as simple as adding a @Reference to a Tika
> Detector to the SlingWebDavServlet and then passing that to the
> SlingServletConfig.
> Cheers,
> Robert
> [1]: https://issues.apache.org/jira/browse/SLING-1059
> [2]: https://issues.apache.org/jira/browse/SLING-255
> {quote}
> Related mailing-list thread on this: 
> http://apache-sling.73963.n3.nabble.com/mime-type-detection-td4050586.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] sling pull request: SLING-4694:Add ability to identify mime type b...

[sdmcraft]

GitHub user sdmcraft opened a pull request:

https://github.com/apache/sling/pull/89

SLING-4694:Add ability to identify mime type based on file content

* Initial checkin. Implements the basic idea. See 
https://issues.apache.org/jira/browse/SLING-4694 for details

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sdmcraft/sling SLING-4694

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/89.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #89


commit fefeec67c83cdd6e23b70784cf732ef692082bb4
Author: Satya Deep Maheshwari 
Date:   2015-05-08T07:55:09Z

SLING-4694:Add ability to identify mime type based on file content
* Initial checkin. Implements the basic idea. See 
https://issues.apache.org/jira/browse/SLING-4694 for details




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [RT] Move to Oak

[Chetan Mehrotra]

+1
Chetan Mehrotra


On Tue, May 12, 2015 at 1:46 AM, Carsten Ziegeler  wrote:
> Am 11.05.15 um 22:08 schrieb Oliver Lietz:
>
>>
>> e.g.  Auth, Servlets, Content Loader, WebDav, DavEx handle workspaces. Do we
>> remove that code also in future releases or do we want to keep it?
>
> Ah ok, I think we already removed the support in the servlets resolver
> some years ago (same in resource resolver). I think we could remove this
> stuff over time, although there might be no real reason to do so.
> I assume that all of this works on Oak as long as workspaces are not used.
>
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

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

[Apache Jenkins Server]

See 

Changes:

[sseifert] SLING-4710 do not export javax.inject in sling models API bundle
add javax.inject dependency in launchpad from 
org.apache.geronimo.specs/geronimo-atinject_1.0_spec/1.0 because the original 
javax.inject jar is not an osgi bundle

--
[...truncated 38228 lines...]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [6.454s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [10.707s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [5.729s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[6.181s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [3.919s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:57.450s]
[INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver  
SUCCESS [48.156s]
[INFO] Apache Sling Versioning Integration Tests . SUCCESS [41.794s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.438s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [5.008s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [5.964s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [3.867s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [7.575s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [1:42.499s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [8.751s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [6.578s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [6.655s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [4.388s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [8.348s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [19.586s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [53.415s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [11.495s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [10.297s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [4.202s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [8.812s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [5.241s]
[INFO] Apache Sling Distributed Event Admin .. SUCCESS [5.769s]
[INFO] Apache Sling Discovery API  SUCCESS [4.291s]
[INFO] Apache Sling Discovery Commons Bundle . SUCCESS [4.642s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS 
[1:17:25.581s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [4.475s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [3.826s]
[INFO] Apache Sling Event Support  FAILURE [3:54.627s]
[INFO] Apache Sling Feature Flags  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Service User Mapper .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Health Check Core  SKIPPED
[INFO] Apache Sling Health Check Annotations . SKIPPED
[INFO] Apache Sling Health Check Samples . SKIPPED
[INFO] Apache Sling Health Check Support Components .. SKIPPED
[INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED
[INFO] Apache Sling Health Check JUnit Bridge  SKIPPED
[INFO] Apache Sling Health Check Integration Tests ... SKIPPED
[INFO] Apache Sling Health Check Reactor POM . SKIPPED
[INFO] Apache Sling Resource Access Security . SKIPPED
[INFO] Apache Sling Resource Access Security Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework API . SKIPPED
[INFO] Apache Sling Validation Framework Core Implementation  SKIPPED
[INFO] Apache Sling Validation Framework Testing Services  SKIPPED
[INFO] Apache Sling Validation Framework Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework Examples  SKIPPED
[INFO] Apache Sling Validation Framework Builder . SKIPPED
[INFO] Apache Sling Models API ... SKIPPED
[INFO] Apache Sling Models Implementation  SKIPPED
[INFO] Apache Sling Launchpad Application Builder  SKIPPED
[INFO] Apache Sling Models Integration Tests . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Sc

Jenkins build became unstable: sling-trunk-1.8 #1099

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Implements simple Comments service

--
[...truncated 19374 lines...]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [18.684s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [9.533s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [5.603s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[5.051s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [5.068s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [2:28.443s]
[INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver  
SUCCESS [46.964s]
[INFO] Apache Sling Versioning Integration Tests . SUCCESS [47.365s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [7.451s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [4.519s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [4.949s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [5.153s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [4.614s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [1:27.726s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [6.264s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [6.814s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [6.177s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [3.862s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [4.560s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [16.446s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [47.833s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [10.274s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [10.490s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [4.895s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [6.114s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [8.148s]
[INFO] Apache Sling Distributed Event Admin .. SUCCESS [7.621s]
[INFO] Apache Sling Discovery API  SUCCESS [4.124s]
[INFO] Apache Sling Discovery Commons Bundle . SUCCESS [8.019s]
[INFO] Apache Sling Resource-Based Discovery Service . FAILURE [54:15.596s]
[INFO] Apache Sling Discovery Support Bundle . SKIPPED
[INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED
[INFO] Apache Sling Event Support  SKIPPED
[INFO] Apache Sling Feature Flags  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Service User Mapper .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Health Check Core  SKIPPED
[INFO] Apache Sling Health Check Annotations . SKIPPED
[INFO] Apache Sling Health Check Samples . SKIPPED
[INFO] Apache Sling Health Check Support Components .. SKIPPED
[INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED
[INFO] Apache Sling Health Check JUnit Bridge  SKIPPED
[INFO] Apache Sling Health Check Integration Tests ... SKIPPED
[INFO] Apache Sling Health Check Reactor POM . SKIPPED
[INFO] Apache Sling Resource Access Security . SKIPPED
[INFO] Apache Sling Resource Access Security Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework API . SKIPPED
[INFO] Apache Sling Validation Framework Core Implementation  SKIPPED
[INFO] Apache Sling Validation Framework Testing Services  SKIPPED
[INFO] Apache Sling Validation Framework Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework Examples  SKIPPED
[INFO] Apache Sling Validation Framework Builder . SKIPPED
[INFO] Apache Sling Models API ... SKIPPED
[INFO] Apache Sling Models Implementation  SKIPPED
[INFO] Apache Sling Models Integration Tests . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Health Checks .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] Apache Sling JUnit Performance  SKIPPED
[INFO] Apache Sling Testing Resource Resolver Mock ...

Jenkins build is back to normal : sling-trunk-1.8 #1098

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-4710) remove javax.inject from org.apache.sling.models.api

[Stefan Seifert (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Stefan Seifert resolved SLING-4710.
---
Resolution: Fixed

Completed: At revision: 1678823  

javax.inject export removed in sling models API 1.2.0

in sling launchpad 8-SNAPSHOT i added the dependency 
{{org.apache.geronimo.specs/geronimo-atinject_1.0_spec/1.0}} as recommended by 
oliver (the original javax.inject jar from maven central is not an osgi bundle).

> remove javax.inject from org.apache.sling.models.api
> 
>
> Key: SLING-4710
> URL: https://issues.apache.org/jira/browse/SLING-4710
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
>  Labels: models
> Fix For: Sling Models API 1.2.0
>
>
> see discussion in SLING-3944
> javax.inject should not be exported by the models api bundle, but deployed 
> via a separate bundle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-3944) org.apache.sling.scripting.java bundle exports javax.inject package in wrong version

[Stefan Seifert (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538600#comment-14538600
 ] 

Stefan Seifert commented on SLING-3944:
---

+1 from my side, i created SLING-4710 to remove the embedded javax.inject from 
the sling models API bundle.

> org.apache.sling.scripting.java bundle exports javax.inject package in wrong 
> version
> 
>
> Key: SLING-3944
> URL: https://issues.apache.org/jira/browse/SLING-3944
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
>Affects Versions: Scripting Java 2.0.10
>Reporter: Markus Haack
>Assignee: Oliver Lietz
>Priority: Critical
> Fix For: Scripting Java 2.0.12
>
> Attachments: Screen Shot 2015-05-06 at 12.36.05.png
>
>
> The org.apache.sling.scripting.java bundle exports the package javax.inject 
> in the version of the bundle, which is wrong and should be fixed. 
> This can lead to bundle version problems for other bundles which depend on 
> javax.inject in version "[1.0,2)" - the correct version (like Jersey Web 
> Services libraries).
> Either export javax.inject with version 0.0.0 or even better with the correct 
> version 1.0.0.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4710) remove javax.inject from org.apache.sling.models.api

[Stefan Seifert (JIRA)]

Stefan Seifert created SLING-4710:
-

 Summary: remove javax.inject from org.apache.sling.models.api
 Key: SLING-4710
 URL: https://issues.apache.org/jira/browse/SLING-4710
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Stefan Seifert
Assignee: Stefan Seifert
Priority: Minor
 Fix For: Sling Models API 1.2.0


see discussion in SLING-3944

javax.inject should not be exported by the models api bundle, but deployed via 
a separate bundle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [RT] Move to Oak

[Carsten Ziegeler]

Am 11.05.15 um 22:08 schrieb Oliver Lietz:

> 
> e.g.  Auth, Servlets, Content Loader, WebDav, DavEx handle workspaces. Do we 
> remove that code also in future releases or do we want to keep it?

Ah ok, I think we already removed the support in the servlets resolver
some years ago (same in resource resolver). I think we could remove this
stuff over time, although there might be no real reason to do so.
I assume that all of this works on Oak as long as workspaces are not used.

Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Jenkins build became unstable: sling-trunk-1.7 #1807

[Apache Jenkins Server]

See 

Re: [RT] Move to Oak

[Oliver Lietz]

On Monday 11 May 2015 21:52:02 Carsten Ziegeler wrote:
> Am 11.05.15 um 21:35 schrieb Oliver Lietz:
> > On Monday 11 May 2015 20:40:51 Carsten Ziegeler wrote:
> >> Hi,
> >> 
> >> what about moving our launchpad completely to Oak and forget about the
> >> "old" jackrabbit in there? I don't think we should provide both in our
> >> launchpad in the long run.
> > 
> > +1 if we are on par with Jackrabbit, but we don't even have a release of
> > Oak server yet - see SLING-4528.
> > 
> > Does it mean dropping Jackrabbit completely and e.g. removing support for
> > workspaces?
> 
> Not sure, what you mean by this? This means not having jackrabbit in the
> launchpad but just Oak. This launchpad has then no support for
> workspaces, but if users need it they can replace it with the jackrabbit
> version themselves. Apart from that I don't think we have any workspace
> support in any other bundle.

e.g.  Auth, Servlets, Content Loader, WebDav, DavEx handle workspaces. Do we 
remove that code also in future releases or do we want to keep it?

O.

> Carsten

Build failed in Jenkins: sling-trunk-1.8 #1097

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Revert update to latest jackrabbit server

[cziegeler] SLING-4709 : Update to jackrabbit 2.10.0

[cziegeler] SLING-4709 : Update to jackrabbit 2.10.0

--
[...truncated 18186 lines...]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [5.130s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [10.579s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [3.309s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[3.332s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [3.556s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [2:16.183s]
[INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver  
SUCCESS [52.249s]
[INFO] Apache Sling Versioning Integration Tests . SUCCESS [43.485s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.532s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [5.422s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.458s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [8.298s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [5.060s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [1:23.309s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [4.094s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [4.951s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [4.930s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [2.095s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [1.863s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [11.795s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [47.921s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [5.663s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [5.315s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [2.786s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [3.497s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [3.218s]
[INFO] Apache Sling Distributed Event Admin .. SUCCESS [5.231s]
[INFO] Apache Sling Discovery API  SUCCESS [2.880s]
[INFO] Apache Sling Discovery Commons Bundle . SUCCESS [3.928s]
[INFO] Apache Sling Resource-Based Discovery Service . FAILURE [50:59.660s]
[INFO] Apache Sling Discovery Support Bundle . SKIPPED
[INFO] Apache Sling Discovery Standalone Implementation .. SKIPPED
[INFO] Apache Sling Event Support  SKIPPED
[INFO] Apache Sling Feature Flags  SKIPPED
[INFO] Apache Sling Filesystem Resource Provider . SKIPPED
[INFO] Apache Sling javax.activation bundle .. SKIPPED
[INFO] Apache Sling Service User Mapper .. SKIPPED
[INFO] Apache Sling Settings . SKIPPED
[INFO] Apache Sling Web Console Branding . SKIPPED
[INFO] Apache Sling Web Console Security Provider  SKIPPED
[INFO] Apache Sling Explorer . SKIPPED
[INFO] Apache Sling Health Check Core  SKIPPED
[INFO] Apache Sling Health Check Annotations . SKIPPED
[INFO] Apache Sling Health Check Samples . SKIPPED
[INFO] Apache Sling Health Check Support Components .. SKIPPED
[INFO] Apache Sling Health Check Webconsole Plugin ... SKIPPED
[INFO] Apache Sling Health Check JUnit Bridge  SKIPPED
[INFO] Apache Sling Health Check Integration Tests ... SKIPPED
[INFO] Apache Sling Health Check Reactor POM . SKIPPED
[INFO] Apache Sling Resource Access Security . SKIPPED
[INFO] Apache Sling Resource Access Security Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework API . SKIPPED
[INFO] Apache Sling Validation Framework Core Implementation  SKIPPED
[INFO] Apache Sling Validation Framework Testing Services  SKIPPED
[INFO] Apache Sling Validation Framework Integration Tests  SKIPPED
[INFO] Apache Sling Validation Framework Examples  SKIPPED
[INFO] Apache Sling Validation Framework Builder . SKIPPED
[INFO] Apache Sling Models API ... SKIPPED
[INFO] Apache Sling Models Implementation  SKIPPED
[INFO] Apache Sling Models Integration Tests . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core ... SKIPPED
[INFO] Apache Sling JUnit Scriptable Tests Provider .. SKIPPED
[INFO] Apache Sling JUnit Health Checks .. SKIPPED
[INFO] Apache Sling JUnit Remote Tests Runners ... SKIPPED
[INFO] A

Re: [RT] Move to Oak

[Carsten Ziegeler]

Am 11.05.15 um 21:35 schrieb Ruben Reusser:
> just my 2c - will somebody go through all the samples/documentation when
> moving to oak and make sure everything still works/update the
> documentation?
> 
The goal is to do this - reality will hit us here, I'm pretty sure.

However, most of this is already outdated, so we have to do that anyway.

Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [RT] Move to Oak

[Carsten Ziegeler]

Am 11.05.15 um 21:35 schrieb Oliver Lietz:
> On Monday 11 May 2015 20:40:51 Carsten Ziegeler wrote:
>> Hi,
>>
>> what about moving our launchpad completely to Oak and forget about the
>> "old" jackrabbit in there? I don't think we should provide both in our
>> launchpad in the long run.
> 
> +1 if we are on par with Jackrabbit, but we don't even have a release of Oak 
> server yet - see SLING-4528.
> 
> Does it mean dropping Jackrabbit completely and e.g. removing support for 
> workspaces?
> 
Not sure, what you mean by this? This means not having jackrabbit in the
launchpad but just Oak. This launchpad has then no support for
workspaces, but if users need it they can replace it with the jackrabbit
version themselves. Apart from that I don't think we have any workspace
support in any other bundle.

Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-4649) FullTextIndexingTest.testUploadedPdfIsIndexed fails on Oak

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538525#comment-14538525
 ] 

Carsten Ziegeler commented on SLING-4649:
-

The framework properties are part of the model, so this could somehow be used 
to create a Karaf feature

> FullTextIndexingTest.testUploadedPdfIsIndexed fails on Oak
> --
>
> Key: SLING-4649
> URL: https://issues.apache.org/jira/browse/SLING-4649
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad, Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>  Labels: sling-IT
> Fix For: Launchpad Builder 8
>
>
> Failed tests: 
>   FullTextIndexingTest.testUploadedPdfIsIndexed:57 RetryLoop failed, 
> condition is false after 10 seconds: A document containing 'Excepteur' is 
> found under /FullTextIndexingTest
> This last worked on Jenkins with [sling-oak-it-1.7 
> 42|https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.7/42/] - 
> r1673619, Apr 17, 2015 5:20:55 PM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-4649) FullTextIndexingTest.testUploadedPdfIsIndexed fails on Oak

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538516#comment-14538516
 ] 

Oliver Lietz commented on SLING-4649:
-

Exactly. We ([~cziegeler], [~bosschaert] and myself) discussed at adaptTo() 
2014, if/how it is possible to use the new provisioning model to generate 
Slingfeatures, Karaf Features and OSGi Subsystems. This is a long way to go, 
but a common configuration would help for sure.

> FullTextIndexingTest.testUploadedPdfIsIndexed fails on Oak
> --
>
> Key: SLING-4649
> URL: https://issues.apache.org/jira/browse/SLING-4649
> Project: Sling
>  Issue Type: Bug
>  Components: Launchpad, Oak
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>  Labels: sling-IT
> Fix For: Launchpad Builder 8
>
>
> Failed tests: 
>   FullTextIndexingTest.testUploadedPdfIsIndexed:57 RetryLoop failed, 
> condition is false after 10 seconds: A document containing 'Excepteur' is 
> found under /FullTextIndexingTest
> This last worked on Jenkins with [sling-oak-it-1.7 
> 42|https://builds.apache.org/view/S-Z/view/Sling/job/sling-oak-it-1.7/42/] - 
> r1673619, Apr 17, 2015 5:20:55 PM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [RT] Move to Oak

[Oliver Lietz]

On Monday 11 May 2015 20:40:51 Carsten Ziegeler wrote:
> Hi,
> 
> what about moving our launchpad completely to Oak and forget about the
> "old" jackrabbit in there? I don't think we should provide both in our
> launchpad in the long run.

+1 if we are on par with Jackrabbit, but we don't even have a release of Oak 
server yet - see SLING-4528.

Does it mean dropping Jackrabbit completely and e.g. removing support for 
workspaces?

Regards,
O.

> The bundles for jackrabbit are still around if someone wants to use them
> 
> Carsten

Re: [RT] Move to Oak

[Ruben Reusser]

just my 2c - will somebody go through all the samples/documentation when 
moving to oak and make sure everything still works/update the 
documentation?


Ruben

On 5/11/2015 12:29 PM, Antonio Sanso wrote:

+1

regards

antonio

On May 11, 2015, at 8:40 PM, Carsten Ziegeler  wrote:


Hi,

what about moving our launchpad completely to Oak and forget about the
"old" jackrabbit in there? I don't think we should provide both in our
launchpad in the long run.

The bundles for jackrabbit are still around if someone wants to use them

Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

Re: [RT] Move to Oak

[Antonio Sanso]

+1

regards

antonio

On May 11, 2015, at 8:40 PM, Carsten Ziegeler  wrote:

> Hi,
> 
> what about moving our launchpad completely to Oak and forget about the
> "old" jackrabbit in there? I don't think we should provide both in our
> launchpad in the long run.
> 
> The bundles for jackrabbit are still around if someone wants to use them
> 
> Carsten
> -- 
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org

Re: [RT] Move to Oak

[Ian Boston]

+1
Ian

On 11 May 2015 at 19:40, Carsten Ziegeler  wrote:

> Hi,
>
> what about moving our launchpad completely to Oak and forget about the
> "old" jackrabbit in there? I don't think we should provide both in our
> launchpad in the long run.
>
> The bundles for jackrabbit are still around if someone wants to use them
>
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

[jira] [Commented] (SLING-4528) Moving to Oak

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538488#comment-14538488
 ] 

Oliver Lietz commented on SLING-4528:
-

[~rombert] removed {{JcrRepositoryHacks}} in SLING-4690

> Moving to Oak
> -
>
> Key: SLING-4528
> URL: https://issues.apache.org/jira/browse/SLING-4528
> Project: Sling
>  Issue Type: Task
>  Components: JCR
>Reporter: Oliver Lietz
>  Labels: oak
> Fix For: JCR Oak Server 1.0.0
>
>
> _Apache Sling Oak Repository Server_ ({{org.apache.sling.jcr.oak.server}}) is 
> not released and contains some TODOs and {{JcrRepositoryHacks}}.
> What needs to be done for a first release, [~bdelacretaz] and [~mduerig]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [RT] Move to Oak

[Tommaso Teofili]

+1

Tommaso

2015-05-11 20:40 GMT+02:00 Carsten Ziegeler :

> Hi,
>
> what about moving our launchpad completely to Oak and forget about the
> "old" jackrabbit in there? I don't think we should provide both in our
> launchpad in the long run.
>
> The bundles for jackrabbit are still around if someone wants to use them
>
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

[jira] [Commented] (SLING-4709) Update to Jackrabbit 2.10.0

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538438#comment-14538438
 ] 

Oliver Lietz commented on SLING-4709:
-

While you're at it, can you look at SLING-4645?

> Update to Jackrabbit 2.10.0
> ---
>
> Key: SLING-4709
> URL: https://issues.apache.org/jira/browse/SLING-4709
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Jackrabbit Server 2.2.2
>
>
> We're currently using a very old version of jackrabbit 2 (2.6.5); however the 
> api bundles used in the launchpad are already at 2.10.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RT] Move to Oak

[Carsten Ziegeler]

Hi,

what about moving our launchpad completely to Oak and forget about the
"old" jackrabbit in there? I don't think we should provide both in our
launchpad in the long run.

The bundles for jackrabbit are still around if someone wants to use them

Carsten
-- 
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org

[jira] [Commented] (SLING-4709) Update to Jackrabbit 2.10.0

[Carsten Ziegeler (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538392#comment-14538392
 ] 

Carsten Ziegeler commented on SLING-4709:
-

Yepp, I tried this and it seems some stuff is at least working; however there 
seem to be regressions. For example the system user stuff is only implemented 
partially

> Update to Jackrabbit 2.10.0
> ---
>
> Key: SLING-4709
> URL: https://issues.apache.org/jira/browse/SLING-4709
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Jackrabbit Server 2.2.2
>
>
> We're currently using a very old version of jackrabbit 2 (2.6.5); however the 
> api bundles used in the launchpad are already at 2.10.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4709) Update to Jackrabbit 2.10.0

[Carsten Ziegeler (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler updated SLING-4709:

Assignee: (was: Carsten Ziegeler)

> Update to Jackrabbit 2.10.0
> ---
>
> Key: SLING-4709
> URL: https://issues.apache.org/jira/browse/SLING-4709
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
> Fix For: JCR Jackrabbit Server 2.2.2
>
>
> We're currently using a very old version of jackrabbit 2 (2.6.5); however the 
> api bundles used in the launchpad are already at 2.10.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-4709) Update to Jackrabbit 2.10.0

[Oliver Lietz (JIRA)]

[ 
https://issues.apache.org/jira/browse/SLING-4709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538386#comment-14538386
 ] 

Oliver Lietz commented on SLING-4709:
-

Some packages moved to other/new bundle(s), so the update is not 
straightforward.

> Update to Jackrabbit 2.10.0
> ---
>
> Key: SLING-4709
> URL: https://issues.apache.org/jira/browse/SLING-4709
> Project: Sling
>  Issue Type: Improvement
>  Components: JCR
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: JCR Jackrabbit Server 2.2.2
>
>
> We're currently using a very old version of jackrabbit 2 (2.6.5); however the 
> api bundles used in the launchpad are already at 2.10.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4709) Update to Jackrabbit 2.10.0

[Carsten Ziegeler (JIRA)]

Carsten Ziegeler created SLING-4709:
---

 Summary: Update to Jackrabbit 2.10.0
 Key: SLING-4709
 URL: https://issues.apache.org/jira/browse/SLING-4709
 Project: Sling
  Issue Type: Improvement
  Components: JCR
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
 Fix For: JCR Jackrabbit Server 2.2.2


We're currently using a very old version of jackrabbit 2 (2.6.5); however the 
api bundles used in the launchpad are already at 2.10.0



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4708) Move the File System Classloader from contrib to bundles

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-4708:

Description: The File System Classloader should be moved from 
{{contrib/commons/fsclassloader}} to {{bundles/commons/fsclassloader}}.

> Move the File System Classloader from contrib to bundles
> 
>
> Key: SLING-4708
> URL: https://issues.apache.org/jira/browse/SLING-4708
> Project: Sling
>  Issue Type: Sub-task
>  Components: Scripting
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Launchpad Builder 8
>
>
> The File System Classloader should be moved from 
> {{contrib/commons/fsclassloader}} to {{bundles/commons/fsclassloader}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4708) Move the File System Classloader from contrib to bundles

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4708:
---

 Summary: Move the File System Classloader from contrib to bundles
 Key: SLING-4708
 URL: https://issues.apache.org/jira/browse/SLING-4708
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4707) Replace the JCR Classloader with the File System Classloader

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4707:
---

 Summary: Replace the JCR Classloader with the File System 
Classloader
 Key: SLING-4707
 URL: https://issues.apache.org/jira/browse/SLING-4707
 Project: Sling
  Issue Type: Improvement
  Components: Launchpad
Affects Versions: Launchpad Builder 8
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor
 Fix For: Launchpad Builder 8


The File System Classloader should replace the JCR Classloader from the Sling 
launchpad given the benefits of writing Java classes directly to the file 
system compared to generating IO operations in the repository.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4703) Add Sightly to the Sling launchpad

[Radu Cotescu (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Radu Cotescu updated SLING-4703:

Description: Once Sightly is moved from {{contrib/scripting/sightly}} to 
{{bundles/scripting/sightly}}, the Sightly artifacts, together with their 
dependencies, should be added to Sling's launchpad.  (was: Once Sightly is 
moved from {{contrib/scripting/sightly}} to {{bundles/scripting/sightly}}, the 
artifacts should be added to Sling's launchpad.)

> Add Sightly to the Sling launchpad
> --
>
> Key: SLING-4703
> URL: https://issues.apache.org/jira/browse/SLING-4703
> Project: Sling
>  Issue Type: Task
>  Components: Launchpad
>Affects Versions: Launchpad Builder 8
>Reporter: Radu Cotescu
>Assignee: Radu Cotescu
>Priority: Minor
> Fix For: Launchpad Builder 8
>
>
> Once Sightly is moved from {{contrib/scripting/sightly}} to 
> {{bundles/scripting/sightly}}, the Sightly artifacts, together with their 
> dependencies, should be added to Sling's launchpad.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4706) Move the i18n bundle from contrib to bundles

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4706:
---

 Summary: Move the i18n bundle from contrib to bundles
 Key: SLING-4706
 URL: https://issues.apache.org/jira/browse/SLING-4706
 Project: Sling
  Issue Type: Sub-task
  Components: Extensions
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor


The i18n bundle should be moved from {{contrib/extensions/i18n}} to 
{{bundles/extensions/i18n}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4705) Move the XSS Protection bundle from contrib to bundles

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4705:
---

 Summary: Move the XSS Protection bundle from contrib to bundles
 Key: SLING-4705
 URL: https://issues.apache.org/jira/browse/SLING-4705
 Project: Sling
  Issue Type: Sub-task
  Components: Extensions
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor


The XSS Protection bundle should be moved from {{contrib/extensions/xss}} to 
{{bundles/extensions/xss}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4704) Move the Sightly scripting engine artifacts from contrib to bundles

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4704:
---

 Summary: Move the Sightly scripting engine artifacts from contrib 
to bundles
 Key: SLING-4704
 URL: https://issues.apache.org/jira/browse/SLING-4704
 Project: Sling
  Issue Type: Sub-task
  Components: Scripting
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor


The Sightly artifacts should be moved from {{contrib/scripting/sightly}} to 
{{bundles/scripting/sightly}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (SLING-4703) Add Sightly to the Sling launchpad

[Radu Cotescu (JIRA)]

Radu Cotescu created SLING-4703:
---

 Summary: Add Sightly to the Sling launchpad
 Key: SLING-4703
 URL: https://issues.apache.org/jira/browse/SLING-4703
 Project: Sling
  Issue Type: Task
  Components: Launchpad
Affects Versions: Launchpad Builder 8
Reporter: Radu Cotescu
Assignee: Radu Cotescu
Priority: Minor
 Fix For: Launchpad Builder 8


Once Sightly is moved from {{contrib/scripting/sightly}} to 
{{bundles/scripting/sightly}}, the artifacts should be added to Sling's 
launchpad.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Jenkins build is still unstable: sling-contrib-1.7 #72

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.8 #1096

[Apache Jenkins Server]

See 

Changes:

[mpetria] [maven-release-plugin] prepare for next development iteration

[mpetria] [maven-release-plugin] prepare release 
org.apache.sling.distribution.core-0.1.2

--
[...truncated 49056 lines...]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [4.336s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [12.002s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [2.762s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[4.563s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [1.757s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:36.827s]
[INFO] Apache Sling Testing Sling Mock Jackrabbit-based Resource Resolver  
SUCCESS [35.060s]
[INFO] Apache Sling Versioning Integration Tests . SUCCESS [28.168s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [3.725s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [6.703s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [3.372s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [2.319s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [5.249s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [1:18.843s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [3.854s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [3.558s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [4.179s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [2.134s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [2.103s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [14.635s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [32.766s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [5.635s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [5.125s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [2.004s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [3.097s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [2.175s]
[INFO] Apache Sling Distributed Event Admin .. SUCCESS [3.264s]
[INFO] Apache Sling Discovery API  SUCCESS [2.110s]
[INFO] Apache Sling Discovery Commons Bundle . SUCCESS [2.834s]
[INFO] Apache Sling Resource-Based Discovery Service . SUCCESS [19:05.198s]
[INFO] Apache Sling Discovery Support Bundle . SUCCESS [2.349s]
[INFO] Apache Sling Discovery Standalone Implementation .. SUCCESS [2.610s]
[INFO] Apache Sling Event Support  SUCCESS [23:39.915s]
[INFO] Apache Sling Feature Flags  SUCCESS [2.885s]
[INFO] Apache Sling Filesystem Resource Provider . SUCCESS [2.608s]
[INFO] Apache Sling javax.activation bundle .. SUCCESS [4.273s]
[INFO] Apache Sling Service User Mapper .. SUCCESS [3.359s]
[INFO] Apache Sling Settings . SUCCESS [3.447s]
[INFO] Apache Sling Web Console Branding . SUCCESS [2.031s]
[INFO] Apache Sling Web Console Security Provider  SUCCESS [3.804s]
[INFO] Apache Sling Explorer . SUCCESS [3.335s]
[INFO] Apache Sling Health Check Core  SUCCESS [10.818s]
[INFO] Apache Sling Health Check Annotations . SUCCESS [1.814s]
[INFO] Apache Sling Health Check Samples . SUCCESS [4.592s]
[INFO] Apache Sling Health Check Support Components .. SUCCESS [3.473s]
[INFO] Apache Sling Health Check Webconsole Plugin ... SUCCESS [3.093s]
[INFO] Apache Sling Health Check JUnit Bridge  SUCCESS [2.804s]
[INFO] Apache Sling Health Check Integration Tests ... SUCCESS [29.173s]
[INFO] Apache Sling Health Check Reactor POM . SUCCESS [1.058s]
[INFO] Apache Sling Resource Access Security . SUCCESS [2.818s]
[INFO] Apache Sling Resource Access Security Integration Tests  SUCCESS 
[45.061s]
[INFO] Apache Sling Validation Framework API . SUCCESS [3.574s]
[INFO] Apache Sling Validation Framework Core Implementation  SUCCESS [45.421s]
[INFO] Apache Sling Validation Framework Testing Services  SUCCESS [2.605s]
[INFO] Apache Sling Validation Framework Integration Tests  FAILURE [7.128s]
[INFO] Apache Sling Validation Framework Examples  SKIPPED
[INFO] Apache Sling Validation Framework Builder . SKIPPED
[INFO] Apache Sling Models API ... SKIPPED
[INFO] Apache Sling Models Implementation  SKIPPED
[INFO] Apache Sling Models Integration Tests . SKIPPED
[INFO] Apache Sling Test Tools ... SKIPPED
[INFO] Apache Sling JUnit Core .

Jenkins build is still unstable: sling-contrib-1.7 #71

[Apache Jenkins Server]

See 

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.2

[Tommaso Teofili]

+1 (not binding)

Tommaso

2015-05-11 13:06 GMT+02:00 Marius Petria :

> Hi,
>
> We solved 9 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12332053
>
> There are still some outstanding issues:
> https://issues.apache.org/jira/browse/SLING/component/12323405
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1250/
>
> You can use this UNIX script to download the release and verify the
> signatures:
> http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
> Usage:
> sh check_staged_release.sh 1250 /tmp/sling-staging
>
> Please vote to approve this release:
>
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
>
> This majority vote is open for at least 72 hours.
>

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.2

[Stefan Egli]

+1,

Cheers,
Stefan

On 5/11/15 1:06 PM, "Marius Petria"  wrote:

>Hi,
>
>We solved 9 issues in this release:
>https://issues.apache.org/jira/browse/SLING/fixforversion/12332053
>
>There are still some outstanding issues:
>https://issues.apache.org/jira/browse/SLING/component/12323405
>
>Staging repository:
>https://repository.apache.org/content/repositories/orgapachesling-1250/
>
>You can use this UNIX script to download the release and verify the
>signatures:
>http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
>
>Usage:
>sh check_staged_release.sh 1250 /tmp/sling-staging
>
>Please vote to approve this release:
>
>  [ ] +1 Approve the release
>  [ ]  0 Don't care
>  [ ] -1 Don't release, because ...
>
>This majority vote is open for at least 72 hours.

Re: SLING-1437 as a part of Google Summer of Code 2015

[Bertrand Delacretaz]

Hi Petr,

On Fri, May 8, 2015 at 1:06 PM, Petr Shypila  wrote:
> ...Here are my plans until coding period will start:
> Today-May 17th(17.05) I will look on tests examples from
>  bundles/extensions/healthcheck and
> bundles/extensions/models modules.
> And 17.05-24.05 I will look for some first module where I can start to work
> on...

Sounds good to me!
-Bertrand

[VOTE] Release Apache Sling Content Distribution Core version 0.1.2

[Marius Petria]

Hi,

We solved 9 issues in this release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12332053

There are still some outstanding issues:
https://issues.apache.org/jira/browse/SLING/component/12323405

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1250/

You can use this UNIX script to download the release and verify the signatures:
http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh

Usage:
sh check_staged_release.sh 1250 /tmp/sling-staging

Please vote to approve this release:

  [ ] +1 Approve the release
  [ ]  0 Don't care
  [ ] -1 Don't release, because ...

This majority vote is open for at least 72 hours.

[jira] [Closed] (SLING-4647) Max pull items for http transport handler should only be applied to PULL requests

[Marius Petria (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marius Petria closed SLING-4647.


> Max pull items for http transport handler should only be applied to PULL 
> requests
> -
>
> Key: SLING-4647
> URL: https://issues.apache.org/jira/browse/SLING-4647
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Affects Versions: Content Distribution Core 0.1.1
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.2
>
>
> Only pull requests can produce different results and hence the other types 
> (TEST, ADD, DELETE) should only be iterated once.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4651) Ensure that pulled packages are only deleted when they reach the coordinator queue

[Marius Petria (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marius Petria updated SLING-4651:
-
Fix Version/s: (was: Content Distribution Core 0.1.2)

> Ensure that pulled packages are only deleted when they reach the coordinator 
> queue
> --
>
> Key: SLING-4651
> URL: https://issues.apache.org/jira/browse/SLING-4651
> Project: Sling
>  Issue Type: Bug
>  Components: Distribution
>Affects Versions: Content Distribution Core 0.1.1
>Reporter: Marius Petria
>Assignee: Marius Petria
>
> Packages pulled from a remote endpoint are deleted when they reach the 
> coordinating instance, but they should be deleted when they are actually 
> added to the processing queue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-4148) Put JCR dependent components into a distribution.jcr bundle

[Marius Petria (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marius Petria updated SLING-4148:
-
Fix Version/s: (was: Content Distribution Core 0.1.2)

> Put JCR dependent components into a distribution.jcr bundle
> ---
>
> Key: SLING-4148
> URL: https://issues.apache.org/jira/browse/SLING-4148
> Project: Sling
>  Issue Type: Task
>  Components: Distribution
>Reporter: Tommaso Teofili
>Assignee: Tommaso Teofili
>
> Some components (triggers, serialization, etc.) in 
> _org.apache.sling.distribution.core_ are JCR dependent, meaning that they 
> will only work if Sling is backed by JCR, so they should be put in a separate 
> _org.apache.sling.distribution.jcr_ bundle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (SLING-4629) Configure agent to distribute directly to a passive queue

[Marius Petria (JIRA)]

 [ 
https://issues.apache.org/jira/browse/SLING-4629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Marius Petria resolved SLING-4629.
--
Resolution: Fixed

> Configure agent to distribute directly to a passive queue
> -
>
> Key: SLING-4629
> URL: https://issues.apache.org/jira/browse/SLING-4629
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Affects Versions: Content Distribution 0.1.0
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.2
>
>
> Currently the sync/reverse agents can only import to a remote endpoint.
> It would be useful to also import the packages in a passive queue from where 
> they can be exported by other agents.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)