Re: [VOTE] Release Apache Sling Parent version 31

[Daniel Klco]

+1

On Fri, Aug 4, 2017 at 8:43 AM, Carsten Ziegeler 
wrote:

> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org
>

[jira] [Updated] (SLING-7031) Write (subset) of metrics to log file on a recurring basis

[Justin Edelson (JIRA)]

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

Justin Edelson updated SLING-7031:
--
Attachment: SLING-7031.diff

proposed change

> Write (subset) of metrics to log file on a recurring basis
> --
>
> Key: SLING-7031
> URL: https://issues.apache.org/jira/browse/SLING-7031
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Justin Edelson
> Attachments: SLING-7031.diff
>
>
> For ease of visibility and extraction, we should provide a way to output a 
> set of metrics to the log file on a recurring basis. Most of this 
> functionality is already provided by the Metrics library, we can just wrap it 
> in a nice OSGi config-based component.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7031) Write (subset) of metrics to log file on a recurring basis

[Justin Edelson (JIRA)]

Justin Edelson created SLING-7031:
-

 Summary: Write (subset) of metrics to log file on a recurring basis
 Key: SLING-7031
 URL: https://issues.apache.org/jira/browse/SLING-7031
 Project: Sling
  Issue Type: Improvement
  Components: Commons
Reporter: Justin Edelson


For ease of visibility and extraction, we should provide a way to output a set 
of metrics to the log file on a recurring basis. Most of this functionality is 
already provided by the Metrics library, we can just wrap it in a nice OSGi 
config-based component.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Sling Security 1.1.6

[Carsten Ziegeler]

Konrad Windszus wrote
> A lot of redundant things are defined in the pom.xml with regards to the 
> maven-bundle-plugin 
> (https://github.com/apache/sling/blob/trunk/contrib/extensions/security/pom.xml#L56)
> 
> - the execution of "manifest"
> - exportScr=true
> - Bundle-Category=sling
> 
> all those things are already defined in the sling parent 30 and should IMHO 
> not be repeated in derived poms.
>
Probably,  but I don't think this blocks the release as the artifact is
correct, right?

Carsten

 

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

Re: [VOTE] Release Apache Sling Security 1.1.6

[Konrad Windszus]

A lot of redundant things are defined in the pom.xml with regards to the 
maven-bundle-plugin 
(https://github.com/apache/sling/blob/trunk/contrib/extensions/security/pom.xml#L56)

- the execution of "manifest"
- exportScr=true
- Bundle-Category=sling

all those things are already defined in the sling parent 30 and should IMHO not 
be repeated in derived poms.
Konrad


> On 4. Aug 2017, at 14:48, Karl Pauls  wrote:
> 
> +1
> 
> regards,
> 
> Karl
> 
> On Fri, Aug 4, 2017 at 2:47 PM, Carsten Ziegeler  wrote:
>> +1
>> 
>> 
>> 
>> --
>> Carsten Ziegeler
>> Adobe Research Switzerland
>> cziege...@apache.org
> 
> 
> 
> -- 
> Karl Pauls
> karlpa...@gmail.com

[jira] [Resolved] (SLING-7027) Progress ETA seems to be calculated incorrectly and not to be updated on update.

[Karl Pauls (JIRA)]

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

Karl Pauls resolved SLING-7027.
---
Resolution: Fixed

Fixed in r1804116.

> Progress ETA seems to be calculated incorrectly and not to be updated on 
> update.
> 
>
> Key: SLING-7027
> URL: https://issues.apache.org/jira/browse/SLING-7027
> Project: Sling
>  Issue Type: Bug
>  Components: Event
>Affects Versions: Event 4.2.4
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Minor
> Fix For: Event 4.3.0
>
> Attachments: eta.patch
>
>
> It looks to me like the eta is not correctly calculated in 
> JobImpl.setProgress and not set correctly in JobImp.update. 
> I would like to apply the attached patch to fix it. Does that look correct to 
> others?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7027) Progress ETA seems to be calculated incorrectly and not to be updated on update.

[Karl Pauls (JIRA)]

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

Karl Pauls commented on SLING-7027:
---

[~cziegeler], you are absolutely right - I was thinking about the eta (in which 
case it would be correct) which I think would maybe be more correct but harder 
to maintain - hence, we should stick with the elapsed and use your calculation. 
I'll go ahead and do that.

> Progress ETA seems to be calculated incorrectly and not to be updated on 
> update.
> 
>
> Key: SLING-7027
> URL: https://issues.apache.org/jira/browse/SLING-7027
> Project: Sling
>  Issue Type: Bug
>  Components: Event
>Affects Versions: Event 4.2.4
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Minor
> Fix For: Event 4.3.0
>
> Attachments: eta.patch
>
>
> It looks to me like the eta is not correctly calculated in 
> JobImpl.setProgress and not set correctly in JobImp.update. 
> I would like to apply the attached patch to fix it. Does that look correct to 
> others?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-7027) Progress ETA seems to be calculated incorrectly and not to be updated on update.

[Karl Pauls (JIRA)]

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

Karl Pauls reassigned SLING-7027:
-

Assignee: Karl Pauls

> Progress ETA seems to be calculated incorrectly and not to be updated on 
> update.
> 
>
> Key: SLING-7027
> URL: https://issues.apache.org/jira/browse/SLING-7027
> Project: Sling
>  Issue Type: Bug
>  Components: Event
>Affects Versions: Event 4.2.4
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Minor
> Fix For: Event 4.3.0
>
> Attachments: eta.patch
>
>
> It looks to me like the eta is not correctly calculated in 
> JobImpl.setProgress and not set correctly in JobImp.update. 
> I would like to apply the attached patch to fix it. Does that look correct to 
> others?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Re: [VOTE] Release Apache Sling Security 1.1.6

[Karl Pauls]

+1

regards,

Karl

On Fri, Aug 4, 2017 at 2:47 PM, Carsten Ziegeler  wrote:
> +1
>
>
>
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziege...@apache.org



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Scripting HTL Engine 1.0.38, Apache Sling Scripting HTL Compiler 1.0.10, Apache Sling HTL Maven Plugin 1.0.8

[Karl Pauls]

+1

regards,

Karl

On Thu, Aug 3, 2017 at 4:30 PM, Robert Munteanu  wrote:
> On Wed, 2017-08-02 at 11:20 +, Radu Cotescu wrote:
>> Please vote to approve this release:
>
> +1
>
> Robert



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Security 1.1.6

[Carsten Ziegeler]

+1

 

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

[VOTE] Release Apache Sling Security 1.1.6

[Carsten Ziegeler]

Hi,
We solved 1 issues in this release:

https://issues.apache.org/jira/browse/SLING-7030

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1762/
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 1762 /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.

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

Re: [VOTE] Release Apache Sling Parent version 31

[Carsten Ziegeler]

+1

 

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

Re: [VOTE] Release Apache Sling Parent version 31

[Karl Pauls]

+1

regards,

Karl

On Friday, August 4, 2017, Robert Munteanu  wrote:

> On Fri, 2017-08-04 at 14:05 +0200, Konrad Windszus wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert



-- 
Karl Pauls
karlpa...@gmail.com

Re: [VOTE] Release Apache Sling Parent version 31

[Robert Munteanu]

On Fri, 2017-08-04 at 14:05 +0200, Konrad Windszus wrote:
> Please vote to approve this release: 

+1

Robert

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

[VOTE] Release Apache Sling Parent version 31

[Konrad Windszus]

Hi, 
We solved 2 issues in this release:
https://issues.apache.org/jira/projects/SLING/versions/12339842

Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1761/ 
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 1761 /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.

Thanks,
Konrad

[jira] [Commented] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[JIRA]

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

Dominique Jäggi commented on SLING-7030:


[~cziegeler], looks perfect, thanks for processing and cleanup

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
>Assignee: Carsten Ziegeler
> Fix For: Security 1.1.6
>
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed1.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-7030.
-
Resolution: Fixed

Thanks for the patch ,[~dominique.jaeggi]
I've applied a slightly modified version in rev 1804102 which removes the 
dependency on commons.lang and also removes embedding the unused commons.osgi 
classes.
Please cross check

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
>Assignee: Carsten Ziegeler
> Fix For: Security 1.1.6
>
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed1.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler reassigned SLING-7030:
---

Assignee: Carsten Ziegeler

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
>Assignee: Carsten Ziegeler
> Fix For: Security 1.1.6
>
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed1.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[JIRA]

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

Dominique Jäggi updated SLING-7030:
---
Attachment: 
SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed1.patch

Updated patch and removed old SCR dependency

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
> Fix For: Security 1.1.6
>
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed1.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[JIRA]

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

Dominique Jäggi updated SLING-7030:
---
Attachment: (was: 
SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed.patch)

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
> Fix For: Security 1.1.6
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-7030:

Fix Version/s: Security 1.1.6

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
> Fix For: Security 1.1.6
>
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-7030:


[~dominique.jaeggi] Please also remove the dependency towards 
{{org.apache.felix.scr.annotations}} to make sure no other components are using 
legacy annotations.

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[JIRA]

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

Dominique Jäggi updated SLING-7030:
---
Attachment: 
SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed.patch

attaching patch with migration of annotations to new format

> ReferrerFilter broken as legacy SCR Annotations are not processed
> -
>
> Key: SLING-7030
> URL: https://issues.apache.org/jira/browse/SLING-7030
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Security 1.1.4
>Reporter: Dominique Jäggi
> Attachments: 
> SLING_7030___ReferrerFilter_broken_as_legacy_SCR_Annotations_are_not_processed.patch
>
>
> The org.apache.sling.security-1.1.4 bundle is broken, since it uses the 
> latest sling parent which no longer processes old SCR annotations. I will 
> provide a patch to the sling team with converted annotations.
> /cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-3014) [build] Generate SCR descriptors using Maven

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-3014:


[~kwin] - I don't have the time to apply and test right now. If you find the 
time please do that yourself. Otherwise I'll take a look next time I will work 
on the IDE tooling, but I don't see that happening in the next two weeks.

> [build] Generate SCR descriptors using Maven
> 
>
> Key: SLING-3014
> URL: https://issues.apache.org/jira/browse/SLING-3014
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.2.0
>
> Attachments: SLING-3014-1.patch
>
>
> _Edit_: updated the issue title to reflect the fact that we're looking to use 
> Maven, not a specific plug-in.
> Since we're starting to use SCR descriptors when building the Sling IDE tools 
> it would be nice to generate them using the maven-scr-plugin. I have the 
> build working in the CLI, but not yet in the IDE ( see 
> http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is 
> done I'll commit my changes to trunk.
> Note that plain Maven projects work just fine, this is about Tycho-driven 
> builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-3014) [build] Generate SCR descriptors using Maven

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-3014:


[~rombert] Can you reapply your patch together with the workaround listed in 
https://issues.apache.org/jira/browse/SLING-3014?focusedCommentId=15965936=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15965936?
 I think that solution is much better than manually maintaining those XML files.

> [build] Generate SCR descriptors using Maven
> 
>
> Key: SLING-3014
> URL: https://issues.apache.org/jira/browse/SLING-3014
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.2.0
>
> Attachments: SLING-3014-1.patch
>
>
> _Edit_: updated the issue title to reflect the fact that we're looking to use 
> Maven, not a specific plug-in.
> Since we're starting to use SCR descriptors when building the Sling IDE tools 
> it would be nice to generate them using the maven-scr-plugin. I have the 
> build working in the CLI, but not yet in the IDE ( see 
> http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is 
> done I'll commit my changes to trunk.
> Note that plain Maven projects work just fine, this is about Tycho-driven 
> builds.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7030) ReferrerFilter broken as legacy SCR Annotations are not processed

[JIRA]

Dominique Jäggi created SLING-7030:
--

 Summary: ReferrerFilter broken as legacy SCR Annotations are not 
processed
 Key: SLING-7030
 URL: https://issues.apache.org/jira/browse/SLING-7030
 Project: Sling
  Issue Type: Bug
  Components: Extensions
Affects Versions: Security 1.1.4
Reporter: Dominique Jäggi


The org.apache.sling.security-1.1.4 bundle is broken, since it uses the latest 
sling parent which no longer processes old SCR annotations. I will provide a 
patch to the sling team with converted annotations.

/cc [~asanso]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7027) Progress ETA seems to be calculated incorrectly and not to be updated on update.

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-7027:
-

Good catch [~karlpauls]
I think the calculation should rather be (if I'm not confusing things):
final long eta = System.currentTimeMillis() + (elapsed / current) * (steps - 
current);
elapsed is the time taken for the steps so far (current number of steps)
elapsed/current is the average for a single step
(steps-current) is the number of remaining steps

> Progress ETA seems to be calculated incorrectly and not to be updated on 
> update.
> 
>
> Key: SLING-7027
> URL: https://issues.apache.org/jira/browse/SLING-7027
> Project: Sling
>  Issue Type: Bug
>  Components: Event
>Affects Versions: Event 4.2.4
>Reporter: Karl Pauls
>Priority: Minor
> Fix For: Event 4.3.0
>
> Attachments: eta.patch
>
>
> It looks to me like the eta is not correctly calculated in 
> JobImpl.setProgress and not set correctly in JobImp.update. 
> I would like to apply the attached patch to fix it. Does that look correct to 
> others?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[GitHub] sling pull request #249: method to stop a bundle added.

[asfgit]

Github user asfgit closed the pull request at:

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


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

[jira] [Resolved] (SLING-7029) Extension - adding method to stop a bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-7029.

Resolution: Fixed

Applied in [r1804073|https://svn.apache.org/r1804073], thanks for the 
contribution!

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7029) Extension - adding method to stop a bundle

[Andreea Dieaconu (JIRA)]

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

Andreea Dieaconu commented on SLING-7029:
-

Yes, you re right [~rombert]

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (SLING-7029) Extension - adding method to stop a bundle

[Andreea Dieaconu (JIRA)]

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

Andreea Dieaconu updated SLING-7029:

Comment: was deleted

(was: https://github.com/apache/sling/pull/249 )

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7029) Extension - adding method to stop a bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-7029:
---
Fix Version/s: Testing Clients 1.1.6

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (SLING-7029) Extension - adding method to stop a bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-7029:
--

Assignee: Robert Munteanu

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7029) Extension - adding method to stop a bundle

[Andreea Dieaconu (JIRA)]

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

Andreea Dieaconu commented on SLING-7029:
-

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

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Assignee: Robert Munteanu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (SLING-7029) Extension - adding method to stop a bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu updated SLING-7029:
---
Component/s: (was: Extensions)
 Testing

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Reporter: Andreea Dieaconu
>Priority: Trivial
> Fix For: Testing Clients 1.1.6
>
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (SLING-7029) Extension - adding method to stop a bundle

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-7029:


[~andreeadieaconu] - I assume this is for 
https://github.com/apache/sling/pull/249, right?

> Extension - adding method to stop a bundle
> --
>
> Key: SLING-7029
> URL: https://issues.apache.org/jira/browse/SLING-7029
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Andreea Dieaconu
>Priority: Trivial
>
> It would be useful to have a method to stop bundles of sling.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (SLING-7029) Extension - adding method to stop a bundle

[Andreea Dieaconu (JIRA)]

Andreea Dieaconu created SLING-7029:
---

 Summary: Extension - adding method to stop a bundle
 Key: SLING-7029
 URL: https://issues.apache.org/jira/browse/SLING-7029
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Andreea Dieaconu
Priority: Trivial


It would be useful to have a method to stop bundles of sling.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)