Re: TopologyConnectorServlet
On 10 October 2013 05:40, Felix Meschberger fmesc...@adobe.com wrote: Hi Am 09.10.2013 um 09:05 schrieb Ian Boston: Hi, On 9 October 2013 16:21, Felix Meschberger fmesc...@adobe.com wrote: Hi Am 08.10.2013 um 10:40 schrieb Ian Boston: Hi, The whitelist configuration in this servlet is causing some problems where the contents of the whitelist is potentially large and changing, since it requires constant re-configuration. What is the problem with that ? When the whitelist in the central discovery endpoint depends on the topology itself, it causes production deployment problems, especially when the configuration of the end point and the management of the topology of the production deployment are managed by different roles within the organisation. This is typical of many organisations. Engineers don't manage operations and TechOps don't manage engineering. Normally configuration would be managed by TechOps but Fully agreed ! Which is exactly the reason why conceptually we have to separate development from deployment and which is why configuration *is* in fact a deployment issue and not a development issue. with Sling that doesn't appear to be the case. How come ? That is not the intent of how Sling should be used. Many systems that are managed by TechOps are configured by files on disk (eg Apache httpd.conf etc). As a result much of the tooling to manage production environments works best managing those files. Things that are not files on disk, are generally considered part of the application, unless the application itself is a TechOps application (eg Ldap). Sling (and tbh many Java applications) puts its configuration into database files or repositories, accessed only once the application is running which means TechOps cant use standard tools (Puppet, Cactus etc) to manage the application. TechOps have to use application level tooling and build systems (mvn) to interact with the configuration or take undocumented routes to configuring the application (eg manipulating the private Felix configuration files). Because OSGi makes it easy to configure components, applications based on Sling have large volumes of configuration, much of which is not so much about deployment, and more about configuring the application. In real life, that tends to be poorly documented and the effort level required for TechOps to write build, deploy and maintain those configuration files is too high. Hence the developer teams provide them as part of application startup for TechOps to deploy. There is nothing wrong with this, provided the configuration does not depend on the deployment topology. When it does, it falls between the gaps. There are 2 potential solutions: A. Create something along the lines of Puppet or Cactus to bring deployment level Sling configuration into line with those systems. (or whatever the chosen deployment tooling is). B. Ensure that configuration performed in Sling is not dependent on the deployment architecture and topology so that 99% of the configuration can be used unchanged when deploying 10 or 1 instances. In this case, B is a lot less effort than A. A is not impossible, but it is not as simple as writing a puppet module with a few curl operations, for a start, deployment should be achievable with the application not running. In short, *if* all configuration is a deployment issue, then it should work with existing deployment tooling. Best Regards Ian
Re: JIRA access
Bertrand, Felix, Thanks, I'll hopefully take a look soon if I make some free time(!) around project work. I've been developing with CQ for awhile have become a fan of Sling itself, so will be nice to contribute :) Best Dave On 10/10/2013 05:40, Felix Meschberger fmesc...@adobe.com wrote: Hi Or better yet, create new issues pertaining to concrete tests you add. BTW: Thanks a lot for taking a stab. This is very much appreciated. Regards Felix Am 09.10.2013 um 07:19 schrieb Bertrand Delacretaz: Hi, On Wed, Oct 9, 2013 at 4:04 PM, David Moloney david.molo...@lbi.com wrote: ...I was hoping to cut my teeth contributing to Sling by looking into integration tests for SLING-999... Cool! AFAIK that's still relevant. Thought possibly I should request contributor access here, or should I create a patch first attach?... You can create and attach a patch, and we can then grant you contributor status as needed. Have fun! -Bertrand Confidentiality notice This communication is from LBi Ltd, a private limited company registered in Scotland with registered number SC177425 having its registered office at 51 Timberbush, Edinburgh, EH6 6QH. DigitasLBi is a trading name of LBi Limited. This electronic message contains information which may be privileged and confidential. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic message in error, please notify us by telephone or e-mail as above immediately.
Jenkins build is back to normal : sling-trunk-1.7 #328
See https://builds.apache.org/job/sling-trunk-1.7/328/changes
Jenkins build became unstable: sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1960
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1960/
[jira] [Created] (SLING-3158) Warning Property scheduler.runOn ignored for schedule when no property is set
Carsten Ziegeler created SLING-3158: --- Summary: Warning Property scheduler.runOn ignored for schedule when no property is set Key: SLING-3158 URL: https://issues.apache.org/jira/browse/SLING-3158 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Scheduler 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.4.2 When no runOn property is set for a whiteboard scheduler, the warning Property scheduler.runOn ignored for schedule is put out - in this case no warning should be logged as a missing property is fine -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3158) Warning Property scheduler.runOn ignored for schedule when no property is set
[ https://issues.apache.org/jira/browse/SLING-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3158. - Resolution: Fixed Warning Property scheduler.runOn ignored for schedule when no property is set --- Key: SLING-3158 URL: https://issues.apache.org/jira/browse/SLING-3158 Project: Sling Issue Type: Bug Components: Commons Affects Versions: Commons Scheduler 2.4.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Commons Scheduler 2.4.2 When no runOn property is set for a whiteboard scheduler, the warning Property scheduler.runOn ignored for schedule is put out - in this case no warning should be logged as a missing property is fine -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3106) Do not try to sync version control files
[ https://issues.apache.org/jira/browse/SLING-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3106. Resolution: Fixed Assignee: Robert Munteanu Reported fixed Do not try to sync version control files Key: SLING-3106 URL: https://issues.apache.org/jira/browse/SLING-3106 Project: Sling Issue Type: Bug Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Priority: Minor Fix For: Sling Eclipse IDE 1.0.0 If I create a sling content module which contains version control-private files like .svn, these are synced to the repository. Instead, we should ignore these files. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791349#comment-13791349
]
Robert Munteanu commented on SLING-3019:
[~cziegler], [~egli] - I've taken a look at the implementation and I'm
wondering why we make Sling update the bundle based on the local directory,
instead of building the jar on the client side and then uploading it.
Thinking in that direction, couldn't we reuse the Felix/JCR Install mechanisms
for uploading bundles?
The reason I'm asking is that this incremental deploy only works on localhost,
and for remote deployments we can only use Maven deployment, which is IMO too
slow ( and also still not done right, see SLING-3134 for instance).
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Updated] (SLING-3097) Track bundle deployment operations in the Sling console view
[ https://issues.apache.org/jira/browse/SLING-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3097: --- Assignee: Robert Munteanu Track bundle deployment operations in the Sling console view Key: SLING-3097 URL: https://issues.apache.org/jira/browse/SLING-3097 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 To make it transparent to the user, bundle deployment operations should be recorded in the Sling console, just like content sync operations. -- This message was sent by Atlassian JIRA (v6.1#6144)
Jenkins build is back to stable : sling-trunk-1.6 #1961
See https://builds.apache.org/job/sling-trunk-1.6/1961/changes
Jenkins build is back to stable : sling-trunk-1.6 » Apache Sling Launchpad Testing WAR version #1961
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.launchpad.testing-war/1961/
Build failed in Jenkins: sling-trunk-1.7 #329
See https://builds.apache.org/job/sling-trunk-1.7/329/ -- [...truncated 298 lines...] Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:335) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) ... 14 more Caused by: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 33 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: E204899: Cannot create new file '/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) ... 32 more Caused by: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407) ... 34 more Caused by: svn: E204899: Cannot create new file '/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.createEmptyFile(SVNFileUtil.java:346) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.createVersionedDirectory(SVNAdminArea14.java:1553) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory.doCreateVersionedDirectory(SVNAdminArea16Factory.java:30) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.createVersionedDirectory(SVNAdminAreaFactory.java:241) at org.tmatesoft.svn.core.internal.wc.SVNWCManager.ensureAdminAreaExists(SVNWCManager.java:428) at org.tmatesoft.svn.core.internal.wc.SVNUpdateEditor.addDir(SVNUpdateEditor.java:762) at org.tmatesoft.svn.core.internal.wc.SVNCancellableEditor.addDir(SVNCancellableEditor.java:84) at org.tmatesoft.svn.core.internal.io.dav.handlers.DAVEditorHandler.startElement(DAVEditorHandler.java:326) at org.tmatesoft.svn.core.internal.io.dav.handlers.BasicDAVHandler.startElement(BasicDAVHandler.java:89) at
[jira] [Commented] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791365#comment-13791365
]
Carsten Ziegeler commented on SLING-3019:
-
Sure, we could upload the whole jar, but this requires more work to do in
Eclipse - instead of just doing a simple ping to the server.
I believe that in the local case, the current mechanism is a little bit faster
(we could even improve and create the jar just in memory).
The alternative would be to post against the web console and let the web
console do the stuff (install or update, refresh packages etc.) - this would be
the same as the maven sling plugin does ootb
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (SLING-3097) Track bundle deployment operations in the Sling console view
[ https://issues.apache.org/jira/browse/SLING-3097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3097. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1530912 for the local deployment only, as the Maven deployment opens its own console. Track bundle deployment operations in the Sling console view Key: SLING-3097 URL: https://issues.apache.org/jira/browse/SLING-3097 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 To make it transparent to the user, bundle deployment operations should be recorded in the Sling console, just like content sync operations. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791349#comment-13791349
]
Robert Munteanu edited comment on SLING-3019 at 10/10/13 10:54 AM:
---
[~cziegeler], [~egli] - I've taken a look at the implementation and I'm
wondering why we make Sling update the bundle based on the local directory,
instead of building the jar on the client side and then uploading it.
Thinking in that direction, couldn't we reuse the Felix/JCR Install mechanisms
for uploading bundles?
The reason I'm asking is that this incremental deploy only works on localhost,
and for remote deployments we can only use Maven deployment, which is IMO too
slow ( and also still not done right, see SLING-3134 for instance).
was (Author: rombert):
[~cziegler], [~egli] - I've taken a look at the implementation and I'm
wondering why we make Sling update the bundle based on the local directory,
instead of building the jar on the client side and then uploading it.
Thinking in that direction, couldn't we reuse the Felix/JCR Install mechanisms
for uploading bundles?
The reason I'm asking is that this incremental deploy only works on localhost,
and for remote deployments we can only use Maven deployment, which is IMO too
slow ( and also still not done right, see SLING-3134 for instance).
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791377#comment-13791377
]
Robert Munteanu commented on SLING-3019:
Fair enough.
I think that I'd like to have two mechanisms - one which works on local
directories, and is simpler, and one which works by POSTing jars, without going
through Maven. But that's another discussion.
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Created] (SLING-3159) Never try to install bundles from local directory if the support bundle is not installed
Robert Munteanu created SLING-3159: -- Summary: Never try to install bundles from local directory if the support bundle is not installed Key: SLING-3159 URL: https://issues.apache.org/jira/browse/SLING-3159 Project: Sling Issue Type: Bug Reporter: Robert Munteanu Priority: Critical Fix For: Sling Eclipse IDE 1.0.0 As a user, if I check 'Install bundles directly from local directory' but do not install the support bundle, when trying to deploy I bundle I get a success message ( the POST is successful ) but the bundle is not deployed. I only get a hint on the servers view that the status is 404. I should be prompted that the support bundle is not installed and asked to install it. Or maybe the bundle should be automatically installed. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791395#comment-13791395
]
Stefan Egli commented on SLING-3019:
bq. I think that I'd like to have two mechanisms
+1
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
Build failed in Jenkins: sling-trunk-1.6 #1963
See https://builds.apache.org/job/sling-trunk-1.6/1963/changes Changes: [rombert] SLING-3097 - Track bundle deployment operations in the Sling console view Add a TracingOsgiClient which optionally wraps the main OsgiClient, if the EventAdmin is not available. The Maven deployment was not instrumented to display in the Sling console since it opens its own console when running. [rombert] SLING-3097 - Track bundle deployment operations in the Sling console view Deleted empty SlingConsole class. -- [...truncated 14609 lines...] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Servlet Resolver . SUCCESS [8.581s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Default GET Servlets . SUCCESS [6.003s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Default POST Servlets SUCCESS [9.201s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Compat Servlets .. SUCCESS [8.229s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting Implementation API . SUCCESS [3.647s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting Core implementation SUCCESS [9.433s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting JavaScript Support . SUCCESS [29.909s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Scripting JSP Support SUCCESS [9.728s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSP Tag Library .. SUCCESS [4.986s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling JSP Standard Tag Library . SUCCESS [4.037s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Adapter Manager Implementation ... SUCCESS [4.229s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Bundle Resource Provider . SUCCESS [4.958s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery API SUCCESS [3.157s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Resource-Based Discovery Service . FAILURE [2:55.251s] Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery Support Bundle . SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Discovery Standalone Implementation .. SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Event Support SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Filesystem Resource Provider . SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling javax.activation bundle .. SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Settings . SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Thread Dumper SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Web Console Branding . SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Web Console Security Provider SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Groovy Extensions SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Explorer . SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check Core SKIPPED Oct 10, 2013 11:19:32 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Apache Sling Health Check Samples . SKIPPED Oct 10, 2013 11:19:32 AM
Build failed in Jenkins: sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #1963
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/1963/ -- Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building Apache Sling Resource-Based Discovery Service 1.0.1-SNAPSHOT Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ org.apache.sling.discovery.impl --- [INFO] Deleting https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:38 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ org.apache.sling.discovery.impl --- Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (set-bundle-required-execution-environment) @ org.apache.sling.discovery.impl --- [INFO] Executing tasks main: [INFO] Executed tasks Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.4:process (default) @ org.apache.sling.discovery.impl --- Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.6:resources (default-resources) @ org.apache.sling.discovery.impl --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 1 resource [INFO] Copying 3 resources Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-antrun-plugin:1.7:run (check-memory-task) @ org.apache.sling.discovery.impl --- [INFO] Executing tasks main: [echo] WARNING (SLING-443/SLING-1782) ** [echo] On most platforms, you'll get OutOfMemoryErrors when building unless you set [echo] on 32bit platforms: MAVEN_OPTS=-Xmx256M -XX:MaxPermSize=256M, see SLING-443 [echo] on 64bit platforms: MAVEN_OPTS=-Xmx512M -XX:MaxPermSize=512M, see SLING-1782 [echo] ** [INFO] Executed tasks Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:39 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:compile (default-compile) @ org.apache.sling.discovery.impl --- [INFO] Compiling 30 source files to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/classes Oct 10, 2013 11:16:40 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Oct 10, 2013 11:16:40 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-scr-plugin:1.14.0:scr (generate-scr-scrdescriptor) @ org.apache.sling.discovery.impl --- [INFO] Generating 1 MetaType Descriptors in https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/metatype/org.apache.sling.discovery.impl.Config.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/org.apache.sling.discovery.impl.cluster.ClusterViewServiceImpl.xml [INFO] Writing 1 Service Component Descriptors to https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/ws/target/scr-plugin-generated/OSGI-INF/org.apache.sling.discovery.impl.cluster.voting.VotingHandler.xml [INFO] Writing 1 Service Component Descriptors to
Jenkins build became unstable: sling-trunk-1.7 » Apache Sling Sample Integration Tests #330
See https://builds.apache.org/job/sling-trunk-1.7/org.apache.sling$org.apache.sling.testing.samples.integrationtests/330/
[jira] [Commented] (SLING-3019) Provide a mechanism to install a bundle based on a directory
[
https://issues.apache.org/jira/browse/SLING-3019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13791403#comment-13791403
]
Carsten Ziegeler commented on SLING-3019:
-
Yes, I think we should go the full way and enhance the current install bundle
to also take a jar via post and install it - so we won't rely on any
additional stuff being there (like the web console etc) and the only
difference between those two mechanisms would be that the local case first
creates the jar and performs the action while the remote gets the jar and
performs the exact same action.
Provide a mechanism to install a bundle based on a directory
Key: SLING-3019
URL: https://issues.apache.org/jira/browse/SLING-3019
Project: Sling
Issue Type: New Feature
Components: IDE
Reporter: Carsten Ziegeler
Assignee: Carsten Ziegeler
With an IDE integration and incremental builds, it would be great to have a
mechanism to install/update a bundle based on the output directory of a
project.
I'll start with a prototype of a bundle which receives post requests
containing the path of a local directory. The servlet will then either
install or update the bundle from that directory
For this to work, the scr descriptor files of a project should go into a
bundle. So configure the scr plugin like this:
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-scr-plugin/artifactId
configuration
outputDirectory${project.build.directory}/classes/outputDirectory
/configuration
/plugin
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Resolved] (SLING-3110) Add key binding for importing content from the repository
[ https://issues.apache.org/jira/browse/SLING-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu resolved SLING-3110. Resolution: Fixed Fixed in http://svn.apache.org/viewvc?view=revisionrevision=1530933 , by adding a Ctrl+Shift+I keybinding. Add key binding for importing content from the repository - Key: SLING-3110 URL: https://issues.apache.org/jira/browse/SLING-3110 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Since importing content from the repository will be an operation which will happen quite often, it's important to streamline it. Therefore, add a keybinding to it and try hard to infer from the selection to which project it refers to. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3110) Add key binding for importing content from the repository
[ https://issues.apache.org/jira/browse/SLING-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3110: --- Assignee: Robert Munteanu Add key binding for importing content from the repository - Key: SLING-3110 URL: https://issues.apache.org/jira/browse/SLING-3110 Project: Sling Issue Type: Improvement Components: IDE Reporter: Robert Munteanu Assignee: Robert Munteanu Fix For: Sling Eclipse IDE 1.0.0 Since importing content from the repository will be an operation which will happen quite often, it's important to streamline it. Therefore, add a keybinding to it and try hard to infer from the selection to which project it refers to. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3160) Creating ResourceResolverFactory as ServiceFactory leads to multiple MapEntries creation
Chetan Mehrotra created SLING-3160: -- Summary: Creating ResourceResolverFactory as ServiceFactory leads to multiple MapEntries creation Key: SLING-3160 URL: https://issues.apache.org/jira/browse/SLING-3160 Project: Sling Issue Type: Bug Components: ResourceResolver Affects Versions: Resource Resolver 1.1.0 Reporter: Chetan Mehrotra With SLING-2944 ResourceResolverFactory is now being created as ServiceFactory leading to multiple instances being created for each consuming bundle. Each ResourceResolverFactoryImpl instance keeps a reference to MapEntries which internally spawns a thread to keep the entries upto date. Due to creation of multiple instances there are multiple MapEntries Update thread getting created which is probably not desirable. I think all the ResourceResolverFactoryImpl must *share* a singleton state where only single instance of MapEntries gets created -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3160) Creating ResourceResolverFactory as ServiceFactory leads to multiple MapEntries creation
[ https://issues.apache.org/jira/browse/SLING-3160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chetan Mehrotra updated SLING-3160: --- Attachment: threaddump.txt Thread dump where you can see 18 threads of MapEntries Update getting created possibly for each bundle which asks for ResourceResolverFactory Creating ResourceResolverFactory as ServiceFactory leads to multiple MapEntries creation Key: SLING-3160 URL: https://issues.apache.org/jira/browse/SLING-3160 Project: Sling Issue Type: Bug Components: ResourceResolver Affects Versions: Resource Resolver 1.1.0 Reporter: Chetan Mehrotra Attachments: threaddump.txt With SLING-2944 ResourceResolverFactory is now being created as ServiceFactory leading to multiple instances being created for each consuming bundle. Each ResourceResolverFactoryImpl instance keeps a reference to MapEntries which internally spawns a thread to keep the entries upto date. Due to creation of multiple instances there are multiple MapEntries Update thread getting created which is probably not desirable. I think all the ResourceResolverFactoryImpl must *share* a singleton state where only single instance of MapEntries gets created -- This message was sent by Atlassian JIRA (v6.1#6144)
Build failed in Jenkins: sling-trunk-1.7 #331
See https://builds.apache.org/job/sling-trunk-1.7/331/ -- [...truncated 286 lines...] at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: hudson.scm.subversion.UpdaterException: failed to perform svn update ... 15 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:335) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1289) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:837) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:507) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:157) ... 14 more Caused by: svn: E175002: REPORT /repos/asf/!svn/vcc/default failed at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) ... 33 more Caused by: org.tmatesoft.svn.core.SVNException: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default' svn: E204899: Cannot create new file '/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:748) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) ... 32 more Caused by: svn: E204899: REPORT request failed on '/repos/asf/!svn/vcc/default' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:154) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:97) at org.tmatesoft.svn.core.SVNErrorMessage.wrap(SVNErrorMessage.java:407) ... 34 more Caused by: svn: E204899: Cannot create new file '/home/hudson/jenkins-slave/workspace/sling-trunk-1.7/trunk/samples/espblog/src/main/java/org/apache/sling/samples/espblog/.svn/lock' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:171) at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:126) at org.tmatesoft.svn.core.internal.wc.SVNFileUtil.createEmptyFile(SVNFileUtil.java:346) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea14.createVersionedDirectory(SVNAdminArea14.java:1553) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminArea16Factory.doCreateVersionedDirectory(SVNAdminArea16Factory.java:30) at org.tmatesoft.svn.core.internal.wc.admin.SVNAdminAreaFactory.createVersionedDirectory(SVNAdminAreaFactory.java:241) at org.tmatesoft.svn.core.internal.wc.SVNWCManager.ensureAdminAreaExists(SVNWCManager.java:428) at org.tmatesoft.svn.core.internal.wc.SVNUpdateEditor.addDir(SVNUpdateEditor.java:762)
Jenkins build is back to normal : sling-trunk-1.6 » Apache Sling Resource-Based Discovery Service #1964
See https://builds.apache.org/job/sling-trunk-1.6/org.apache.sling$org.apache.sling.discovery.impl/1964/
Jenkins build is back to normal : sling-trunk-1.6 #1964
See https://builds.apache.org/job/sling-trunk-1.6/1964/changes
[jira] [Resolved] (SLING-3028) Support for progress tracking of jobs and keeping jobs
[ https://issues.apache.org/jira/browse/SLING-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3028. - Resolution: Fixed Support for progress tracking of jobs and keeping jobs -- Key: SLING-3028 URL: https://issues.apache.org/jira/browse/SLING-3028 Project: Sling Issue Type: Improvement Components: Extensions Reporter: Victor Saar Assignee: Carsten Ziegeler Labels: jobs Fix For: Extensions Event 3.3.0 Attachments: SLING-3028.patch For long-running jobs, it would be useful to have some means to track progress, which can be shown in a console for the user. This should include the following: * ETA * Completeness value computed from (optional, defaults to 1.0) max and current value (e.g. 42% or 23/100) * Log output stream for detailed progress information * Failure reason in case job failed AFAICS this requires a few changes to the existing implementation: * Jobs need additional support for setting properties, e.g. max and current progress value * Jobs need to be kept at least for a while after they completed/failed to give access to failure information/log stream -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3139) Provide a way to schedule jobs
[ https://issues.apache.org/jira/browse/SLING-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3139. - Resolution: Fixed Provide a way to schedule jobs -- Key: SLING-3139 URL: https://issues.apache.org/jira/browse/SLING-3139 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 3.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.3.0 The current way of scheduling jobs is not very user friendly: it requires to send an event via event admin. We should add a java api to create scheduled job creation. In addition, we could add a new queue type: maintenance queue which is an order queue with the difference of running jobs exactly at the point of time when they are created. So a scheduled maintenance job is executed exactly at the scheduled time - unless another job is currently running. Apart from starting such jobs, stopping a job would be another nice addition -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (SLING-3041) Mark job as failed if async job consumer disappears
[ https://issues.apache.org/jira/browse/SLING-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carsten Ziegeler resolved SLING-3041. - Resolution: Fixed Mark job as failed if async job consumer disappears --- Key: SLING-3041 URL: https://issues.apache.org/jira/browse/SLING-3041 Project: Sling Issue Type: Improvement Components: Extensions Affects Versions: Extensions Event 3.2.0 Reporter: Carsten Ziegeler Assignee: Carsten Ziegeler Fix For: Extensions Event 3.3.0 If a job consumer is processing events async and goes down while doing so, the jobs should be marked as failed. Otherwise the queue keeps these jobs in the async state -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3161) SlingIDE Import Content wizard should respect .vltignore filess
Justin Edelson created SLING-3161: - Summary: SlingIDE Import Content wizard should respect .vltignore filess Key: SLING-3161 URL: https://issues.apache.org/jira/browse/SLING-3161 Project: Sling Issue Type: Bug Reporter: Justin Edelson Fix For: Sling Eclipse IDE 1.0.0 Given in repository: /apps/foo/install /apps/foo/install/.vltignore = *.jar /apps/foo/install/foo.jar Then running import content should not copy foo.jar into the local working copy. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3161) SlingIDE Import Content wizard should respect .vltignore filess
[ https://issues.apache.org/jira/browse/SLING-3161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3161: -- Component/s: IDE SlingIDE Import Content wizard should respect .vltignore filess --- Key: SLING-3161 URL: https://issues.apache.org/jira/browse/SLING-3161 Project: Sling Issue Type: Bug Components: IDE Reporter: Justin Edelson Fix For: Sling Eclipse IDE 1.0.0 Given in repository: /apps/foo/install /apps/foo/install/.vltignore = *.jar /apps/foo/install/foo.jar Then running import content should not copy foo.jar into the local working copy. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3162) Sling virtual resource tree only appears in project when in Java EE perspective, not Java perspective
Justin Edelson created SLING-3162: - Summary: Sling virtual resource tree only appears in project when in Java EE perspective, not Java perspective Key: SLING-3162 URL: https://issues.apache.org/jira/browse/SLING-3162 Project: Sling Issue Type: Bug Components: IDE Reporter: Justin Edelson Priority: Minor This requirement doesn't seem intuitive to me as Sling != Java EE :) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (SLING-3163) XML Namespaces shouldn't appear in JCR Properties List
Justin Edelson created SLING-3163: - Summary: XML Namespaces shouldn't appear in JCR Properties List Key: SLING-3163 URL: https://issues.apache.org/jira/browse/SLING-3163 Project: Sling Issue Type: Bug Components: IDE Reporter: Justin Edelson Fix For: Sling Eclipse IDE 1.0.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SLING-3163) XML Namespaces shouldn't appear in JCR Properties List
[ https://issues.apache.org/jira/browse/SLING-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Edelson updated SLING-3163: -- Description: by which I mean the xmlns:* properties XML Namespaces shouldn't appear in JCR Properties List -- Key: SLING-3163 URL: https://issues.apache.org/jira/browse/SLING-3163 Project: Sling Issue Type: Bug Components: IDE Reporter: Justin Edelson Fix For: Sling Eclipse IDE 1.0.0 by which I mean the xmlns:* properties -- This message was sent by Atlassian JIRA (v6.1#6144)
