[jira] [Commented] (SLING-3501) Unexpected behaviour when using multiple tags in the web console to run checks

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-3501:


I agree that OR might be more appropriate in some situations, but it depends on 
how your HC tag space is structured.

IIUC your patch removes the AND variant, do you see a way to provide both AND 
or OR? Ideally without breaking compatibility, so maybe something like

  tag1,tag2 -> tag1 AND tag2 as now
  tag1 OR tag2 -> obvious
  tag1 AND tag2 -> obvious

We don't need to support any more complex combinations than this IMO, but both 
OR and AND make sense.

> Unexpected behaviour when using multiple tags in the web console to run checks
> --
>
> Key: SLING-3501
> URL: https://issues.apache.org/jira/browse/SLING-3501
> Project: Sling
>  Issue Type: Bug
>  Components: Health Check
>Reporter: Georg Henzler
>Assignee: Bertrand Delacretaz
> Attachments: SLING-3501-filter-for-taglist-fix.patch
>
>
> Multiple tags (e.g. "category1,category2") are connected with a logical AND 
> at the moment, that means for the given example only HCs with both category 
> tags would be run. 
> From a user's point of view this behaviour is not intuitive (IMHO, also see 
> Björn's comment in the sling-users list [1]). Using the tags 
> "category1,category2" should rather cause all checks of both categories to be 
> run (union instead of intersection). 
> The problem is evident for both the web console [2] and when configuring 
> CompositeHealthChecks (both use HealthCheckFilter).
> [1] 
> http://apache-sling.73963.n3.nabble.com/Healthcheck-Unexpected-behavior-with-tags-td4032090.html
> [2] http://localhost:4502/system/console/healthcheck



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3624) Add SlingHealthCheck annotation

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz commented on SLING-3624:


Interesting, thanks for your contribution!

Could you provide a test that demonstrates an annotation-based health check? 
The best is probably to add it to the healthcheck/it module which already runs 
with pax exam. Let me know via the dev list if I need to add any infrastructure 
to enable that.

> Add SlingHealthCheck annotation
> ---
>
> Key: SLING-3624
> URL: https://issues.apache.org/jira/browse/SLING-3624
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Affects Versions: Health Check Core 1.1.0
>Reporter: Bjoern Weide
>Priority: Minor
> Fix For: Health Check Core 1.1.2
>
> Attachments: slinghealthcheck_annotation.txt
>
>
> Add a SlingHealthCheck annotation (similar to SlingServlet). The metatype 
> property should set to true per default since its probably common to 
> configure healthchecks. Usage examples:
> {code:title=Examples|borderStyle=solid}
> @SlingHealthCheck(name = BundlesStartedCheck.HC_NAME, label = "Apache Sling 
> Health Check - " + BundlesStartedCheck.HC_NAME, description = "Checks whether 
> all bundles are started.", tags = "osgi")
> @SlingHealthCheck(name = DiskSpaceCheck.HC_NAME, label = "Apache Sling Health 
> Check - " + DiskSpaceCheck.HC_NAME,
> description = "Checks whether enough disk space is available.", tags 
> = "resources", configurationFactory = true,
> configurationPolicy = ConfigurationPolicy.REQUIRE)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3217) Automatically expose SlingBindings object through EL

[Felix Meschberger (JIRA)]

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

Felix Meschberger commented on SLING-3217:
--

[~justinedelson] Ah, missed your update. If the namespaces are indeed separate, 
lets do it.

> Automatically expose SlingBindings object through EL
> 
>
> Key: SLING-3217
> URL: https://issues.apache.org/jira/browse/SLING-3217
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Justin Edelson
> Attachments: SLING-3217.patch
>
>
> JSP scripts need to use the  (or a subclass) in order 
> to expose the Sling Bindings objects (i.e. `resource`) for use in a JSP page. 
> This shouldn't be necessary if we provide a custom ELResolver.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3624) Add SlingHealthCheck annotation

[Georg Henzler (JIRA)]

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

Georg Henzler commented on SLING-3624:
--

[~bjoernweide] I just noticed that the property hc.mbean.name is missing in the 
annotation - it should be able to generate all HC-specific properties as 
declared in the HealthCheck interface 
(http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/healthcheck/core/src/main/java/org/apache/sling/hc/api/HealthCheck.java)

> Add SlingHealthCheck annotation
> ---
>
> Key: SLING-3624
> URL: https://issues.apache.org/jira/browse/SLING-3624
> Project: Sling
>  Issue Type: Improvement
>  Components: Health Check
>Affects Versions: Health Check Core 1.1.0
>Reporter: Bjoern Weide
>Priority: Minor
> Fix For: Health Check Core 1.1.2
>
> Attachments: slinghealthcheck_annotation.txt
>
>
> Add a SlingHealthCheck annotation (similar to SlingServlet). The metatype 
> property should set to true per default since its probably common to 
> configure healthchecks. Usage examples:
> {code:title=Examples|borderStyle=solid}
> @SlingHealthCheck(name = BundlesStartedCheck.HC_NAME, label = "Apache Sling 
> Health Check - " + BundlesStartedCheck.HC_NAME, description = "Checks whether 
> all bundles are started.", tags = "osgi")
> @SlingHealthCheck(name = DiskSpaceCheck.HC_NAME, label = "Apache Sling Health 
> Check - " + DiskSpaceCheck.HC_NAME,
> description = "Checks whether enough disk space is available.", tags 
> = "resources", configurationFactory = true,
> configurationPolicy = ConfigurationPolicy.REQUIRE)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build became unstable: sling-trunk-1.6 #2148

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Models Integration Tests #2148

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Changes:

[rombert] Use released versions of org.apache.sling.tooling.support.install and
sling-bundle-archetype

[rombert] impl-resources: correct Service-Component header

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Whitelabel support for the SlingConsoleFactory.

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Enrich and consistently use the WhitelabelSupport class throughout the
UI classes.

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Allow reuse of the ImportWizard

- use more meaningful ids for the import wizard and its category
- move the ImportWizard to an exported package

[rombert] Cleanup plugin.xml in eclipse-m2e-ui

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Whitelabel suport for views

- export the org.apache.sling.ide.eclipse.ui.views package
- use more relevant ids for the view and view category

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

More neutral wording for the bundle/content modules.

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Add a generic server icon for the launch configuration.

[rombert] SLING-3031 - [Tooling] add whitelabel support for slingclipse

Allow overriding the property page to show for Sling projects.

[justin] SLING-3499 - adding support for custom annotation per injector (thanks 
Konrad Windszus for the patch!)

--
[...truncated 38627 lines...]
[INFO] Sling Servlet Archetype ... SUCCESS [11.025s]
[INFO] Sling Bundle Archetype  SUCCESS [8.321s]
[INFO] Sling JCRInstall Bundle Archetype . SUCCESS [8.568s]
[INFO] Sling Taglib Archetype  SUCCESS [3.360s]
[INFO] Apache Sling API .. SUCCESS [10.876s]
[INFO] Apache Sling Resource Resolver  SUCCESS [11.462s]
[INFO] Apache Sling System Bundle Extension: Java Transaction API  SUCCESS 
[3.360s]
[INFO] Apache Sling System Bundle Extension: XML APIs  SUCCESS [3.196s]
[INFO] Apache Sling System Bundle Extension: Activation API  SUCCESS [3.018s]
[INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [3.035s]
[INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [12.673s]
[INFO] Apache Sling Commons Java Compiler  SUCCESS [7.248s]
[INFO] Apache Sling JSON Library . SUCCESS [5.558s]
[INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [35.381s]
[INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [5.083s]
[INFO] Apache Sling MIME type mapping support  SUCCESS [6.738s]
[INFO] Apache Sling Commons OSGi support . SUCCESS [6.182s]
[INFO] Apache Sling Scheduler Support  SUCCESS [5.398s]
[INFO] Apache Sling Testing Utilities  SUCCESS [18.486s]
[INFO] Apache Sling Thread Dumper  SUCCESS [3.764s]
[INFO] Apache Sling Thread Support ... SUCCESS [3.668s]
[INFO] Apache Sling Authentication Service ... SUCCESS [6.511s]
[INFO] Apache Sling OpenID Authentication  SUCCESS [6.782s]
[INFO] Apache Sling Form Based Authentication Handler  SUCCESS [8.715s]
[INFO] Apache Sling Authentication Selector .. SUCCESS [3.819s]
[INFO] Apache Sling Engine Implementation  SUCCESS [35.494s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [3.341s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [5.587s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [3.515s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [6.721s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [8.328s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [5.264s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[5.146s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [2.841s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [5.358s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [35.036s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [5.456s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [5.755s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [5.467s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [3.350s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [3.975s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [22.759s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [6.116s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [5.483s]
[INFO] Apache Sling Default POST Servle

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Models Integration Tests #524

[Apache Jenkins Server]

See 

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling JCR Installer #524

[Apache Jenkins Server]

See 


--
[...truncated 123 lines...]
00:08:38.427 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:38.429 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:38.429 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:38.432 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:38.432 INFO  [JcrInstaller.1] WatchedFolder.java:92   Watching folder 
/libs/tnwf/install.dev (priority 101)
00:08:38.936 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:38.937 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:38.938 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:38.940 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:40.442 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:40.444 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:40.445 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:40.447 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:40.448 INFO  [JcrInstaller.1] WatchedFolder.java:92   Watching folder 
/apps/tnwf/install (priority 200)
00:08:40.951 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:40.952 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:40.953 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:40.955 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:42.457 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:42.460 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:42.461 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:42.463 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:42.463 INFO  [JcrInstaller.1] WatchedFolder.java:92   Watching folder 
/apps/tnwf/install.staging (priority 201)
00:08:42.965 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:42.967 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:42.968 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:42.970 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:44.473 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:44.475 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:44.476 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:44.478 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:44.478 INFO  [JcrInstaller.1] WatchedFolder.java:92   Watching folder 
/apps/tnwf/install.staging.dev (priority 202)
00:08:44.981 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:44.983 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:44.984 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:44.986 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:48.489 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:48.491 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:48.493 INFO  [JcrInstaller.1] TransientRepository.java:384 Session opened
00:08:48.495 INFO  [JcrInstaller.1] TransientRepository.java:423 Session closed
00:08:48.496 INFO  [JcrInstaller.1] JcrInstaller.java:550   Deleting 
WatchedFolder:/libs/tnwf/install.dev, path does not exist anymore
00:08:49.813 INFO  [main] TransientRepository.java:423  Session closed
00:08:49.814 INFO  [main] JcrInstaller.java:380 Deactivating Apache 
Sling JCR Installer
00:08:49.814 INFO  [JcrInstaller.1] JcrInstaller.java:296   Background thread 
JcrInstaller.1 done
00:08:49.816 INFO  [main] TransientRepository.java:423  Session closed
00:08:49.819 INFO  [main] TransientRepository.java:384  Session opened
00:08:49.962 INFO  [main] JcrInstaller.java:319 Activating Apache 
Sling JCR Installer
00:08:49.963 INFO  [JcrInstaller.2] JcrInstaller.java:218   Background thread 
JcrInstaller.2 starting
00:08:49.965 INFO  [JcrInstaller.2] TransientRepository.java:384 Session opened
00:08:49.965 INFO  [JcrInstaller.2] RootFolderListener.java:49 Watching /apps 
to detect potential changes in subfolders
00:08:49.966 INFO  [JcrInstaller.2] RootFolderListener.java:49 Watching /libs 
to detect potential changes in subfolders
00:08:49.967 INFO  [JcrInstaller.2] TransientRepository.java:384 Session opened
00:08:49.970 INFO  [JcrInstaller.2] TransientRepository.java:423 Session closed
00:08:49.973 INFO  [JcrInstaller.2] TransientRepository.java:384 Session opened
00:08:49.978 INFO  [JcrInstaller.2] TransientRepository.java:423 Session closed
00:08:49.980 INFO  [JcrInstaller.2] WatchedFolder.java:92  

[jira] [Resolved] (SLING-3218) enable a list of JSP taglib prefixes to be registered automatically

[Justin Edelson (JIRA)]

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

Justin Edelson resolved SLING-3218.
---

Resolution: Won't Fix

After further consideration, I think this is a bad idea as it would lead to the 
same JSP code not compiling across installations which had different 
configurations.

> enable a list of JSP taglib prefixes to be registered automatically
> ---
>
> Key: SLING-3218
> URL: https://issues.apache.org/jira/browse/SLING-3218
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Justin Edelson
> Attachments: SLING-3218.patch
>
>
> To avoid boilerplate JSP code, it should be possible to configure the JSP 
> compiler with a set of default prefixes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3217) Automatically expose SlingBindings object through EL

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-3217:
---

I forgot that this issue was never resolved. [~fmeschbe] would you care to 
revisit your comment? As I wrote above, I think the divergence between EL scope 
and scripting variables is acceptable (and, frankly) pre-existing.

> Automatically expose SlingBindings object through EL
> 
>
> Key: SLING-3217
> URL: https://issues.apache.org/jira/browse/SLING-3217
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Reporter: Justin Edelson
> Attachments: SLING-3217.patch
>
>
> JSP scripts need to use the  (or a subclass) in order 
> to expose the Sling Bindings objects (i.e. `resource`) for use in a JSP page. 
> This shouldn't be necessary if we provide a custom ELResolver.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-920) Sling Jenkins setup

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-920:
---

Updated sling-ide-1.6 build

* Checkout the tooling/ide directory straightaway, since we no longer need to 
build the tooling bundle
* Remove the extra step to build the tooling bundle
* Increase timeout to 15 minutes, to account for extra tests

> Sling Jenkins setup
> ---
>
> Key: SLING-920
> URL: https://issues.apache.org/jira/browse/SLING-920
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Bertrand Delacretaz
>
> Use this issue to record changes to the Hudson continuous environment setup 
> at http://hudson.zones.apache.org/hudson/view/Sling/



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Build failed in Jenkins: sling-oak-it-1.6 #36

[Apache Jenkins Server]

See 

--
[...truncated 136 lines...]
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.resourceresolver/1.0.7-SNAPSHOT/org.apache.sling.resourceresolver-1.0.7-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.auth.core/1.1.4/org.apache.sling.auth.core-1.1.4.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.engine/2.2.10/org.apache.sling.engine-2.2.10.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.auth.openid/1.0.3-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.auth.openid/1.0.3-SNAPSHOT/maven-metadata.xml
 (1016 B at 3.4 KB/sec)
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.auth.openid/1.0.3-SNAPSHOT/org.apache.sling.auth.openid-1.0.3-SNAPSHOT.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.auth.form/1.0.5-SNAPSHOT/maven-metadata.xml
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.auth.form/1.0.5-SNAPSHOT/org.apache.sling.auth.form-1.0.5-SNAPSHOT.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.auth.selector/1.0.5-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.auth.selector/1.0.5-SNAPSHOT/maven-metadata.xml
 (1018 B at 1.8 KB/sec)
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.auth.selector/1.0.5-SNAPSHOT/org.apache.sling.auth.selector-1.0.5-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.adapter/2.1.0/org.apache.sling.adapter-2.1.0.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.servlets.resolver/2.2.5-SNAPSHOT/maven-metadata.xml
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.servlets.resolver/2.2.5-SNAPSHOT/org.apache.sling.servlets.resolver-2.2.5-SNAPSHOT.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.servlets.get/2.1.5-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.servlets.get/2.1.5-SNAPSHOT/maven-metadata.xml
 (1009 B at 2.4 KB/sec)
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.servlets.get/2.1.5-SNAPSHOT/org.apache.sling.servlets.get-2.1.5-SNAPSHOT.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.servlets.post/2.3.3-SNAPSHOT/maven-metadata.xml
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.servlets.post/2.3.3-SNAPSHOT/org.apache.sling.servlets.post-2.3.3-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.jcr.contentloader/2.1.6/org.apache.sling.jcr.contentloader-2.1.6.jar
 

Build failed in Jenkins: sling-oak-it-1.6 » Apache Sling Launchpad Testing #36

[Apache Jenkins Server]

See 


--
[...truncated 103 lines...]
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/commons-lang/commons-lang/2.5/commons-lang-2.5.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/commons/commons-math/2.2/commons-math-2.2.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/geronimo/bundles/commons-httpclient/3.1_1/commons-httpclient-3.1_1.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.osgi/2.2.1-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.osgi/2.2.1-SNAPSHOT/maven-metadata.xml
 (1009 B at 1.3 KB/sec)
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.osgi/2.2.1-SNAPSHOT/org.apache.sling.commons.osgi-2.2.1-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.mime/2.1.4/org.apache.sling.commons.mime-2.1.4.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.classloader/1.3.0/org.apache.sling.commons.classloader-1.3.0.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.scheduler/2.4.3-SNAPSHOT/maven-metadata.xml
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.scheduler/2.4.3-SNAPSHOT/org.apache.sling.commons.scheduler-2.4.3-SNAPSHOT.jar
 to 

Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.commons.threads/3.2.1-SNAPSHOT/maven-metadata.xml
[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.commons.threads/3.2.1-SNAPSHOT/org.apache.sling.commons.threads-3.2.1-SNAPSHOT.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.discovery.api/1.0.0/org.apache.sling.discovery.api-1.0.0.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.discovery.support/1.0.0/org.apache.sling.discovery.support-1.0.0.jar
 to 

[INFO] Copying bundle from 
/home/jenkins/jenkins-slave/maven-repositories/1/org/apache/sling/org.apache.sling.discovery.impl/1.0.0/org.apache.sling.discovery.impl-1.0.0.jar
 to 

Downloading: 
http://repository.apache.org/snap

[VOTE][RESULT] Release Apache Sling Tooling Support Install 1.0.0

[Robert Munteanu]

Hi,

The vote has passed with the following result :

+1 (binding): Bertrand Delacretaz, Carsten Ziegeler, Robert Munteanu

I will copy this release to the Sling dist directory and promote the
artifacts to the central Maven repository.

Robert

Re: [VOTE] Release Apache Sling Tooling Support Install 1.0.0

[Robert Munteanu]

To solve this conundrum, I am able to recast my vote as binding, so here goes:

+1 (binding).

On Mon, May 26, 2014 at 5:42 PM, Robert Munteanu  wrote:
> Sorry to nag, but we're still missing one binding vote and this is one
> of the must-have items for the Sling IDE tooling 1.0 release.
>
> Robert
>
> On Mon, May 12, 2014 at 5:25 PM, Robert Munteanu  wrote:
>> For completeness, here's my +1 ( non-binding )
>>
>> On Tue, May 6, 2014 at 12:26 PM, Robert Munteanu  wrote:
>>> We're missing one binding vote, can someone else please take a look?
>>>
>>> Robert
>>>
>>> On Tue, May 6, 2014 at 9:16 AM, Carsten Ziegeler  
>>> wrote:
 +1


 2014-05-05 17:16 GMT+02:00 Bertrand Delacretaz :

> Hi,
>
> On Fri, May 2, 2014 at 2:32 PM, Robert Munteanu 
> wrote:
> ...
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1056/
> ...
>
> +1, checked signatures, build and svn tag of
>
> MD5
> (./org.apache.sling.tooling.support.install/1.0.0/org.apache.sling.tooling.support.install-1.0.0-source-release.zip)
> = ab3ea7fdb9e874f4a5b8f0562cb7afbd
>
> -Bertrand
>



 --
 Carsten Ziegeler
 cziege...@apache.org

Jenkins build is back to stable : sling-trunk-1.6 #2147

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2147

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #523

[Apache Jenkins Server]

See 

[jira] [Updated] (SLING-3499) Support custom annotations with Sling Models

[Justin Edelson (JIRA)]

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

Justin Edelson updated SLING-3499:
--

Fix Version/s: Sling Models Implementation 1.0.0

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
> Fix For: Sling Models Implementation 1.0.6
>
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3499) Support custom annotations with Sling Models

[Justin Edelson (JIRA)]

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

Justin Edelson resolved SLING-3499.
---

Resolution: Fixed
  Assignee: Justin Edelson

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
>Assignee: Justin Edelson
> Fix For: Sling Models Implementation 1.0.6
>
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3499) Support custom annotations with Sling Models

[Justin Edelson (JIRA)]

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

Justin Edelson updated SLING-3499:
--

Fix Version/s: (was: Sling Models Implementation 1.0.0)
   Sling Models Implementation 1.0.6

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
> Fix For: Sling Models Implementation 1.0.6
>
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3499) Support custom annotations with Sling Models

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-3499:
---

OK. I moved that along. Commited in r1600469.

[~kwin] any chance you feel like submitting a patch for the documentation?

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3031) [Tooling] add whitelabel support for slingclipse

[Robert Munteanu (JIRA)]

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

Robert Munteanu resolved SLING-3031.


Resolution: Fixed

* http://svn.apache.org/viewvc?view=revision&revision=1600470  - allow 
overriding the property page to show
* http://svn.apache.org/viewvc?view=revision&revision=1600471 - add generic 
server icon for the launch configurations
* http://svn.apache.org/viewvc?view=revision&revision=1600472 - more neutral 
wording for the bundle/content modules
* http://svn.apache.org/viewvc?view=revision&revision=1600474  - whitelabel 
support for views
* http://svn.apache.org/viewvc?view=revision&revision=1600476 - allow reuse of 
the import wizards
* http://svn.apache.org/viewvc?view=revision&revision=1600477 - enhance and 
consistently reuse the Whitelabel support class in Java code
* http://svn.apache.org/viewvc?view=revision&revision=1600478 - whitelabel 
support for the console factory

> [Tooling] add whitelabel support for slingclipse
> 
>
> Key: SLING-3031
> URL: https://issues.apache.org/jira/browse/SLING-3031
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> For the slingclipse plugin, at certain locations, it should be possible to 
> 'brand' the plugins. Eg add custom icons, labels etc



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (SLING-3592) Remove embedded bundle archetype in favour of released version

[Robert Munteanu (JIRA)]

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

Robert Munteanu reassigned SLING-3592:
--

Assignee: Robert Munteanu

> Remove embedded bundle archetype in favour of released version
> --
>
> Key: SLING-3592
> URL: https://issues.apache.org/jira/browse/SLING-3592
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> The vote for the sling-bundle-archetype 1.0.2 is complete, and we should:
> * remove the embedded archetype we package
> * allow usage of versions >= 1.0.2 in our wizard
> I think we can safely assume that the user has access to Maven Central, usage 
> of the archetype won't work otherwise.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3612) Provide a m2e project configurator for packaging "bundle"

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-3612:


I don't think it does any major harm, but basically it's unexpected. Also, we 
enable the validation builder since we have our own validator, and that may not 
be what the user wants.

Isn't it possible for the configurator to check for the maven-sling-plugin 
instead of the maven-bundle-plugin? Or is that decided by the primary 
configurator?

> Provide a m2e project configurator for packaging "bundle"
> -
>
> Key: SLING-3612
> URL: https://issues.apache.org/jira/browse/SLING-3612
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> That configurator should automatically setup the project with the correct 
> facets (to make it possible to deploy via Sling IDE Tools). That configurator 
> would e.g. be triggered, when a new project is imported into the IDE (e.g. 
> from  an existing local Maven project, or via Subclipe/Subversive/eGit)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (SLING-3612) Provide a m2e project configurator for packaging "bundle"

[Konrad Windszus (JIRA)]

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

Konrad Windszus edited comment on SLING-3612 at 6/4/14 7:12 PM:


You are right, that if now the plugin is installed all bundle projects would 
end up with the sling facet. I am not sure, how to check for the 
maven-sling-plugin, but probably I can figure out something. Does the Sling 
Facet do any harm? Also I am not sure that maven-sling-plugin is the right 
criteria, because even that could be used for non-Sling bundles (because it 
basically deploys via the Apache Felix Webconsole). 


was (Author: kwin):
You are right, that if now the plugin is installed all bundle projects would 
end up with the sling facet. I am not sure, how to check for the 
maven-sling-plugin, but probably I can figure out something. Does the Sling 
Facet do any harm?

> Provide a m2e project configurator for packaging "bundle"
> -
>
> Key: SLING-3612
> URL: https://issues.apache.org/jira/browse/SLING-3612
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> That configurator should automatically setup the project with the correct 
> facets (to make it possible to deploy via Sling IDE Tools). That configurator 
> would e.g. be triggered, when a new project is imported into the IDE (e.g. 
> from  an existing local Maven project, or via Subclipe/Subversive/eGit)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3612) Provide a m2e project configurator for packaging "bundle"

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-3612:


You are right, that if now the plugin is installed all bundle projects would 
end up with the sling facet. I am not sure, how to check for the 
maven-sling-plugin, but probably I can figure out something. Does the Sling 
Facet do any harm?

> Provide a m2e project configurator for packaging "bundle"
> -
>
> Key: SLING-3612
> URL: https://issues.apache.org/jira/browse/SLING-3612
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> That configurator should automatically setup the project with the correct 
> facets (to make it possible to deploy via Sling IDE Tools). That configurator 
> would e.g. be triggered, when a new project is imported into the IDE (e.g. 
> from  an existing local Maven project, or via Subclipe/Subversive/eGit)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3612) Provide a m2e project configurator for packaging "bundle"

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-3612:


[~kwin] - thanks for the pull request. I have question about the mapping 
though. It seems to look after the maven-bundle-plugin. Doesn't this mean that 
all bundle projects would be configured with the sling.bundle facet? I think 
that's too broad.

Is it viable to bind the configurator to the maven-sling-plugin instead?

> Provide a m2e project configurator for packaging "bundle"
> -
>
> Key: SLING-3612
> URL: https://issues.apache.org/jira/browse/SLING-3612
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> That configurator should automatically setup the project with the correct 
> facets (to make it possible to deploy via Sling IDE Tools). That configurator 
> would e.g. be triggered, when a new project is imported into the IDE (e.g. 
> from  an existing local Maven project, or via Subclipe/Subversive/eGit)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[GitHub] sling pull request: SLING-3612, add m2 project configuration for p...

[kwin]

GitHub user kwin opened a pull request:

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

SLING-3612, add m2 project configuration for packaging bundle (secondary to 
tycho)

Add project configurator which adds the Sling Bundle Facets automatically 
for all Maven Projects with packaging "bundle"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kwin/sling SLING-3612-m2e-bundle-lifecycle

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #18


commit 6ef5234452a46267ed1da67ad1bd799703e735f3
Author: Konrad Windszus 
Date:   2014-06-04T18:06:25Z

SLING-3612, add m2 project configuration for packaging bundle (secondary
to tycho)




---
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] [Commented] (SLING-3612) Provide a m2e project configurator for packaging "bundle"

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on SLING-3612:
---

GitHub user kwin opened a pull request:

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

SLING-3612, add m2 project configuration for packaging bundle (secondary to 
tycho)

Add project configurator which adds the Sling Bundle Facets automatically 
for all Maven Projects with packaging "bundle"

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/kwin/sling SLING-3612-m2e-bundle-lifecycle

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/sling/pull/18.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #18


commit 6ef5234452a46267ed1da67ad1bd799703e735f3
Author: Konrad Windszus 
Date:   2014-06-04T18:06:25Z

SLING-3612, add m2 project configuration for packaging bundle (secondary
to tycho)




> Provide a m2e project configurator for packaging "bundle"
> -
>
> Key: SLING-3612
> URL: https://issues.apache.org/jira/browse/SLING-3612
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Konrad Windszus
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> That configurator should automatically setup the project with the correct 
> facets (to make it possible to deploy via Sling IDE Tools). That configurator 
> would e.g. be triggered, when a new project is imported into the IDE (e.g. 
> from  an existing local Maven project, or via Subclipe/Subversive/eGit)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build became unstable: sling-trunk-1.7 #522

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 #2146

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2146

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #522

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-3499) Support custom annotations with Sling Models

[Justin Edelson (JIRA)]

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

Justin Edelson commented on SLING-3499:
---

[~kwin] the only thing left to be done is that I want to write a test or two 
for the default capability. I should be able to do that in the next week. Just 
been busy.

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is unstable: sling-oak-it-1.6 #35

[Apache Jenkins Server]

See 

Jenkins build is unstable: sling-oak-it-1.6 » Apache Sling Launchpad Testing #35

[Apache Jenkins Server]

See 

[jira] [Commented] (SLING-3499) Support custom annotations with Sling Models

[Konrad Windszus (JIRA)]

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

Konrad Windszus commented on SLING-3499:


Hi [~justinedelson], any progress on this? Do you need more information from me?

> Support custom annotations with Sling Models
> 
>
> Key: SLING-3499
> URL: https://issues.apache.org/jira/browse/SLING-3499
> Project: Sling
>  Issue Type: New Feature
>  Components: Extensions
>Affects Versions: Sling Models API 1.0.0, Sling Models Implementation 1.0.2
>Reporter: Konrad Windszus
>
> To support custom annotations the API needs to be extended. 
> The reasons for custom annotations are listed in 
> http://www.mail-archive.com/dev%40sling.apache.org/msg27918.html. Also it is 
> much more comfortable for developers, since they can use code completion in 
> the IDE to see which options are available for each injector-specific 
> annotation, apart from that it is less code to write (instead of multiple 
> annotations on one field/method I would only have to write one annotation 
> with some attributes).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Assigned] (SLING-3638) Add 'upload (full republish)' action to module context menu in wst server view

[Stefan Egli (JIRA)]

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

Stefan Egli reassigned SLING-3638:
--

Assignee: Stefan Egli

> Add 'upload (full republish)' action to module context menu in wst server view
> --
>
> Key: SLING-3638
> URL: https://issues.apache.org/jira/browse/SLING-3638
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> (tentatively marking this as 1.0.0)
> It might be useful to have a 'upload to repository/full republish to server' 
> action on a content module in the wst server. 
> Currently there is no intuitive way of 'republishing one/all module(s)'. The 
> way to do this is to use 'export' (which is going to be renamed to 'upload') 
> in the Project's context menu. This might be a bit hidden and adding a second 
> way in the wst server's view might be helpful.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is back to stable : sling-trunk-1.6 #2145

[Apache Jenkins Server]

See 

[jira] [Updated] (SLING-3031) [Tooling] add whitelabel support for slingclipse

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3031:
---

Assignee: Robert Munteanu  (was: Stefan Egli)

> [Tooling] add whitelabel support for slingclipse
> 
>
> Key: SLING-3031
> URL: https://issues.apache.org/jira/browse/SLING-3031
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> For the slingclipse plugin, at certain locations, it should be possible to 
> 'brand' the plugins. Eg add custom icons, labels etc



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3643) JCR Properties view property type display bug

[Stefan Egli (JIRA)]

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

Stefan Egli resolved SLING-3643.


Resolution: Fixed

fixed

> JCR Properties view property type display bug
> -
>
> Key: SLING-3643
> URL: https://issues.apache.org/jira/browse/SLING-3643
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> For a newly created property the type selection does not work correctly.
> create a new property and give it a name
> select the property type
> click the value field -> property type filed is empty again



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (SLING-3643) JCR Properties view property type display bug

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3643:
--

 Summary: JCR Properties view property type display bug
 Key: SLING-3643
 URL: https://issues.apache.org/jira/browse/SLING-3643
 Project: Sling
  Issue Type: Task
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli
Priority: Minor
 Fix For: Sling Eclipse IDE 1.0.0


For a newly created property the type selection does not work correctly.

create a new property and give it a name
select the property type
click the value field -> property type filed is empty again



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3635) [Javascript] Optimization level for byte code generator in Rhino should be configurable

[Marius-Andrei Danila (JIRA)]

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

Marius-Andrei Danila updated SLING-3635:


Attachment: SLING-3635.diff

> [Javascript] Optimization level for byte code generator in Rhino should be 
> configurable
> ---
>
> Key: SLING-3635
> URL: https://issues.apache.org/jira/browse/SLING-3635
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting JavaScript 2.0.12
>Reporter: Marius-Andrei Danila
> Attachments: SLING-3635.diff
>
>
> The Rhino Javascript engine allows you to choose the level of optimization 
> for the generated byte code or it lets you select whether the scripts should 
> be run in interpreted mode [0].
> Currently, there is no way to configure this. By default, Rhino compiles 
> scripts into JVM classes using the optimization level 0.
> This option should be configurable, and the default value for this 
> configuration should be "-1" - meaning run scripts in interpreted mode. Since 
> we are not caching script compilation artifacts, the interpreted mode gives 
> the best performance for short-running scripts.
> The attached patch implements this improvement by exposing a configuration 
> entry in the Rhino Javascript engine factory component.
> [0] 
> https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Optimization



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (SLING-3635) [Javascript] Optimization level for byte code generator in Rhino should be configurable

[Marius-Andrei Danila (JIRA)]

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

Marius-Andrei Danila updated SLING-3635:


Attachment: (was: SLING-3635.patch)

> [Javascript] Optimization level for byte code generator in Rhino should be 
> configurable
> ---
>
> Key: SLING-3635
> URL: https://issues.apache.org/jira/browse/SLING-3635
> Project: Sling
>  Issue Type: Improvement
>  Components: Scripting
>Affects Versions: Scripting JavaScript 2.0.12
>Reporter: Marius-Andrei Danila
> Attachments: SLING-3635.diff
>
>
> The Rhino Javascript engine allows you to choose the level of optimization 
> for the generated byte code or it lets you select whether the scripts should 
> be run in interpreted mode [0].
> Currently, there is no way to configure this. By default, Rhino compiles 
> scripts into JVM classes using the optimization level 0.
> This option should be configurable, and the default value for this 
> configuration should be "-1" - meaning run scripts in interpreted mode. Since 
> we are not caching script compilation artifacts, the interpreted mode gives 
> the best performance for short-running scripts.
> The attached patch implements this improvement by exposing a configuration 
> entry in the Rhino Javascript engine factory component.
> [0] 
> https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino/Optimization



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2145

[Apache Jenkins Server]

See 

[jira] [Resolved] (SLING-3642) Support modifying of DataSource properties at runtime without restart

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra resolved SLING-3642.


Resolution: Fixed

Added support in http://svn.apache.org/r1600199

> Support modifying of DataSource properties at runtime without restart
> -
>
> Key: SLING-3642
> URL: https://issues.apache.org/jira/browse/SLING-3642
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: DataSource Provider 0.0.2
>
>
> Tomcat JDBC Pool supports changing the connection pool properties at runtime 
> also. Sling DataSource provider should support that and avoid deregistration 
> of DataSource service as much as possible



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3637) Create connection pool lazily in DataSource Provider bundle

[Chetan Mehrotra (JIRA)]

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

Chetan Mehrotra resolved SLING-3637.


Resolution: Fixed

Added support in http://svn.apache.org/r1600198

> Create connection pool lazily in DataSource Provider bundle
> ---
>
> Key: SLING-3637
> URL: https://issues.apache.org/jira/browse/SLING-3637
> Project: Sling
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Chetan Mehrotra
>Assignee: Chetan Mehrotra
> Fix For: DataSource Provider 0.0.2
>
>
> DataSource provider bundle currently creates and initializes the connection 
> pool upon activation itself. Instead the connection pool should be 
> initialized lazily as that would 
> # Move the costly init operation out of main thread
> # Allow looking up of Driver class from bundle which have yet not started (at 
> least in current start level)



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

[Apache Jenkins Server]

See 

Jenkins build is back to stable : sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #521

[Apache Jenkins Server]

See 

[jira] [Updated] (SLING-3609) StringIndexOutOfBoundsException with empty {Binary} property

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3609:
---

Fix Version/s: Sling Eclipse IDE 1.0.0

a candidate for 1.0.0?

> StringIndexOutOfBoundsException with empty {Binary} property
> 
>
> Key: SLING-3609
> URL: https://issues.apache.org/jira/browse/SLING-3609
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: sling3609-1.0(1).zip
>
>
> When importing an 'empty' binary property - which gets serialized by vault as 
> shown below - an StringIndexOutOfBoundsException occurs:
> {code}abin="{Binary}"{code}
> {code}java.lang.StringIndexOutOfBoundsException: String index out of range: 0
>   at java.lang.String.charAt(String.java:686)
>   at 
> org.apache.sling.ide.impl.vlt.serialization.ContentXmlHandler$TypeHint.parsePossiblyTypedValue(ContentXmlHandler.java:223)
>   at 
> org.apache.sling.ide.impl.vlt.serialization.ContentXmlHandler.startElement(ContentXmlHandler.java:67)
>   at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:504)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:401)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2763)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140)
>   at 
> com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:513)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:815)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:744)
>   at 
> com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:128)
>   at 
> com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1208)
>   at 
> com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:543)
>   at javax.xml.parsers.SAXParser.parse(SAXParser.java:395)
>   at javax.xml.parsers.SAXParser.parse(SAXParser.java:198)
>   at 
> org.apache.sling.ide.impl.vlt.serialization.VltSerializationManager.readSerializationData(VltSerializationManager.java:232)
> {code}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3636) Out of date "Getting and Building Sling"

[Alexander Muthmann (JIRA)]

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

Alexander Muthmann commented on SLING-3636:
---

ah ok, no i didn't encounter any problems.

> Out of date "Getting and Building Sling"
> 
>
> Key: SLING-3636
> URL: https://issues.apache.org/jira/browse/SLING-3636
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Alexander Muthmann
>Assignee: Oliver Lietz
>Priority: Minor
>
> If you follow the instructions from Getting and Building Sling 
> (http://sling.apache.org/documentation/development/getting-and-building-sling.html)
>  you may find the following issue:
> The requirements lists maven 3.0.2 as required but the parent mom requires 
> 3.0.4.
> Furthermore it might be helpful to have a note which describes the 
> possibility to use the parentpom's sling.java.version property to build Java 
> 7 code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3636) Out of date "Getting and Building Sling"

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-3636:
-

Setting {{sling.java.version}} to the version of your JDK is not needed (and 
wanted). You can build with 7 and run on 5 or 6, but there are bundles which 
use newer language features and do not longer support 5. Did you encounter any 
problems?

> Out of date "Getting and Building Sling"
> 
>
> Key: SLING-3636
> URL: https://issues.apache.org/jira/browse/SLING-3636
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Alexander Muthmann
>Assignee: Oliver Lietz
>Priority: Minor
>
> If you follow the instructions from Getting and Building Sling 
> (http://sling.apache.org/documentation/development/getting-and-building-sling.html)
>  you may find the following issue:
> The requirements lists maven 3.0.2 as required but the parent mom requires 
> 3.0.4.
> Furthermore it might be helpful to have a note which describes the 
> possibility to use the parentpom's sling.java.version property to build Java 
> 7 code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3636) Out of date "Getting and Building Sling"

[Alexander Muthmann (JIRA)]

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

Alexander Muthmann commented on SLING-3636:
---

probably an additional information, that the user building sling should adjust 
the setting according to his jdk would be an idea, but that's fine, thank you!

> Out of date "Getting and Building Sling"
> 
>
> Key: SLING-3636
> URL: https://issues.apache.org/jira/browse/SLING-3636
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Alexander Muthmann
>Assignee: Oliver Lietz
>Priority: Minor
>
> If you follow the instructions from Getting and Building Sling 
> (http://sling.apache.org/documentation/development/getting-and-building-sling.html)
>  you may find the following issue:
> The requirements lists maven 3.0.2 as required but the parent mom requires 
> 3.0.4.
> Furthermore it might be helpful to have a note which describes the 
> possibility to use the parentpom's sling.java.version property to build Java 
> 7 code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (SLING-3636) Out of date "Getting and Building Sling"

[Oliver Lietz (JIRA)]

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

Oliver Lietz commented on SLING-3636:
-

The {{sling.java.version}} property is used for the [{{source}} and {{target}} 
properties of Maven Compiler 
Plugin|http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html],
 Animal Sniffer Maven Plugin and for the 
{{Bundle-RequiredExecutionEnvironment}} manifest header.

Is this description sufficient, [~amuthmann]? First point is fixed in r1600116.

> Out of date "Getting and Building Sling"
> 
>
> Key: SLING-3636
> URL: https://issues.apache.org/jira/browse/SLING-3636
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Alexander Muthmann
>Assignee: Oliver Lietz
>Priority: Minor
>
> If you follow the instructions from Getting and Building Sling 
> (http://sling.apache.org/documentation/development/getting-and-building-sling.html)
>  you may find the following issue:
> The requirements lists maven 3.0.2 as required but the parent mom requires 
> 3.0.4.
> Furthermore it might be helpful to have a note which describes the 
> possibility to use the parentpom's sling.java.version property to build Java 
> 7 code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

[Apache Jenkins Server]

See 

[jira] [Assigned] (SLING-3636) Out of date "Getting and Building Sling"

[Oliver Lietz (JIRA)]

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

Oliver Lietz reassigned SLING-3636:
---

Assignee: Oliver Lietz

> Out of date "Getting and Building Sling"
> 
>
> Key: SLING-3636
> URL: https://issues.apache.org/jira/browse/SLING-3636
> Project: Sling
>  Issue Type: Bug
>  Components: Documentation
>Reporter: Alexander Muthmann
>Assignee: Oliver Lietz
>Priority: Minor
>
> If you follow the instructions from Getting and Building Sling 
> (http://sling.apache.org/documentation/development/getting-and-building-sling.html)
>  you may find the following issue:
> The requirements lists maven 3.0.2 as required but the parent mom requires 
> 3.0.4.
> Furthermore it might be helpful to have a note which describes the 
> possibility to use the parentpom's sling.java.version property to build Java 
> 7 code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Launchpad Application Builder #2144

[Apache Jenkins Server]

See 

Jenkins build is still unstable: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #2144

[Apache Jenkins Server]

See 

[jira] [Updated] (SLING-3641) Refine 'link with editor' behavior with properties view(s)

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3641:
---

Fix Version/s: (was: Sling Eclipse IDE 1.0.0)
   Sling Eclipse IDE 1.0.2

For 1.0.0: moved the non-intuitive behavior of bringing the properties view to 
top when 'link with editor' is checked in the project explorer - to a new, 
explicit 'sync' toggle in the JCR Properties view.

This can be reviewed for 1.0.2 together with the merge of SLING-3628

> Refine 'link with editor' behavior with properties view(s)
> --
>
> Key: SLING-3641
> URL: https://issues.apache.org/jira/browse/SLING-3641
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Currently there is code that automatically brings the standard eclipse 
> Properties view to top, when 'link with editor' is enabled eg in the Project 
> Explorer.
> This might not necessarily be such a good idea, as it doesn't follow the 
> standard UI behavior.
> Instead we should have a 'link with editor and selection' toggle button in 
> the JCR Properties view itself, and have that enabled by default maybe.
> Later, when we merge the JCR Properties view into the standard Eclipse 
> Properties view (SLING-3628), we can review this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

[Apache Jenkins Server]

See 

[jira] [Created] (SLING-3642) Support modifying of DataSource properties at runtime without restart

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created SLING-3642:
--

 Summary: Support modifying of DataSource properties at runtime 
without restart
 Key: SLING-3642
 URL: https://issues.apache.org/jira/browse/SLING-3642
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
 Fix For: DataSource Provider 0.0.2


Tomcat JDBC Pool supports changing the connection pool properties at runtime 
also. Sling DataSource provider should support that and avoid deregistration of 
DataSource service as much as possible



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Jenkins build is back to normal : sling-trunk-1.7 » Apache Sling Launchpad Application Builder #520

[Apache Jenkins Server]

See 

Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Resource-Based Discovery Service #520

[Apache Jenkins Server]

See 

[jira] [Created] (SLING-3641) Refine 'link with editor' behavior with properties view(s)

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3641:
--

 Summary: Refine 'link with editor' behavior with properties view(s)
 Key: SLING-3641
 URL: https://issues.apache.org/jira/browse/SLING-3641
 Project: Sling
  Issue Type: Task
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli
 Fix For: Sling Eclipse IDE 1.0.0


Currently there is code that automatically brings the standard eclipse 
Properties view to top, when 'link with editor' is enabled eg in the Project 
Explorer.

This might not necessarily be such a good idea, as it doesn't follow the 
standard UI behavior.

Instead we should have a 'link with editor and selection' toggle button in the 
JCR Properties view itself, and have that enabled by default maybe.

Later, when we merge the JCR Properties view into the standard Eclipse 
Properties view (SLING-3628), we can review this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (SLING-3640) Creation of a non-nt:folder folder or partially-aggregated child does not correctly refresh

[Stefan Egli (JIRA)]

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

Stefan Egli resolved SLING-3640.


Resolution: Fixed

fixed

> Creation of a non-nt:folder folder or partially-aggregated child does not 
> correctly refresh
> ---
>
> Key: SLING-3640
> URL: https://issues.apache.org/jira/browse/SLING-3640
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Creating one of the following two child node types
>  * folder other than nt:folder, eg sling:Folder
>  * child node which results in partial aggregation serialization, eg 
> nt:unstructured
> first creates a plain (eclipse) IFolder, which results in the Project 
> Explorer to show it as 
> {code}
> newfolder [nt:folder]
> {code}
> and only then adds the newfolder/.content.xml - which does not correctly 
> refresh in all cases.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (SLING-3640) Creation of a non-nt:folder folder or partially-aggregated child does not correctly refresh

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3640:
--

 Summary: Creation of a non-nt:folder folder or 
partially-aggregated child does not correctly refresh
 Key: SLING-3640
 URL: https://issues.apache.org/jira/browse/SLING-3640
 Project: Sling
  Issue Type: Bug
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli
 Fix For: Sling Eclipse IDE 1.0.0


Creating one of the following two child node types

 * folder other than nt:folder, eg sling:Folder
 * child node which results in partial aggregation serialization, eg 
nt:unstructured

first creates a plain (eclipse) IFolder, which results in the Project Explorer 
to show it as 
{code}
newfolder [nt:folder]
{code}
and only then adds the newfolder/.content.xml - which does not correctly 
refresh in all cases.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Application Builder #519

[Carsten Ziegeler]

Thanks Robert

Carsten


2014-06-04 10:17 GMT+02:00 Robert Munteanu :

> On Wed, Jun 4, 2014 at 10:43 AM, Apache Jenkins Server
>  wrote:
> > See <
> https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.launchpad/519/changes
> >
> > Downloading:
> http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/maven-metadata.xml
> > Downloading:
> http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/org.apache.sling.installer.core-3.5.3.SNAPSHOT.pom
> > [WARNING] The POM for
> org.apache.sling:org.apache.sling.installer.core:jar:3.5.3.SNAPSHOT is
> missing, no dependency information available
>
> The dependency to org.apache.sling.installer.core should be
> 3.5.3-SNAPSHOT . Fixed in http://svn.apache.org/r1599972
>
> Robert
>



-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Created] (SLING-3639) Changing node types to/from sling:Folder within .content.xml fails

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3639:
--

 Summary: Changing node types to/from sling:Folder within 
.content.xml fails
 Key: SLING-3639
 URL: https://issues.apache.org/jira/browse/SLING-3639
 Project: Sling
  Issue Type: Bug
  Components: IDE
Reporter: Stefan Egli
Assignee: Stefan Egli
 Fix For: Sling Eclipse IDE 1.0.0


When changing the type of a node serialized into a .content.xml to/from 
sling:Folder, various exceptions occur.

This ticket is to have a reference between the various bugfixes related to this.

An earlier fix likely related to this is : http://svn.apache.org/r156

Consider the following structure:
{code}
grandparent [nt:unstructured]
\- parent [nt:unstructured]
 |- child1 [nt:unstructured]
 \- child2 [nt:unstructured]
{code}

initially the structure is serialized into one:
{code}
grandparent/.content.xml
{code}

If child2 is changed to sling:Folder, the content is published and re-imported, 
the underlying vault serialization looks as follows:

{code}
grandparent/.content.xml
grandparent/parent/child2/.content.xml
{code}

Changing child2 back to nt:unstructured results in:

{code}
[June 4, 2014 10:52:04 AM CEST] AddOrUpdateNodeCommand -> 
/content/okapp/grandparent/parent : JcrResult[ success:true] (53 ms)
[June 4, 2014 10:52:39 AM CEST] AddOrUpdateNodeCommand -> 
/content/okapp/grandparent/parent/child2 : JcrResult[ success:false, exception: 
org.apache.sling.ide.transport.RepositoryException - 
javax.jcr.nodetype.ConstraintViolationException: node 
/content/okapp/grandparent/parent/child2: no applicable definition found in 
parent node's node type] (48 ms)
org.apache.sling.ide.transport.RepositoryException: 
javax.jcr.nodetype.ConstraintViolationException: node 
/content/okapp/grandparent/parent/child2: no applicable definition found in 
parent node's node type
at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:62)
at 
org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:43)
at 
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.execute(SlingLaunchpadBehaviour.java:364)
at 
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishContentModule(SlingLaunchpadBehaviour.java:330)
at 
org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:182)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
at 
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at 
org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3154)
at 
org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: javax.jcr.nodetype.ConstraintViolationException: node 
/content/okapp/grandparent/parent/child2: no applicable definition found in 
parent node's node type
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
at 
org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:69)
at 
org.apache.jackrabbit.spi2dav.ExceptionConverter.generate(ExceptionConverter.java:51)
at 
org.apache.jackrabbit.spi2davex.RepositoryServiceImpl$BatchImpl.start(RepositoryServiceImpl.java:611)
at 
org.apache.jackrabbit.spi2davex.RepositoryServiceImpl$BatchImpl.access$600(RepositoryServiceImpl.java:547)
at 
org.apache.jackrabbit.spi2davex.RepositoryServiceImpl.submit(RepositoryServiceImpl.java:452)
at 
org.apache.jackrabbit.jcr2spi.WorkspaceManager$OperationVisitorImpl.execute(WorkspaceManager.java:858)
at 
org.apache.jackrabbit.jcr2spi.WorkspaceManager$OperationVisitorImpl.access$500(WorkspaceManager.java:817)
at 
org.apache.jackrabbit.jcr2spi.WorkspaceManager.execute(WorkspaceManager.java:620)
at 
org.apache.jackrabbit.jcr2spi.state.SessionItemStateManager.save(SessionItemStateManager.java:139)
at org.apache.jackrabbit.jcr2spi.ItemImpl.save(ItemImpl.java:250)
at org.apache.jackrabbit.jcr2spi.SessionImpl.save(SessionImpl.java:333)
at 
org.apache.sling.ide.impl.vlt.Ad

Build failed in Jenkins: sling-trunk-1.6 #2143

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Use latest installer snapshots during release

[cziegeler] Use latest snapshots for integration tests

[cziegeler] [maven-release-plugin] prepare for next development iteration

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.installer.factory.configuration-1.0.14

[cziegeler] [maven-release-plugin] prepare for next development iteration

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.installer.core-3.5.2

--
[...truncated 83626 lines...]
[INFO] Sling Launchpad Standalone Archetype .. SUCCESS [26.771s]
[INFO] Sling Launchpad Webapp Archetype .. SUCCESS [21.688s]
[INFO] Sling Initial Content Archetype ... SUCCESS [10.298s]
[INFO] Sling Servlet Archetype ... SUCCESS [12.710s]
[INFO] Sling Bundle Archetype  SUCCESS [12.691s]
[INFO] Sling JCRInstall Bundle Archetype . SUCCESS [12.142s]
[INFO] Sling Taglib Archetype  SUCCESS [7.382s]
[INFO] Apache Sling API .. SUCCESS [21.650s]
[INFO] Apache Sling Resource Resolver  SUCCESS [17.521s]
[INFO] Apache Sling System Bundle Extension: Java Transaction API  SUCCESS 
[7.683s]
[INFO] Apache Sling System Bundle Extension: XML APIs  SUCCESS [7.947s]
[INFO] Apache Sling System Bundle Extension: Activation API  SUCCESS [8.437s]
[INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [8.229s]
[INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [18.889s]
[INFO] Apache Sling Commons Java Compiler  SUCCESS [10.636s]
[INFO] Apache Sling JSON Library . SUCCESS [8.785s]
[INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [45.456s]
[INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [7.605s]
[INFO] Apache Sling MIME type mapping support  SUCCESS [9.304s]
[INFO] Apache Sling Commons OSGi support . SUCCESS [8.691s]
[INFO] Apache Sling Scheduler Support  SUCCESS [7.817s]
[INFO] Apache Sling Testing Utilities  SUCCESS [1:07.977s]
[INFO] Apache Sling Thread Dumper  SUCCESS [7.766s]
[INFO] Apache Sling Thread Support ... SUCCESS [9.327s]
[INFO] Apache Sling Authentication Service ... SUCCESS [9.920s]
[INFO] Apache Sling OpenID Authentication  SUCCESS [11.156s]
[INFO] Apache Sling Form Based Authentication Handler  SUCCESS [15.538s]
[INFO] Apache Sling Authentication Selector .. SUCCESS [9.124s]
[INFO] Apache Sling Engine Implementation  SUCCESS [27.681s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [6.273s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [12.057s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [8.798s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [9.807s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [14.890s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [8.802s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[8.237s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [8.113s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [8.503s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [1:10.559s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [8.892s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [9.596s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [8.936s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [6.403s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [9.475s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [51.722s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [10.267s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [9.682s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [14.778s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [8.421s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [8.779s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [14.892s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [41.115s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [20.582s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [7.634s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [9.565s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [6.685s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [6.225s]
[

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

[Apache Jenkins Server]

See 

Changes:

[cziegeler] Use latest installer snapshots during release

[cziegeler] Use latest snapshots for integration tests

[cziegeler] [maven-release-plugin] prepare for next development iteration

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.installer.factory.configuration-1.0.14

[cziegeler] [maven-release-plugin] prepare for next development iteration

[cziegeler] [maven-release-plugin] prepare release 
org.apache.sling.installer.core-3.5.2

--
[...truncated 32182 lines...]
[INFO] Sling Launchpad Standalone Archetype .. SUCCESS [23.753s]
[INFO] Sling Launchpad Webapp Archetype .. SUCCESS [16.874s]
[INFO] Sling Initial Content Archetype ... SUCCESS [11.721s]
[INFO] Sling Servlet Archetype ... SUCCESS [12.914s]
[INFO] Sling Bundle Archetype  SUCCESS [15.219s]
[INFO] Sling JCRInstall Bundle Archetype . SUCCESS [14.362s]
[INFO] Sling Taglib Archetype  SUCCESS [7.729s]
[INFO] Apache Sling API .. SUCCESS [20.989s]
[INFO] Apache Sling Resource Resolver  SUCCESS [15.908s]
[INFO] Apache Sling System Bundle Extension: Java Transaction API  SUCCESS 
[9.755s]
[INFO] Apache Sling System Bundle Extension: XML APIs  SUCCESS [6.455s]
[INFO] Apache Sling System Bundle Extension: Activation API  SUCCESS [8.608s]
[INFO] Apache Sling System Bundle Extension: WS APIs . SUCCESS [9.394s]
[INFO] Apache Sling Dynamic Class Loader Support . SUCCESS [19.347s]
[INFO] Apache Sling Commons Java Compiler  SUCCESS [9.084s]
[INFO] Apache Sling JSON Library . SUCCESS [14.425s]
[INFO] Apache Sling SLF4J Implementation (Logback) ... SUCCESS [43.359s]
[INFO] Apache Sling OSGi LogService Implementation ... SUCCESS [9.898s]
[INFO] Apache Sling MIME type mapping support  SUCCESS [11.719s]
[INFO] Apache Sling Commons OSGi support . SUCCESS [14.857s]
[INFO] Apache Sling Scheduler Support  SUCCESS [9.894s]
[INFO] Apache Sling Testing Utilities  SUCCESS [21.749s]
[INFO] Apache Sling Thread Dumper  SUCCESS [9.530s]
[INFO] Apache Sling Thread Support ... SUCCESS [9.362s]
[INFO] Apache Sling Authentication Service ... SUCCESS [14.112s]
[INFO] Apache Sling OpenID Authentication  SUCCESS [7.790s]
[INFO] Apache Sling Form Based Authentication Handler  SUCCESS [15.550s]
[INFO] Apache Sling Authentication Selector .. SUCCESS [8.800s]
[INFO] Apache Sling Engine Implementation  SUCCESS [36.705s]
[INFO] Apache Sling Repository API Bundle  SUCCESS [8.835s]
[INFO] Apache Sling JCR Base Bundle .. SUCCESS [8.379s]
[INFO] Apache Sling JCR ClassLoader .. SUCCESS [9.317s]
[INFO] Apache Sling Initial Content Loader ... SUCCESS [11.960s]
[INFO] Apache Sling Jackrabbit Embedded Repository ... SUCCESS [12.904s]
[INFO] Apache Sling Jackrabbit UserManager Support ... SUCCESS [12.171s]
[INFO] Apache Sling Jackrabbit JSR-283 Access Control Manager Support  SUCCESS 
[9.210s]
[INFO] Apache Sling Wrapper Bundle for the JCR API ... SUCCESS [9.324s]
[INFO] Apache Sling Object Content Mapping ... SUCCESS [10.470s]
[INFO] Apache Sling JCR Resource Resolver  SUCCESS [38.694s]
[INFO] Apache Sling JCR Repository Registration .. SUCCESS [11.272s]
[INFO] Apache Sling Simple WebDAV Access to repositories . SUCCESS [10.766s]
[INFO] Apache Sling DavEx Access to repositories . SUCCESS [9.480s]
[INFO] Apache Sling JCR WebConsole Bundle  SUCCESS [8.468s]
[INFO] Apache Sling Oak Repository Server  SUCCESS [9.505s]
[INFO] Apache Sling SlingRepository Integration Tests  SUCCESS [27.102s]
[INFO] Apache Sling Servlet Resolver . SUCCESS [14.721s]
[INFO] Apache Sling Default GET Servlets . SUCCESS [12.282s]
[INFO] Apache Sling Default POST Servlets  SUCCESS [14.101s]
[INFO] Apache Sling Compat Servlets .. SUCCESS [8.890s]
[INFO] Apache Sling Scripting Implementation API . SUCCESS [7.530s]
[INFO] Apache Sling Scripting Core implementation  SUCCESS [17.542s]
[INFO] Apache Sling Scripting JavaScript Support . SUCCESS [17.988s]
[INFO] Apache Sling Scripting JSP Support  SUCCESS [15.559s]
[INFO] Apache Sling JSP Tag Library .. SUCCESS [11.181s]
[INFO] Apache Sling JSP Standard Tag Library . SUCCESS [7.698s]
[INFO] Apache Sling Adapter Manager Implementation ... SUCCESS [11.691s]
[INFO] Apache Sling Bundle Resource Provider . SUCCESS [7.118

Re: Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Application Builder #519

[Robert Munteanu]

On Wed, Jun 4, 2014 at 10:43 AM, Apache Jenkins Server
 wrote:
> See 
> 
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/maven-metadata.xml
> Downloading: 
> http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/org.apache.sling.installer.core-3.5.3.SNAPSHOT.pom
> [WARNING] The POM for 
> org.apache.sling:org.apache.sling.installer.core:jar:3.5.3.SNAPSHOT is 
> missing, no dependency information available

The dependency to org.apache.sling.installer.core should be
3.5.3-SNAPSHOT . Fixed in http://svn.apache.org/r1599972

Robert

Build failed in Jenkins: sling-trunk-1.7 » Apache Sling Launchpad Application Builder #519

[Apache Jenkins Server]

See 


Changes:

[cziegeler] Use latest installer snapshots during release

--
[INFO] 
[INFO] 
[INFO] Building Apache Sling Launchpad Application Builder 7-SNAPSHOT
[INFO] 
Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/maven-metadata.xml
Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/org.apache.sling.installer.core-3.5.3.SNAPSHOT.pom
[WARNING] The POM for 
org.apache.sling:org.apache.sling.installer.core:jar:3.5.3.SNAPSHOT is missing, 
no dependency information available
Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.contentloader/2.1.7-SNAPSHOT/maven-metadata.xml
Downloaded: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.jcr.contentloader/2.1.7-SNAPSHOT/maven-metadata.xml
 (1022 B at 0.7 KB/sec)
Downloading: 
http://repository.apache.org/snapshots/org/apache/sling/org.apache.sling.installer.core/3.5.3.SNAPSHOT/org.apache.sling.installer.core-3.5.3.SNAPSHOT.jar
[JENKINS] Archiving disabled

[jira] [Created] (SLING-3638) Add 'upload (full republish)' action to module context menu in wst server view

[Stefan Egli (JIRA)]

Stefan Egli created SLING-3638:
--

 Summary: Add 'upload (full republish)' action to module context 
menu in wst server view
 Key: SLING-3638
 URL: https://issues.apache.org/jira/browse/SLING-3638
 Project: Sling
  Issue Type: Task
  Components: IDE
Reporter: Stefan Egli
 Fix For: Sling Eclipse IDE 1.0.0


(tentatively marking this as 1.0.0)

It might be useful to have a 'upload to repository/full republish to server' 
action on a content module in the wst server. 

Currently there is no intuitive way of 'republishing one/all module(s)'. The 
way to do this is to use 'export' (which is going to be renamed to 'upload') in 
the Project's context menu. This might be a bit hidden and adding a second way 
in the wst server's view might be helpful.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Release Apache Sling Installer Core 3.5.2 and Installer Configuration Factoy 1.0.14

[Carsten Ziegeler]

+1

Carsten


2014-06-04 8:13 GMT+02:00 Ian Boston :

> +1
> Signatures checked.
> Ian
>
> On 4 June 2014 07:06, Carsten Ziegeler  wrote:
> > Hi,
> >
> > We solved 3 issues in Installer Core 3.5.2
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12325943
> >
> > We solved 1 issue in Installer Configuration Factory 1.0.14
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12326553
> >
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1068
> >
> > 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 1068 /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.
> >
> > Regards
> > Carsten
> > --
> > Carsten Ziegeler
> > cziege...@apache.org
>



-- 
Carsten Ziegeler
cziege...@apache.org

[jira] [Created] (SLING-3637) Create connection pool lazily in DataSource Provider bundle

[Chetan Mehrotra (JIRA)]

Chetan Mehrotra created SLING-3637:
--

 Summary: Create connection pool lazily in DataSource Provider 
bundle
 Key: SLING-3637
 URL: https://issues.apache.org/jira/browse/SLING-3637
 Project: Sling
  Issue Type: Improvement
  Components: Extensions
Reporter: Chetan Mehrotra
Assignee: Chetan Mehrotra
 Fix For: DataSource Provider 0.0.2


DataSource provider bundle currently creates and initializes the connection 
pool upon activation itself. Instead the connection pool should be initialized 
lazily as that would 

# Move the costly init operation out of main thread
# Allow looking up of Driver class from bundle which have yet not started (at 
least in current start level)



--
This message was sent by Atlassian JIRA
(v6.2#6252)