Build failed in Hudson: sling-trunk-1.5 #945

[Apache Hudson Server]

See 

Changes:

[justin] adding some debug logging during bootstrapping

--
[...truncated 5325 lines...]
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[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] [bundle:bundle {execution: 
default-bundle}]

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

 to 
/home/hudson/hudson/jobs/sling-trunk-1.5/modules/org.apache.sling$org.apache.sling.scripting.jsp.taglib/builds/2010-10-28_21-54-32/archive/org.apache.sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/pom.xml
[HUDSON] Archiving 

 to 
/home/hudson/hudson/jobs/sling-trunk-1.5/modules/org.apache.sling$org.apache.sling.scripting.jsp.taglib/builds/2010-10-28_21-54-32/archive/org.apache.sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/org.apache.sling.scripting.jsp.taglib-2.1.1-SNAPSHOT.jar
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [source:jar {execution: attach-sources}]
[INFO] Building jar: 

[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: 
org.apache.sling.scripting.jsp.taglib-2.1.1-SNAPSHOT.jar
[INFO] Checking legal files in: 
org.apache.sling.scripting.jsp.taglib-2.1.1-SNAPSHOT-sources.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing 

 to 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/org.apache.sling.scripting.jsp.taglib-2.1.1-SNAPSHOT.jar
[INFO] Installing 

 to 
/home/hudson/.m2/repository/org/apache/sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/org.apache.sling.scripting.jsp.taglib-2.1.1-SNAPSHOT-sources.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Local OBR update disabled (enable with -DobrRepository)
[INFO] [deploy:deploy {execution: default-deploy}]
[INFO] Retrieving previous build number from apache.snapshots.https
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/org.apache.sling.scripting.jsp.taglib-2.1.1-20101028.215456-11.jar
23K uploaded  
(org.apache.sling.scripting.jsp.taglib-2.1.1-20101028.215456-11.jar)
[INFO] Retrieving previous metadata from apache.snapshots.https
[INFO] Uploading repository metadata for: 'artifact 
org.apache.sling:org.apache.sling.scripting.jsp.taglib'
[INFO] Retrieving previous metadata from apache.snapshots.https
[INFO] Uploading repository metadata for: 'snapshot 
org.apache.sling:org.apache.sling.scripting.jsp.taglib:2.1.1-SNAPSHOT'
[INFO] Uploading project information for org.apache.sling.scripting.jsp.taglib 
2.1.1-20101028.215456-11
[INFO] Retrieving previous build number from apache.snapshots.https
Uploading: 
https://repository.apache.org/content/repositories/snapshots/org/apache/sling/org.apache.sling.scripting.jsp.taglib/2.1.1-SNAPSHOT/org.apache.sling.scripting.jsp.taglib-2.1.1-20101028.215456-11-sources.jar
19K uploaded  
(org.apache.sling.scripting.jsp.taglib-2.1.1-20101028.215456-11-sources.jar)
[INFO] [bundle:deploy {execution: default-deploy}]
[INFO] Remote OBR update disabled (enable with -DremoteOBR)
[HUDSON] Archiving 

 to 
/home/hudson/hudson/jobs/sling-trunk-1.5/modules/org

Build failed in Hudson: sling-trunk-1.5 » Apache Sling Bundle Resource Provider #945

[Apache Hudson Server]

See 


--
[INFO] 
[INFO] Building Apache Sling Bundle Resource Provider
[INFO]task-segment: [clean, deploy]
[INFO] 
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set: 

 (included: [**], excluded: [])
[INFO] [enforcer:enforce {execution: enforce-java}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 0 resource
[INFO] Copying 3 resources
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
 [echo]  WARNING (SLING-443/SLING-1782) 
**
 [echo] On most platforms, you'll get OutOfMemoryErrors when building 
unless you set
 [echo] on 32bit platforms: MAVEN_OPTS="-Xmx256M -XX:MaxPermSize=256M", see 
SLING-443
 [echo] on 64bit platforms: MAVEN_OPTS="-Xmx512M -XX:MaxPermSize=512M", see 
SLING-1782
 [echo] 
**
[INFO] Executed tasks
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 9 source files to 

[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] No sources to compile
[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] [bundle:bundle {execution: 
default-bundle}]

java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor39.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at aQute.lib.osgi.Macro.doCommand(Macro.java:183)
at aQute.lib.osgi.Macro.doCommands(Macro.java:171)
at aQute.lib.osgi.Macro.replace(Macro.java:118)
at aQute.lib.osgi.Macro.process(Macro.java:62)
at aQute.lib.osgi.Macro.process(Macro.java:78)
at aQute.lib.osgi.Macro.process(Macro.java:48)
at aQute.lib.osgi.Macro.process(Macro.java:43)
at aQute.lib.osgi.Processor.getProperty(Processor.java:609)
at aQute.lib.osgi.Processor.getProperty(Processor.java:387)
at aQute.lib.osgi.Analyzer.getImportPackages(Analyzer.java:248)
at aQute.lib.osgi.Builder.getImportPackages(Builder.java:149)
at aQute.lib.osgi.Analyzer.analyze(Analyzer.java:146)
at aQute.lib.osgi.Builder.analyze(Builder.java:198)
at aQute.lib.osgi.Analyzer.calcManifest(Analyzer.java:283)
at aQute.lib.osgi.Builder.build(Builder.java:78)
at 
org.apache.felix.bundleplugin.BundlePlugin.buildOSGiBundle(BundlePlugin.java:395)
at 
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:286)
at 
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:240)
at 
org.apache.felix.bundleplugin.BundlePlugin.execute(BundlePlugin.java:231)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at 
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.D

Re: Bootloader not updating jars

[Justin Edelson]

On Oct 28, 2010, at 7:43 AM, Ian Boston wrote:

> 
> On 28 Oct 2010, at 12:29, Justin Edelson wrote:
> 
>> I don't think that's happened yet. What might be happening is that the 
>> bundles aren't reloaded unless the timestamp of the launchpad base JAR has 
>> changed.
> 
> Checked that,
> Recreated the jar, and the bundle jars inside with all the timestamps after 
> everything in the sling folder. No update happens.  

I'm almost 100% sure that's the problem. I just added some debug info, which 
you can see by running launchpad with -l INFO.

> 
> Its not that much a problem we manage our servers with puppetd, and we can 
> change the upgrade mechanism to loading over http or one of the felix 
> mechanisms. (eg filesystem). The production team here don't like the idea of 
> putting the jars in the JCR, so we probably wont use that one.
> 
>> 
>> Ian- try running a debugger and you should be able to see where in 
>> BootstapInstaller the decision is made to skip installation/upgrade.
>> 
>> What I had to so is delete the bootstapinstaller.ser file manually. If this 
>> file is missing, bundles will always be installed/upgraded.
> 
> Ok thats a good workaround and a safe switch, and upgrades just the new ones 
> as before. If possible it would be really helpful to keep that "feature"

Better yet, set org.apache.sling.launchpad.force.package.bundle.loading to 
true, i.e.

java -Dorg.apache.sling.launchpad.force.package.bundle.loading=true 
launchpad.jar -l INFO

I forgot about that option.

Justin

> Thanks
> Ian
> 
>> 
>> Justin
>> 
>> On Oct 28, 2010, at 5:57 AM, Felix Meschberger  wrote:
>> 
>>> Hi,
>>> 
>>> IIRC we just discussed to remove this functionality from the launchpad
>>> and replace it with an extension to the OSGi Installer.
>>> 
>>> But I do not exactly know where are standing here  Maybe Carsten
>>> and/or Justin know more.
>>> 
>>> Regards
>>> Felix
>>> 
>>> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: 
 Hi,
 
 I might have missed a change in the launchpad/bootloader
 
 When re rebuild the standalone jar with additional bundles or updatede 
 bundles and restart and existing Sling instance, the new or updated 
 bundles are not updated. The only way to update jars appears to be via one 
 of the other methods (web console, file install, jcr installer).
 
 Was there a change to the launchpad ?
 I am sure this used to work.
 Ian
 
>>> 
>>> 
> 

Re: release managment help

[Justin Edelson]

On Oct 28, 2010, at 5:58 AM, Mike Müller wrote:

> Hi
> 
> Okay, here we are - I need some help to promote the 
> sling explorer release 1.0.0:
> 
> 1) Which of the files I do have to copy to
> /x1/www/www.apache.org/dist/sling on people.apache.org?
> All files which are under [1]? If yes, which is the most efficient
> way to download them all from there (locally I do not have the 
> md5 and sh1 files).
> 

Yeah. You should have all the files in your local Maven repository.

> 2) Should I deploy Sling Explorer also to Sling OBR?

Yes. But only after the central sync has happened, which is usually after your 
Release the staging repository in Nexus.

Justin

> 
> 
> [1] 
> https://repository.apache.org/content/repositories/orgapachesling-007/org/apache/sling/org.apache.sling.extensions.explorer/1.0.0/
> 
> best regards
> mike

Re: Bootloader not updating jars

[Ian Boston]

On 28 Oct 2010, at 12:29, Justin Edelson wrote:

> I don't think that's happened yet. What might be happening is that the 
> bundles aren't reloaded unless the timestamp of the launchpad base JAR has 
> changed.

Checked that,
Recreated the jar, and the bundle jars inside with all the timestamps after 
everything in the sling folder. No update happens.  

Its not that much a problem we manage our servers with puppetd, and we can 
change the upgrade mechanism to loading over http or one of the felix 
mechanisms. (eg filesystem). The production team here don't like the idea of 
putting the jars in the JCR, so we probably wont use that one.

> 
> Ian- try running a debugger and you should be able to see where in 
> BootstapInstaller the decision is made to skip installation/upgrade.
> 
> What I had to so is delete the bootstapinstaller.ser file manually. If this 
> file is missing, bundles will always be installed/upgraded.

Ok thats a good workaround and a safe switch, and upgrades just the new ones as 
before. If possible it would be really helpful to keep that "feature"
Thanks
Ian

> 
> Justin
> 
> On Oct 28, 2010, at 5:57 AM, Felix Meschberger  wrote:
> 
>> Hi,
>> 
>> IIRC we just discussed to remove this functionality from the launchpad
>> and replace it with an extension to the OSGi Installer.
>> 
>> But I do not exactly know where are standing here  Maybe Carsten
>> and/or Justin know more.
>> 
>> Regards
>> Felix
>> 
>> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: 
>>> Hi,
>>> 
>>> I might have missed a change in the launchpad/bootloader
>>> 
>>> When re rebuild the standalone jar with additional bundles or updatede 
>>> bundles and restart and existing Sling instance, the new or updated bundles 
>>> are not updated. The only way to update jars appears to be via one of the 
>>> other methods (web console, file install, jcr installer).
>>> 
>>> Was there a change to the launchpad ?
>>> I am sure this used to work.
>>> Ian
>>> 
>> 
>> 

Re: Bootloader not updating jars

[Justin Edelson]

I don't think that's happened yet. What might be happening is that the bundles 
aren't reloaded unless the timestamp of the launchpad base JAR has changed.

Ian- try running a debugger and you should be able to see where in 
BootstapInstaller the decision is made to skip installation/upgrade.

What I had to so is delete the bootstapinstaller.ser file manually. If this 
file is missing, bundles will always be installed/upgraded.

Justin

On Oct 28, 2010, at 5:57 AM, Felix Meschberger  wrote:

> Hi,
> 
> IIRC we just discussed to remove this functionality from the launchpad
> and replace it with an extension to the OSGi Installer.
> 
> But I do not exactly know where are standing here  Maybe Carsten
> and/or Justin know more.
> 
> Regards
> Felix
> 
> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: 
>> Hi,
>> 
>> I might have missed a change in the launchpad/bootloader
>> 
>> When re rebuild the standalone jar with additional bundles or updatede 
>> bundles and restart and existing Sling instance, the new or updated bundles 
>> are not updated. The only way to update jars appears to be via one of the 
>> other methods (web console, file install, jcr installer).
>> 
>> Was there a change to the launchpad ?
>> I am sure this used to work.
>> Ian
>> 
> 
> 

Re: Bootloader not updating jars

[Ian Boston]

Ok, thanks
We will have to find a work around, using one of the other techniques, I will 
talk to the production teams, they were building new jars as part of the 
deployment strategy and wondering why nothing was updating.
Ian


On 28 Oct 2010, at 10:57, Felix Meschberger wrote:

> Hi,
> 
> IIRC we just discussed to remove this functionality from the launchpad
> and replace it with an extension to the OSGi Installer.
> 
> But I do not exactly know where are standing here  Maybe Carsten
> and/or Justin know more.
> 
> Regards
> Felix
> 
> Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: 
>> Hi,
>> 
>> I might have missed a change in the launchpad/bootloader
>> 
>> When re rebuild the standalone jar with additional bundles or updatede 
>> bundles and restart and existing Sling instance, the new or updated bundles 
>> are not updated. The only way to update jars appears to be via one of the 
>> other methods (web console, file install, jcr installer).
>> 
>> Was there a change to the launchpad ?
>> I am sure this used to work.
>> Ian
>> 
> 
> 

[jira] Closed: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[JIRA]

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

Michael Dürig closed SLING-1856.



Thanks Crasten, works great. 

> Scala Scripting: Upgrade to Scala 2.8
> -
>
> Key: SLING-1856
> URL: https://issues.apache.org/jira/browse/SLING-1856
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Michael Dürig
>Assignee: Carsten Ziegeler
> Fix For: Scripting Scala 1.0.0
>
> Attachments: SLING-1856.patch
>
>
> Scala 2.8 is out since a while now. The Sling Scala scripting engine is still 
> at version 2.7.7. I suggest to upgrade to 2.8

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

release managment help

[Mike Müller]

Hi

Okay, here we are - I need some help to promote the 
sling explorer release 1.0.0:

1) Which of the files I do have to copy to
/x1/www/www.apache.org/dist/sling on people.apache.org?
All files which are under [1]? If yes, which is the most efficient
way to download them all from there (locally I do not have the 
md5 and sh1 files).

2) Should I deploy Sling Explorer also to Sling OBR?


[1] 
https://repository.apache.org/content/repositories/orgapachesling-007/org/apache/sling/org.apache.sling.extensions.explorer/1.0.0/

best regards
mike

Re: Bootloader not updating jars

[Felix Meschberger]

Hi,

IIRC we just discussed to remove this functionality from the launchpad
and replace it with an extension to the OSGi Installer.

But I do not exactly know where are standing here  Maybe Carsten
and/or Justin know more.

Regards
Felix

Am Donnerstag, den 28.10.2010, 10:10 +0100 schrieb Ian Boston: 
> Hi,
> 
> I might have missed a change in the launchpad/bootloader
> 
> When re rebuild the standalone jar with additional bundles or updatede 
> bundles and restart and existing Sling instance, the new or updated bundles 
> are not updated. The only way to update jars appears to be via one of the 
> other methods (web console, file install, jcr installer).
> 
> Was there a change to the launchpad ?
> I am sure this used to work.
> Ian
> 

[RESULT] [VOTE] Apache Sling Explorer 1.0.0

[Mike Müller]

Hi,

The vote has passed with the following result :

5 +1 (all binding): Felix Meschberger, Ian Boston, Carsten Ziegler, Bertrand 
Delacretaz, Mike Müller

Thanks for voting - I'll release the artifacts asap, maybe I come back seeking 
some help...

best regards
mike

RE: [VOTE] Apache Sling Explorer 1.0.0

[Mike Müller]

+1 from me of course ;-))

best regards
mike

> -Original Message-
> From: Mike Müller [mailto:mike...@mysign.ch]
> Sent: Monday, October 25, 2010 11:56 AM
> To: 'dev@sling.apache.org'
> Subject: [VOTE] Apache Sling Explorer 1.0.0
> 
> Hi,
> 
> I tried to get out my first release, so be prepared, someting goes wrong ;-))
> 
> We solved 16 issues in this release:
> https://issues.apache.org/jira/browse/SLING/fixforversion/12315319
> 
> There are no outstanding issues:
> 
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-007/
> 
> 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 007 /tmp/sling-staging
> 
> Please vote to approve this release:
> 
>   [ ] +1 Approve the release
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...
> 
> This vote will be open for 72 hours.

[jira] Resolved: (SLING-1249) Commons Threads should be an optional dependency

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-1249.
-

Resolution: Won't Fix

Rethinking this, it doesn't really make sense - using the thread pool makes 
configuration and management easier

> Commons Threads should be an optional dependency
> 
>
> Key: SLING-1249
> URL: https://issues.apache.org/jira/browse/SLING-1249
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons Scheduler 2.1.0
>Reporter: Carsten Ziegeler
>
> The scheduler currently requires the thread pool bundle to be present, this 
> could be made optional.

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

Bootloader not updating jars

[Ian Boston]

Hi,

I might have missed a change in the launchpad/bootloader

When re rebuild the standalone jar with additional bundles or updatede bundles 
and restart and existing Sling instance, the new or updated bundles are not 
updated. The only way to update jars appears to be via one of the other methods 
(web console, file install, jcr installer).

Was there a change to the launchpad ?
I am sure this used to work.
Ian

[jira] Resolved: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler resolved SLING-1856.
-

   Resolution: Fixed
Fix Version/s: Scripting Scala 1.0.0

Thanks Michael for your patch - it's applied in revision 1028221

> Scala Scripting: Upgrade to Scala 2.8
> -
>
> Key: SLING-1856
> URL: https://issues.apache.org/jira/browse/SLING-1856
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Michael Dürig
>Assignee: Carsten Ziegeler
> Fix For: Scripting Scala 1.0.0
>
> Attachments: SLING-1856.patch
>
>
> Scala 2.8 is out since a while now. The Sling Scala scripting engine is still 
> at version 2.7.7. I suggest to upgrade to 2.8

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

[jira] Assigned: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[Carsten Ziegeler (JIRA)]

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

Carsten Ziegeler reassigned SLING-1856:
---

Assignee: Carsten Ziegeler

> Scala Scripting: Upgrade to Scala 2.8
> -
>
> Key: SLING-1856
> URL: https://issues.apache.org/jira/browse/SLING-1856
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Michael Dürig
>Assignee: Carsten Ziegeler
> Attachments: SLING-1856.patch
>
>
> Scala 2.8 is out since a while now. The Sling Scala scripting engine is still 
> at version 2.7.7. I suggest to upgrade to 2.8

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

[jira] Updated: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[JIRA]

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

Michael Dürig updated SLING-1856:
-

Attachment: SLING-1856.patch

Patch for upgrading to Scala 2.8

> Scala Scripting: Upgrade to Scala 2.8
> -
>
> Key: SLING-1856
> URL: https://issues.apache.org/jira/browse/SLING-1856
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Michael Dürig
> Attachments: SLING-1856.patch
>
>
> Scala 2.8 is out since a while now. The Sling Scala scripting engine is still 
> at version 2.7.7. I suggest to upgrade to 2.8

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

[jira] Created: (SLING-1856) Scala Scripting: Upgrade to Scala 2.8

[JIRA]

Scala Scripting: Upgrade to Scala 2.8
-

 Key: SLING-1856
 URL: https://issues.apache.org/jira/browse/SLING-1856
 Project: Sling
  Issue Type: Improvement
  Components: Scripting
Reporter: Michael Dürig
 Attachments: SLING-1856.patch

Scala 2.8 is out since a while now. The Sling Scala scripting engine is still 
at version 2.7.7. I suggest to upgrade to 2.8

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