[jira] [Assigned] (SLING-12053) Upgrade Sling GraphQL Core to Graphql-Java 21.x

[ https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-12053: Assignee: Andreas Schaefer > Upgrade Sling GraphQL Core to Graphql-Java 21.x >

[jira] [Commented] (SLING-12053) Upgrade Sling GraphQL Core to Graphql-Java 21.x

[ https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770495#comment-17770495 ] Andreas Schaefer commented on SLING-12053: -- I suggested a version check in the garaphql-java

[jira] [Commented] (SLING-12053) Upgrade Sling GraphQL Core to Graphql-Java 21.x

[ https://issues.apache.org/jira/browse/SLING-12053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17770244#comment-17770244 ] Andreas Schaefer commented on SLING-12053: -- When I took Sling GraphQL Core 0.0.25-SNAPSHOT and

[jira] [Created] (SLING-12053) Upgrade Sling GraphQL Core to Graphql-Java 21.x

Andreas Schaefer created SLING-12053: Summary: Upgrade Sling GraphQL Core to Graphql-Java 21.x Key: SLING-12053 URL: https://issues.apache.org/jira/browse/SLING-12053 Project: Sling

[jira] [Commented] (SLING-12027) GraphQL core fails to build with Java 17

[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768921#comment-17768921 ] Andreas Schaefer commented on SLING-12027: -- [~radu] Does not do the trick. I upgraded to the

[jira] [Commented] (SLING-12027) GraphQL core fails to build with Java 17

[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767252#comment-17767252 ] Andreas Schaefer commented on SLING-12027: -- I found the cause of the issue. During the handling

[jira] [Commented] (SLING-12027) GraphQL core fails to build with Java 17

[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767199#comment-17767199 ] Andreas Schaefer commented on SLING-12027: -- Here are some excerpts of the output: a) Where the

[jira] [Commented] (SLING-12027) GraphQL core fails to build with Java 17

[ https://issues.apache.org/jira/browse/SLING-12027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767174#comment-17767174 ] Andreas Schaefer commented on SLING-12027: -- The current PR for this ticket is:

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

[ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10901: - Fix Version/s: GraphQL Core 0.0.26 (was: GraphQL Core 0.0.24) >

[jira] [Updated] (SLING-12014) GraphQL Core needs to support additional fields from GraphQL Java

[ https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-12014: - Fix Version/s: GraphQL Core 0.0.24 > GraphQL Core needs to support additional fields

[jira] [Resolved] (SLING-12014) GraphQL Core needs to support additional fields from GraphQL Java

[ https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-12014. -- Resolution: Fixed PR was merged into master > GraphQL Core needs to support

[jira] [Closed] (SLING-12014) GraphQL Core needs to support additional fields from GraphQL Java

[ https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer closed SLING-12014. > GraphQL Core needs to support additional fields from GraphQL Java >

[jira] [Commented] (SLING-12014) GraphQL Core needs to Support Addition Fields from GraphQL Java

[ https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17760638#comment-17760638 ] Andreas Schaefer commented on SLING-12014: -- Create a PR for this enhancements:

[jira] [Assigned] (SLING-12014) GraphQL Core needs to Support Addition Fields from GraphQL Java

[ https://issues.apache.org/jira/browse/SLING-12014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-12014: Assignee: Andreas Schaefer > GraphQL Core needs to Support Addition Fields from

[jira] [Assigned] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-11458: Assignee: Andreas Schaefer (was: Radu Cotescu) > Regress - "Writer has already

[jira] [Created] (SLING-12014) GraphQL Core needs to Support Addition Fields from GraphQL Java

Andreas Schaefer created SLING-12014: Summary: GraphQL Core needs to Support Addition Fields from GraphQL Java Key: SLING-12014 URL: https://issues.apache.org/jira/browse/SLING-12014 Project:

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754179#comment-17754179 ] Andreas Schaefer commented on SLING-11458: -- The Servlet Writer should not be closed inside the

[jira] [Commented] (SLING-11920) Expose Object Type Names in Selected Field

[ https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17741219#comment-17741219 ] Andreas Schaefer commented on SLING-11920: -- I created a PR

[jira] [Updated] (SLING-11920) Expose Object Type Names in Selected Field

[ https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11920: - Description: Intermediary fields are not exposed as Selected Fields in Graphql-java and

[jira] [Commented] (SLING-11920) Expose Object Type Names in Selected Field

[ https://issues.apache.org/jira/browse/SLING-11920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17738806#comment-17738806 ] Andreas Schaefer commented on SLING-11920: -- This is a follow up of SLING-10900 and the release

[jira] [Created] (SLING-11920) Expose Object Type Names in Selected Field

Andreas Schaefer created SLING-11920: Summary: Expose Object Type Names in Selected Field Key: SLING-11920 URL: https://issues.apache.org/jira/browse/SLING-11920 Project: Sling Issue

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

[ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10901: - Fix Version/s: GraphQL Core 0.0.22 (was: GraphQL Core 0.0.20) >

[jira] [Updated] (SLING-10900) Update graphql-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10900: - Fix Version/s: GraphQL Core 0.0.20 (was: GraphQL Core 0.0.18) >

[jira] [Updated] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10900: - Fix Version/s: GraphQL Core 0.0.18 (was: GraphQL Core 0.0.16) >

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

[ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10901: - Fix Version/s: GraphQL Core 0.0.20 (was: GraphQL Core 0.0.18) >

[jira] [Updated] (SLING-10901) Allow terminating a GraphQL query after a configured timeout

[ https://issues.apache.org/jira/browse/SLING-10901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-10901: - Fix Version/s: GraphQL Core 0.0.18 (was: GraphQL Core 0.0.16) >

[jira] [Resolved] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-10900. -- Resolution: Fixed Upgraded to graphql-java 20.1 (latest release) as there are nearly

[jira] [Commented] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17705660#comment-17705660 ] Andreas Schaefer commented on SLING-10900: -- After graphql-java released 20.1 with the necessary

[jira] [Comment Edited] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17695824#comment-17695824 ] Andreas Schaefer edited comment on SLING-10900 at 3/2/23 5:06 PM: --

[jira] [Commented] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17695824#comment-17695824 ] Andreas Schaefer commented on SLING-10900: -- After some help from the graphql-java team I was

[jira] [Commented] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17694235#comment-17694235 ] Andreas Schaefer commented on SLING-10900: -- After testing with AEM this is the current state:

[jira] [Commented] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17691777#comment-17691777 ] Andreas Schaefer commented on SLING-10900: -- All graphql-java version newer that 17.4 have an

[jira] [Assigned] (SLING-10900) Update graphl-java to version 17

[ https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-10900: Assignee: Andreas Schaefer (was: Radu Cotescu) > Update graphl-java to version

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17637398#comment-17637398 ] Andreas Schaefer commented on SLING-11458: -- [~radu] I don't mind fixing the issue upstream or

[jira] [Comment Edited] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634573#comment-17634573 ] Andreas Schaefer edited comment on SLING-11458 at 11/16/22 10:02 PM: -

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634573#comment-17634573 ] Andreas Schaefer commented on SLING-11458: -- The problem here is that the Johnson's JsonWriter

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17634524#comment-17634524 ] Andreas Schaefer commented on SLING-11458: -- [~radu] Do you know if anything was done regarding

[jira] [Commented] (SLING-11486) Allow to use a Writer that check for close as used in Response Context Support

[ https://issues.apache.org/jira/browse/SLING-11486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17569618#comment-17569618 ] Andreas Schaefer commented on SLING-11486: -- PR for this ticket can be found here:

[jira] [Created] (SLING-11486) Allow to use a Writer that check for close as used in Response Context Support

Andreas Schaefer created SLING-11486: Summary: Allow to use a Writer that check for close as used in Response Context Support Key: SLING-11486 URL: https://issues.apache.org/jira/browse/SLING-11486

[jira] [Commented] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17567402#comment-17567402 ] Andreas Schaefer commented on SLING-11458: -- I encountered that issue in AEM when using the AEM

[jira] [Updated] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11458: - Description: The GraphQLServlet shouldn't call {{response.getWriter().flush()}} as the

[jira] [Assigned] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

[ https://issues.apache.org/jira/browse/SLING-11458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-11458: Assignee: Andreas Schaefer (was: Bertrand Delacretaz) > Regress - "Writer has

[jira] [Created] (SLING-11458) Regress - "Writer has already been closed" exception in GraphQLServlet

Andreas Schaefer created SLING-11458: Summary: Regress - "Writer has already been closed" exception in GraphQLServlet Key: SLING-11458 URL: https://issues.apache.org/jira/browse/SLING-11458

[jira] [Resolved] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-11427. -- Resolution: Fixed A fix was created in PR #24, approved and merged into master >

[jira] [Commented] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560684#comment-17560684 ] Andreas Schaefer commented on SLING-11427: -- I created a simple 'fix' for that on this PR:

[jira] [Commented] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17560672#comment-17560672 ] Andreas Schaefer commented on SLING-11427: -- Adding this line to the end of test-40.txt:

[jira] [Updated] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11427: - Description: Registering a Namespace in the repoinit fails when the URI contains a

[jira] [Updated] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11427: - Description: Registering a Namespace in the repoinit fails when the URI contains a

[jira] [Updated] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11427: - Description: Registering a Namespace in the repoinit fails when the URI contains a

[jira] [Updated] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

[ https://issues.apache.org/jira/browse/SLING-11427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-11427: - Description: Registering a Namespace in the repoinit fails when the URI contains a

[jira] [Created] (SLING-11427) Registering a Namespace does not allow Hashtag in the URI

Andreas Schaefer created SLING-11427: Summary: Registering a Namespace does not allow Hashtag in the URI Key: SLING-11427 URL: https://issues.apache.org/jira/browse/SLING-11427 Project: Sling

[jira] [Commented] (SLING-10157) Converter fails with duplicate configuration PIDs

[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293813#comment-17293813 ] Andreas Schaefer commented on SLING-10157: -- [~cziegeler] Yes, that fixed my problems. >

[jira] [Comment Edited] (SLING-10157) Converter fails with duplicate configuration PIDs

[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293125#comment-17293125 ] Andreas Schaefer edited comment on SLING-10157 at 3/1/21, 7:31 PM: --- It

[jira] [Commented] (SLING-10157) Converter fails with duplicate configuration PIDs

[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17293125#comment-17293125 ] Andreas Schaefer commented on SLING-10157: -- It works but I ran into a few issues: - in

[jira] [Commented] (SLING-10157) Converter fails with duplicate configuration PIDs

[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17290504#comment-17290504 ] Andreas Schaefer commented on SLING-10157: -- The issue I encounter is a little bit more delicate

[jira] [Commented] (SLING-10157) Converter fails with duplicate configuration PIDs

[ https://issues.apache.org/jira/browse/SLING-10157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17289419#comment-17289419 ] Andreas Schaefer commented on SLING-10157: -- The CP Converter has a mergeConfiguration flag that

[jira] [Commented] (SLING-10126) Repository Initializer should support Empty or Single Value Lists

[ https://issues.apache.org/jira/browse/SLING-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17279838#comment-17279838 ] Andreas Schaefer commented on SLING-10126: -- Created a PR for a potential fix:

[jira] [Assigned] (SLING-10126) Repository Initializer should support Empty or Single Value Lists

[ https://issues.apache.org/jira/browse/SLING-10126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-10126: Assignee: Andreas Schaefer > Repository Initializer should support Empty or

[jira] [Created] (SLING-10126) Repository Initializer should support Empty or Single Value Lists

Andreas Schaefer created SLING-10126: Summary: Repository Initializer should support Empty or Single Value Lists Key: SLING-10126 URL: https://issues.apache.org/jira/browse/SLING-10126 Project:

[jira] [Commented] (SLING-10122) A Equal Sign (=) in a set properties instruction makes the Converter fail

[ https://issues.apache.org/jira/browse/SLING-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278939#comment-17278939 ] Andreas Schaefer commented on SLING-10122: -- As stated this is not an issue so I closed it. > A

[jira] [Resolved] (SLING-10122) A Equal Sign (=) in a set properties instruction makes the Converter fail

[ https://issues.apache.org/jira/browse/SLING-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-10122. -- Resolution: Invalid > A Equal Sign (=) in a set properties instruction makes the

[jira] [Commented] (SLING-10122) A Equal Sign (=) in a set properties instruction makes the Converter fail

[ https://issues.apache.org/jira/browse/SLING-10122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17278339#comment-17278339 ] Andreas Schaefer commented on SLING-10122: -- Enhanced the Repository Initializer test to

[jira] [Created] (SLING-10122) A Equal Sign (=) in a set properties instruction makes the Converter fail

Andreas Schaefer created SLING-10122: Summary: A Equal Sign (=) in a set properties instruction makes the Converter fail Key: SLING-10122 URL: https://issues.apache.org/jira/browse/SLING-10122

[jira] [Commented] (SLING-10069) The generated features target dir is created in the wrong place

[ https://issues.apache.org/jira/browse/SLING-10069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17267971#comment-17267971 ] Andreas Schaefer commented on SLING-10069: -- I ran this against the project that caused the

[jira] [Commented] (SLING-10035) Sling Feature fails when Generated Features Directory is missing

[ https://issues.apache.org/jira/browse/SLING-10035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17257077#comment-17257077 ] Andreas Schaefer commented on SLING-10035: -- Created a PR for this: 

[jira] [Created] (SLING-10035) Sling Feature fails when Generated Features Directory is missing

Andreas Schaefer created SLING-10035: Summary: Sling Feature fails when Generated Features Directory is missing Key: SLING-10035 URL: https://issues.apache.org/jira/browse/SLING-10035 Project:

[jira] [Commented] (SLING-9800) Extract a service to be able to execute GraphQL queries directly

[ https://issues.apache.org/jira/browse/SLING-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17221811#comment-17221811 ] Andreas Schaefer commented on SLING-9800: - [~bdelacretaz] I am working on the AEM GraphQL

[jira] [Updated] (SLING-9761) Properties (-D) is not supported in Kickstart Project

[ https://issues.apache.org/jira/browse/SLING-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9761: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.10)

[jira] [Updated] (SLING-9581) Reduce implementation duplication between kickstart and feature-launcher maven plugin

[ https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9581: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.12)

[jira] [Updated] (SLING-9581) Reduce implementation duplication between kickstart and feature-launcher maven plugin

[ https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9581: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.10)

[jira] [Commented] (SLING-9581) Reduce implementation duplication between kickstart and feature-launcher maven plugin

[ https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17217127#comment-17217127 ] Andreas Schaefer commented on SLING-9581: - I started to look into the two Maven Plugin. The

[jira] [Reopened] (SLING-9800) Extract a service to be able to execute GraphQL queries directly

[ https://issues.apache.org/jira/browse/SLING-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reopened SLING-9800: - The QueryExecutor.execute() and .validate() is requiring a Resource (queryResource) which

[jira] [Commented] (SLING-9800) Extract a service to be able to execute GraphQL queries directly

[ https://issues.apache.org/jira/browse/SLING-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17211452#comment-17211452 ] Andreas Schaefer commented on SLING-9800: - The isValid() is ok but as a caller I would need to

[jira] [Resolved] (SLING-9761) Properties (-D) is not supported in Kickstart Project

[ https://issues.apache.org/jira/browse/SLING-9761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-9761. - Resolution: Fixed Simple fix added to the current snapshot > Properties (-D) is not

[jira] [Created] (SLING-9761) Properties (-D) is not supported in Kickstart Project

Andreas Schaefer created SLING-9761: --- Summary: Properties (-D) is not supported in Kickstart Project Key: SLING-9761 URL: https://issues.apache.org/jira/browse/SLING-9761 Project: Sling

[jira] [Updated] (SLING-9581) Reduce implementation duplication between kickstart and feature-launcher maven plugin

[ https://issues.apache.org/jira/browse/SLING-9581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9581: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.8)

[jira] [Commented] (SLING-9635) Create a kickstart jar during the Sling Starter build

[ https://issues.apache.org/jira/browse/SLING-9635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173210#comment-17173210 ] Andreas Schaefer commented on SLING-9635: - The Kickstart Maven Plugin is OOTB just starting /

[jira] [Resolved] (SLING-9507) Add an option to Kickstart to prevent the use of the bundled Sling FM

[ https://issues.apache.org/jira/browse/SLING-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-9507. - Resolution: Fixed Added a flag '-S' that will not use provided Sling Feature Archive or

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: (was: Feature Model Sling Kickstart Plugin 0.0.6)

[jira] [Updated] (SLING-9452) Log Configuration does not work on Kickstart

[ https://issues.apache.org/jira/browse/SLING-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9452: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.4) > Log Configuration

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.6)

[jira] [Updated] (SLING-9452) Log Configuration does not work on Kickstart

[ https://issues.apache.org/jira/browse/SLING-9452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9452: Fix Version/s: Feature Model Sling Kickstart Project 0.0.6 > Log Configuration does not

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: (was: Feature Model Sling Maven Kickstart Plugin 0.0.4) > Add Support

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: Feature Model Sling Kickstart Project 0.0.6 > Add Support for Feature

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: Feature Model Sling Kickstart Project 0.0.6 > Add Support for Feature

[jira] [Updated] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9543: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.6) > Add Support for

[jira] [Resolved] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

[ https://issues.apache.org/jira/browse/SLING-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-9543. - Resolution: Fixed Fixed and committed > Add Support for Feature Archives and Provide

[jira] [Created] (SLING-9543) Add Support for Feature Archives and Provide the ability to use a custom Kickstart

Andreas Schaefer created SLING-9543: --- Summary: Add Support for Feature Archives and Provide the ability to use a custom Kickstart Key: SLING-9543 URL: https://issues.apache.org/jira/browse/SLING-9543

[jira] [Updated] (SLING-9507) Add an option to Kickstart to prevent the use of the bundled Sling FM

[ https://issues.apache.org/jira/browse/SLING-9507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer updated SLING-9507: Fix Version/s: (was: Feature Model Sling Kickstart Project 0.0.4)

[jira] [Reopened] (SLING-9516) Allow to specify execution environment as part of the feature model

[ https://issues.apache.org/jira/browse/SLING-9516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reopened SLING-9516: - I using the Feature Launcher in Kickstart and w/o this is breaking now. If I reverse the

[jira] [Commented] (SLING-9512) InternalRequest helper

[ https://issues.apache.org/jira/browse/SLING-9512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17132636#comment-17132636 ] Andreas Schaefer commented on SLING-9512: - Works for me. There are a few things to consider: *

[jira] [Created] (SLING-9507) Add an option to Kickstart to prevent the use of the bundled Sling FM

Andreas Schaefer created SLING-9507: --- Summary: Add an option to Kickstart to prevent the use of the bundled Sling FM Key: SLING-9507 URL: https://issues.apache.org/jira/browse/SLING-9507 Project:

[jira] [Commented] (SLING-9498) Create feature model aggregates on the fly from the Sling Starter build

[ https://issues.apache.org/jira/browse/SLING-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126058#comment-17126058 ] Andreas Schaefer commented on SLING-9498: - [~rombert] I fixed that issue > Create feature model

[jira] [Commented] (SLING-9498) Create feature model aggregates on the fly from the Sling Starter build

[ https://issues.apache.org/jira/browse/SLING-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124506#comment-17124506 ] Andreas Schaefer commented on SLING-9498: - [~rombert] BTW if you want to see how I convert the

[jira] [Commented] (SLING-9497) Announce + discuss intention to drop WAR file support to users

[ https://issues.apache.org/jira/browse/SLING-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124456#comment-17124456 ] Andreas Schaefer commented on SLING-9497: - >From my point of view a WAR file becomes obsolete for

[jira] [Commented] (SLING-9498) Create feature model aggregates on the fly from the Sling Starter build

[ https://issues.apache.org/jira/browse/SLING-9498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17124453#comment-17124453 ] Andreas Schaefer commented on SLING-9498: - In the long run Sling Starter will be retired, I

[jira] [Resolved] (SLING-9483) Sling Feature is not supporting jar:file URLs on Windows

[ https://issues.apache.org/jira/browse/SLING-9483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer resolved SLING-9483. - Resolution: Fixed Added the check for a Windows drive letter to the path and then

[jira] [Created] (SLING-9483) Sling Feature is not supporting jar:file URLs on Windows

Andreas Schaefer created SLING-9483: --- Summary: Sling Feature is not supporting jar:file URLs on Windows Key: SLING-9483 URL: https://issues.apache.org/jira/browse/SLING-9483 Project: Sling

[jira] [Created] (SLING-9462) Sub Maven Project fails in Check Preprocessor Run

Andreas Schaefer created SLING-9462: --- Summary: Sub Maven Project fails in Check Preprocessor Run Key: SLING-9462 URL: https://issues.apache.org/jira/browse/SLING-9462 Project: Sling Issue

[jira] [Assigned] (SLING-9458) Support Feature Model files inside a JAR File

[ https://issues.apache.org/jira/browse/SLING-9458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Schaefer reassigned SLING-9458: --- Assignee: Andreas Schaefer > Support Feature Model files inside a JAR File >

  1   2   3   4   >