Re: Installing ESA Files

[Roy Teeuwen]

Hey David,

I’m currently using the Sling launchpad 9-SNAPSHOT, and I can indeed directly 
install the subsystems felix webconsole, so perfect, thanks!

But now when I try to iinstall an esa I get following exception. Is there 
anything extra I should to do get it working in Sling?

13.11.2015 00:18:00.060 *ERROR* [Thread-119] 
org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in 
Thread Thread[Thread-119,5,main]
org.osgi.service.subsystem.SubsystemException: 
org.osgi.service.resolver.ResolutionException: Unable to resolve 
/var/folders/h1/k9tr352j615f8jrrzh5yr5b8gn/T/inputStreamExtract4257393115279757160.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar:
 missing requirement 
org.apache.aries.subsystem.core.archive.RequireCapabilityRequirement: 
namespace=osgi.service, attributes={}, 
directives={filter=(objectClass=org.apache.sling.event.jobs.JobManager), 
effective=active, resolution=mandatory, cardinality=single}, 
resource=/var/folders/h1/k9tr352j615f8jrrzh5yr5b8gn/T/inputStreamExtract4257393115279757160.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:395)
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:356)
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:98)
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:90)
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:54)
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:30)
at java.security.AccessController.doPrivileged(Native Method)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:646)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:690)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:278)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:65)
at 
org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$1.exec(WebConsolePlugin.java:191)
at 
org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$5.run(WebConsolePlugin.java:267)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve 
/var/folders/h1/k9tr352j615f8jrrzh5yr5b8gn/T/inputStreamExtract4257393115279757160.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar:
 missing requirement 
org.apache.aries.subsystem.core.archive.RequireCapabilityRequirement: 
namespace=osgi.service, attributes={}, 
directives={filter=(objectClass=org.apache.sling.event.jobs.JobManager), 
effective=active, resolution=mandatory, cardinality=single}, 
resource=/var/folders/h1/k9tr352j615f8jrrzh5yr5b8gn/T/inputStreamExtract4257393115279757160.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar
at 
org.apache.felix.resolver.ResolutionError.toException(ResolutionError.java:42)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:235)
at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:158)
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:373)

It is generated by following plugin and is a feature, so by my knowledge all 
services/bundles should just be imported/exported. The dependencies are 3 
bundles with all the rest of their dependencies already available in the 
standard Sling 9-SNAPSHOT (if I install the 3 bundles separately through the 
webconsole, everything works fine so):


org.apache.aries
esa-maven-plugin
1.0.0
true

true
dependencies

osgi.subsystem.feature




Thanks alot!
Greets
Roy

> On 12 Nov 2015, at 13:24, David Bosschaert  wrote:
> 
> Hi Roy,
> 
> That blog post references old-ish versions of the relevant bundles.
> You might want to take a look at
> http://aries.apache.org/modules/subsystems.html for a newer list of
> bundles required.
> 
> Alternatively you can just use the latest Sling launchpad (9-SNAPSHOT,
> which you'd have to build yourself). It has all the deps for
> Subsystems installed. Just install the webconsole plugin on top of
> that and it should work - I just tried it and it works for me :)
> 
> Cheers,
> 
> David
> 
> On 12 November 2015 at 11:58, Roy Teeuwen  wrote:
>> Hey David,
>> 
>> I tried your second approach.
>> 
>> I first installed subsystems on felix by following this guide:
>> 
>> http://coderthoughts.blogspot.be/2014/01/osgi-subsytems-on-apache-felix.html 
>> 

Re: [VOTE] Release Apache Sling Service User Mapper 1.2.2

[Daniel Klco]

+1 -- checked signatures and build

On Thu, Nov 12, 2015 at 8:44 AM, Robert Munteanu  wrote:

> On Wed, 2015-11-11 at 14:56 +, Marius Petria wrote:
> > Please vote to approve this release:
>
> +1
>
> Robert
>

[jira] [Closed] (SLING-5271) maven-sling-plugin: Update commons.json dependency for latest JSON Validator improvements

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5271.
-

> maven-sling-plugin: Update commons.json dependency for latest JSON Validator 
> improvements
> -
>
> Key: SLING-5271
> URL: https://issues.apache.org/jira/browse/SLING-5271
> Project: Sling
>  Issue Type: Improvement
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven Sling Plugin 2.1.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Maven Sling Plugin 2.1.6
>
>
> we should update to Commons JSON 2.0.14 to get the latest json validation 
> improvments from SLING-5270.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5272) maven-sling-plugin: Potential resource leak in JAR file handling

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5272.
-

> maven-sling-plugin: Potential resource leak in JAR file handling
> 
>
> Key: SLING-5272
> URL: https://issues.apache.org/jira/browse/SLING-5272
> Project: Sling
>  Issue Type: Bug
>  Components: Maven Plugins and Archetypes
>Affects Versions: Maven Sling Plugin 2.1.2
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Trivial
> Fix For: Maven Sling Plugin 2.1.6
>
>
> eclipse complains about a resource leak in the 
> AbstractBundleDeployMojo.changeVersion method - a "JarFile" instance is not 
> closed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5184) JSONRenderer.quote should not use synchronized StringWriter with unspecified length

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5184.
-

> JSONRenderer.quote should not use synchronized StringWriter with unspecified 
> length
> ---
>
> Key: SLING-5184
> URL: https://issues.apache.org/jira/browse/SLING-5184
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons JSON 2.0.12
>Reporter: Joel Richard
>Assignee: Robert Munteanu
>Priority: Minor
>  Labels: json, performance
> Fix For: Commons JSON 2.0.16
>
>
> StringWriter uses a StringBuffer internally which is synchronized. By using a 
> StringBuilder instead and initializing it with the estimated size, this 
> methods becomes 5 times faster (in my real test case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5152) JsonJcrNode and JsonItemWriter should use prop.isMultiple() instead of def.isMultiple()

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5152.
-

> JsonJcrNode and JsonItemWriter should use prop.isMultiple() instead of 
> def.isMultiple()
> ---
>
> Key: SLING-5152
> URL: https://issues.apache.org/jira/browse/SLING-5152
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Affects Versions: Commons JSON 2.0.12
>Reporter: Joel Richard
>Assignee: Robert Munteanu
>Priority: Minor
>  Labels: json, performance
> Fix For: Commons JSON 2.0.16
>
>
> In Oak, node.getDefinition().isMultiple() is is around 35 times slower than 
> prop.isMultiple(). In addition to this, MockProperty.isMultiple has to be 
> implemented because otherwise the tests fail (for which I will open another 
> issue shortly).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5276) Validator.validate throws StackOverflowError

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5276.
-

> Validator.validate throws StackOverflowError
> 
>
> Key: SLING-5276
> URL: https://issues.apache.org/jira/browse/SLING-5276
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons JSON 2.0.12
> Environment: Linux
>Reporter: Krzysztof Otrebski
>Assignee: Stefan Seifert
>Priority: Critical
> Fix For: Commons JSON 2.0.16
>
>
> If I pass string "[" to org.apache.sling.commons.json.util.Validator.validate 
> I will get  StackOverflowError



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5270) comons.json: JSON Validator does not fail on too many closing brackets

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5270.
-

> comons.json: JSON Validator does not fail on too many closing brackets
> --
>
> Key: SLING-5270
> URL: https://issues.apache.org/jira/browse/SLING-5270
> Project: Sling
>  Issue Type: Bug
>  Components: Commons
>Affects Versions: Commons JSON 2.0.12
>Reporter: Stefan Seifert
>Assignee: Stefan Seifert
>Priority: Minor
> Fix For: Commons JSON 2.0.16
>
> Attachments: SLING-5270-ValidatorTest.java.patch
>
>
> the JSON validator (which is also used by the maven-sling-plugin) does not 
> fail when the JSON contains too many closing brackets, esp.:
> * too many "}" at the end of file
> * too many "]" at the end of file
> * too many "}" within the file
> attached is a patch file with unit tests, three of them do not fail although 
> the json is invalid.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4744) provide a default testcase name for MDC

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-4744.
-

> provide a default testcase name for MDC
> ---
>
> Key: SLING-4744
> URL: https://issues.apache.org/jira/browse/SLING-4744
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Commons Testing 2.0.18, Launchpad Integration Tests 1.0.0
> Environment: Apache Karaf (3.0.3)
>Reporter: Oliver Lietz
>Assignee: Oliver Lietz
> Fix For: Commons Testing 2.0.22, Launchpad Integration Tests 1.0.2
>
>
> When running Lauchpad's integration tests against Launchpad Karaf 
> (SLING-3821) lots of tests fail due to NPE in setting up MDC (SLING-1659) for 
> logging.
> {noformat}
> ---
> Test set: 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest
> ---
> Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 0 sec <<< 
> FAILURE! - in 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest
> testDeniedWriteForUser(org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException: null
>   at java.util.Hashtable.put(Hashtable.java:459)
>   at org.ops4j.pax.logging.PaxContext.put(PaxContext.java:75)
>   at 
> org.ops4j.pax.logging.slf4j.Slf4jMDCAdapter.put(Slf4jMDCAdapter.java:57)
>   at org.slf4j.MDC.put(MDC.java:116)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.setUp(HttpTestBase.java:144)
>   at 
> org.apache.sling.commons.testing.integration.HttpTest.setUp(HttpTest.java:70)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest.setup(AccessPrivilegesInfoTest.java:54)
> testSLING_1090(org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException: null
>   at java.util.Hashtable.put(Hashtable.java:459)
>   at org.ops4j.pax.logging.PaxContext.put(PaxContext.java:75)
>   at 
> org.ops4j.pax.logging.slf4j.Slf4jMDCAdapter.put(Slf4jMDCAdapter.java:57)
>   at org.slf4j.MDC.put(MDC.java:116)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.setUp(HttpTestBase.java:144)
>   at 
> org.apache.sling.commons.testing.integration.HttpTest.setUp(HttpTest.java:70)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest.setup(AccessPrivilegesInfoTest.java:54)
> testGrantedWriteForUser(org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException: null
>   at java.util.Hashtable.put(Hashtable.java:459)
>   at org.ops4j.pax.logging.PaxContext.put(PaxContext.java:75)
>   at 
> org.ops4j.pax.logging.slf4j.Slf4jMDCAdapter.put(Slf4jMDCAdapter.java:57)
>   at org.slf4j.MDC.put(MDC.java:116)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.setUp(HttpTestBase.java:144)
>   at 
> org.apache.sling.commons.testing.integration.HttpTest.setUp(HttpTest.java:70)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest.setup(AccessPrivilegesInfoTest.java:54)
> testDeniedWriteForGroup(org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException: null
>   at java.util.Hashtable.put(Hashtable.java:459)
>   at org.ops4j.pax.logging.PaxContext.put(PaxContext.java:75)
>   at 
> org.ops4j.pax.logging.slf4j.Slf4jMDCAdapter.put(Slf4jMDCAdapter.java:57)
>   at org.slf4j.MDC.put(MDC.java:116)
>   at 
> org.apache.sling.commons.testing.integration.HttpTestBase.setUp(HttpTestBase.java:144)
>   at 
> org.apache.sling.commons.testing.integration.HttpTest.setUp(HttpTest.java:70)
>   at 
> org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest.setup(AccessPrivilegesInfoTest.java:54)
> testGrantedWriteForGroup(org.apache.sling.launchpad.webapp.integrationtest.accessManager.AccessPrivilegesInfoTest)
>   Time elapsed: 0 sec  <<< ERROR!
> java.lang.NullPointerException: null
>   at java.util.Hashtable.put(Hashtable.java:459)
>   at org.ops4j.pax.logging.PaxContext.put(PaxContext.java:75)
>   at 
> org.ops4j.pax.logging.slf4j.Slf4jMDCAdapter.put(Slf4jMDCAdapter.java:57)
>   at org.slf4j.MDC.put(MDC.java:116)
>   at 
> org.apache.sling.commons.testing.inte

[jira] [Closed] (SLING-4681) HttpTestBase: default content type for readiness test should be selectable

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-4681.
-

> HttpTestBase: default content type for readiness test should be selectable
> --
>
> Key: SLING-4681
> URL: https://issues.apache.org/jira/browse/SLING-4681
> Project: Sling
>  Issue Type: Improvement
>  Components: Testing
>Affects Versions: Commons Testing 2.0.18
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>Priority: Minor
> Fix For: Commons Testing 2.0.22
>
>
> HttpTestBase uses hardcoded .txt / text/plain values to for its GET requests 
> used to check readiness. This should be settable to make the readiness 
> algorithm more reusable.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5114) Remove OakOnly and JackrabbitOnly annotations

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5114.
-

> Remove OakOnly and JackrabbitOnly annotations
> -
>
> Key: SLING-5114
> URL: https://issues.apache.org/jira/browse/SLING-5114
> Project: Sling
>  Issue Type: Task
>  Components: Testing
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Commons Testing 2.0.22
>
>
> Since we have moved to Oak only and Jackrabbit is no longer used ( SLING-5098 
> ) we don't need these annotations anymore



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-5153) MockProperty.isMultiple returns always false

[Stefan Seifert (JIRA)]

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

Stefan Seifert closed SLING-5153.
-

> MockProperty.isMultiple returns always false
> 
>
> Key: SLING-5153
> URL: https://issues.apache.org/jira/browse/SLING-5153
> Project: Sling
>  Issue Type: Bug
>  Components: Testing
>Affects Versions: Commons Testing 2.0.18
>Reporter: Joel Richard
>Assignee: Robert Munteanu
>Priority: Minor
> Fix For: Commons Testing 2.0.22
>
>
> property.isMultiple() should return the same as 
> property.getDefinition().isMultiple().



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[RESULT] [VOTE] Release Apache Sling Commons Testing 2.0.22, Commons JSON 2.0.16, Maven Sling Plugin 2.1.6

[Stefan Seifert]

Hi,

The vote has passed with the following result :

+1 (binding): Stefan Seifert, Stefan Egli, Robert Munteanu

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


stefan

[jira] [Assigned] (SLING-5288) Restrict which classes can be deserialized

[Bertrand Delacretaz (JIRA)]

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

Bertrand Delacretaz reassigned SLING-5288:
--

Assignee: Bertrand Delacretaz

> Restrict which classes can be deserialized
> --
>
> Key: SLING-5288
> URL: https://issues.apache.org/jira/browse/SLING-5288
> Project: Sling
>  Issue Type: Bug
>  Components: General
>Reporter: Bertrand Delacretaz
>Assignee: Bertrand Delacretaz
>
> To avoid a recently reported Java deserialization vulnerability [1], we 
> should restrict which classes are accepted when deserializing binaries.
> I have created a prototype SafeObjectInputStream at [2], which refuses to 
> operate on classes that are outside a whitelist.
> We probably also need a wrapper for ObjectInputStreams provided by the 
> environment, that looks a bit harder to create, for now we can already 
> discuss this prototype to see if we want to pursue the idea.
> [1] 
> https://blogs.apache.org/foundation/entry/apache_commons_statement_to_widespread
> [2] 
> https://svn.apache.org/repos/asf/sling/whiteboard/bdelacretaz/safe-object-input-stream



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (SLING-5263) Request to implement junit test cases for LogSupport.java

[Robert Munteanu (JIRA)]

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

Robert Munteanu commented on SLING-5263:


[~tiennv90] - thanks for the pull request! I will have a look in the coming days

> Request to implement junit test cases for LogSupport.java
> -
>
> Key: SLING-5263
> URL: https://issues.apache.org/jira/browse/SLING-5263
> Project: Sling
>  Issue Type: Improvement
>  Components: Commons
>Reporter: Tien Nguyen Viet
>Priority: Trivial
>
> org.apache.sling.commons.logservice.internal.LogSupport.java is not 100% 
> covered by junit test cases, can i request to let me implement the test cases 
> ?
> CC: [~cziegeler]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [VOTE] Release Apache Sling discovery.commons 1.0.4, discovery.base 1.1.0, discovery.oak 1.1.0 and discovery.impl 1.2.2

[Robert Munteanu]

On Wed, 2015-11-11 at 11:23 +0100, Stefan Egli wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Content Distribution Core version 0.1.10 and Distribution Sample 0.1.4

[Robert Munteanu]

On Wed, 2015-11-11 at 12:51 +, Marius Petria wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Service User Mapper 1.2.2

[Robert Munteanu]

On Wed, 2015-11-11 at 14:56 +, Marius Petria wrote:
> Please vote to approve this release:

+1

Robert


signature.asc
Description: This is a digitally signed message part

Re: [VOTE] Release Apache Sling Commons Testing 2.0.22, Commons JSON 2.0.16, Maven Sling Plugin 2.1.6

[Robert Munteanu]

On Mon, 2015-11-09 at 12:31 +, Stefan Seifert wrote:
> Please vote to approve this release:

+1

Robert

signature.asc
Description: This is a digitally signed message part

Re: Installing ESA Files

[Roy Teeuwen]

Hey David,

Hehe sorry, of course, I meant the sling-maven-plugin ;). Was mixing it up a 
bit.

It would be great if the sling maven plugin could also install esa files

Greetings,
Roy
> On 12 Nov 2015, at 13:56, David Bosschaert  wrote:
> 
> Hi Roy,
> 
> On 12 November 2015 at 10:17, Roy Teeuwen  wrote:
>> Is there any willingness to also make the maven-bundle-plugin install esa 
>> files? This would surely be a lot handier when integrating the esa files 
>> into a CI system.
> 
> I'm not sure whether the maven-bundle-plugin is the best option for
> installing subsystems as it really depends on what your target
> environment is how you want to install them. However maybe the
> sling-maven-plugin might be useful here. It has a sling:install goal
> which can be used to install bundles. It currently doesn't accept
> subsystems (yet) but it should be easy to add I think...
> 
> Just a thought...
> 
> David
> 
> [1] http://sling.apache.org/site/sling.html

Re: Installing ESA Files

[David Bosschaert]

Hi Roy,

On 12 November 2015 at 10:17, Roy Teeuwen  wrote:
> Is there any willingness to also make the maven-bundle-plugin install esa 
> files? This would surely be a lot handier when integrating the esa files into 
> a CI system.

I'm not sure whether the maven-bundle-plugin is the best option for
installing subsystems as it really depends on what your target
environment is how you want to install them. However maybe the
sling-maven-plugin might be useful here. It has a sling:install goal
which can be used to install bundles. It currently doesn't accept
subsystems (yet) but it should be easy to add I think...

Just a thought...

David

[1] http://sling.apache.org/site/sling.html

Re: Installing ESA Files

[Roy Teeuwen]

Perfect! Thanks :)

Greets
Roy
> On 12 Nov 2015, at 13:24, David Bosschaert  wrote:
> 
> Hi Roy,
> 
> That blog post references old-ish versions of the relevant bundles.
> You might want to take a look at
> http://aries.apache.org/modules/subsystems.html for a newer list of
> bundles required.
> 
> Alternatively you can just use the latest Sling launchpad (9-SNAPSHOT,
> which you'd have to build yourself). It has all the deps for
> Subsystems installed. Just install the webconsole plugin on top of
> that and it should work - I just tried it and it works for me :)
> 
> Cheers,
> 
> David
> 
> On 12 November 2015 at 11:58, Roy Teeuwen  wrote:
>> Hey David,
>> 
>> I tried your second approach.
>> 
>> I first installed subsystems on felix by following this guide:
>> 
>> http://coderthoughts.blogspot.be/2014/01/osgi-subsytems-on-apache-felix.html 
>> 
>> 
>> Afterwords I tried to install a subsystem through the webconsole, but the 
>> error.log returns following exception:
>> 
>> 12.11.2015 12:48:31.624 *ERROR* [Thread-65] 
>> org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
>> in Thread Thread[Thread-65,5,main]
>> org.osgi.service.subsystem.SubsystemException: 
>> java.net.MalformedURLException: Unknown protocol: inputstream
>>at 
>> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:101)
>>at 
>> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:31)
>>at java.security.AccessController.doPrivileged(Native Method)
>>at 
>> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:560)
>>at 
>> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:252)
>>at 
>> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:58)
>>at 
>> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$1.exec(WebConsolePlugin.java:191)
>>at 
>> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$5.run(WebConsolePlugin.java:267)
>>at java.lang.Thread.run(Thread.java:745)
>> Caused by: java.net.MalformedURLException: Unknown protocol: inputstream
>>at java.net.URL.(URL.java:620)
>>at java.net.URL.(URL.java:483)
>>at java.net.URL.(URL.java:432)
>>at java.net.URI.toURL(URI.java:1089)
>>at 
>> org.apache.aries.subsystem.core.internal.Location.(Location.java:69)
>>at 
>> org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:113)
>>at 
>> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:92)
>>at 
>> org.apache.aries.subsystem.core.internal.InstallAction.createSubsystemResource(InstallAction.java:128)
>>at 
>> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:62)
>>... 8 common frames omitted
>> Caused by: java.lang.IllegalStateException: Unknown protocol: inputstream
>>at 
>> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
>>at java.net.URL.(URL.java:615)
>>... 16 common frames omitted
>> 
>> 
>> Any idea where it’s going wrong?
>> 
>> Greetings
>> Roy
>> 
>>> On 12 Nov 2015, at 11:11, David Bosschaert  
>>> wrote:
>>> 
>>> Hi Roy,
>>> 
>>> You currently have a couple of options in Sling to install subsystems.
>>> 
>>> 1. Directly by calling the OSGi Subsystem Service
>>> https://osgi.org/javadoc/r6/enterprise/org/osgi/service/subsystem/Subsystem.html
>>> but this requires you to create some code around it.
>>> 2. With the webconsole subsystem plugin
>>> https://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/subsystems
>>> this plugin is currently under vote for its first release, but you can
>>> build it yourself from that URL and install it into sling. That plugin
>>> looks like this: http://tinypic.com/r/2z8tbpe/8
>>> 3. You can also feed .esa files to the OSGi Installer in sling, e.g.
>>> by putting them in the install directory...
>>> 
>>> If you're just experimenting, option 2 is definitely the easiest.
>>> 
>>> Cheers,
>>> 
>>> David
>>> 
>>> On 12 November 2015 at 09:31, Roy Teeuwen  wrote:
 Hey all,
 
 I have fetched the sling launchpad 8 from maven central and I made a 
 subsystem with the esa maven plugin from apache aries. Now when I want to 
 install it, I get a popup with the error “You cannot select a .esa file. 
 Try again…"
 
 Is this not the way to install OSGi subsystems? And would it be possible 
 to install this esa with the maven-bundle plugin?
 
 Greetings,
 Roy
 
 
>> 

Re: Installing ESA Files

[David Bosschaert]

Hi Roy,

That blog post references old-ish versions of the relevant bundles.
You might want to take a look at
http://aries.apache.org/modules/subsystems.html for a newer list of
bundles required.

Alternatively you can just use the latest Sling launchpad (9-SNAPSHOT,
which you'd have to build yourself). It has all the deps for
Subsystems installed. Just install the webconsole plugin on top of
that and it should work - I just tried it and it works for me :)

Cheers,

David

On 12 November 2015 at 11:58, Roy Teeuwen  wrote:
> Hey David,
>
> I tried your second approach.
>
> I first installed subsystems on felix by following this guide:
>
> http://coderthoughts.blogspot.be/2014/01/osgi-subsytems-on-apache-felix.html 
> 
>
> Afterwords I tried to install a subsystem through the webconsole, but the 
> error.log returns following exception:
>
> 12.11.2015 12:48:31.624 *ERROR* [Thread-65] 
> org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception 
> in Thread Thread[Thread-65,5,main]
> org.osgi.service.subsystem.SubsystemException: 
> java.net.MalformedURLException: Unknown protocol: inputstream
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:101)
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:31)
> at java.security.AccessController.doPrivileged(Native Method)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:560)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:252)
> at 
> org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:58)
> at 
> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$1.exec(WebConsolePlugin.java:191)
> at 
> org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$5.run(WebConsolePlugin.java:267)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.MalformedURLException: Unknown protocol: inputstream
> at java.net.URL.(URL.java:620)
> at java.net.URL.(URL.java:483)
> at java.net.URL.(URL.java:432)
> at java.net.URI.toURL(URI.java:1089)
> at 
> org.apache.aries.subsystem.core.internal.Location.(Location.java:69)
> at 
> org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:113)
> at 
> org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:92)
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.createSubsystemResource(InstallAction.java:128)
> at 
> org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:62)
> ... 8 common frames omitted
> Caused by: java.lang.IllegalStateException: Unknown protocol: inputstream
> at 
> org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
> at java.net.URL.(URL.java:615)
> ... 16 common frames omitted
>
>
> Any idea where it’s going wrong?
>
> Greetings
> Roy
>
>> On 12 Nov 2015, at 11:11, David Bosschaert  
>> wrote:
>>
>> Hi Roy,
>>
>> You currently have a couple of options in Sling to install subsystems.
>>
>> 1. Directly by calling the OSGi Subsystem Service
>> https://osgi.org/javadoc/r6/enterprise/org/osgi/service/subsystem/Subsystem.html
>> but this requires you to create some code around it.
>> 2. With the webconsole subsystem plugin
>> https://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/subsystems
>> this plugin is currently under vote for its first release, but you can
>> build it yourself from that URL and install it into sling. That plugin
>> looks like this: http://tinypic.com/r/2z8tbpe/8
>> 3. You can also feed .esa files to the OSGi Installer in sling, e.g.
>> by putting them in the install directory...
>>
>> If you're just experimenting, option 2 is definitely the easiest.
>>
>> Cheers,
>>
>> David
>>
>> On 12 November 2015 at 09:31, Roy Teeuwen  wrote:
>>> Hey all,
>>>
>>> I have fetched the sling launchpad 8 from maven central and I made a 
>>> subsystem with the esa maven plugin from apache aries. Now when I want to 
>>> install it, I get a popup with the error “You cannot select a .esa file. 
>>> Try again…"
>>>
>>> Is this not the way to install OSGi subsystems? And would it be possible to 
>>> install this esa with the maven-bundle plugin?
>>>
>>> Greetings,
>>> Roy
>>>
>>>
>

Re: Installing ESA Files

[Roy Teeuwen]

Hey David,

I tried your second approach.

I first installed subsystems on felix by following this guide:

http://coderthoughts.blogspot.be/2014/01/osgi-subsytems-on-apache-felix.html 


Afterwords I tried to install a subsystem through the webconsole, but the 
error.log returns following exception:

12.11.2015 12:48:31.624 *ERROR* [Thread-65] 
org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in 
Thread Thread[Thread-65,5,main]
org.osgi.service.subsystem.SubsystemException: java.net.MalformedURLException: 
Unknown protocol: inputstream
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:101)
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:31)
at java.security.AccessController.doPrivileged(Native Method)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:560)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:252)
at 
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:58)
at 
org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$1.exec(WebConsolePlugin.java:191)
at 
org.apache.felix.webconsole.plugins.subsystem.internal.WebConsolePlugin$5.run(WebConsolePlugin.java:267)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.net.MalformedURLException: Unknown protocol: inputstream
at java.net.URL.(URL.java:620)
at java.net.URL.(URL.java:483)
at java.net.URL.(URL.java:432)
at java.net.URI.toURL(URI.java:1089)
at 
org.apache.aries.subsystem.core.internal.Location.(Location.java:69)
at 
org.apache.aries.subsystem.core.internal.RawSubsystemResource.(RawSubsystemResource.java:113)
at 
org.apache.aries.subsystem.core.internal.SubsystemResource.(SubsystemResource.java:92)
at 
org.apache.aries.subsystem.core.internal.InstallAction.createSubsystemResource(InstallAction.java:128)
at 
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:62)
... 8 common frames omitted
Caused by: java.lang.IllegalStateException: Unknown protocol: inputstream
at 
org.apache.felix.framework.URLHandlersStreamHandlerProxy.parseURL(URLHandlersStreamHandlerProxy.java:373)
at java.net.URL.(URL.java:615)
... 16 common frames omitted


Any idea where it’s going wrong?

Greetings
Roy

> On 12 Nov 2015, at 11:11, David Bosschaert  wrote:
> 
> Hi Roy,
> 
> You currently have a couple of options in Sling to install subsystems.
> 
> 1. Directly by calling the OSGi Subsystem Service
> https://osgi.org/javadoc/r6/enterprise/org/osgi/service/subsystem/Subsystem.html
> but this requires you to create some code around it.
> 2. With the webconsole subsystem plugin
> https://svn.apache.org/repos/asf/felix/trunk/webconsole-plugins/subsystems
> this plugin is currently under vote for its first release, but you can
> build it yourself from that URL and install it into sling. That plugin
> looks like this: http://tinypic.com/r/2z8tbpe/8
> 3. You can also feed .esa files to the OSGi Installer in sling, e.g.
> by putting them in the install directory...
> 
> If you're just experimenting, option 2 is definitely the easiest.
> 
> Cheers,
> 
> David
> 
> On 12 November 2015 at 09:31, Roy Teeuwen  wrote:
>> Hey all,
>> 
>> I have fetched the sling launchpad 8 from maven central and I made a 
>> subsystem with the esa maven plugin from apache aries. Now when I want to 
>> install it, I get a popup with the error “You cannot select a .esa file. Try 
>> again…"
>> 
>> Is this not the way to install OSGi subsystems? And would it be possible to 
>> install this esa with the maven-bundle plugin?
>> 
>> Greetings,
>> Roy
>> 
>> 

[jira] [Updated] (SLING-5243) discovery.impl.cluster.SingleInstanceTest.testBootstrap failed on jenkins

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-5243:
---
Component/s: Extensions

> discovery.impl.cluster.SingleInstanceTest.testBootstrap failed on jenkins
> -
>
> Key: SLING-5243
> URL: https://issues.apache.org/jira/browse/SLING-5243
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.1.8
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.2.2
>
> Attachments: SingleInstanceTest.testBootstrap.failure1918.full.txt, 
> SingleInstanceTest.testBootstrap.failure1918.txt
>
>
> the following test failed: 
> https://builds.apache.org/job/sling-trunk-1.8/org.apache.sling$org.apache.sling.discovery.impl/1918/testReport/junit/org.apache.sling.discovery.impl.cluster/SingleInstanceTest/testBootstrap/
> {code}
> Error Message
> expected:<1> but was:<0>
> Stacktrace
> java.lang.AssertionError: expected:<1> but was:<0>
>   at org.junit.Assert.fail(Assert.java:88)
>   at org.junit.Assert.failNotEquals(Assert.java:743)
>   at org.junit.Assert.assertEquals(Assert.java:118)
>   at org.junit.Assert.assertEquals(Assert.java:555)
>   at org.junit.Assert.assertEquals(Assert.java:542)
>   at 
> org.apache.sling.discovery.base.its.AbstractSingleInstanceTest.testBootstrap(AbstractSingleInstanceTest.java:284)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:483)
>   at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
>   at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
>   at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
>   at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
>   at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
>   at 
> org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
>   at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
>   at 
> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
>   at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
>   at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
>   at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
>   at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
>   at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
>   at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
>   at 
> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
>   at 
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-4640) Possibility of duplicate leaders w/discovery.impl on eventually consistent repo

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-4640.
--

> Possibility of duplicate leaders w/discovery.impl on eventually consistent 
> repo
> ---
>
> Key: SLING-4640
> URL: https://issues.apache.org/jira/browse/SLING-4640
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.1.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>
> Note: This is a fork of SLING-3432 based on a 
> [comment|https://issues.apache.org/jira/browse/SLING-3432?focusedCommentId=14495936&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14495936].
>  So here is that comment again:
> Note that [the 
> above|https://issues.apache.org/jira/browse/SLING-3432?focusedCommentId=14492494&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14492494]
>  does not solve the problem where the underlying repository is eventually 
> consistent and the heartbeat configured is too low to catch all possible 
> delays (that such an eventually consistent repository might produce under 
> load). Consider the following:
> # a cluster consisting of 3 nodes: A, B and C, A is the leader
> # writes from B and C are fast - and can be read by all 3 nodes fast
> # writes from A though are slow (ie A behaves asymmetric: slow writes but 
> fast reads)
> # at some point writes from A are slower than the configured heartbeat 
> timeout: at this point B and C find out about this and vote on a new 
> clusterView consisting only of B and C and (let's say) B becomes leader.
> #* meanwhile at A however: A is still happy: it sees the heartbeats of B and 
> C in time and would not start a new voting.
> # at some later point (with a *certain read delay*) A sees that B and C have 
> declared a new {{/establishedViews}} - at this point it would (according to 
> the new rule above) immediately send a TOPOLOGY_CHANGING and things would be 
> 'ok' again. 
> #* *but* until it does send this event - *between 4. and 5. - we have two 
> leaders: A and B*! -> thus could see issues reported here in SLING-3432 still 
> during that small timeframe (which is basically the amount of time it takes 
> for the new established view declared by B and C to be read by A).
> #* at a later time, when eg the delays in the repository have come down, A 
> would rejoin the cluster - but would have to *not become leader* again, as 
> the leader is B and must stay stable.
> This IMHO highlights the problem that using an eventually consistent 
> repository (that has no max guaranteed delay) is *not* 
> pseudo-network-partition/duplicate-leader free under load.
> Note that what is described here is not fixed by SLING-4627.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3495.
--

> TopologyTest.testLargeTopologyWithHub failures on Jenkins
> -
>
> Key: SLING-3495
> URL: https://issues.apache.org/jira/browse/SLING-3495
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.6
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.10
>
> Attachments: 2014-05-17.log, 
> TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, 
> TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt
>
>
> TopologyTest.testLargeTopologyWithHub has failed in the last testing run for 
> both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] .
> The errors are attached, in case the build results will expire.
> [1]: 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/
> [2]: 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3495) TopologyTest.testLargeTopologyWithHub failures on Jenkins

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3495:
---
Fix Version/s: Discovery Impl 1.0.10

> TopologyTest.testLargeTopologyWithHub failures on Jenkins
> -
>
> Key: SLING-3495
> URL: https://issues.apache.org/jira/browse/SLING-3495
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.6
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.10
>
> Attachments: 2014-05-17.log, 
> TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.6.txt, 
> TopologyTest.testLargeTopologyWithHub-failure-sling-trunk-1.7.txt
>
>
> TopologyTest.testLargeTopologyWithHub has failed in the last testing run for 
> both sling-trunk-1.6 [1] and sling-trunk-1.7 [2] .
> The errors are attached, in case the build results will expire.
> [1]: 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.6/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/
> [2]: 
> https://builds.apache.org/view/S-Z/view/Sling/job/sling-trunk-1.7/lastBuild/org.apache.sling$org.apache.sling.discovery.impl/testReport/org.apache.sling.discovery.impl.topology/TopologyTest/testLargeTopologyWithHub/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3056) [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3056:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
   Sling Eclipse IDE 1.0.0

> [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse
> -
>
> Key: SLING-3056
> URL: https://issues.apache.org/jira/browse/SLING-3056
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> At the moment slingclipse contains extensions which require m2eclipse plugin 
> to be installed as a hard-dependency from slingclipse. These extensions 
> should, as a minimum, be separated from the remaining extensions, such that 
> the user can choose to install them or not. Technically, the separation will 
> be bundled into a separate feature



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3030) [Tooling] support (auto-) deploy of content-bundles

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3030:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
   Sling Eclipse IDE 1.0.0

> [Tooling] support (auto-) deploy of content-bundles
> ---
>
> Key: SLING-3030
> URL: https://issues.apache.org/jira/browse/SLING-3030
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Similar to SLING-3009 in Eclipse it should be possible to (auto-) deploy a 
> content-bundle easily using the configured launchpad-server. This feature 
> will eventually integrate with SLING-2985



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3032) [Tooling] add a 'new' wizard for creating an application based on a maven archetype

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3032:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
   Sling Eclipse IDE 1.0.0

> [Tooling] add a 'new' wizard for creating an application based on a maven 
> archetype
> ---
>
> Key: SLING-3032
> URL: https://issues.apache.org/jira/browse/SLING-3032
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> In Eclipse, in the slingclipse plugin, it should be easily possible to create 
> a new application based on an available maven archetype. The archetype needs 
> to fulfill certain criterias, eg contain 'content-bundle' and 'bundle' 
> modules - besides 'pom' modules that represent the reactor/parent structure. 
> The 'new' wizard takes care of setting up the projects accordingly with any 
> eclipse specific features (eg setting a 'project facet' and setting any sling 
> properties accordingly) - also, the new projects (the 'content-bundle' and 
> the 'bundle' modules that is) should be added to a launchpad server - which 
> either already exists or is created as part of the 'new' wizard. 
> Following the SLING-3031 whitelabel support, this 'new' wizard contains hooks 
> for further 'branding'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3101) [Tooling] integrate with decentXml for minimal changes on .content.xml modifications

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3101:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
   Sling Eclipse IDE 1.0.0

> [Tooling] integrate with decentXml for minimal changes on .content.xml 
> modifications
> 
>
> Key: SLING-3101
> URL: https://issues.apache.org/jira/browse/SLING-3101
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Currently, when modifying properties or adding/removing nodes in the 
> content-browser, ie in .content.xml, the xml gets rewritten and looses 
> formatting, such as newlines within an element between attributes (which is 
> the default in .content.xml generated by vault).
> DecentXml (http://code.google.com/p/decentxml/, 'New BSD License') is a tool 
> which allows to retain the formatting (sax/dom-parsers dont). Integrate with 
> this tool to keep source changes to a minimum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3162:
---
Fix Version/s: (was: Sling Eclipse IDE 1.0.2)
   Sling Eclipse IDE 1.0.0

> Sling virtual resource tree only appears in the Project Explorer, not the 
> Package Explorer
> --
>
> Key: SLING-3162
> URL: https://issues.apache.org/jira/browse/SLING-3162
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Justin Edelson
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> In the Java EE perspective, the default navigator view is the Project 
> Explorer. In the Java perspective, it is the Package Explorer. Personally, I 
> never use the Java EE perspective (and thus the Project Explorer) because 
> Sling != JavaEE :)
> It seems to be OK if I just remove the Package Explorer view from the Java 
> perspective and add the Project Explorer. But IMHO, this isn't intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3162:
---
Fix Version/s: (was: Discovery Impl 1.0.2)
   Sling Eclipse IDE 1.0.2

> Sling virtual resource tree only appears in the Project Explorer, not the 
> Package Explorer
> --
>
> Key: SLING-3162
> URL: https://issues.apache.org/jira/browse/SLING-3162
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Justin Edelson
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> In the Java EE perspective, the default navigator view is the Project 
> Explorer. In the Java perspective, it is the Package Explorer. Personally, I 
> never use the Java EE perspective (and thus the Project Explorer) because 
> Sling != JavaEE :)
> It seems to be OK if I just remove the Package Explorer view from the Java 
> perspective and add the Project Explorer. But IMHO, this isn't intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3101) [Tooling] integrate with decentXml for minimal changes on .content.xml modifications

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3101:
---
Fix Version/s: (was: Discovery Impl 1.0.2)
   Sling Eclipse IDE 1.0.2

> [Tooling] integrate with decentXml for minimal changes on .content.xml 
> modifications
> 
>
> Key: SLING-3101
> URL: https://issues.apache.org/jira/browse/SLING-3101
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Currently, when modifying properties or adding/removing nodes in the 
> content-browser, ie in .content.xml, the xml gets rewritten and looses 
> formatting, such as newlines within an element between attributes (which is 
> the default in .content.xml generated by vault).
> DecentXml (http://code.google.com/p/decentxml/, 'New BSD License') is a tool 
> which allows to retain the formatting (sax/dom-parsers dont). Integrate with 
> this tool to keep source changes to a minimum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3032) [Tooling] add a 'new' wizard for creating an application based on a maven archetype

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3032:
---
Fix Version/s: (was: Discovery Impl 1.0.2)
   Sling Eclipse IDE 1.0.2

> [Tooling] add a 'new' wizard for creating an application based on a maven 
> archetype
> ---
>
> Key: SLING-3032
> URL: https://issues.apache.org/jira/browse/SLING-3032
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> In Eclipse, in the slingclipse plugin, it should be easily possible to create 
> a new application based on an available maven archetype. The archetype needs 
> to fulfill certain criterias, eg contain 'content-bundle' and 'bundle' 
> modules - besides 'pom' modules that represent the reactor/parent structure. 
> The 'new' wizard takes care of setting up the projects accordingly with any 
> eclipse specific features (eg setting a 'project facet' and setting any sling 
> properties accordingly) - also, the new projects (the 'content-bundle' and 
> the 'bundle' modules that is) should be added to a launchpad server - which 
> either already exists or is created as part of the 'new' wizard. 
> Following the SLING-3031 whitelabel support, this 'new' wizard contains hooks 
> for further 'branding'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3030) [Tooling] support (auto-) deploy of content-bundles

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3030:
---
Fix Version/s: (was: Discovery Impl 1.0.2)
   Sling Eclipse IDE 1.0.2

> [Tooling] support (auto-) deploy of content-bundles
> ---
>
> Key: SLING-3030
> URL: https://issues.apache.org/jira/browse/SLING-3030
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Similar to SLING-3009 in Eclipse it should be possible to (auto-) deploy a 
> content-bundle easily using the configured launchpad-server. This feature 
> will eventually integrate with SLING-2985



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3056) [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3056:
---
Fix Version/s: (was: Discovery Impl 1.0.2)
   Sling Eclipse IDE 1.0.2

> [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse
> -
>
> Key: SLING-3056
> URL: https://issues.apache.org/jira/browse/SLING-3056
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> At the moment slingclipse contains extensions which require m2eclipse plugin 
> to be installed as a hard-dependency from slingclipse. These extensions 
> should, as a minimum, be separated from the remaining extensions, such that 
> the user can choose to install them or not. Technically, the separation will 
> be bundled into a separate feature



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3030) [Tooling] support (auto-) deploy of content-bundles

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3030:
---
Fix Version/s: Discovery Impl 1.0.2

> [Tooling] support (auto-) deploy of content-bundles
> ---
>
> Key: SLING-3030
> URL: https://issues.apache.org/jira/browse/SLING-3030
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> Similar to SLING-3009 in Eclipse it should be possible to (auto-) deploy a 
> content-bundle easily using the configured launchpad-server. This feature 
> will eventually integrate with SLING-2985



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3030) [Tooling] support (auto-) deploy of content-bundles

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3030.
--

> [Tooling] support (auto-) deploy of content-bundles
> ---
>
> Key: SLING-3030
> URL: https://issues.apache.org/jira/browse/SLING-3030
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> Similar to SLING-3009 in Eclipse it should be possible to (auto-) deploy a 
> content-bundle easily using the configured launchpad-server. This feature 
> will eventually integrate with SLING-2985



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3101) [Tooling] integrate with decentXml for minimal changes on .content.xml modifications

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3101.
--

> [Tooling] integrate with decentXml for minimal changes on .content.xml 
> modifications
> 
>
> Key: SLING-3101
> URL: https://issues.apache.org/jira/browse/SLING-3101
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> Currently, when modifying properties or adding/removing nodes in the 
> content-browser, ie in .content.xml, the xml gets rewritten and looses 
> formatting, such as newlines within an element between attributes (which is 
> the default in .content.xml generated by vault).
> DecentXml (http://code.google.com/p/decentxml/, 'New BSD License') is a tool 
> which allows to retain the formatting (sax/dom-parsers dont). Integrate with 
> this tool to keep source changes to a minimum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3056) [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3056.
--

> [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse
> -
>
> Key: SLING-3056
> URL: https://issues.apache.org/jira/browse/SLING-3056
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> At the moment slingclipse contains extensions which require m2eclipse plugin 
> to be installed as a hard-dependency from slingclipse. These extensions 
> should, as a minimum, be separated from the remaining extensions, such that 
> the user can choose to install them or not. Technically, the separation will 
> be bundled into a separate feature



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3162.
--

> Sling virtual resource tree only appears in the Project Explorer, not the 
> Package Explorer
> --
>
> Key: SLING-3162
> URL: https://issues.apache.org/jira/browse/SLING-3162
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Justin Edelson
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.2
>
>
> In the Java EE perspective, the default navigator view is the Project 
> Explorer. In the Java perspective, it is the Package Explorer. Personally, I 
> never use the Java EE perspective (and thus the Project Explorer) because 
> Sling != JavaEE :)
> It seems to be OK if I just remove the Package Explorer view from the Java 
> perspective and add the Project Explorer. But IMHO, this isn't intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3032) [Tooling] add a 'new' wizard for creating an application based on a maven archetype

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3032.
--

> [Tooling] add a 'new' wizard for creating an application based on a maven 
> archetype
> ---
>
> Key: SLING-3032
> URL: https://issues.apache.org/jira/browse/SLING-3032
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> In Eclipse, in the slingclipse plugin, it should be easily possible to create 
> a new application based on an available maven archetype. The archetype needs 
> to fulfill certain criterias, eg contain 'content-bundle' and 'bundle' 
> modules - besides 'pom' modules that represent the reactor/parent structure. 
> The 'new' wizard takes care of setting up the projects accordingly with any 
> eclipse specific features (eg setting a 'project facet' and setting any sling 
> properties accordingly) - also, the new projects (the 'content-bundle' and 
> the 'bundle' modules that is) should be added to a launchpad server - which 
> either already exists or is created as part of the 'new' wizard. 
> Following the SLING-3031 whitelabel support, this 'new' wizard contains hooks 
> for further 'branding'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3233) NPE in TopologyRequestValidator

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3233.
--

> NPE in TopologyRequestValidator
> ---
>
> Key: SLING-3233
> URL: https://issues.apache.org/jira/browse/SLING-3233
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Ian Boston
>Assignee: Ian Boston
> Fix For: Discovery Impl 1.0.2
>
>
> NPE reported in TopologyRequestValidator on missing header. Fix in a moment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3162) Sling virtual resource tree only appears in the Project Explorer, not the Package Explorer

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3162:
---
Fix Version/s: Discovery Impl 1.0.2

> Sling virtual resource tree only appears in the Project Explorer, not the 
> Package Explorer
> --
>
> Key: SLING-3162
> URL: https://issues.apache.org/jira/browse/SLING-3162
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Justin Edelson
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.2
>
>
> In the Java EE perspective, the default navigator view is the Project 
> Explorer. In the Java perspective, it is the Package Explorer. Personally, I 
> never use the Java EE perspective (and thus the Project Explorer) because 
> Sling != JavaEE :)
> It seems to be OK if I just remove the Package Explorer view from the Java 
> perspective and add the Project Explorer. But IMHO, this isn't intuitive.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3056) [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3056:
---
Fix Version/s: Discovery Impl 1.0.2

> [Tooling] Separate m2eclipse dependent extensions from others, in slingclipse
> -
>
> Key: SLING-3056
> URL: https://issues.apache.org/jira/browse/SLING-3056
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> At the moment slingclipse contains extensions which require m2eclipse plugin 
> to be installed as a hard-dependency from slingclipse. These extensions 
> should, as a minimum, be separated from the remaining extensions, such that 
> the user can choose to install them or not. Technically, the separation will 
> be bundled into a separate feature



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3154) Add Topology Message Verification to the Discovery service.

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3154.
--

> Add Topology Message Verification to the Discovery service.
> ---
>
> Key: SLING-3154
> URL: https://issues.apache.org/jira/browse/SLING-3154
> Project: Sling
>  Issue Type: Improvement
>  Components: General
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Ian Boston
>Assignee: Ian Boston
> Fix For: Discovery Impl 1.0.2
>
>
> The discovery service provides support for whitelisting sources of topology 
> information, but in a cluster where the topology this creates a 
> re-configuration load of order M*(n*(n-1)) where n is the number of nodes in 
> the topology and M is the number of changes. That load rises rapidly as the 
> number of changes and/or nodes increases. 
> To address this there are 2 proposals.
> 1. To provide an SPI exported from the Discovery Impl bundle that allows 
> implementors to implement whitelisting based on the request. This will need 
> to support creating the request and validating the request.
> 2. Embed functionality within the Discovery Impl bundle that supports 
> validation and encryption of topology requests.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3101) [Tooling] integrate with decentXml for minimal changes on .content.xml modifications

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3101:
---
Fix Version/s: Discovery Impl 1.0.2

> [Tooling] integrate with decentXml for minimal changes on .content.xml 
> modifications
> 
>
> Key: SLING-3101
> URL: https://issues.apache.org/jira/browse/SLING-3101
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> Currently, when modifying properties or adding/removing nodes in the 
> content-browser, ie in .content.xml, the xml gets rewritten and looses 
> formatting, such as newlines within an element between attributes (which is 
> the default in .content.xml generated by vault).
> DecentXml (http://code.google.com/p/decentxml/, 'New BSD License') is a tool 
> which allows to retain the formatting (sax/dom-parsers dont). Integrate with 
> this tool to keep source changes to a minimum.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-3032) [Tooling] add a 'new' wizard for creating an application based on a maven archetype

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-3032:
---
Fix Version/s: Discovery Impl 1.0.2

> [Tooling] add a 'new' wizard for creating an application based on a maven 
> archetype
> ---
>
> Key: SLING-3032
> URL: https://issues.apache.org/jira/browse/SLING-3032
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.2
>
>
> In Eclipse, in the slingclipse plugin, it should be easily possible to create 
> a new application based on an available maven archetype. The archetype needs 
> to fulfill certain criterias, eg contain 'content-bundle' and 'bundle' 
> modules - besides 'pom' modules that represent the reactor/parent structure. 
> The 'new' wizard takes care of setting up the projects accordingly with any 
> eclipse specific features (eg setting a 'project facet' and setting any sling 
> properties accordingly) - also, the new projects (the 'content-bundle' and 
> the 'bundle' modules that is) should be added to a launchpad server - which 
> either already exists or is created as part of the 'new' wizard. 
> Following the SLING-3031 whitelabel support, this 'new' wizard contains hooks 
> for further 'branding'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2895) NPE in VotingHelper.getWinningVoting

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2895.
--

> NPE in VotingHelper.getWinningVoting
> 
>
> Key: SLING-2895
> URL: https://issues.apache.org/jira/browse/SLING-2895
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Dominique Pfister
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> On shutdown of a Felix container, I get the following stack trace:
> 31.05.2013 13:27:29.632 *ERROR* [pool-6-thread-4] 
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job 
> execution of 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler@4366e290 : 
> null java.lang.NullPointerException
>   at 
> org.apache.sling.discovery.impl.cluster.voting.VotingHelper.getWinningVoting(VotingHelper.java:145)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:307)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
>   at 
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:56)
>   at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2879) Avoid concurrency issues in a cluster by using ResourceUtil.getOrCreateResource

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2879.
--

> Avoid concurrency issues in a cluster by using 
> ResourceUtil.getOrCreateResource
> ---
>
> Key: SLING-2879
> URL: https://issues.apache.org/jira/browse/SLING-2879
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> org.apache.sling.discovery.impl.common.resource.ResourceHelper.getOrCreateResource/createResource
>  use own code to create a resource. This code is not as stable/fault-tolerant 
> as the ResourceUtil.getOrCreateResource. The latter deals with situations 
> where the underlying repository throws stale item exceptions and such. The 
> ResourceHelper should use ResourceUtil.getOrCreateResource and not reinvent 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2885) Race condition in VotingHandler.promote()

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2885.
--

> Race condition in VotingHandler.promote()
> -
>
> Key: SLING-2885
> URL: https://issues.apache.org/jira/browse/SLING-2885
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
> Environment: Discovery Impl version: 0.1.0.R1484784
>Reporter: Marcel Reutegger
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
> Attachments: error.log
>
>
> Sometimes on initial startup of Sling Discovery it happens that two threads 
> try to promote the same winning vote at the same time. This leads to a failed 
> commit in the repository. The system seems to be OK after the exception. 
> There is an established view and the (single) cluster node is the leader.
> Please note, this is running on Jackrabbit Oak, but might also happen on 
> Jackrabbit 2.x because the basic issue is two sessions trying to add the same 
> child node.
> See attached log excerpt for more details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2883) deal with - eg encode - "/" in property names (was: proper encode properties - and filter anything like jcr:created...)

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2883.
--

> deal with - eg encode - "/" in property names (was: proper encode properties 
> - and filter anything like jcr:created...)
> ---
>
> Key: SLING-2883
> URL: https://issues.apache.org/jira/browse/SLING-2883
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> properties provided by PropertyProviders in discovery.impl are currently 
> handed 1:1 as name (key) to jcr/repository. This will not work for special 
> characters. A proper encoding must be implemented.
> Similarly, any jcr name including ':' (eg 'jcr:created' etc) must not be 
> treated as a property and not be made visible to the users of the 
> discovery.api - the filter done as a hotfix in SLING-2880 is not sufficient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2968.
--

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2992) lower isolated mode error to info

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2992.
--

> lower isolated mode error to info
> -
>
> Key: SLING-2992
> URL: https://issues.apache.org/jira/browse/SLING-2992
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> At startup of discovery.impl, when a node joins a cluster for example and an 
> established view already exists, there is the following error:
> getEstablishedView: the existing established view does not incude the local 
> instance yet! Assming isolated mode.
> this can be lowered to info and typo-fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2882) too much logging of discovery.impl connector with connection errors

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2882.
--

> too much logging of discovery.impl connector with connection errors
> ---
>
> Key: SLING-2882
> URL: https://issues.apache.org/jira/browse/SLING-2882
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> A topology connector (in the discovery.impl) will be pinged every heartbeat 
> interval. If the connector cannot successfully connect - for example because 
> the URL points to nowhere - there are log.warns issued. These loggings occur 
> too often and should be reduced after a while.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2880) ignore properties that contain ':'

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2880.
--

> ignore properties that contain ':'
> --
>
> Key: SLING-2880
> URL: https://issues.apache.org/jira/browse/SLING-2880
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Blocker
> Fix For: Discovery Impl 1.0.0
>
>
> In DiscoveryServiceImpl.doUpdateProperties filter any properties that contain 
> ':' instead of just 'jcr:primaryType'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2955) Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance twice"

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2955.
--

> Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance 
> twice"
> -
>
> Key: SLING-2955
> URL: https://issues.apache.org/jira/browse/SLING-2955
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> Apparently, adding/removing/adding/removing of instances to/from the cluster 
> cause the following unnecessary (and scary) error - while everything works 
> fine:
> 08.07.2013 17:09:36.513 *ERROR* [Apche Sling JCR Resource Event Queue 
> Processor for path '/'] 
> org.apache.sling.discovery.impl.topology.TopologyViewImpl addInstance: cannot 
> add same instance twice: an 
> InstanceDescription[slindId=23c62a57-2505-410a-9329-7a7f72bdffb4, 
> isLeader=true, isOwn=false, 
> clusterViewId=9249b4de-c6ae-4810-a107-efca0d024a7c, 
> properties={com.adobe.granite.offloading.infrastructure.osgiconsole.path=/system/console,
>  job.consumermanager.whitelist=*, 
> org.apache.sling.instance.endpoints=http://./,http://./}]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2879) Avoid concurrency issues in a cluster by using ResourceUtil.getOrCreateResource

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2879:
---
Fix Version/s: Discovery Impl 1.0.0

> Avoid concurrency issues in a cluster by using 
> ResourceUtil.getOrCreateResource
> ---
>
> Key: SLING-2879
> URL: https://issues.apache.org/jira/browse/SLING-2879
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> org.apache.sling.discovery.impl.common.resource.ResourceHelper.getOrCreateResource/createResource
>  use own code to create a resource. This code is not as stable/fault-tolerant 
> as the ResourceUtil.getOrCreateResource. The latter deals with situations 
> where the underlying repository throws stale item exceptions and such. The 
> ResourceHelper should use ResourceUtil.getOrCreateResource and not reinvent 
> it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2885) Race condition in VotingHandler.promote()

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2885:
---
Fix Version/s: Discovery Impl 1.0.0

> Race condition in VotingHandler.promote()
> -
>
> Key: SLING-2885
> URL: https://issues.apache.org/jira/browse/SLING-2885
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
> Environment: Discovery Impl version: 0.1.0.R1484784
>Reporter: Marcel Reutegger
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
> Attachments: error.log
>
>
> Sometimes on initial startup of Sling Discovery it happens that two threads 
> try to promote the same winning vote at the same time. This leads to a failed 
> commit in the repository. The system seems to be OK after the exception. 
> There is an established view and the (single) cluster node is the leader.
> Please note, this is running on Jackrabbit Oak, but might also happen on 
> Jackrabbit 2.x because the basic issue is two sessions trying to add the same 
> child node.
> See attached log excerpt for more details.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2992) lower isolated mode error to info

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2992:
---
Fix Version/s: Discovery Impl 1.0.0

> lower isolated mode error to info
> -
>
> Key: SLING-2992
> URL: https://issues.apache.org/jira/browse/SLING-2992
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> At startup of discovery.impl, when a node joins a cluster for example and an 
> established view already exists, there is the following error:
> getEstablishedView: the existing established view does not incude the local 
> instance yet! Assming isolated mode.
> this can be lowered to info and typo-fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2880) ignore properties that contain ':'

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2880:
---
Fix Version/s: Discovery Impl 1.0.0

> ignore properties that contain ':'
> --
>
> Key: SLING-2880
> URL: https://issues.apache.org/jira/browse/SLING-2880
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Blocker
> Fix For: Discovery Impl 1.0.0
>
>
> In DiscoveryServiceImpl.doUpdateProperties filter any properties that contain 
> ':' instead of just 'jcr:primaryType'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2895) NPE in VotingHelper.getWinningVoting

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2895:
---
Fix Version/s: Discovery Impl 1.0.0

> NPE in VotingHelper.getWinningVoting
> 
>
> Key: SLING-2895
> URL: https://issues.apache.org/jira/browse/SLING-2895
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Dominique Pfister
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> On shutdown of a Felix container, I get the following stack trace:
> 31.05.2013 13:27:29.632 *ERROR* [pool-6-thread-4] 
> org.apache.sling.commons.scheduler.impl.QuartzScheduler Exception during job 
> execution of 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler@4366e290 : 
> null java.lang.NullPointerException
>   at 
> org.apache.sling.discovery.impl.cluster.voting.VotingHelper.getWinningVoting(VotingHelper.java:145)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.doCheckView(HeartbeatHandler.java:307)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.checkView(HeartbeatHandler.java:277)
>   at 
> org.apache.sling.discovery.impl.common.heartbeat.HeartbeatHandler.run(HeartbeatHandler.java:153)
>   at 
> org.apache.sling.commons.scheduler.impl.QuartzJobExecutor.execute(QuartzJobExecutor.java:56)
>   at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
>   at java.lang.Thread.run(Thread.java:680)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2955) Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance twice"

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2955:
---
Fix Version/s: Discovery Impl 1.0.0

> Unnecessary errors "TopologyViewImpl addInstance: cannot add same instance 
> twice"
> -
>
> Key: SLING-2955
> URL: https://issues.apache.org/jira/browse/SLING-2955
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Discovery Impl 1.0.0
>
>
> Apparently, adding/removing/adding/removing of instances to/from the cluster 
> cause the following unnecessary (and scary) error - while everything works 
> fine:
> 08.07.2013 17:09:36.513 *ERROR* [Apche Sling JCR Resource Event Queue 
> Processor for path '/'] 
> org.apache.sling.discovery.impl.topology.TopologyViewImpl addInstance: cannot 
> add same instance twice: an 
> InstanceDescription[slindId=23c62a57-2505-410a-9329-7a7f72bdffb4, 
> isLeader=true, isOwn=false, 
> clusterViewId=9249b4de-c6ae-4810-a107-efca0d024a7c, 
> properties={com.adobe.granite.offloading.infrastructure.osgiconsole.path=/system/console,
>  job.consumermanager.whitelist=*, 
> org.apache.sling.instance.endpoints=http://./,http://./}]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2968) DiscoveryServiceImpl can make HTTP calls before Sling is properly started up

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2968:
---
Fix Version/s: Discovery Impl 1.0.0

> DiscoveryServiceImpl can make HTTP calls before Sling is properly started up
> 
>
> Key: SLING-2968
> URL: https://issues.apache.org/jira/browse/SLING-2968
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> If the DiscoveryServiceImpl starts up before the application is completely 
> initalized, the first requests fail:
> {code}03.07.2013 14:24:43.821 *ERROR* [127.0.0.1 [1372850683817] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.908 *ERROR* [127.0.0.1 [1372850683908] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:43.996 *ERROR* [127.0.0.1 [1372850683996] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 503
> 03.07.2013 14:24:44.258 *ERROR* [127.0.0.1 [1372850684258] PUT 
> /libs/sling/topology/connector.40a70c95-c7de-4aea-bfdb-419f6329102b.json 
> HTTP/1.1] org.apache.sling.engine.impl.SlingRequestProcessorImpl 
> ServletResolver service missing, cannot service requests , sending status 
> 503{code}
> The solution would be to call the initialization code from inside a 
> {{StartupListener}}, rather than on component activation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2882) too much logging of discovery.impl connector with connection errors

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2882:
---
Fix Version/s: Discovery Impl 1.0.0

> too much logging of discovery.impl connector with connection errors
> ---
>
> Key: SLING-2882
> URL: https://issues.apache.org/jira/browse/SLING-2882
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> A topology connector (in the discovery.impl) will be pinged every heartbeat 
> interval. If the connector cannot successfully connect - for example because 
> the URL points to nowhere - there are log.warns issued. These loggings occur 
> too often and should be reduced after a while.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (SLING-2883) deal with - eg encode - "/" in property names (was: proper encode properties - and filter anything like jcr:created...)

[Stefan Egli (JIRA)]

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

Stefan Egli updated SLING-2883:
---
Fix Version/s: Discovery Impl 1.0.0

> deal with - eg encode - "/" in property names (was: proper encode properties 
> - and filter anything like jcr:created...)
> ---
>
> Key: SLING-2883
> URL: https://issues.apache.org/jira/browse/SLING-2883
> Project: Sling
>  Issue Type: Bug
>  Components: Extensions
>Affects Versions: Discovery Impl 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Discovery Impl 1.0.0
>
>
> properties provided by PropertyProviders in discovery.impl are currently 
> handed 1:1 as name (key) to jcr/repository. This will not work for special 
> characters. A proper encoding must be implemented.
> Similarly, any jcr name including ':' (eg 'jcr:created' etc) must not be 
> treated as a property and not be made visible to the users of the 
> discovery.api - the filter done as a hotfix in SLING-2880 is not sufficient.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3124) SetupServerWizardPage should not hardcode username/password to admin/admin

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3124.
--

> SetupServerWizardPage should not hardcode username/password to admin/admin
> --
>
> Key: SLING-3124
> URL: https://issues.apache.org/jira/browse/SLING-3124
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3622) Support changing jcr:primaryType to/from nt:folder

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3622.
--

> Support changing jcr:primaryType to/from nt:folder
> --
>
> Key: SLING-3622
> URL: https://issues.apache.org/jira/browse/SLING-3622
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> While changing jcr:primaryType in general is supported - when this changes 
> the underlying (vlt) serialization though this will fail. Esp changing 
> nt:folder to sling:Folder does not work currently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3710) Incorrect handling of nt:hierarchyNode instances nested within jcr:content nodes of other nt:hieararchyNode node

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3710.
--

> Incorrect handling of nt:hierarchyNode instances nested within jcr:content 
> nodes of other nt:hieararchyNode node
> 
>
> Key: SLING-3710
> URL: https://issues.apache.org/jira/browse/SLING-3710
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Consider the following content structure
> {code}
> - mapping1 [sling:Mapping]
> \- jcr:content [nt:unstructured]
>  \- par1 [nt:unstructured]
>   \- par2 [nt:unstructured]
> + jcr:title = "Title"
>\- folder [sling:Folder]
> {code}
> FileVault will try to collapse all nodes under the jcr:content child node in 
> the same .content.xml aggregate. However, since it encounters an nt:folder 
> node, it will create the filesystem hierarchy as well, leading to the 
> following filesystem representation:
> {code}
> .
> └── mapping1
> ├── .content.xml
> └── _jcr_content
> └── par2
> └── folder
> └── .content.xml
> {code}
> Since we encounter a plain folder at {{mapping1/_jcr_content/par2}}, we 
> assume it's a nt:folder node and don't look at {{mapping1/.content.xml}} to 
> see if its attributes are serialized there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3768) Be more resilient when .content.xml listing and filesystem disagree on child nodes

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3768.
--

> Be more resilient when .content.xml listing and filesystem disagree on child 
> nodes
> --
>
> Key: SLING-3768
> URL: https://issues.apache.org/jira/browse/SLING-3768
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Right now the child resources of a ResourceProxy are read directly from the 
> .content.xml aggregate if they exist, without taking the filesystem into 
> account. The problems can appear in several ways:
> * An added child node can be spuriously deleted after the sync of its parent 
> node if it is not listed in the .content.xml file
> * Sorting can try to reorder inexistent nodes and fail
> The list is probably incomplete, but what's important is that we 
> augment/sanitize the resource's children based on the filesystem data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3691) Add Cut / Copy / Paste nodes to content navigator

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3691.
--

> Add Cut / Copy / Paste nodes to content navigator
> -
>
> Key: SLING-3691
> URL: https://issues.apache.org/jira/browse/SLING-3691
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Catalin Buzoiu
>Assignee: Stefan Egli
>Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> In day-to-day activities, being able to manipulate nodes in the content 
> navigator with Cut / Copy / Paste operations is really critical.
> /cc [~fvisser]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3777) In NodeTypeRegistry, load rep:residualChildNodeDefinitions children properly

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3777.
--

> In NodeTypeRegistry, load rep:residualChildNodeDefinitions children properly
> 
>
> Key: SLING-3777
> URL: https://issues.apache.org/jira/browse/SLING-3777
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> In the VltNodeTypeRegistry, currently only 2 levels of children of 
> jcr:system/jcr:nodeTypes are loaded - while as for registering the children 
> of rep:residualChildNodeDefinitions the 3rd level is needed - as well as a 
> loop into those children (which currently is missing).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3748) Provide single update site url which works for the latest version

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3748.
--

> Provide single update site url which works for the latest version
> -
>
> Key: SLING-3748
> URL: https://issues.apache.org/jira/browse/SLING-3748
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> As asked by [~kwin] on the dev list ( 
> http://sling-dev.markmail.org/thread/oxfu6vkggjjmp655 ) , we should provide 
> an update site URL which always points to the latest release.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3741) When processing deleted folders, check for a covering aggregate higher in the filesytem hierarchy

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3741.
--

> When processing deleted folders, check for a covering aggregate higher in the 
> filesytem hierarchy
> -
>
> Key: SLING-3741
> URL: https://issues.apache.org/jira/browse/SLING-3741
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: sling3741.zip
>
>
> Minimal scenario reported by [~egli]
> * Create:
> {code}
> grandparent [nt:unstructured]
> \- parent [nt:unstructured]
>  |- child1 [nt:unstructured]
>  \- child2 [nt:unstructured]
> {code}
> * Then change child2 to sling:Folder
> * Changing child2 back to nt:unstructured then causes the deletion of parent 
> (since I delete parent/child2 and parent folders explicitly, as they are no 
> longer needed)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3769) [tooling] Improved wording for content-sync operations

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3769.
--

> [tooling] Improved wording for content-sync operations
> --
>
> Key: SLING-3769
> URL: https://issues.apache.org/jira/browse/SLING-3769
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> The following actions should be renamed:
>  * export content.. -> push to server
>  * import content.. -> pull from server



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3739) No repository found at ... : ClassNotFoundException org.apache.jackrabbit.jcr2spi.Jcr2spiRepositoryFactory

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3739.
--

> No repository found at ... : ClassNotFoundException 
> org.apache.jackrabbit.jcr2spi.Jcr2spiRepositoryFactory
> --
>
> Key: SLING-3739
> URL: https://issues.apache.org/jira/browse/SLING-3739
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
>Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> This seems to be a rehash of SLING-3647. When starting up a server on a 
> freshly launched Eclipse instance I sometimes get this error
> {code}java.lang.IllegalArgumentException: No repository found at 
> http://localhost:4504/
> http://localhost:4504/server/-/jcr:root : java.lang.ClassNotFoundException: 
> org.apache.jackrabbit.jcr2spi.Jcr2spiRepositoryFactory
> http://localhost:4504/crx/-/jcr:root : java.lang.ClassNotFoundException: 
> org.apache.jackrabbit.jcr2spi.Jcr2spiRepositoryFactory
>   at 
> org.apache.sling.ide.jcr.RepositoryUtils.getRepositoryAddress(RepositoryUtils.java:94)
>   at 
> org.apache.sling.ide.jcr.RepositoryUtils.getRepository(RepositoryUtils.java:44)
>   at 
> org.apache.sling.ide.impl.vlt.VltRepository.connect(VltRepository.java:65)
>   at 
> org.apache.sling.ide.impl.vlt.VltRepositoryFactory.connectRepository(VltRepositoryFactory.java:69)
>   at 
> org.apache.sling.ide.eclipse.core.ServerUtil.connectRepository(ServerUtil.java:154)
>   at 
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.start(SlingLaunchpadBehaviour.java:88)
>   at 
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadLaunchConfigurationDelegate.launch(SlingLaunchpadLaunchConfigurationDelegate.java:45)
>   at 
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:858)
>   at 
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:707)
>   at 
> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:700)
>   at 
> org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541)
>   at 
> org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477)
>   at 
> org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367)
>   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53){code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3753) Avoid 'Widget is disposed' errors

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3753.
--

> Avoid 'Widget is disposed' errors
> -
>
> Key: SLING-3753
> URL: https://issues.apache.org/jira/browse/SLING-3753
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> In the Project Explorer, when fiddling around with the content browser by eg 
> copy/pasting, drag-dropping, changing node types etc, it sometimes can occur, 
> that when selecting a (jcr) node, an error box saying "Widget is disposed" 
> shows up.
> Below is the full stacktrace for reference:
> {code}
> org.eclipse.swt.SWTException: Widget is disposed
>   at org.eclipse.swt.SWT.error(SWT.java:4397)
>   at org.eclipse.swt.SWT.error(SWT.java:4312)
>   at org.eclipse.swt.SWT.error(SWT.java:4283)
>   at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
>   at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:573)
>   at org.eclipse.swt.widgets.Widget.getData(Widget.java:845)
>   at 
> org.eclipse.jface.viewers.AbstractTreeViewer.associate(AbstractTreeViewer.java:712)
>   at 
> org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1022)
>   at 
> org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:485)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
>   at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2167)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.internalUpdate(StructuredViewer.java:2150)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:2089)
>   at org.eclipse.jface.viewers.ColumnViewer.update(ColumnViewer.java:561)
>   at org.eclipse.ui.navigator.CommonViewer.update(CommonViewer.java:535)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.update(StructuredViewer.java:2033)
>   at 
> org.eclipse.jface.viewers.StructuredViewer.handleLabelProviderChanged(StructuredViewer.java:1191)
>   at 
> org.eclipse.ui.navigator.CommonViewer.handleLabelProviderChanged(CommonViewer.java:235)
>   at 
> org.eclipse.jface.viewers.ContentViewer$1.labelProviderChanged(ContentViewer.java:97)
>   at 
> org.eclipse.jface.viewers.BaseLabelProvider$1.run(BaseLabelProvider.java:74)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
>   at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
>   at 
> org.eclipse.jface.viewers.BaseLabelProvider.fireLabelProviderChanged(BaseLabelProvider.java:72)
>   at 
> org.eclipse.jface.viewers.DecoratingStyledCellLabelProvider$1.labelProviderChanged(DecoratingStyledCellLabelProvider.java:77)
>   at 
> org.eclipse.ui.internal.decorators.DecoratorManager$1.run(DecoratorManager.java:430)
>   at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
>   at 
> org.eclipse.ui.internal.decorators.DecoratorManager.fireListener(DecoratorManager.java:428)
>   at 
> org.eclipse.ui.internal.decorators.DecorationScheduler$3.runInUIThread(DecorationScheduler.java:530)
>   at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
>   at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
>   at 
> org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
>   at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3976)
>   at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3653)
>   at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
>   at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>   at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
>   at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:140)
>   at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
>   at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
>   at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
>   at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
>   at 
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
>   at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
>   at 

[jira] [Closed] (SLING-3779) Export Wizard does not report all errors

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3779.
--

> Export Wizard does not report all errors
> 
>
> Key: SLING-3779
> URL: https://issues.apache.org/jira/browse/SLING-3779
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> The export wizard does not report errors from runtime exceptions and pressing 
> 'Finish' leads to a confusing state - the wizard is not closed but no error 
> message is displayed. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3774) Allow changing node type even if checks say it's not allowed

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3774.
--

> Allow changing node type even if checks say it's not allowed
> 
>
> Key: SLING-3774
> URL: https://issues.apache.org/jira/browse/SLING-3774
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> I had an example where I wanted to change an nt:folder to a sling:Folder and 
> it complained that that was not possible. But on the server-side it was 
> possible (parent was cq:ClientLibraryFolder). So as a quick fix, allow the 
> user to overwrite whatever the check says on case-by-case basis.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3628) Consider reusing the properties view for the custom JCR properties view

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3628.
--

> Consider reusing the properties view for the custom JCR properties view
> ---
>
> Key: SLING-3628
> URL: https://issues.apache.org/jira/browse/SLING-3628
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> The properties view is something which is already known to the Eclipse 
> developers and it would be good to reuse it. At the same time, it remains to 
> be seen whether we can customize it just like we did for the JCR Properties 
> view.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3690) Cannot create JCR Nodes under a sling:Folder

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3690.
--

> Cannot create JCR Nodes under a sling:Folder
> 
>
> Key: SLING-3690
> URL: https://issues.apache.org/jira/browse/SLING-3690
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Catalin Buzoiu
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> The {{New > Node...}} option is not shown when right-clicking on 
> {{sling:Folder}} nodes, although JCR Nodes should be allowed there.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3778) [tooling] multi valued properties are not correctly exported to the server

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3778.
--

> [tooling] multi valued properties are not correctly exported to the server
> --
>
> Key: SLING-3778
> URL: https://issues.apache.org/jira/browse/SLING-3778
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> Consider the following .content.xml:
> {code}
> 
>  xmlns:sling="http://sling.apache.org/jcr/sling/1.0";
> xmlns:jcr="http://www.jcp.org/jcr/1.0";
> jcr:primaryType="sling:Folder"
> multi="[first]"/>
> {code}
> This content is not correctly exported to the server - the property ends up 
> as a non-mvp.
> A subsequent change of the properties an array with 2 entries results in :
> {code}
> [July 21, 2014 9:28:44 PM CEST] AddOrUpdateNodeCommand -> 
> /apps/beispielapp/foo : JcrResult[ success:false, exception: 
> org.apache.sling.ide.transport.RepositoryException - 
> javax.jcr.ValueFormatException: /apps/beispielapp/foo/multiMultivalue 
> definition of /apps/beispielapp/foo/multi does not match to given value(s).] 
> (92 ms)
> org.apache.sling.ide.transport.RepositoryException: 
> javax.jcr.ValueFormatException: /apps/beispielapp/foo/multiMultivalue 
> definition of /apps/beispielapp/foo/multi does not match to given value(s).
>   at org.apache.sling.ide.impl.vlt.JcrResult.failure(JcrResult.java:33)
>   at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:65)
>   at 
> org.apache.sling.ide.transport.TracingCommand.execute(TracingCommand.java:43)
>   at 
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.execute(SlingLaunchpadBehaviour.java:455)
>   at 
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishContentModule(SlingLaunchpadBehaviour.java:415)
>   at 
> org.apache.sling.ide.eclipse.core.internal.SlingLaunchpadBehaviour.publishModule(SlingLaunchpadBehaviour.java:231)
>   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.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:137)
>   at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
>   at 
> org.apache.sling.ide.eclipse.core.internal.ServerBehaviourDelegateWithModulePublishSupport.publish(ServerBehaviourDelegateWithModulePublishSupport.java:54)
>   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.ValueFormatException: 
> /apps/beispielapp/foo/multiMultivalue definition of 
> /apps/beispielapp/foo/multi does not match to given value(s).
>   at 
> org.apache.jackrabbit.jcr2spi.PropertyImpl.checkIsWritable(PropertyImpl.java:511)
>   at 
> org.apache.jackrabbit.jcr2spi.PropertyImpl.setValue(PropertyImpl.java:117)
>   at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:283)
>   at org.apache.jackrabbit.jcr2spi.NodeImpl.setProperty(NodeImpl.java:269)
>   at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.updateNode(AddOrUpdateNodeCommand.java:304)
>   at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.update(AddOrUpdateNodeCommand.java:99)
>   at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:80)
>   at 
> org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand.execute0(AddOrUpdateNodeCommand.java:1)
>   at org.apache.sling.ide.impl.vlt.JcrCommand.execute(JcrCommand.java:57)
>   ... 12 more
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3764) Incorrect resource processing order - directory artifact processed before primary artifact

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3764.
--

> Incorrect resource processing order - directory artifact processed before 
> primary artifact
> --
>
> Key: SLING-3764
> URL: https://issues.apache.org/jira/browse/SLING-3764
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> It seems that with a specific content  structure a clean publish fails:
> Here's what we have:
> {code}
> en [cq:Page]
>  jcr:content [nt:unstructured]
>   image [nt:unstructured]
> file [nt:file] ! <-- has file.dir/.content.xml
>   jcr:content [nt:resource]
> dam:thumbnails [nt:folder]
>   _dam_thumbnail_319.png [nt:file]
> {code}
> The error comes up when trying to create the nt:resource node at 
> en/jcr:content/image/file/jcr:content since the parent 'file' node does not 
> exist. Debugging the list of changes, it seems that the _jcr_content folder 
> comes in before the .content.xml file belonging to the file folder.
> {code}
> 36 - ModuleFolder [file.dir, content/testproject/_jcr_content/image/file.dir]
> 37 - ModuleFolder [_jcr_content, 
> content/testproject/_jcr_content/image/file.dir/_jcr_content]
> 38 - ModuleFolder [_dam_thumbnails, 
> content/testproject/_jcr_content/image/file.dir/_jcr_content/_dam_thumbnails]
> 39 - ModuleFile [_dam_thumbnail_319.png, 
> content/testproject/_jcr_content/image/file.dir/_jcr_content/_dam_thumbnails/_dam_thumbnail_319.png,
>  1404475333440]
> 40 - ModuleFile [.content.xml, 
> content/testproject/_jcr_content/image/file.dir/.content.xml, 1404475333414]
> {code}
> This is visible when debugging the SlingContentModuleAdapter
> {code}
> [ test002.ui] :  added resource at content/testproject/_jcr_content
> [ test002.ui] :  added resource at content/testproject/_jcr_content/image
> [ test002.ui] :  added resource at 
> content/testproject/_jcr_content/image/file.dir
> [ test002.ui] :  added resource at 
> content/testproject/_jcr_content/image/file.dir/_jcr_content
> [ test002.ui] :  added resource at 
> content/testproject/_jcr_content/image/file.dir/_jcr_content/_dam_thumbnails
> [ test002.ui] :  added resource at 
> content/testproject/_jcr_content/image/file.dir/_jcr_content/_dam_thumbnails/_dam_thumbnail_319.png
> [ test002.ui] :  added resource at 
> content/testproject/_jcr_content/image/file.dir/.content.xml
> [ test002.ui] :  added resource at content/testproject/_jcr_content/image/file
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3740) Remove need to manually install the tooling support bundle

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3740.
--

> Remove need to manually install the tooling support bundle
> --
>
> Key: SLING-3740
> URL: https://issues.apache.org/jira/browse/SLING-3740
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> The initial workflow is a bit strange in terms of how we deploy bundles. We 
> should stop prompting the user to install the tooling bundle and simply do 
> that as part of the first connection to the server.
> The manual controls should stay for now, but in the regular workflow there 
> should be no need to do anything by hand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3765) Sorting node children can trigger a StackOverFlowError

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3765.
--

> Sorting node children can trigger a StackOverFlowError
> --
>
> Key: SLING-3765
> URL: https://issues.apache.org/jira/browse/SLING-3765
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.2
>
> Attachments: screenshot.png, trace-log-snippet.txt
>
>
> Under certain circumstances it is possible for the reordering operation to 
> not succeed and attempt _ad infinitum_ to perform the same reorder operation. 
> There is probably an error in the ordering logic which needs to be fixed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3639.
--

> 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.2
>
>
> 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 
> o

[jira] [Closed] (SLING-3689) JCR Properties shows up empty the first time

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3689.
--

> JCR Properties shows up empty the first time
> 
>
> Key: SLING-3689
> URL: https://issues.apache.org/jira/browse/SLING-3689
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Catalin Buzoiu
>Assignee: Stefan Egli
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.2
>
>
> First time the {{JCR Properties}} view is displayed, it shows up empty, even 
> if there is a node selected in the Project Explorer. Clinking on another node 
> and then back to the original node shows correctly the expected properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (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 closed SLING-3641.
--

> 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.3.4#6332)

[jira] [Closed] (SLING-3660) Refine 'connected' state of a (vlt) repository, cache node types after disconnection properly

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3660.
--

> Refine 'connected' state of a (vlt) repository, cache node types after 
> disconnection properly
> -
>
> Key: SLING-3660
> URL: https://issues.apache.org/jira/browse/SLING-3660
> Project: Sling
>  Issue Type: Improvement
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Currently the ServerUtil.getDefaultRepository always returns a valid 
> repository with which you can do getNodeTypeRegistry() and that in turn 
> connects to the server and loads the node types. This seemed convenient.
> But the problem is, it doesn't give the user any control when to connect to 
> the server and when not. And it will result in connection errors at places 
> where the user maybe didn't intend or know that a connection would be done.
> Hence a new, simpler schema:
>  * when the server is stopped, no 'repository connection' is being 
> established, including for the node type registry
>  ** hence, with a stopped server, the node type registry can be null - hence 
> some actions require adjustments for that situation
>  * when the server is started ('connected to'), the repository is connected 
> and the node type registry loaded
>  ** at this stage the node type registry can be used for various actions, 
> including code completion, property type display
>  * when the server is stopped again, the node type registry is cached and 
> still provided to the various actions (without any server interaction going 
> on though)
> This should be more intuitive and make initial content-browsing in 'offline 
> mode' simpler



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2634) [Tooling] Slingclipse should expose the operations it performs and their results

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2634.
--

> [Tooling] Slingclipse should expose the operations it performs and their 
> results
> 
>
> Key: SLING-2634
> URL: https://issues.apache.org/jira/browse/SLING-2634
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2634-1.diff, SLING-2634-2.diff, 
> SLING-2634-proof-of-design.diff
>
>
> I think that it's important for the user to know what Slingclipse is doing, 
> especially since it uses some heuristics to detect Sling-based projects.
> My first thoughts would be: 
> * from a UI point of view start with something simple like a text-only 
> console . The subclipse console is a good starting point, we can simply log 
> things like
> ADD $SLING_URL $PROJECT/$RESOURCE 200 OK
> REMOVE $SLING_URL $PROJECT/$RESOURCE 500 Internal Server Error
> * from an implementation point of view we could use something like a command 
> pattern ( SaveResource command, DeleteResourceCommand ) . This would have the 
> benefit of allowing this logging easily + encapsulating the operations for 
> batching, handling of offline operations, redo etc.
> Thoughts? I'm willing to look into this, at least for a first iteration.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3237) Refine new node creation workflow

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3237.
--

> Refine new node creation workflow
> -
>
> Key: SLING-3237
> URL: https://issues.apache.org/jira/browse/SLING-3237
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> When creating a new node the dialog unconditionally generates a 
> ${node-name}.xml file. This doesn't really account for whether we are allowed 
> to generate such a node in this location, or whether the node has full or 
> partial coverage.
> This can lead to invalid structures being serialized on disk.
> Originally reported by [~dsuess]



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2636) [Tooling] Add ability to Import from Sling Repository

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2636.
--

> [Tooling] Add ability to Import from Sling Repository
> -
>
> Key: SLING-2636
> URL: https://issues.apache.org/jira/browse/SLING-2636
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Dan Klco
>Assignee: Antonio Sanso
>Priority: Minor
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2636-Import-IN-PROGRESS.diff, 
> SLING-2636-Import-Wizard.diff
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3630) Provide Date/Time Cell-Editor for the properties view

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3630.
--

> Provide Date/Time Cell-Editor for the properties view
> -
>
> Key: SLING-3630
> URL: https://issues.apache.org/jira/browse/SLING-3630
> Project: Sling
>  Issue Type: Task
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Provide a CellEditor for editing date(-time) properties



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3051) [Tooling] add 'new sling bundle' wizard to the slingclipse plugins

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3051.
--

> [Tooling] add 'new sling bundle' wizard to the slingclipse plugins
> --
>
> Key: SLING-3051
> URL: https://issues.apache.org/jira/browse/SLING-3051
> Project: Sling
>  Issue Type: New Feature
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Stefan Egli
>Assignee: Stefan Egli
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Add a wizard which simplifies creation of a new sling bundle, adding it to a 
> launchpad server, all in one wizard. This extends the 
> AbstractNewSlingApplicationWizard. The archetype to be used for this is 
> org.apache.sling:sling-bundle-archetype



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-2637) [Tooling] Ignore Build Output & Eclipse Metadata

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-2637.
--

> [Tooling] Ignore Build Output & Eclipse Metadata
> 
>
> Key: SLING-2637
> URL: https://issues.apache.org/jira/browse/SLING-2637
> Project: Sling
>  Issue Type: Sub-task
>  Components: IDE
>Reporter: Dan Klco
>Assignee: Antonio Sanso
>Priority: Trivial
> Fix For: Sling Eclipse IDE 1.0.0
>
> Attachments: SLING-2637-Ignore-Pattern.diff
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> I prefer to ignore the following patters:
> .project
> .classpath
> target
> .settings
> They can all be rebuilt from the Maven POM



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3694) Full coverage nodes are imported without the XML extension

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3694.
--

> Full coverage nodes are imported without the XML extension
> --
>
> Key: SLING-3694
> URL: https://issues.apache.org/jira/browse/SLING-3694
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.0
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> When importing content from the repository full coverage nodes ( e.g. those 
> with primary type {{sling:OsgiConfig}} ) are imported without extension.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (SLING-3096) New Sling bundle wizard does not detect archetype - drop-down is stuck with 'loading, please wait...'

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3096.
--

> New Sling bundle wizard does not detect archetype - drop-down is stuck with 
> 'loading, please wait...'
> -
>
> Key: SLING-3096
> URL: https://issues.apache.org/jira/browse/SLING-3096
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Robert Munteanu
>Assignee: Robert Munteanu
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:421)
> at 
> org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at 
> org.eclipse.ui.internal.progress.ProgressMonitorJobsDialog.run(ProgressMonitorJobsDialog.java:275)
> at 
> org.eclipse.ui.internal.progress.ProgressManager.run(ProgressManager.java:1162)
> at 
> org.apache.sling.ide.eclipse.ui.wizards.np.ChooseArchetypeWizardPage.initialize(ChooseArchetypeWizardPage.java:179)
> at 
> org.apache.sling.ide.eclipse.ui.wizards.np.ChooseArchetypeWizardPage.createControl(ChooseArchetypeWizardPage.java:159)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:174)
> at 
> org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:736)
> at 
> org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:608)
> at org.eclipse.jface.window.Window.create(Window.java:432)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1104)
> at 
> org.eclipse.ui.internal.actions.NewWizardShortcutAction.run(NewWizardShortcutAction.java:122)
> at 
> org.eclipse.ui.internal.quickaccess.WizardElement.execute(WizardElement.java:41)
> at 
> org.eclipse.ui.internal.quickaccess.SearchField$2.handleElementSelected(SearchField.java:164)
> at 
> org.eclipse.ui.internal.quickaccess.QuickAccessContents.handleSelection(QuickAccessContents.java:438)
> at 
> org.eclipse.ui.internal.quickaccess.QuickAccessContents.access$0(QuickAccessContents.java:428)
> at 
> org.eclipse.ui.internal.quickaccess.QuickAccessContents$1.keyPressed(QuickAccessContents.java:472)
> at 
> org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:167)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1428)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:829)
> at 
> org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3236)
> at org.eclipse.swt.widgets.Text.gtk_key_press_event(Text.java:1763)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2096)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5467)
> at org.eclipse.swt.widgets.Text.windowProc(Text.java:2702)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4569)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8707)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1243)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native 
> Method)
> at 
> org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2287)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3361)
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at 
> org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at 
> org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at 
> org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at 
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at 
> org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at 
> org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at 
> org.eclipse.core.runtime.internal.adaptor

[jira] [Closed] (SLING-3663) IllegalArgumentException when creating a bundle - Add and remove cannot be both null/empty

[Stefan Egli (JIRA)]

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

Stefan Egli closed SLING-3663.
--

> IllegalArgumentException when creating a bundle - Add and remove cannot be 
> both null/empty
> --
>
> Key: SLING-3663
> URL: https://issues.apache.org/jira/browse/SLING-3663
> Project: Sling
>  Issue Type: Bug
>  Components: IDE
>Reporter: Stefan Egli
>Assignee: Stefan Egli
>Priority: Critical
> Fix For: Sling Eclipse IDE 1.0.0
>
>
> Following stacktrace occured when creating a new project:
> {code}
> java.lang.IllegalArgumentException: Add and remove cannot both be null/empty
> at 
> org.eclipse.wst.server.core.internal.Server.canModifyModules(Server.java:2461)
> at 
> org.eclipse.wst.server.core.internal.ServerWorkingCopy.modifyModules(ServerWorkingCopy.java:544)
> at 
> org.apache.sling.ide.eclipse.ui.wizards.AbstractNewSlingApplicationWizard.deployProjectsOnServer(AbstractNewSlingApplicationWizard.java:183)
> at 
> org.apache.sling.ide.eclipse.ui.wizards.AbstractNewSlingApplicationWizard$3.execute(AbstractNewSlingApplicationWizard.java:131)
> at 
> org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at 
> org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118)
> at 
> org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1028)
> at 
> org.apache.sling.ide.eclipse.ui.wizards.AbstractNewSlingApplicationWizard.performFinish(AbstractNewSlingApplicationWizard.java:127)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)