[JBoss JIRA] (WFCORE-4943) Remove duplicate elytron's duplicate dependency to controller-client
by Jeff Mesnil (Jira)
[ https://issues.redhat.com/browse/WFCORE-4943?page=com.atlassian.jira.plug... ]
Jeff Mesnil reassigned WFCORE-4943:
-----------------------------------
Assignee: Jeff Mesnil (was: Darran Lofthouse)
> Remove duplicate elytron's duplicate dependency to controller-client
> --------------------------------------------------------------------
>
> Key: WFCORE-4943
> URL: https://issues.redhat.com/browse/WFCORE-4943
> Project: WildFly Core
> Issue Type: Bug
> Components: Security
> Reporter: Jeff Mesnil
> Assignee: Jeff Mesnil
> Priority: Major
> Fix For: 12.0.0.Beta2
>
>
> When running `mvn clean install` on wildfly-core master branch, Maven reports a warning:
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.wildfly.core:wildfly-elytron-integration:jar:12.0.0.Beta2-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.wildfly.core:wildfly-controller-client:jar -> duplicate declaration
> of version (?) @ org.wildfly.core:wildfly-elytron-integration:[unknown-version], /Users/jmesnil/Developer/wildfly-core/elytron/pom.xml, line 150, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> {code}
> The org.wildfly.core:wildfly-elytron-integration Maven module defines twice a dependency to org.wildfly.core:wildfly-controller-client: one without a scope and the other with a test scope.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFCORE-4943) Remove duplicate elytron's duplicate dependency to controller-client
by Jeff Mesnil (Jira)
Jeff Mesnil created WFCORE-4943:
-----------------------------------
Summary: Remove duplicate elytron's duplicate dependency to controller-client
Key: WFCORE-4943
URL: https://issues.redhat.com/browse/WFCORE-4943
Project: WildFly Core
Issue Type: Bug
Components: Security
Reporter: Jeff Mesnil
Assignee: Darran Lofthouse
Fix For: 12.0.0.Beta2
When running `mvn clean install` on wildfly-core master branch, Maven reports a warning:
{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.wildfly.core:wildfly-elytron-integration:jar:12.0.0.Beta2-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.wildfly.core:wildfly-controller-client:jar -> duplicate declaration
of version (?) @ org.wildfly.core:wildfly-elytron-integration:[unknown-version], /Users/jmesnil/Developer/wildfly-core/elytron/pom.xml, line 150, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
{code}
The org.wildfly.core:wildfly-elytron-integration Maven module defines twice a dependency to org.wildfly.core:wildfly-controller-client: one without a scope and the other with a test scope.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (JGRP-2471) Parse version from POM
by Bela Ban (Jira)
[ https://issues.redhat.com/browse/JGRP-2471?page=com.atlassian.jira.plugin... ]
Bela Ban commented on JGRP-2471:
--------------------------------
OK, so *just in the ant/ivy case*, we're extracting version and codename from the POM and copy it into {{./classes/JGROUPS_VERSION.properties}}. (In maven, this is done as part of the build process).
{{Version}} initializes itself from this file.
> Parse version from POM
> ----------------------
>
> Key: JGRP-2471
> URL: https://issues.redhat.com/browse/JGRP-2471
> Project: JGroups
> Issue Type: Enhancement
> Reporter: Bela Ban
> Assignee: Bela Ban
> Priority: Minor
> Fix For: 5.0.0.Alpha6
>
>
> Currently, the version is set in the POM (maven), but also in {{conf/JGROUPS_VERSION.properties}}. This is cumbersome, as we have to update both files on a release (and change the version back to {{XXX-SNAPSHOT}} after the release).
> With the introduction of maven release-plugin, modifying the file is manual work that's unwanted.
> Therefore get rid of {{JGROUPS-VERSION.properties}} and read the version directly from the POM.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (DROOLS-5264) Cancelling artifact upload dialog does not clear file chooser field
by Jozef Marko (Jira)
[ https://issues.redhat.com/browse/DROOLS-5264?page=com.atlassian.jira.plug... ]
Jozef Marko updated DROOLS-5264:
--------------------------------
Description:
Behavior before the fix:
[^artifact-upload-not-cleared.webm]
Behavior after fix:
[^artifact-upload-cleared.webm]
was:
Behavior before the fix:
[^artifact-upload-not-cleared.webm]
> Cancelling artifact upload dialog does not clear file chooser field
> -------------------------------------------------------------------
>
> Key: DROOLS-5264
> URL: https://issues.redhat.com/browse/DROOLS-5264
> Project: Drools
> Issue Type: Bug
> Components: Artifact Repository
> Affects Versions: 7.37.0.Final
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Priority: Minor
> Labels: drools-tools
> Attachments: artifact-upload-cleared.webm, artifact-upload-not-cleared.webm
>
>
> Behavior before the fix:
> [^artifact-upload-not-cleared.webm]
> Behavior after fix:
> [^artifact-upload-cleared.webm]
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13360) Log INFO message when EJB does not implement Business interface
by Panagiotis Sotiropoulos (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Panagiotis Sotiropoulos commented on WFLY-13360:
------------------------------------------------
Second testcase for possible additional interface view from session bean that already exposes one ...
: https://github.com/jboss-set/eap-additional-testsuite/pull/135
> Log INFO message when EJB does not implement Business interface
> ---------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> {code}
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> {code}
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> {code}
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (SWSQE-1134) Mirror bookinfo
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1134?page=com.atlassian.jira.plugi... ]
Filip Brychta updated SWSQE-1134:
---------------------------------
Description:
Bookinfo is not available after OCP disconnected installation. We need to mirror it.
It seems we have two options:
# mirror all images via oc image mirror and update yamls to point to images in mirror registry to deploy it
# update kiali-test-mesh operator to work in restricted OCP and then mirror it the same way like operators from https://issues.redhat.com/browse/SWSQE-1133
was:Bookinfo is not available after OCP disconnected installation. We need to mirror it.
> Mirror bookinfo
> ---------------
>
> Key: SWSQE-1134
> URL: https://issues.redhat.com/browse/SWSQE-1134
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> Bookinfo is not available after OCP disconnected installation. We need to mirror it.
> It seems we have two options:
> # mirror all images via oc image mirror and update yamls to point to images in mirror registry to deploy it
> # update kiali-test-mesh operator to work in restricted OCP and then mirror it the same way like operators from https://issues.redhat.com/browse/SWSQE-1133
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (WFLY-13360) Log INFO message when EJB does not implement Business interface
by Panagiotis Sotiropoulos (Jira)
[ https://issues.redhat.com/browse/WFLY-13360?page=com.atlassian.jira.plugi... ]
Panagiotis Sotiropoulos updated WFLY-13360:
-------------------------------------------
Summary: Log INFO message when EJB does not implement Business interface (was: Log WARN when EJB does not implement Business interface and is not compliant with EJB 3.2 spec)
> Log INFO message when EJB does not implement Business interface
> ---------------------------------------------------------------
>
> Key: WFLY-13360
> URL: https://issues.redhat.com/browse/WFLY-13360
> Project: WildFly
> Issue Type: Enhancement
> Components: EJB
> Reporter: Panagiotis Sotiropoulos
> Assignee: Panagiotis Sotiropoulos
> Priority: Major
>
> From the specification every business interface need to be declared explicitly as a business interface by @Remote or @Local annotation or deployment descriptor.
> {code}
> EJB 3.2 specification
> 4.9.7 Session Bean’s Business Interface
> - The bean class must implement the interface or the interface must be designated as a local or remote business interface of the bean by means of the Local or Remote annotation or in the deployment descriptor.
> - All business interfaces must be explicitly designated as such if any of the following is true:
> - the bean exposes a no-interface view
> - any interface of the bean class is explicitly designated as a business interface of the bean by either of the following means:
> - using the Local or Remote annotation with a non-empty value on the bean class
> - using the Local or Remote annotation on the interface
> - in the deployment descriptor
> {code}
> If EJB A implements I and EJB B extends A , EJB B must also declare it implements I in order to be spec compliant:
> {code}
> public interface I {...}
>
> @Stateless
> public class A implements I {...}
>
> @Stateless
> public class B extends A {...}
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (SWSQE-1133) Mirror operators from quay.io/maistra and redhat-operators
by Filip Brychta (Jira)
[ https://issues.redhat.com/browse/SWSQE-1133?page=com.atlassian.jira.plugi... ]
Filip Brychta commented on SWSQE-1133:
--------------------------------------
Mirroring everything from redhat-operators is taking too long, we have following options:
You can use the
--manifest-dir='': Local path to cache manifests when downloading.
To output the manifest and then manipulate them if you so desire to create a new catalog using number 6 from 4.2 install instructions[1].
Another approach would be to take the catalog, use oc adm catalog mirror command with
-dry-run=false: Print the actions that would be taken and exit without writing to the destinations.
This will output the mapping.txt that you can change to only mirror the images that you would like and use oc image mirror -f mapping.txt. Either way this will change the amount of content being mirrored.
I believe that you may be interested in some work that is happening to make the entire process for testing images from brew builds here https://projects.engineering.redhat.com/projects/REGISTRY/issues/REGISTRY... . This will drastically reduce the need to mirror unless you testing the mirroring workflow specifically.
> Mirror operators from quay.io/maistra and redhat-operators
> ----------------------------------------------------------
>
> Key: SWSQE-1133
> URL: https://issues.redhat.com/browse/SWSQE-1133
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> When the disconnected OCP cluster is provisioned there is nothing in operator hub. It's necessary to mirror required catalog.
> We will need redhat-operators and operators from quay.io/maistra
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years