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

See

Re: [VOTE] Release Apache Sling FileSystem ClassLoader 1.0.2

+1 On Tue, Jun 16, 2015 at 7:44 AM, Robert Munteanu wrote: > On Tue, 2015-06-16 at 09:53 +0200, Carsten Ziegeler wrote: > > Please vote to approve this release: > > +1 > > Robert >

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

See Changes: [bdelacretaz] SLING-4728 - down to 2 failing Sling integration tests (but TODOs in model.txt) -- [...truncated 77693 lines...] [INFO] Apache Sling Resource-Based Discovery Service .

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

See

Jenkins build is still unstable: sling-crankstart #27

See

Jenkins build is still unstable: sling-trunk-1.8 #1224

See

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

See

[jira] [Commented] (SLING-4795) Only discard the ResourceBundles if they are really invalid

[ https://issues.apache.org/jira/browse/SLING-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588371#comment-14588371 ] Alexander Klimetschek commented on SLING-4795: -- Note that with json dictionar

Re: Maven release:perform results in missing md5/sha1 files

On Tue, Jun 16, 2015 at 5:57 PM, Chetan Mehrotra wrote: > ...What combination of mvn/jdk are others using to perform the release?... mvn 3.2.3 and JDK 1.7 or 1.8 on macosx. -Bertrand

Re: Maven release:perform results in missing md5/sha1 files

I used 3.0.5 till recently and now switched to latest, 3.3.x Carsten Am 16.06.15 um 17:57 schrieb Chetan Mehrotra: > Trying to release now from home I get only one staging repository > created. However now Nexus complains that md5/sha1 files are missing > > Missing SHA1: > '/org/apache/sling/or

Re: slingstart plugin: deployed artifact does not have "slingfeature" classifier?

Am 16.06.15 um 17:46 schrieb Bertrand Delacretaz: > On Tue, Jun 16, 2015 at 11:39 AM, Carsten Ziegeler > wrote: >> Am 16.06.15 um 11:19 schrieb Bertrand Delacretaz: >>> ... That doesn't work for my contrib/crankstart/test-model model - as you >>> say it's the main artifact of that module so it's

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

See

Jenkins build is still unstable: sling-trunk-1.8 #1223

See

Maven release:perform results in missing md5/sha1 files

Trying to release now from home I get only one staging repository created. However now Nexus complains that md5/sha1 files are missing Missing SHA1: '/org/apache/sling/org.apache.sling.tracer/0.0.2/org.apache.sling.tracer-0.0.2-source-release.zip.sha1' Saw a similar issue reported earlier [1] bu

Jenkins build is back to stable : sling-oak-it-1.7 #178

See

Re: slingstart plugin: deployed artifact does not have "slingfeature" classifier?

On Tue, Jun 16, 2015 at 11:39 AM, Carsten Ziegeler wrote: > Am 16.06.15 um 11:19 schrieb Bertrand Delacretaz: >>... That doesn't work for my contrib/crankstart/test-model model - as you >> say it's the main artifact of that module so it's deployed without the >> "slingfeature" type or classifier,

Jenkins build is back to stable : sling-trunk-1.7 #1936

See

Jenkins build is unstable: sling-crankstart #26

See

[jira] [Commented] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588172#comment-14588172 ] Konrad Windszus commented on SLING-4806: My previous comment was not referring to

[jira] [Commented] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588159#comment-14588159 ] Carsten Ziegeler commented on SLING-4806: - No, I meant: https://osgi.org/javadoc/r

[jira] [Commented] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588096#comment-14588096 ] Carsten Ziegeler commented on SLING-4806: - I guess we could do some tricky stuff w

[jira] [Commented] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588102#comment-14588102 ] Konrad Windszus commented on SLING-4806: Could this maybe be achieved by sending a

[jira] [Updated] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4806: --- Attachment: SLING-4806-notworking.patch > Only invalidate those DynamicClassLoaderManagers whi

[jira] [Commented] (SLING-4806) Only invalidate those DynamicClassLoaderManagers which are becoming invalid

[ https://issues.apache.org/jira/browse/SLING-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588080#comment-14588080 ] Konrad Windszus commented on SLING-4806: I tried with the attached patch but that

Jenkins build is unstable: sling-trunk-1.7 #1935

See

[jira] [Updated] (SLING-4795) Only discard the ResourceBundles if they are really invalid

[ https://issues.apache.org/jira/browse/SLING-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4795: --- Affects Version/s: (was: i18n 2.4.4) > Only discard the ResourceBundles if they are really

[jira] [Commented] (SLING-4795) Only discard the ResourceBundles if they are really invalid

[ https://issues.apache.org/jira/browse/SLING-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587927#comment-14587927 ] Konrad Windszus commented on SLING-4795: I updated the PR at https://github.com/ap

[jira] [Commented] (SLING-4795) Only discard the ResourceBundles if they are really invalid

[ https://issues.apache.org/jira/browse/SLING-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587923#comment-14587923 ] Konrad Windszus commented on SLING-4795: The advantage heavily depends on the numb

Re: [VOTE] Release Apache Sling FileSystem ClassLoader 1.0.2

On Tue, 2015-06-16 at 09:53 +0200, Carsten Ziegeler wrote: > Please vote to approve this release: +1 Robert

Jenkins build is unstable: sling-trunk-1.8 #1222

See

[jira] [Commented] (SLING-4813) Support OSGi service mocked by e.g Mockito

[ https://issues.apache.org/jira/browse/SLING-4813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587901#comment-14587901 ] Krystian Panek commented on SLING-4813: --- https://github.com/apache/sling/pull/97 >

[GitHub] sling pull request: Support CGLIB enhanced classes for Mockito bas...

GitHub user krystianpanek opened a pull request: https://github.com/apache/sling/pull/97 Support CGLIB enhanced classes for Mockito based service mocks You can merge this pull request into a Git repository by running: $ git pull https://github.com/krystianpanek/sling SLING-481

[jira] [Created] (SLING-4813) Support OSGi service mocked by e.g Mockito

Krystian Panek created SLING-4813: - Summary: Support OSGi service mocked by e.g Mockito Key: SLING-4813 URL: https://issues.apache.org/jira/browse/SLING-4813 Project: Sling Issue Type: Improv

[jira] [Commented] (SLING-4811) Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin

[ https://issues.apache.org/jira/browse/SLING-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587852#comment-14587852 ] Chetan Mehrotra commented on SLING-4811: You can possibly use [Scheduler.schedule(

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

See Changes: [cziegeler] [maven-release-plugin] prepare for next development iteration [cziegeler] [maven-release-plugin] prepare release org.apache.sling.commons.fsclassloader-1.0.2 [cziegeler] SLING-4809 : Filesystem classwriter do

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

See

Re: slingstart plugin: deployed artifact does not have "slingfeature" classifier?

Am 16.06.15 um 11:19 schrieb Bertrand Delacretaz: > Hi Carsten, > > On Mon, Jun 15, 2015 at 3:29 PM, Carsten Ziegeler > wrote: >> Am 15.06.15 um 15:18 schrieb Bertrand Delacretaz: >>> ...you get a bunch of Maven artifact URLs and need >>> to sort them out into bundles, Sling provisioning models,

Re: slingstart plugin: deployed artifact does not have "slingfeature" classifier?

Hi Carsten, On Mon, Jun 15, 2015 at 3:29 PM, Carsten Ziegeler wrote: > Am 15.06.15 um 15:18 schrieb Bertrand Delacretaz: >> ...you get a bunch of Maven artifact URLs and need >> to sort them out into bundles, Sling provisioning models, etc. >> > Yes, that's what the type is used for, so in your

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

See

Re: [VOTE] Release Apache Sling FileSystem ClassLoader 1.0.2

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

[jira] [Resolved] (SLING-4808) Empty config values parsed in VaultDistributionPackageBuilderFactory should be treated as null

[ https://issues.apache.org/jira/browse/SLING-4808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marius Petria resolved SLING-4808. -- Resolution: Fixed Committed revision 1685733. > Empty config values parsed in VaultDistributio

[jira] [Created] (SLING-4812) Incorrect event handling for initially empty dictionary

Konrad Windszus created SLING-4812: -- Summary: Incorrect event handling for initially empty dictionary Key: SLING-4812 URL: https://issues.apache.org/jira/browse/SLING-4812 Project: Sling Iss

[jira] [Updated] (SLING-4811) Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin

[ https://issues.apache.org/jira/browse/SLING-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4811: --- Description: Since Apache Felix blacklists all OSGi Event Handlers which take too long to com

[jira] [Commented] (SLING-4811) Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin

[ https://issues.apache.org/jira/browse/SLING-4811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587668#comment-14587668 ] Konrad Windszus commented on SLING-4811: There are three different options on how

[jira] [Commented] (SLING-4795) Only discard the ResourceBundles if they are really invalid

[ https://issues.apache.org/jira/browse/SLING-4795?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14587656#comment-14587656 ] Konrad Windszus commented on SLING-4795: [~justinedelson] Thanks for the hint, but

[jira] [Created] (SLING-4811) Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin

Konrad Windszus created SLING-4811: -- Summary: Handle OSGi event in a separate thread to prevent being blacklisted by the OSGi Event Admin Key: SLING-4811 URL: https://issues.apache.org/jira/browse/SLING-4811

Jenkins build is still unstable: sling-trunk-1.8 #1220

See

Re: [VOTE] Release Apache Sling FileSystem ClassLoader 1.0.2

+1, Cheers, Stefan On 6/16/15 9:53 AM, "Carsten Ziegeler" wrote: >Hi, > >We solved 2 issues in this release: >https://issues.apache.org/jira/browse/SLING/fixforversion/12324751 > >Staging repository: >https://repository.apache.org/content/repositories/orgapachesling-1268/ > >You can use this UN

[VOTE] Release Apache Sling FileSystem ClassLoader 1.0.2

Hi, We solved 2 issues in this release: https://issues.apache.org/jira/browse/SLING/fixforversion/12324751 Staging repository: https://repository.apache.org/content/repositories/orgapachesling-1268/ You can use this UNIX script to download the release and verify the signatures: http://svn.apache

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

See Changes: [chetanm] [maven-release-plugin] prepare for next development iteration [chetanm] [maven-release-plugin] prepare release org.apache.sling.tracer-0.0.2 [chetanm] SLING-4739 - Log Tracer - To enable logs for specific catego

[jira] [Closed] (SLING-4755) DiscoveryService isn't shutdown aware (Asynchronously sending topology events)

[ https://issues.apache.org/jira/browse/SLING-4755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Egli closed SLING-4755. -- > DiscoveryService isn't shutdown aware (Asynchronously sending topology events) > -

[jira] [Resolved] (SLING-4810) FS ClassLoader not invalidated if resources change

[ https://issues.apache.org/jira/browse/SLING-4810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-4810. - Resolution: Invalid Fix Version/s: (was: File System ClassLoader 1.0.2)

[jira] [Created] (SLING-4810) FS ClassLoader not invalidated if resources change

Carsten Ziegeler created SLING-4810: --- Summary: FS ClassLoader not invalidated if resources change Key: SLING-4810 URL: https://issues.apache.org/jira/browse/SLING-4810 Project: Sling Issue

[jira] [Resolved] (SLING-4809) Filesystem classwriter does not delete directories

[ https://issues.apache.org/jira/browse/SLING-4809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-4809. - Resolution: Fixed Solved by recursively deleting the directory > Filesystem classwriter d

Re: Maven release:perform resulting in 2 staged repositories

On Tue, Jun 16, 2015 at 12:47 PM, Stefan Egli wrote: > No concrete pointers but what I just noticed when you dropped the > repositories that they origin from 2 different ips Interesting. I attempted again with wifi off but still see 2 different ip. Looks like some network issue here would try lat

Re: Maven release:perform resulting in 2 staged repositories

Hi Chetan, No concrete pointers but what I just noticed when you dropped the repositories that they origin from 2 different ips. Maybe a wifi problem during release:perform? Cheers, Stefan On 6/16/15 8:58 AM, "Chetan Mehrotra" wrote: >Hi Team, > >I am trying to perform release for Sling Tracer