[jira] [Updated] (SLING-5318) Sling provisioning model does not propagate Artifact metadata during processing

2015-11-20 Thread David Bosschaert (JIRA) 

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

David Bosschaert updated SLING-5318:

Attachment: sling.diff

The attached patch contains a fix for the problem and also a unit test.

> Sling provisioning model does not propagate Artifact metadata during 
> processing
> ---
>
> Key: SLING-5318
> URL: https://issues.apache.org/jira/browse/SLING-5318
> Project: Sling
>  Issue Type: Bug
>Reporter: David Bosschaert
> Attachments: sling.diff
>
>
> The sling provisioning model does not propagate Artifact metadata in 
> EffectiveModelProcessor.processArtifact. This means that if Artifact Metadata 
> is specified in the model.txt file like this:
> {code}commons-collections/commons-collections/3.2.1/jar 
> [mykey=myvalue]{code}
> the {{mykey=myvalue}} it will be lost at some point during processing.



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

[jira] [Created] (SLING-5318) Sling provisioning model does not propagate Artifact metadata during processing

2015-11-20 Thread David Bosschaert (JIRA) 
David Bosschaert created SLING-5318:
---

 Summary: Sling provisioning model does not propagate Artifact 
metadata during processing
 Key: SLING-5318
 URL: https://issues.apache.org/jira/browse/SLING-5318
 Project: Sling
  Issue Type: Bug
Reporter: David Bosschaert


The sling provisioning model does not propagate Artifact metadata in 
EffectiveModelProcessor.processArtifact. This means that if Artifact Metadata 
is specified in the model.txt file like this:
{code}commons-collections/commons-collections/3.2.1/jar 
[mykey=myvalue]{code}
the {{mykey=myvalue}} it will be lost at some point during processing.



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

[jira] [Resolved] (SLING-5294) Make test resources available to teleported tests

2015-11-20 Thread Bertrand Delacretaz (JIRA) 

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

Bertrand Delacretaz resolved SLING-5294.

Resolution: Fixed
  Assignee: Bertrand Delacretaz

> Make test resources available to teleported tests
> -
>
> Key: SLING-5294
> URL: https://issues.apache.org/jira/browse/SLING-5294
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: JUnit Tests Teleporter 1.0.2
>Reporter: Thierry Ygé
>Assignee: Bertrand Delacretaz
> Fix For: JUnit Tests Teleporter 1.0.4, JUnit Core 1.0.14
>
> Attachments: ClientSideTeleporter.java_patch, 
> ClientSideTeleporter.java_patch_v2
>
>
> Currently you can add classes to the bundle, but not resources.
> It would be nice to simply add the following code (see attached diff).



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

Re: [VOTE] Release org.apache.sling.junit.core 1.0.14 and org.apache.sling:org.apache.sling.junit.teleporter 1.0.4

2015-11-20 Thread Bertrand Delacretaz 
Hi Robert,

On Fri, Nov 20, 2015 at 8:33 AM, Robert Munteanu  wrote:
> ...The issue is not marked as resolved, is that by omission?...

You are correct, thanks! I have now resolved SLING-5294

-Bertrand

Re: [VOTE] Release org.apache.sling.bgservlets 1.0.2

2015-11-20 Thread Antonio Sanso 
+1 

regards

antonio
On Nov 19, 2015, at 10:03 PM, Bertrand Delacretaz  
wrote:

> Hi,
> 
> We solved 2 issues in this release:
> 
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Background%20Servlets%201.0.2%22%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1373/
> 
> 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 1373 /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.
> 
> Here's my +1
> 
> -Bertrand

Re: [VOTE] Release org.apache.sling.junit.core 1.0.14 and org.apache.sling:org.apache.sling.junit.teleporter 1.0.4

2015-11-20 Thread Antonio Sanso 
+1 

regards

antonio
On Nov 19, 2015, at 10:15 PM, Bertrand Delacretaz  
wrote:

> Hi,
> 
> We solved 1 issue with these releases:
> 
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333656
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333655
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1374/
> 
> 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 1374 /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.
> 
> Here's my +1.
> 
> -Bertrand

Re: [VOTE] Release org.apache.sling.junit.core 1.0.14 and org.apache.sling:org.apache.sling.junit.teleporter 1.0.4

2015-11-20 Thread Robert Munteanu 
On Thu, 2015-11-19 at 16:15 -0500, Bertrand Delacretaz wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release org.apache.sling.junit.core 1.0.14 and org.apache.sling:org.apache.sling.junit.teleporter 1.0.4

2015-11-20 Thread Robert Munteanu 
Hi Bertrand,

On Thu, 2015-11-19 at 16:15 -0500, Bertrand Delacretaz wrote:
> We solved 1 issue with these releases:
> 
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333656
> https://issues.apache.org/jira/browse/SLING/fixforversion/12333655

The issue is not marked as resolved, is that by omission?

Thanks,

Robert

Re: [VOTE] Release org.apache.sling.bgservlets 1.0.2

2015-11-20 Thread Robert Munteanu 
On Thu, 2015-11-19 at 16:03 -0500, Bertrand Delacretaz wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

[jira] [Created] (SLING-5317) PropertiesUtil does not have a toFloat method

2015-11-20 Thread Satya Deep Maheshwari (JIRA) 
Satya Deep Maheshwari created SLING-5317:


 Summary: PropertiesUtil does not have a toFloat method
 Key: SLING-5317
 URL: https://issues.apache.org/jira/browse/SLING-5317
 Project: Sling
  Issue Type: Improvement
  Components: API
Reporter: Satya Deep Maheshwari
Priority: Minor


org.apache.sling.commons.osgi.PropertiesUtil does not have a toFloat method. 



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

[jira] [Resolved] (SLING-5316) Expose user id in distribution queue resources

2015-11-20 Thread Marius Petria (JIRA) 

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

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

Committed revision 1715339.


> Expose user id in distribution queue resources
> --
>
> Key: SLING-5316
> URL: https://issues.apache.org/jira/browse/SLING-5316
> Project: Sling
>  Issue Type: Improvement
>  Components: Distribution
>Reporter: Marius Petria
>Assignee: Marius Petria
> Fix For: Content Distribution Core 0.1.12
>
>
> We should expose a property that contains the calling userid in queue 
> resources.



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

[jira] [Created] (SLING-5316) Expose user id in distribution queue resources

2015-11-20 Thread Marius Petria (JIRA) 
Marius Petria created SLING-5316:


 Summary: Expose user id in distribution queue resources
 Key: SLING-5316
 URL: https://issues.apache.org/jira/browse/SLING-5316
 Project: Sling
  Issue Type: Improvement
  Components: Distribution
Reporter: Marius Petria
Assignee: Marius Petria
 Fix For: Content Distribution Core 0.1.12


We should expose a property that contains the calling userid in queue resources.



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

[jira] [Commented] (SLING-5078) Missing indexes on MongoDBResourceProvider

2015-11-20 Thread ASF GitHub Bot (JIRA) 

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

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

GitHub user nleite opened a pull request:

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

SLING-5078

- adding creation of mandatory indexes on `_path` and `_parentPath` fields 

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

$ git pull https://github.com/nleite/sling trunk

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

https://github.com/apache/sling/pull/113.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 #113


commit ea53eb93bb5d24d592a024ffd0c1252678fab980
Author: Norberto 
Date:   2015-09-30T13:44:04Z

SLING-5078: Missing indexes on MongoDBResourceProv
Simple first approach of adding a single build indexes method that is 
called for all collections.

commit 5cd3ec67eb0570d7e42c96d4501fe2384a25f1d4
Author: Norberto 
Date:   2015-09-30T14:08:33Z

Merge branch 'trunk' of github.com:nleite/sling into trunk

commit f6602984888e7da49323faf592a7f5b0646a7187
Author: Norberto 
Date:   2015-11-19T19:45:14Z

Merge branch 'trunk' of github.com:apache/sling into trunk

commit e1f2a91231fa37f3e55ed48f1a378498b56a3b56
Author: Norberto 
Date:   2015-11-20T11:10:56Z

Adding mandatory indexes - https://issues.apache.org/jira/browse/SLING-5078
- Adding index on `_path` and `_parentPath` fields
- Added integration test to validate the correct creation of the indexes




> Missing indexes on MongoDBResourceProvider
> --
>
> Key: SLING-5078
> URL: https://issues.apache.org/jira/browse/SLING-5078
> Project: Sling
>  Issue Type: Improvement
>  Components: NoSQL
>Affects Versions: NoSQL MongoDB Resource Provider 1.0.0
>Reporter: Norberto Leite
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> MongoDB supports secondary indexes but those are missing from the existing 
> implementation. 
> Not only for performance but also for uniqueness guarantee we should have the 
> following indexes: 
> *_path* - unique 
> *_parent* - unique 



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

[GitHub] sling pull request: SLING-5078

2015-11-20 Thread nleite 
GitHub user nleite opened a pull request:

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

SLING-5078

- adding creation of mandatory indexes on `_path` and `_parentPath` fields 

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

$ git pull https://github.com/nleite/sling trunk

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

https://github.com/apache/sling/pull/113.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 #113


commit ea53eb93bb5d24d592a024ffd0c1252678fab980
Author: Norberto 
Date:   2015-09-30T13:44:04Z

SLING-5078: Missing indexes on MongoDBResourceProv
Simple first approach of adding a single build indexes method that is 
called for all collections.

commit 5cd3ec67eb0570d7e42c96d4501fe2384a25f1d4
Author: Norberto 
Date:   2015-09-30T14:08:33Z

Merge branch 'trunk' of github.com:nleite/sling into trunk

commit f6602984888e7da49323faf592a7f5b0646a7187
Author: Norberto 
Date:   2015-11-19T19:45:14Z

Merge branch 'trunk' of github.com:apache/sling into trunk

commit e1f2a91231fa37f3e55ed48f1a378498b56a3b56
Author: Norberto 
Date:   2015-11-20T11:10:56Z

Adding mandatory indexes - https://issues.apache.org/jira/browse/SLING-5078
- Adding index on `_path` and `_parentPath` fields
- Added integration test to validate the correct creation of the indexes




---
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.
---