willing to contribute to sling in GSOC 2010

[Subash Chaturanga]

Hi !. I am Subash Chaturanga from *University Of Moratuwa*.

I would love if I can contribute to apache Sling in GSOC 2010. Because im
really interested in JCR.

I am currently working on a project called *WSO2 Governance Registry JCR *(JSR
283) as *an intern* in an open source company called *WSO2* in Sri lanka.

I almost went through (but still some more to cover ) in JCR 2 spec.So
I thought that is not a bad  start as a beginner to contribute Sling.

Is that the correct path for a beginner like me to start on a sling project?

I saw the two suggestions :

   -  mini CMS for sling
   -   unit and integration tests for Sling

Does sling wish to introduce both of these projects or only one of them at
the end of the day?


Thanks
Subash Chaturanga

[jira] Commented: (SLING-514) Expose current session through currentSession binding

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-514:
--

ugh. wish I hadn't called the class CurrentNodeBindingsValuesProvider. Should 
obviously be renamed to something like JcrObjectsBindingsValuesProvider

> Expose current session through currentSession binding
> -
>
> Key: SLING-514
> URL: https://issues.apache.org/jira/browse/SLING-514
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Affects Versions: JCR Resource 2.0.6
>Reporter: David Nuescheler
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: JCR Resource 2.0.8
>
>
> i think it would be great to expose a currentSession variable in scripting 
> similar to the currentNode.
> in a usecase that i ran to recently i needed access to the session and tried 
> to go through currentNode.getSession() which didn't work because my 
> currentNode did not really exist since it was a synthetic resource that i 
> requested.
> of course one can go through the 
> request.getResourceResolver().adaptTo(Packages.javax.jcr.Session) to acquire 
> the session but i think a short-hand would be nice since this is a very 
> common case

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is still unstable: sling-trunk-1.6 #331

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #331

[Apache Hudson Server]

See 

[jira] Updated: (SLING-874) Use new commons compiler for java servlet scripting

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-874:
---

Affects Version/s: Scripting Java 1.0.0
Fix Version/s: Scripting Java 1.0.2

> Use new commons compiler for java servlet scripting
> ---
>
> Key: SLING-874
> URL: https://issues.apache.org/jira/browse/SLING-874
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting Java 1.0.0
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Scripting Java 1.0.2
>
>
> Currently the java servlet scripting bundle embeds its own version of the 
> eclipse compiler. This can be changed to use the new commons compiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-514) Expose current session through currentSession binding

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler updated SLING-514:
---

  Component/s: (was: Scripting)
   JCR
Affects Version/s: (was: Scripting JavaScript 2.0.2)
   JCR Resource 2.0.6
Fix Version/s: JCR Resource 2.0.8
  Summary: Expose current session through currentSession binding  
(was: expose currentSession)

Moving this to the jcr resource bundle which now does adding the jcr based 
bindings

> Expose current session through currentSession binding
> -
>
> Key: SLING-514
> URL: https://issues.apache.org/jira/browse/SLING-514
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Affects Versions: JCR Resource 2.0.6
>Reporter: David Nuescheler
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: JCR Resource 2.0.8
>
>
> i think it would be great to expose a currentSession variable in scripting 
> similar to the currentNode.
> in a usecase that i ran to recently i needed access to the session and tried 
> to go through currentNode.getSession() which didn't work because my 
> currentNode did not really exist since it was a synthetic resource that i 
> requested.
> of course one can go through the 
> request.getResourceResolver().adaptTo(Packages.javax.jcr.Session) to acquire 
> the session but i think a short-hand would be nice since this is a very 
> common case

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (SLING-874) Use new commons compiler for java servlet scripting

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler reassigned SLING-874:
--

Assignee: Carsten Ziegeler

> Use new commons compiler for java servlet scripting
> ---
>
> Key: SLING-874
> URL: https://issues.apache.org/jira/browse/SLING-874
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
>
> Currently the java servlet scripting bundle embeds its own version of the 
> eclipse compiler. This can be changed to use the new commons compiler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (SLING-514) expose currentSession

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler reassigned SLING-514:
--

Assignee: Carsten Ziegeler

> expose currentSession
> -
>
> Key: SLING-514
> URL: https://issues.apache.org/jira/browse/SLING-514
> Project: Sling
>  Issue Type: New Feature
>  Components: JCR
>Affects Versions: JCR Resource 2.0.6
>Reporter: David Nuescheler
>Assignee: Carsten Ziegeler
>Priority: Minor
> Fix For: JCR Resource 2.0.8
>
>
> i think it would be great to expose a currentSession variable in scripting 
> similar to the currentNode.
> in a usecase that i ran to recently i needed access to the session and tried 
> to go through currentNode.getSession() which didn't work because my 
> currentNode did not really exist since it was a synthetic resource that i 
> requested.
> of course one can go through the 
> request.getResourceResolver().adaptTo(Packages.javax.jcr.Session) to acquire 
> the session but i think a short-hand would be nice since this is a very 
> common case

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Closed: (SLING-591) NoSuchMethodError exception in javax.script.Bindings when running on Java 5

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler closed SLING-591.
--


> NoSuchMethodError exception in javax.script.Bindings when running on Java 5
> ---
>
> Key: SLING-591
> URL: https://issues.apache.org/jira/browse/SLING-591
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
> Environment: Mac OS X 10.5/Intel64
>Reporter: Oliver Lietz
>
> running scripting on Java 5 leads to runtime errors:
> *ERROR* [btpool0-2] 
> org.apache.sling.scripting.freemarker.FreemarkerScriptEngine Failure running 
> Freemarker script. java.lang.NoSuchMethodError: 
> javax.script.Bindings.put(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/Object;
>   at 
> org.apache.sling.scripting.freemarker.FreemarkerScriptEngine.eval(FreemarkerScriptEngine.java:69)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:135)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:106)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:219)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:462)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.processRequest(SlingMainServlet.java:419)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:48)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:54)
>   at 
> org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter.doFilter(RequestProgressTrackerLogFilter.java:59)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:52)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:273)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:171)
> [...]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (SLING-591) NoSuchMethodError exception in javax.script.Bindings when running on Java 5

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-591.


Resolution: Fixed

I think we can set this to fixed now as we're not using the bsf version anymore

> NoSuchMethodError exception in javax.script.Bindings when running on Java 5
> ---
>
> Key: SLING-591
> URL: https://issues.apache.org/jira/browse/SLING-591
> Project: Sling
>  Issue Type: Bug
>  Components: Scripting
> Environment: Mac OS X 10.5/Intel64
>Reporter: Oliver Lietz
>
> running scripting on Java 5 leads to runtime errors:
> *ERROR* [btpool0-2] 
> org.apache.sling.scripting.freemarker.FreemarkerScriptEngine Failure running 
> Freemarker script. java.lang.NoSuchMethodError: 
> javax.script.Bindings.put(Ljava/lang/String;Ljava/lang/Object;)Ljava/lang/Object;
>   at 
> org.apache.sling.scripting.freemarker.FreemarkerScriptEngine.eval(FreemarkerScriptEngine.java:69)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.call(DefaultSlingScript.java:135)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.eval(DefaultSlingScript.java:106)
>   at 
> org.apache.sling.scripting.core.impl.DefaultSlingScript.service(DefaultSlingScript.java:219)
>   at 
> org.apache.sling.engine.impl.request.RequestData.service(RequestData.java:462)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.processRequest(SlingMainServlet.java:419)
>   at 
> org.apache.sling.engine.impl.filter.RequestSlingFilterChain.render(RequestSlingFilterChain.java:48)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:54)
>   at 
> org.apache.sling.engine.impl.debug.RequestProgressTrackerLogFilter.doFilter(RequestProgressTrackerLogFilter.java:59)
>   at 
> org.apache.sling.engine.impl.filter.AbstractSlingFilterChain.doFilter(AbstractSlingFilterChain.java:52)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:273)
>   at 
> org.apache.sling.engine.impl.SlingMainServlet.service(SlingMainServlet.java:171)
> [...]

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: Hudson build is still unstable: sling-trunk-1.5 #632

[Bertrand Delacretaz]

On Fri, Mar 12, 2010 at 5:10 PM, Apache Hudson Server
 wrote:
> See 

I have no idea why the build is still failing, the launchpad/testing
tests get a 404 when trying to POST to find out if Sling is ready.

Maybe it's just the Hudson machine that is very slow, causing a
timeout of those tests after 60 seconds?

The build takes 35 minutes on minerva.apache.org, on my laptop it's
just a few minutes, about 10 times faster I guess.

-Bertrand

[jira] Reopened: (SLING-1425) Sling website downloads page is broken

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz reopened SLING-1425:


  Assignee: (was: Bertrand Delacretaz)

403 Forbidden is back at http://sling.apache.org/site/downloads.cgi

> Sling website downloads page is broken
> --
>
> Key: SLING-1425
> URL: https://issues.apache.org/jira/browse/SLING-1425
> Project: Sling
>  Issue Type: Bug
>  Components: Site
>Reporter: Bertrand Delacretaz
>
> http://sling.apache.org/site/downloads.cgi returns 403 Forbidden.
> I'm not sure if and where we have documentation about how that downloads page 
> is setup, but according to 
> http://www.mail-archive.com/d...@felix.apache.org/msg00964.html it seems like 
> we need a downloads.cgi script as follows:
> !/bin/sh
> # Wrapper script around mirrors.cgi script
> # (we must change to that directory in order for python to pick up the
> #  python includes correctly)
> cd /www/www.apache.org/dyn/mirrors
> /www/www.apache.org/dyn/mirrors/mirrors.cgi $*
> in /www/sling.apache.org/site on people.a.o, alongside the downloads.html 
> page which is exported from Confluence.
> That script was missing, I will re-add it under /www/sling.apache.org/site 
> Do we need it under /www/confluence-exports/SLINGxSITE/ as well? I don't have 
> karma to add it there.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is still unstable: sling-trunk-1.5 #632

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trun k-1.5 » Apache Sling Launchpad Testing #632

[Apache Hudson Server]

See 

[jira] Commented: (SLING-1435) After a NoClassDefError classes are still not found even if they have been installed in the meantime with Java 6

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-1435:
-

I've improved the reloading behaviour of the classloader in revision 922272 to 
only check if a bundle is used if a bundle unresolved event occurs.

> After a NoClassDefError classes are still not found even if they have been 
> installed in the meantime with Java 6
> 
>
> Key: SLING-1435
> URL: https://issues.apache.org/jira/browse/SLING-1435
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons ClassLoader 1.1.4
>Reporter: Carsten Ziegeler
>Assignee: Carsten Ziegeler
> Fix For: Commons ClassLoader 1.1.6
>
>
> Scenario - note that this works fine with Java 5, but on Java 6 we have:
> - A jsp instanties a class from bundle A with the new operator
> - JSP is loaded - everything is working fine
> - Bundle A is uninstalled
> - JSP invocation results in NoClassDefFoundError (which is expected)
> - Bundle A is installed
> - JSP is invoked and as soon as the new operator is called a 
> NoClassDefFoundError is called
> It seems that Java 6 behaves differently than Java 5: The jsp can be loaded 
> and executed, but as soon as the class from Bundle A is used, Java 6 
> memorieses that the class was gone inbetween and it is not possible to update 
> this state somehow. All involved classloaders are not queried anymore

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Hudson build is still unstable: sling-trunk-1.5 #631

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trun k-1.5 » Apache Sling Launchpad Testing #631

[Apache Hudson Server]

See 

Build failed in Hudson: sling-contrib-1.5 #405

[Apache Hudson Server]

See 

Changes:

[cziegeler] SLING-1385 : Recompile java scripts on modifications and avoid 
periodic check - fix error handling and sync problems.

--
[...truncated 3729 lines...]
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 50 resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 7 source files to 

[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 


---
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[org.apache.sling.launchpad.contrib-testing] in 
[
[INFO] Processing war project
[INFO] Copying webapp 
webResources[
 
to[
[INFO] Copying webapp 
webResources[
 
to[
[INFO] Processing overlay[ id 
org.apache.sling:org.apache.sling.launchpad.base:webapp]
[INFO] Webapp assembled in [315 msecs]
[INFO] Building war: 

[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[HUDSON] Archiving 

 to 
/export/home/hudson/hudson/jobs/sling-contrib-1.5/modules/org.apache.sling$org.apache.sling.launchpad.contrib-testing/builds/2010-03-12_12-01-53/archive/org.apache.sling/org.apache.sling.launchpad.contrib-testing/4-SNAPSHOT/pom.xml
[HUDSON] Archiving 

 to 
/export/home/hudson/hudson/jobs/sling-contrib-1.5/modules/org.apache.sling$org.apache.sling.launchpad.contrib-testing/builds/2010-03-12_12-01-53/archive/org.apache.sling/org.apache.sling.launchpad.contrib-testing/4-SNAPSHOT/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT.war
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: 

[INFO] [antrun:run {execution: delete-sling-folder}]
[INFO] Executing tasks
 [echo] SLING-845 - delete parent sling folder before integration tests
   [delete] Deleting directory 

[INFO] Executed tasks
[INFO] [cargo:start {execution: start-container}]
[INFO] [beddedLocalContainer] Jetty 6.x Embedded starting...
2010-03-12 12:13:50.847::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2010-03-12 12:13:50.886::INFO:  jetty-6.1.1rc1
2010-03-12 12:13:50.989::INFO:  Extract 
jar:
 to 
/tmp/Jetty_0_0_0_0_46087_org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT.war__org_apache_sling_launchpad_contrib-testing-4-SNAPSHOT__-6974mw/webapp
log4j:WARN No appenders could be found for logger 
(org.apache.jasper.compiler.JspRuntimeContext).
log4j:WARN Please initialize the log4j system properly.
2010-03-12 
12:13:58.251:/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT:INFO:  
sling: Setting 
sling.home=sling/_org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT 
(servlet context path)
2010-03-12 
12:13:58.257:/org.apach

Build failed in Hudson: sling-contrib-1.5 » Apache Sling Launchpad Contrib Testing #405

[Apache Hudson Server]

See 


--
[...truncated 147 lines...]
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
 [echo] ** WARNING (SLING-443) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=128M", see SLING-443.
 [echo] 
*
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] No sources to compile
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 50 resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 7 source files to 

[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 


---
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[HUDSON] Recording test results
[INFO] [war:war {execution: default-war}]
[INFO] Packaging webapp
[INFO] Assembling webapp[org.apache.sling.launchpad.contrib-testing] in 
[
[INFO] Processing war project
[INFO] Copying webapp 
webResources[
 
to[
[INFO] Copying webapp 
webResources[
 
to[
[INFO] Processing overlay[ id 
org.apache.sling:org.apache.sling.launchpad.base:webapp]
[INFO] Webapp assembled in [315 msecs]
[INFO] Building war: 

[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[HUDSON] Archiving 

 to 
/export/home/hudson/hudson/jobs/sling-contrib-1.5/modules/org.apache.sling$org.apache.sling.launchpad.contrib-testing/builds/2010-03-12_12-01-53/archive/org.apache.sling/org.apache.sling.launchpad.contrib-testing/4-SNAPSHOT/pom.xml
[HUDSON] Archiving 

 to 
/export/home/hudson/hudson/jobs/sling-contrib-1.5/modules/org.apache.sling$org.apache.sling.launchpad.contrib-testing/builds/2010-03-12_12-01-53/archive/org.apache.sling/org.apache.sling.launchpad.contrib-testing/4-SNAPSHOT/org.apache.sling.launchpad.contrib-testing-4-SNAPSHOT.war
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: 

[INFO] [antrun:run {execution: delete-sling-folder}]
[INFO] Executing tasks
 [echo] SLING-845 - delete parent sling folder before integration tests
   [delete] Deleting directory 
/home/hudson/hudson-slave/workspace/sling-contrib-1.5/contrib-1.5/sling
[INFO] Executed tasks
[INFO] [cargo:start {execution: start-container}]
[INFO] [beddedLocalContainer] Jetty 6.x Embedded starting...
2010-03-12 12:13:50.847::INFO:  Logging to STDERR via org.mortbay.log.StdErrLog
2010-03-12 12:13:50.886::INFO:  jetty-6.1.1rc1
2010-03-12 12:13:50.989::INFO:  Extract 
jar:

Hudson build is still unstable: sling-trunk-1.6 #330

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trun k-1.6 » Apache Sling Launchpad Testing #330

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trunk-1.5 #630

[Apache Hudson Server]

See 

Hudson build is still unstable: sling-trun k-1.5 » Apache Sling Launchpad Testing #630

[Apache Hudson Server]

See 

[jira] Commented: (SLING-1437) GSoC 2010: create more unit and integration tests for Sling

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler commented on SLING-1437:
-

In general a gread idea.

For measuring code coverage in integration tests, it would be cool to have some 
Sonar integration - the same goes for coverage of script code.

> GSoC 2010: create more unit and integration tests for Sling
> ---
>
> Key: SLING-1437
> URL: https://issues.apache.org/jira/browse/SLING-1437
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Sling already has fairly good test coverage, but there's always room for 
> improvement. 
> The goal of this Google Summer of Code project is to create more unit and 
> integration tests for Sling.
> The student will have to get familiar with the Sling codebase, identify areas 
> where tests are missing, write unit and integration tests to improve the test 
> coverage, and submit the result as patches that the Sling committers can 
> verify and hopefully apply.
> Another aspect is measuring and reporting (automatically, ideally as part of 
> our Hudson builds) the actual test coverage - that's easy for unit tests 
> which run as part of the module builds, but seems to be harder for 
> integration tests which run in a separate JVM than the one that executes 
> tests.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1438) GSoC 2010: create a mini-CMS to demonstrate Sling

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated SLING-1438:
---

Description: 
This is a suggested project for Google Summer of Code 2010.

The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
practices.

The emphasis is on the quality and readability of the demo code, and we expect 
to have to go through several iterations to refine it and the corresponding JCR 
content model so that they demonstrate Sling best practices. We will not 
necessarily create a full-fledged CMS, the goal is for the result to be 
educational and help Sling newcomers understand how to create web applications 
with it.

Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
server-side scripting, and Java code in OSGi bundles for back-end functionality.

See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
ASF, and http://community.apache.org/gsoc for general GSoC information.

  was:
This is a suggested project for Google Summer of Code 2010.

The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
practices.

The emphasis is on the quality and readability of the demo code, and we expect 
to have to go through several iterations to refine it and the corresponding JCR 
content model so that they demonstrate Sling best practices. We will not 
necessarily create a full-fledged CMS, the goal is for the result to be 
educational and help Sling newcomers understand how to create web applications 
with it.

Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
server-side scripting, and Java code in OSGi bundles for back-end functionality.


> GSoC 2010: create a mini-CMS to demonstrate Sling
> -
>
> Key: SLING-1438
> URL: https://issues.apache.org/jira/browse/SLING-1438
> Project: Sling
>  Issue Type: Task
>  Components: Documentation
>Reporter: Bertrand Delacretaz
>
> This is a suggested project for Google Summer of Code 2010.
> The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
> practices.
> The emphasis is on the quality and readability of the demo code, and we 
> expect to have to go through several iterations to refine it and the 
> corresponding JCR content model so that they demonstrate Sling best 
> practices. We will not necessarily create a full-fledged CMS, the goal is for 
> the result to be educational and help Sling newcomers understand how to 
> create web applications with it.
> Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
> server-side scripting, and Java code in OSGi bundles for back-end 
> functionality.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Created: (SLING-1438) GSoC 2010: create a mini-CMS to demonstrate Sling

[Bertrand Delacretaz (JIRA)]

GSoC 2010: create a mini-CMS to demonstrate Sling
-

 Key: SLING-1438
 URL: https://issues.apache.org/jira/browse/SLING-1438
 Project: Sling
  Issue Type: Task
  Components: Documentation
Reporter: Bertrand Delacretaz


This is a suggested project for Google Summer of Code 2010.

The goal is to create a mini-CMS with Sling, that demonstrates Sling best 
practices.

The emphasis is on the quality and readability of the demo code, and we expect 
to have to go through several iterations to refine it and the corresponding JCR 
content model so that they demonstrate Sling best practices. We will not 
necessarily create a full-fledged CMS, the goal is for the result to be 
educational and help Sling newcomers understand how to create web applications 
with it.

Suggested technologies: jQuery for the front-end, ESP and/or JSP for 
server-side scripting, and Java code in OSGi bundles for back-end functionality.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1437) GSoC 2010: create more unit and integration tests for Sling

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated SLING-1437:
---

Labels: mentor gsoc testing gsoc2010sling  (was: mentor gsoc testing)

> GSoC 2010: create more unit and integration tests for Sling
> ---
>
> Key: SLING-1437
> URL: https://issues.apache.org/jira/browse/SLING-1437
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Sling already has fairly good test coverage, but there's always room for 
> improvement. 
> The goal of this Google Summer of Code project is to create more unit and 
> integration tests for Sling.
> The student will have to get familiar with the Sling codebase, identify areas 
> where tests are missing, write unit and integration tests to improve the test 
> coverage, and submit the result as patches that the Sling committers can 
> verify and hopefully apply.
> Another aspect is measuring and reporting (automatically, ideally as part of 
> our Hudson builds) the actual test coverage - that's easy for unit tests 
> which run as part of the module builds, but seems to be harder for 
> integration tests which run in a separate JVM than the one that executes 
> tests.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (SLING-1437) GSoC 2010: create more unit and integration tests for Sling

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz updated SLING-1437:
---

Description: 
Sling already has fairly good test coverage, but there's always room for 
improvement. 

The goal of this Google Summer of Code project is to create more unit and 
integration tests for Sling.

The student will have to get familiar with the Sling codebase, identify areas 
where tests are missing, write unit and integration tests to improve the test 
coverage, and submit the result as patches that the Sling committers can verify 
and hopefully apply.

Another aspect is measuring and reporting (automatically, ideally as part of 
our Hudson builds) the actual test coverage - that's easy for unit tests which 
run as part of the module builds, but seems to be harder for integration tests 
which run in a separate JVM than the one that executes tests.

See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
ASF, and http://community.apache.org/gsoc for general GSoC information.

  was:
Sling already has fairly good test coverage, but there's always room for 
improvement. 

The goal of this Google Summer of Code project is to create more unit and 
integration tests for Sling.

The student will have to get familiar with the Sling codebase, identify areas 
where tests are missing, write unit and integration tests to improve the test 
coverage, and submit the result as patches that the Sling committers can verify 
and hopefully apply.

Another aspect is measuring and reporting (automatically, ideally as part of 
our Hudson builds) the actual test coverage - that's easy for unit tests which 
run as part of the module builds, but seems to be harder for integration tests 
which run in a separate JVM than the one that executes tests.

See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
ASF.


> GSoC 2010: create more unit and integration tests for Sling
> ---
>
> Key: SLING-1437
> URL: https://issues.apache.org/jira/browse/SLING-1437
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Sling already has fairly good test coverage, but there's always room for 
> improvement. 
> The goal of this Google Summer of Code project is to create more unit and 
> integration tests for Sling.
> The student will have to get familiar with the Sling codebase, identify areas 
> where tests are missing, write unit and integration tests to improve the test 
> coverage, and submit the result as patches that the Sling committers can 
> verify and hopefully apply.
> Another aspect is measuring and reporting (automatically, ideally as part of 
> our Hudson builds) the actual test coverage - that's easy for unit tests 
> which run as part of the module builds, but seems to be harder for 
> integration tests which run in a separate JVM than the one that executes 
> tests.
> See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
> ASF, and http://community.apache.org/gsoc for general GSoC information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

GSoC 2010 should start soon, project proposals are welcome

[Bertrand Delacretaz]

Hi,

The ASF is not yet officially accepted to participate in Google Summer
of Code 2010, but participating organizations will be announced soon
and there's a fair chance for the ASF to be included in that list.

Sling committers are welcome to suggest projects that they'd like to
mentor. You just need to create an issue in our JIRA, with the same
labels as SLING-1437, so that the task appears at
http://tinyurl.com/asfgsoc which is the official list of ASF GSoC 2010
projects.

See http://community.apache.org/gsoc for more info.

-Bertrand

[jira] Created: (SLING-1437) GSoC 2010: create more unit and integration tests for Sling

[Bertrand Delacretaz (JIRA)]

GSoC 2010: create more unit and integration tests for Sling
---

 Key: SLING-1437
 URL: https://issues.apache.org/jira/browse/SLING-1437
 Project: Sling
  Issue Type: Task
  Components: Testing
Reporter: Bertrand Delacretaz


Sling already has fairly good test coverage, but there's always room for 
improvement. 

The goal of this Google Summer of Code project is to create more unit and 
integration tests for Sling.

The student will have to get familiar with the Sling codebase, identify areas 
where tests are missing, write unit and integration tests to improve the test 
coverage, and submit the result as patches that the Sling committers can verify 
and hopefully apply.

Another aspect is measuring and reporting (automatically, ideally as part of 
our Hudson builds) the actual test coverage - that's easy for unit tests which 
run as part of the module builds, but seems to be harder for integration tests 
which run in a separate JVM than the one that executes tests.

See http://tinyurl.com/asfgsoc for the full list of GSoC 2010 projects at the 
ASF.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.