[JBoss JIRA] (ISPN-12059) CliIT allow external module use
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12059?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12059:
--------------------------------
Status: Open (was: New)
> CliIT allow external module use
> -------------------------------
>
> Key: ISPN-12059
> URL: https://issues.redhat.com/browse/ISPN-12059
> Project: Infinispan
> Issue Type: Enhancement
> Components: Test Suite
> Affects Versions: 11.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
>
> CliIT currently loads resources via {{getResource}} and then passes the resource path to the CLI. As the CLI simply resolves these paths as normal File objects, the CLI is unable to find the files when they are located within a jar file. As a workaround we should utilise a working directory for the test and copy the resources from the jar to the local directory before passing the path to the CLI.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12059) CliIT allow external module use
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-12059:
-----------------------------------
Summary: CliIT allow external module use
Key: ISPN-12059
URL: https://issues.redhat.com/browse/ISPN-12059
Project: Infinispan
Issue Type: Enhancement
Components: Test Suite
Affects Versions: 11.0.0.Final
Reporter: Ryan Emerson
Assignee: Ryan Emerson
CliIT currently loads resources via {{getResource}} and then passes the resource path to the CLI. As the CLI simply resolves these paths as normal File objects, the CLI is unable to find the files when they are located within a jar file. As a workaround we should utilise a working directory for the test and copy the resources from the jar to the local directory before passing the path to the CLI.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12058) wildfly/feature-pack module doesn't build with profile java8-test
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12058?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12058:
--------------------------------
Fix Version/s: 11.0.1.Final
> wildfly/feature-pack module doesn't build with profile java8-test
> -----------------------------------------------------------------
>
> Key: ISPN-12058
> URL: https://issues.redhat.com/browse/ISPN-12058
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final, 11.0.1.Final
>
>
> {{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
> The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
> The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
> * If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
> [ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
> [ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
> * If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (branded-modules) on project infinispan-feature-pack: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/dan/Work/build-jdg/wildfly/feature-pack/build.xml:3: /home/dan/Work/build-jdg/wildfly/feature-pack/target/feature-pack/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="build.xml" inheritRefs="true">... @ 4:49 in /home/dan/Work/build-jdg/wildfly/feature-pack/target/antrun/build-main.xml{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12058) wildfly/feature-pack module doesn't build with profile java8-test
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12058?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12058:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8508
> wildfly/feature-pack module doesn't build with profile java8-test
> -----------------------------------------------------------------
>
> Key: ISPN-12058
> URL: https://issues.redhat.com/browse/ISPN-12058
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> {{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
> The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
> The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
> * If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
> [ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
> [ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
> * If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (branded-modules) on project infinispan-feature-pack: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/dan/Work/build-jdg/wildfly/feature-pack/build.xml:3: /home/dan/Work/build-jdg/wildfly/feature-pack/target/feature-pack/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="build.xml" inheritRefs="true">... @ 4:49 in /home/dan/Work/build-jdg/wildfly/feature-pack/target/antrun/build-main.xml{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12058) wildfly/feature-pack module doesn't build with profile java8-test
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12058?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12058:
--------------------------------
Description:
{{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
* If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
{noformat}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
[ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
[ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
* If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
{noformat}
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (branded-modules) on project infinispan-feature-pack: An Ant BuildException has occured: The following error occurred while executing this line:
[ERROR] /home/dan/Work/build-jdg/wildfly/feature-pack/build.xml:3: /home/dan/Work/build-jdg/wildfly/feature-pack/target/feature-pack/modules does not exist.
[ERROR] around Ant part ...<ant antfile="build.xml" inheritRefs="true">... @ 4:49 in /home/dan/Work/build-jdg/wildfly/feature-pack/target/antrun/build-main.xml{noformat}
was:
{{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
* If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
{noformat}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
[ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
[ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
* If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
> wildfly/feature-pack module doesn't build with profile java8-test
> -----------------------------------------------------------------
>
> Key: ISPN-12058
> URL: https://issues.redhat.com/browse/ISPN-12058
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> {{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
> The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
> The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
> * If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
> [ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
> [ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
> * If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (branded-modules) on project infinispan-feature-pack: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/dan/Work/build-jdg/wildfly/feature-pack/build.xml:3: /home/dan/Work/build-jdg/wildfly/feature-pack/target/feature-pack/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="build.xml" inheritRefs="true">... @ 4:49 in /home/dan/Work/build-jdg/wildfly/feature-pack/target/antrun/build-main.xml{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12058) wildfly/feature-pack module doesn't build with profile java8-test
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-12058?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-12058:
--------------------------------
Status: Open (was: New)
> wildfly/feature-pack module doesn't build with profile java8-test
> -----------------------------------------------------------------
>
> Key: ISPN-12058
> URL: https://issues.redhat.com/browse/ISPN-12058
> Project: Infinispan
> Issue Type: Bug
> Components: Build
> Affects Versions: 11.0.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 12.0.0.Final
>
>
> {{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
> The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
> The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
> * If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
> {noformat}
> [ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
> [ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
> [ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
> * If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
> {noformat}
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:3.0.0:run (branded-modules) on project infinispan-feature-pack: An Ant BuildException has occured: The following error occurred while executing this line:
> [ERROR] /home/dan/Work/build-jdg/wildfly/feature-pack/build.xml:3: /home/dan/Work/build-jdg/wildfly/feature-pack/target/feature-pack/modules does not exist.
> [ERROR] around Ant part ...<ant antfile="build.xml" inheritRefs="true">... @ 4:49 in /home/dan/Work/build-jdg/wildfly/feature-pack/target/antrun/build-main.xml{noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12058) wildfly/feature-pack module doesn't build with profile java8-test
by Dan Berindei (Jira)
Dan Berindei created ISPN-12058:
-----------------------------------
Summary: wildfly/feature-pack module doesn't build with profile java8-test
Key: ISPN-12058
URL: https://issues.redhat.com/browse/ISPN-12058
Project: Infinispan
Issue Type: Bug
Components: Build
Affects Versions: 11.0.0.Final
Reporter: Dan Berindei
Assignee: Dan Berindei
Fix For: 12.0.0.Final
{{wildfly/feature-pack/pom.xml}} uses both {{maven-resource-plugin}} and {{maven-antrun-plugin}} to process the {{module.xml}} files. There are 3 {{maven-resource-plugin}} executions copying the files into the build output directory, then a {{maven-antrun-plugin}} execution (using an external {{build.xml}}) renames the slot directories and replaces the token versions in {{module.xml}} with the actual versions.
The problem is that all these 4 executions run in the {{generate-resources}} build phase, and Maven does not guarantee any particular order for plugin executions in the same phase. Normally they run in the source order, and everything works, but activating profiles {{java8-test}} and {{rhdg8-snapshots-repository}} changes the order, and the {{maven-antrun-plugin}} execution runs first.
The result depends on whether a previous build already created the correct {{module.xml}} file in the correct location:
* If the correct files exist, the {{java8-test}} build will create additional modules without replacing the version tokens. The build will then fail with an error like this:
{noformat}
[ERROR] Failed to execute goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build (feature-pack-build) on project infinispan-feature-pack: Execution feature-pack-build of goal org.wildfly.build:wildfly-feature-pack-build-maven-plugin:1.2.13.Final:build failed: java.lang.RuntimeException: Some errors were encountered creating the feature pack
[ERROR] Missing module ModuleIdentifier{name='org.hibernate.search.engine', slot='@hibernate.search.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]
[ERROR] Missing module ModuleIdentifier{name='org.apache.lucene', slot='@lucene.module.slot@'}. Module was required by [ModuleIdentifier{name='org.infinispan', slot='rhdg-8.1'}]{noformat}
* If the target directory is empty, the {{maven-antrun-plugin}} will fail because there are no resource files to move+filter:
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (ISPN-12057) Shorthand configuration for CORS
by Gustavo Fernandes (Jira)
Gustavo Fernandes created ISPN-12057:
----------------------------------------
Summary: Shorthand configuration for CORS
Key: ISPN-12057
URL: https://issues.redhat.com/browse/ISPN-12057
Project: Infinispan
Issue Type: Enhancement
Components: REST
Affects Versions: 11.0.0.Final
Reporter: Gustavo Fernandes
Assignee: Gustavo Fernandes
Fix For: 12.0.0.Final
Provide a way to concisely declare (in XML) that a certain origin has all permissions (methods, headers, etc)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months