[GitHub] [sling-org-apache-sling-starter] dalbani commented on pull request #216: Use Oak only instead of Sling
dalbani commented on PR #216: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/216#issuecomment-1692523815 Sorry, this PR was a mistake, I clicked on the wrong button -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] dalbani closed pull request #216: Use Oak only instead of Sling
dalbani closed pull request #216: Use Oak only instead of Sling URL: https://github.com/apache/sling-org-apache-sling-starter/pull/216 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [sling-org-apache-sling-starter] dalbani opened a new pull request, #216: Use Oak only instead of Sling
dalbani opened a new pull request, #216: URL: https://github.com/apache/sling-org-apache-sling-starter/pull/216 (no comment) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@sling.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Sling IDE Tooling 2.0 prerelease?
Hi, We had a lot of fixes and improvements applied to the Sling IDE tooling since the last release [1]. We released version 1.2.0 in January 2018 (!) and we had 21 Jira issues closed since. In the meantime we made a large refactoring of the modules so there may be some uncertainty with regards to how well things still work in corner cases. I think we could kick off a pre-release with the 2.0.0-beta-1 version just to put this out there for our users. Thoughts? Thanks, Robert [1]: https://issues.apache.org/jira/issues/?jql=project%20%3D%20SLING%20AND%20fixVersion%20%3D%20%22Sling%20Eclipse%20IDE%202.0.0%22%20AND%20resolution%20IS%20NOT%20EMPTY
[jira] [Commented] (SLING-3827) Unable to create nodes with protected properties, e.g. rep:User
[
https://issues.apache.org/jira/browse/SLING-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758589#comment-17758589
]
Konrad Windszus commented on SLING-3827:
Not in the near future, but with more recent FileVault version it should be
easier to generate compliant DocView (as described in
https://jackrabbit.apache.org/filevault/authorizables.html and
https://jackrabbit.apache.org/filevault/acls.html)
> Unable to create nodes with protected properties, e.g. rep:User
> ---
>
> Key: SLING-3827
> URL: https://issues.apache.org/jira/browse/SLING-3827
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.4
>Reporter: Robert Munteanu
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 2.0.0
>
>
> I tried to create a user using the tooling, and I get back an exception:
> The debug trace is
> {noformat}
> | Worker-886 | 2014-08-06 18:10:22.590 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | update | 96 |
> Created node at /home/users/system/blabla with primaryType rep:User |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateMixins
> | 347 | Added new mixin rep:AccessControllable to node at path
> /home/users/system/blabla |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateNode |
> 298 | Setting property rep:principalName with value
> org.apache.jackrabbit.spi.commons.value.QValueValue@b7c2c87f (raw =
> mcm-service) on node at /home/users/system/blabla |
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-3591) Unable to delete all nodes of a full coverage aggregate
[ https://issues.apache.org/jira/browse/SLING-3591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3591: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Unable to delete all nodes of a full coverage aggregate > --- > > Key: SLING-3591 > URL: https://issues.apache.org/jira/browse/SLING-3591 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Robert Munteanu >Priority: Minor > > With the fix for SLING-3590 it is no longer possible to delete all nodes of a > full coverage aggregate. Pushing to 1.0.2 since > - it is not an usual scenario > - it requires some changes to the Sling IDE Resource API, which I'd like to > defer for now. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3556) The Filter API should work on resources, not on filesystem-based paths
[ https://issues.apache.org/jira/browse/SLING-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3556: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > The Filter API should work on resources, not on filesystem-based paths > -- > > Key: SLING-3556 > URL: https://issues.apache.org/jira/browse/SLING-3556 > Project: Sling > Issue Type: Improvement > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.0 >Reporter: Robert Munteanu >Priority: Major > Attachments: SLING-3556-wip-1.patch > > > Today the SlingLaunchpadBehaviour encapsulates lot of knowledge about what it > takes to find out if a resource should be filtered or not ( also visited in > the context of SLING-3122 ). This knowledge should be rooted in the Filter > API, which currently takes paths. > Instead, it should take a ResourceProxy instance, and delegate to the > SerializationKindManager to see what the serialization policy is, so that it > can determine the repository path. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3684) Executed commands should expose the fine-grained operations that have been performed
[ https://issues.apache.org/jira/browse/SLING-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3684: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Executed commands should expose the fine-grained operations that have been > performed > > > Key: SLING-3684 > URL: https://issues.apache.org/jira/browse/SLING-3684 > Project: Sling > Issue Type: Improvement > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.0 >Reporter: Robert Munteanu >Priority: Critical > > Some commands, notably the AddOrUpdateNodeCommand, start having a lot of > logic and can potentially perform many operations, like reodering, child node > deletion and creation. > These operations are now opaque and only visible using debug tracing. > Recording these operations and making them available to the invoker would > serve at least two purposes: > # More detailed logging of what is changed ( for both users and developers ) > # Reconciling the local workspace with changes from the remote repository -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (SLING-3827) Unable to create nodes with protected properties, e.g. rep:User
[
https://issues.apache.org/jira/browse/SLING-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus reassigned SLING-3827:
--
Assignee: (was: Konrad Windszus)
> Unable to create nodes with protected properties, e.g. rep:User
> ---
>
> Key: SLING-3827
> URL: https://issues.apache.org/jira/browse/SLING-3827
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.4
>Reporter: Robert Munteanu
>Priority: Major
> Fix For: Sling Eclipse IDE 2.0.0
>
>
> I tried to create a user using the tooling, and I get back an exception:
> The debug trace is
> {noformat}
> | Worker-886 | 2014-08-06 18:10:22.590 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | update | 96 |
> Created node at /home/users/system/blabla with primaryType rep:User |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateMixins
> | 347 | Added new mixin rep:AccessControllable to node at path
> /home/users/system/blabla |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateNode |
> 298 | Setting property rep:principalName with value
> org.apache.jackrabbit.spi.commons.value.QValueValue@b7c2c87f (raw =
> mcm-service) on node at /home/users/system/blabla |
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (SLING-3980) Reordering values in a multi value properties from the UI
[ https://issues.apache.org/jira/browse/SLING-3980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3980: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Reordering values in a multi value properties from the UI > - > > Key: SLING-3980 > URL: https://issues.apache.org/jira/browse/SLING-3980 > Project: Sling > Issue Type: Improvement > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.2 >Reporter: Catalin Buzoiu >Priority: Minor > > Currently it is not possible to re-order the values in a mvp from the uI, one > needs to manually edit the .content.xml file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3611) Allow users to specify custom archetypes for the Sling bundle project
[ https://issues.apache.org/jira/browse/SLING-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3611: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Allow users to specify custom archetypes for the Sling bundle project > - > > Key: SLING-3611 > URL: https://issues.apache.org/jira/browse/SLING-3611 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Robert Munteanu >Priority: Major > > As requested by [~kwin], we should allow users to contribute maven archetype > coordinates to be used by the new sling bundle project wizard. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3587) Publish not triggered by WST on folder creation
[ https://issues.apache.org/jira/browse/SLING-3587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3587: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Publish not triggered by WST on folder creation > --- > > Key: SLING-3587 > URL: https://issues.apache.org/jira/browse/SLING-3587 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Stefan Egli >Priority: Major > > When you create a folder in a directory that is hooked up to a (WST)server, > the corresponding publish mechanism doesn't get triggered. > The core issue seems to be a WST-bug IMHO: the > org.eclipse.wst.server.core.internal.ResourceManager.getPublishRequiredServers's > IResourceDeltaVisitor.visit() only returns true if anything related to an > IFile has changed. If a folder has changed, it will navigate down to that > folder, but won't necessarily find anything changed below there and thus > ignore the change. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3963) Allow manual publishing with a keyboard shortcut
[ https://issues.apache.org/jira/browse/SLING-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3963: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Allow manual publishing with a keyboard shortcut > > > Key: SLING-3963 > URL: https://issues.apache.org/jira/browse/SLING-3963 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Robert Munteanu >Priority: Minor > > When automatic publishing is disabled it would be nice to be able to quickly > publish a batch of changes by using a keyboard shortcut. Currently this is > not possible unless the servers view is open and the server is selected. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3128) [Tooling] evaluate filter.xml in content-browser: mark nodes if they're not included
[ https://issues.apache.org/jira/browse/SLING-3128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3128: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [Tooling] evaluate filter.xml in content-browser: mark nodes if they're not > included > > > Key: SLING-3128 > URL: https://issues.apache.org/jira/browse/SLING-3128 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Stefan Egli >Priority: Major > > In the slingclipse content-browser, evaluate the filter.xml to mark nodes > that are not included in the filter.xml and thus not synched automatically: > decorate those not included in some way or form visually. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3033) [Tooling] differentiate between internal/embedded and externally (manually) started server
[ https://issues.apache.org/jira/browse/SLING-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3033: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [Tooling] differentiate between internal/embedded and externally (manually) > started server > -- > > Key: SLING-3033 > URL: https://issues.apache.org/jira/browse/SLING-3033 > Project: Sling > Issue Type: New Feature > Components: IDE >Reporter: Stefan Egli >Priority: Major > > Differentiate between two kinds of servers: > * eclipse-internal ones: those are started/stopped by eclipse in the servers > view > * eclipse-external ones: those are started manually by the user outside of > eclipse (the more frequent use case probably) > Reflect this differentiation in the UI accordingly -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3132) [Tooling] provide a filter.xml editor separate and/or as part of the import-content wizard
[ https://issues.apache.org/jira/browse/SLING-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3132: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [Tooling] provide a filter.xml editor separate and/or as part of the > import-content wizard > -- > > Key: SLING-3132 > URL: https://issues.apache.org/jira/browse/SLING-3132 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Stefan Egli >Priority: Major > > As a follow-up of SLING-2984: provide an editor of the filter.xml either > separate and/or as part of the import-content-wizard. That would allow to > import multiple paths in one go in the import-content-wizard. (This > filter.xml-editing would also go hand-in-hand with the "re-import" > button/action.) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3089) Investigate using the same model between the repository sync and the Sling (JCR) content provider
[ https://issues.apache.org/jira/browse/SLING-3089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3089: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Investigate using the same model between the repository sync and the Sling > (JCR) content provider > - > > Key: SLING-3089 > URL: https://issues.apache.org/jira/browse/SLING-3089 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Robert Munteanu >Priority: Major > > If we use the same data model we can benefit from the same code base. Right > now there's some duplication and we potentially miss fixes from one area from > another. For instance, the content provider does not yet support properties > stored in $(nodeName).dir/.content.xml files. > Also, it would help in formalizing the SerializationManager API even more. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3644) Improve handling of binary properties outside nt:file file nodes
[ https://issues.apache.org/jira/browse/SLING-3644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3644: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Improve handling of binary properties outside nt:file file nodes > > > Key: SLING-3644 > URL: https://issues.apache.org/jira/browse/SLING-3644 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Robert Munteanu >Priority: Major > > Currently ( see SLING-3609 ) we ignore binary properties which don't belong > to nt:file nodes. We should be able to recognize them and update them as > needed. > We probably need > * a new property type which points to the binary written on disk > * a way of ignoring these files so we don't recognize them as nt:file nodes > See also the [VaultFS docs on Binary > Properties|https://jackrabbit.apache.org/filevault/vaultfs.html#Binary_Properties] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3014) [build] Generate SCR descriptors using Maven
[ https://issues.apache.org/jira/browse/SLING-3014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3014: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [build] Generate SCR descriptors using Maven > > > Key: SLING-3014 > URL: https://issues.apache.org/jira/browse/SLING-3014 > Project: Sling > Issue Type: Task > Components: IDE >Reporter: Robert Munteanu >Priority: Minor > Attachments: SLING-3014-1.patch > > > _Edit_: updated the issue title to reflect the fact that we're looking to use > Maven, not a specific plug-in. > Since we're starting to use SCR descriptors when building the Sling IDE tools > it would be nice to generate them using the maven-scr-plugin. I have the > build working in the CLI, but not yet in the IDE ( see > http://dev.eclipse.org/mhonarc/lists/tycho-user/msg04764.html ). Once that is > done I'll commit my changes to trunk. > Note that plain Maven projects work just fine, this is about Tycho-driven > builds. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3131) [Tooling] consider raising 'sling console' into its own view
[ https://issues.apache.org/jira/browse/SLING-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3131: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [Tooling] consider raising 'sling console' into its own view > > > Key: SLING-3131 > URL: https://issues.apache.org/jira/browse/SLING-3131 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Stefan Egli >Priority: Major > > The 'Sling Console' becomes a rather central tool as it will allow to see > what is synched between the eclipse workspace and a sling instance. > Currently, it is accessible as a type of console in the normal Console view. > This sort of 'hides' it though - as you can only have one view of the stacked > Console view open at a time. We could consider moving the Sling Console into > its own, separate view (or allow both?), that way also making it more visible > (it will be listed as a separate view, which people might more likely > discover than another type of console) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3607) Resource deletion can delete too much
[ https://issues.apache.org/jira/browse/SLING-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3607: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Resource deletion can delete too much > - > > Key: SLING-3607 > URL: https://issues.apache.org/jira/browse/SLING-3607 > Project: Sling > Issue Type: Bug > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.0 >Reporter: Robert Munteanu >Priority: Minor > > There are two issue with the deletion code: > * it deletes .content.xml files > * it deletes everything under a subtree, even though it would be enough to > just delete the subtree root -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3113) [Tooling] make use of control-port for (re)start/stop of a (launchpad) server
[ https://issues.apache.org/jira/browse/SLING-3113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3113: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > [Tooling] make use of control-port for (re)start/stop of a (launchpad) server > - > > Key: SLING-3113 > URL: https://issues.apache.org/jira/browse/SLING-3113 > Project: Sling > Issue Type: New Feature > Components: IDE >Reporter: Stefan Egli >Priority: Major > > Sling launchpad comes with a control-port, that allows to start/stop/restart > a server (in a separate vm) - details see SLING-2225 and > http://sling.apache.org/documentation/development/embedding-sling.html > Slingclipse should make use of that when controlling the "external" server - > eg for restarting a server. Other use-cases could also be supported (not sure > what though..) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3584) Offline-mode for NodeTypeRegistry
[ https://issues.apache.org/jira/browse/SLING-3584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3584: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Offline-mode for NodeTypeRegistry > - > > Key: SLING-3584 > URL: https://issues.apache.org/jira/browse/SLING-3584 > Project: Sling > Issue Type: Improvement > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.0 >Reporter: Stefan Egli >Priority: Major > > The current NodeTypeRegistry introduced with SLING-3571 only works when > connected to a running server (as it retrieves the nodetypes under > /jcr:system...). During development a server might not always be running > though and/or you might not want to be connected to it all the time (to > support batch-publishing for example). Therefore I think we should have an > offline-mode for the NodeTypeRegistry (by eg storing the node types in the > .settings directory or similar) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-2666) Resource transport layer - checking out resources fails if the DefaultGetServlet does not serve the content
[ https://issues.apache.org/jira/browse/SLING-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-2666: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Resource transport layer - checking out resources fails if the > DefaultGetServlet does not serve the content > --- > > Key: SLING-2666 > URL: https://issues.apache.org/jira/browse/SLING-2666 > Project: Sling > Issue Type: Bug > Components: IDE >Reporter: Antonio Sanso >Priority: Minor > > see discussion at [0] > [0] http://sling.markmail.org/message/rsmysnx6ombk4u4s -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3585) Wizard for creating a new simple OSGi bundle
[ https://issues.apache.org/jira/browse/SLING-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3585: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Wizard for creating a new simple OSGi bundle > > > Key: SLING-3585 > URL: https://issues.apache.org/jira/browse/SLING-3585 > Project: Sling > Issue Type: New Feature > Components: IDE >Affects Versions: Sling Eclipse IDE 1.0.0 >Reporter: Robert Munteanu >Priority: Major > > (Created as a spin-off from SLING-3174). > We should support a simple bundle project which does not require Maven for > execution. Open questions > * how do we resolve the needed jars in order to add them to the classpath? > * what sort of content do we add to the project? A service using DS > annotations is out since we don't have the proper builder installed to > generate the XML descriptors -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3581) Consider prompting the user about uninstalling a bundle/content project when removed from the server
[ https://issues.apache.org/jira/browse/SLING-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3581: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Consider prompting the user about uninstalling a bundle/content project when > removed from the server > > > Key: SLING-3581 > URL: https://issues.apache.org/jira/browse/SLING-3581 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Robert Munteanu >Priority: Minor > > Currently, when removing a bundle or content project from the server they are > not uninstalled. This can be surprising, but also when deleting all related > data from the repository can be surprising. > Let's considering adding using a dialog and maybe a per-workspace preference > ( or per-server? ) for controlling this behaviour. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (SLING-3627) Create warnings for resources under the content sync root which are not covered by filter.xml
[ https://issues.apache.org/jira/browse/SLING-3627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Munteanu updated SLING-3627: --- Fix Version/s: (was: Sling Eclipse IDE 2.0.0) > Create warnings for resources under the content sync root which are not > covered by filter.xml > - > > Key: SLING-3627 > URL: https://issues.apache.org/jira/browse/SLING-3627 > Project: Sling > Issue Type: Improvement > Components: IDE >Reporter: Robert Munteanu >Priority: Minor > > Entries created in the local workspace but not covered by the filter.xml > definition are a cause of confusion, since they are not synchronized to the > remote repository with no warning/error raised about this. > We should create warnings for such files. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (SLING-3827) Unable to create nodes with protected properties, e.g. rep:User
[
https://issues.apache.org/jira/browse/SLING-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17758587#comment-17758587
]
Robert Munteanu commented on SLING-3827:
[~kwin] - you're assigned to this, do you plan to contribute a fix?
> Unable to create nodes with protected properties, e.g. rep:User
> ---
>
> Key: SLING-3827
> URL: https://issues.apache.org/jira/browse/SLING-3827
> Project: Sling
> Issue Type: Bug
> Components: IDE
>Affects Versions: Sling Eclipse IDE 1.0.4
>Reporter: Robert Munteanu
>Assignee: Konrad Windszus
>Priority: Major
> Fix For: Sling Eclipse IDE 2.0.0
>
>
> I tried to create a user using the tooling, and I get back an exception:
> The debug trace is
> {noformat}
> | Worker-886 | 2014-08-06 18:10:22.590 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | update | 96 |
> Created node at /home/users/system/blabla with primaryType rep:User |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateMixins
> | 347 | Added new mixin rep:AccessControllable to node at path
> /home/users/system/blabla |
> | Worker-886 | 2014-08-06 18:10:22.591 | org.apache.sling.ide.impl-vlt |
> /debug | org.apache.sling.ide.impl.vlt.AddOrUpdateNodeCommand | updateNode |
> 298 | Setting property rep:principalName with value
> org.apache.jackrabbit.spi.commons.value.QValueValue@b7c2c87f (raw =
> mcm-service) on node at /home/users/system/blabla |
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[Jenkins] Sling » Modules » sling-org-apache-sling-starter » master #985 is BROKEN
ts-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_mongo_far.far [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_tar_test.slingosgifeature (108 kB at 15 MB/s) [INFO] Uploading to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-sources.jar [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_mongo.slingosgifeature (103 kB at 13 MB/s) [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_tar.slingosgifeature (103 kB at 13 MB/s) [INFO] Uploading to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1.xml.gz [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-sources.jar (11 kB at 1.3 MB/s) [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1.xml.gz (329 kB at 23 MB/s) [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_mongo_far.far (115 MB at 71 MB/s) [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-20230824.111848-1-oak_tar_far.far (116 MB at 71 MB/s) [INFO] Downloading from snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml [INFO] Uploading to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/maven-metadata.xml [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/maven-metadata.xml (7.5 kB at 7.5 MB/s) [INFO] Uploading to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml [INFO] Uploaded to snapshot-repo: file:/home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest/.local-snapshots-dir/org/apache/sling/org.apache.sling.starter/maven-metadata.xml (297 B at 297 kB/s) [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 08:53 min [INFO] Finished at: 2023-08-24T11:27:41Z [INFO] [INFO] [jenkins-event-spy] Generated /home/jenkins/workspace/_org-apache-sling-starter_master/jdk_11_latest@tmp/withMaven0c5532a2/maven-spy-20230824-111848-4012254723301107497682.log [Pipeline] } [withMaven] artifactsPublisher - Archive artifact pom.xml under org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT.pom [withMaven] artifactsPublisher - Archive artifact target/org.apache.sling.starter-13-SNAPSHOT.jar under org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT.jar [withMaven] artifactsPublisher - Archive artifact target/slingfeature-tmp/feature-composum.json under org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-composum.slingosgifeature [withMaven] artifactsPublisher - Archive artifact target/slingfeature-tmp/feature-htl_repl.json under org/apache/sling/org.apache.sling.starter/13-SNAPSHOT/org.apache.sling.starter-13-SNAPSHOT-htl_repl.slingosgifeature [withMaven] artifactsPublisher - Archive artifact target/slingfeature-tmp/feature-slingshot.json under org/apache/sling/org.apache.sl
