[jira] [Created] (SLING-2813) Add helper method for creating a path of resources

Carsten Ziegeler created SLING-2813: --- Summary: Add helper method for creating a path of resources Key: SLING-2813 URL: https://issues.apache.org/jira/browse/SLING-2813 Project: Sling Issue

[jira] [Commented] (SLING-2813) Add helper method for creating a path of resources

[ https://issues.apache.org/jira/browse/SLING-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623451#comment-13623451 ] Carsten Ziegeler commented on SLING-2813: - Added two new methods in revision 14648

[jira] [Commented] (SLING-2813) Add helper method for creating a path of resources

[ https://issues.apache.org/jira/browse/SLING-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623459#comment-13623459 ] Bertrand Delacretaz commented on SLING-2813: I don't see any tests in revision

[jira] [Commented] (SLING-2813) Add helper method for creating a path of resources

[ https://issues.apache.org/jira/browse/SLING-2813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623460#comment-13623460 ] Carsten Ziegeler commented on SLING-2813: - There are none, feel free to add them

Automated tests, at least under /bundles

Hi, We just had a little ironic exchange with Carsten in SLING-2813...am I the only one who thinks that all our core code should be covered by automated tests? I don't mean requiring stupid 100% test coverage everywhere, as that doesn't always make sense, but adding code to our core (i.e. under /

Re: Automated tests, at least under /bundles

While I totally agree that we should try this, there is no way to enforce it - and it always depends on personal opinion about whether something is worth testing or is too simple to be tested - yes, I know better being safe than sorry. So, basically +1 - but I don't consider this a blocker We hav

Re: Automated tests, at least under /bundles

Who could say "no" to this question ? ;-) Regards Felix Am 05.04.2013 um 10:53 schrieb Bertrand Delacretaz: > Hi, > > We just had a little ironic exchange with Carsten in SLING-2813...am I > the only one who thinks that all our core code should be covered by > automated tests? > > I don't mean

Re: Automated tests, at least under /bundles

On Fri, Apr 5, 2013 at 10:56 AM, Carsten Ziegeler wrote: > ...basically +1 - but I don't consider this a blocker > > We have the same situation with documentation... The impact of incomplete documentation is way less than having untested code to our core. Either we care about Sling being a high-

Re: Automated tests, at least under /bundles

+1 2013/4/5 Bertrand Delacretaz > On Fri, Apr 5, 2013 at 10:56 AM, Carsten Ziegeler > wrote: > > ...basically +1 - but I don't consider this a blocker > > > > We have the same situation with documentation... > > The impact of incomplete documentation is way less than having > untested code to

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

See

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

See

Re: Automated tests, at least under /bundles

Am Freitag, 5. April 2013 schrieb Bertrand Delacretaz: > On Fri, Apr 5, 2013 at 10:56 AM, Carsten Ziegeler wrote: hello, > > ...basically +1 - but I don't consider this a blocker > > > > We have the same situation with documentation... > > The impact of incomplete documentation is way less th

RE: Automated tests, at least under /bundles

+1 to documentation and unit tests. Especially documentation in the form of examples. -Original Message- From: Oliver Lietz [mailto:apa...@oliverlietz.de] Sent: Friday, April 05, 2013 6:37 AM To: dev@sling.apache.org Subject: Re: Automated tests, at least under /bundles Am Freitag, 5.

RE: Automated tests, at least under /bundles

+1 To achieve that, it would be good, if there would be some documentation available how testing stuff (especially integration tests) should be done in the Sling project. best regards Mike > -Original Message- > From: Bertrand Delacretaz [mailto:bdelacre...@apache.org] > Sent: Friday, Ap

Re: Automated tests, at least under /bundles

Hi Bertrand, To be clear, are you proposing that no commit can be made to Sling without automated tests? While I'm certainly in favor of automated tests (and better documentation), this is a significantly higher bar than we have today and I just want us to be crystal clear about what is being prop

Move openid and ocm from bundles to contrib?

It seems to me that bundles/auth/openid and bundles/jcr/ocm aren't really "core" modules and are not being actively maintained. Should these be moved to contrib to better represent their state? Regards, Justin

Re: Move openid and ocm from bundles to contrib?

+1 On Apr 5, 2013, at 2:25 PM, Justin Edelson wrote: > It seems to me that bundles/auth/openid and bundles/jcr/ocm aren't really > "core" modules and are not being actively maintained. Should these be moved > to contrib to better represent their state? > > Regards, > Justin

Jenkins build is unstable: sling-trunk-1.6 #1609

See

Re: Move openid and ocm from bundles to contrib?

Yepp, we had a thread about ocm some weeks ago where we discussed moving it to contrib...we came to this conclusion but never moved... 2013/4/5 Antonio Sanso > +1 > > > On Apr 5, 2013, at 2:25 PM, Justin Edelson wrote: > > > It seems to me that bundles/auth/openid and bundles/jcr/ocm aren't rea

Re: Automated tests, at least under /bundles

On Fri, Apr 5, 2013 at 2:22 PM, Justin Edelson wrote: > ...To be clear, are you proposing that no commit can be made to Sling without > automated tests?... For core stuff I think we should clearly aim for that. Another metric that might be more flexible is to look at test coverage before releasi

Re: Move openid and ocm from bundles to contrib?

Hi, On Fri, Apr 5, 2013 at 2:25 PM, Justin Edelson wrote: > It seems to me that bundles/auth/openid and bundles/jcr/ocm aren't really > "core" modules and are not being actively maintained. Should these be moved > to contrib to better represent their state?... +1 for jcr/ocm +0 for auth/openid,

[jira] [Assigned] (SLING-2810) Provide JaCoCo agent servlet to expose code coverage data to HTTP clients during Sling Junit Test execution

[ https://issues.apache.org/jira/browse/SLING-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-2810: -- Assignee: Bertrand Delacretaz > Provide JaCoCo agent servlet to expose code

[jira] [Commented] (SLING-2810) Provide JaCoCo agent servlet to expose code coverage data to HTTP clients during Sling Junit Test execution

[ https://issues.apache.org/jira/browse/SLING-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623677#comment-13623677 ] Bertrand Delacretaz commented on SLING-2810: Thanks very much for your contrib

[jira] [Commented] (SLING-1803) add coverage reporting of integration tests

[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13623683#comment-13623683 ] Bertrand Delacretaz commented on SLING-1803: With the JaCoCo servlet introduce

[jira] [Assigned] (SLING-1803) add coverage reporting of integration tests

[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-1803: -- Assignee: Bertrand Delacretaz (was: Justin Edelson) > add coverage reporti

[jira] [Assigned] (SLING-2002) Migrate the Sling website to the ASF CMS

[ https://issues.apache.org/jira/browse/SLING-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz reassigned SLING-2002: -- Assignee: (was: Bertrand Delacretaz) Un-assigning - this is a group effort

[jira] [Updated] (SLING-1803) add coverage reporting of integration tests

[ https://issues.apache.org/jira/browse/SLING-1803?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated SLING-1803: --- Priority: Major (was: Minor) > add coverage reporting of integration tests > ---

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

See

Re: Automated tests, at least under /bundles

On Saturday, April 6, 2013, Bertrand Delacretaz wrote: > On Fri, Apr 5, 2013 at 2:22 PM, Justin Edelson > > > wrote: > > ...To be clear, are you proposing that no commit can be made to Sling > without > > automated tests?... > > For core stuff I think we should clearly aim for that. Aim, but p

[jira] [Updated] (SLING-2810) Provide JaCoCo agent servlet to expose code coverage data to HTTP clients during Sling Junit Test execution

[ https://issues.apache.org/jira/browse/SLING-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Adamcin updated SLING-2810: Attachment: madamcin_some_adjustments_to_jacoco_instructions.patch Thanks, Bertrand. I think your c

Re: Apache Cassandra backend for Sling: GSoC2013 Project

Hi Ian, In Sling, are we going to ship native Cassandra instance with the sling binary pack? ( is there already a native cassandra server starting at sling server start up ?) I am willing to use hector API to deal with Cassandra, as in most of occasions around . Please let me know if there is any