[JBoss JIRA] (ELY-1568) elytron-client-1.1.xsd xsd:all minOccurs="0"
by Martin Choma (JIRA)
Martin Choma created ELY-1568:
---------------------------------
Summary: elytron-client-1.1.xsd xsd:all minOccurs="0"
Key: ELY-1568
URL: https://issues.jboss.org/browse/ELY-1568
Project: WildFly Elytron
Issue Type: Bug
Components: Authentication Client, XML
Affects Versions: 1.3.0.Final
Reporter: Martin Choma
I am getting error in my IDE during xml validation
*
{noformat}
cvc-complex-type.2.4.b: The content of element 'providers' is not complete. One of '{"urn:elytron:client:1.1":global}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{noformat}
<providers>
<use-service-loader/>
</providers>
{noformat}
*
{noformat}
cvc-complex-type.2.4.b: The content of element 'configuration' is not complete. One of '{"urn:elytron:client:
1.1":set-host, "urn:elytron:client:1.1":set-port, "urn:elytron:client:1.1":set-protocol, "urn:elytron:client:
1.1":abstract-user-spec, "urn:elytron:client:1.1":set-mechanism-realm, "urn:elytron:client:1.1":rewrite-user-
name-regex, "urn:elytron:client:1.1":set-mechanism-properties, "urn:elytron:client:1.1":set-authorization-
name, "urn:elytron:client:1.1":abstract-sasl-factories}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{code:xml|title=wildfly-config.xml}
<configuration name="default">
<sasl-mechanism-selector selector="EXTERNAL"/>
<credentials>
<key-store-reference key-store-name="keystore">
<key-store-clear-password password="${password}"/>
</key-store-reference>
</credentials>
<providers>
<use-service-loader/>
</providers>
</configuration>
{noformat}
Based on [1] I think elements in xsd:all should contain minOccurs="0" explicitly. E.g. <xsd:element ref="abstract-user-spec" minOccurs="0"/>.
I see this problem in providers-type, authentication-configuration-type, key-pair-type and certificate-type
[1] https://www.w3schools.com/xml/el_all.asp
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (ELY-1568) elytron-client-1.1.xsd xsd:all minOccurs="0"
by Martin Choma (JIRA)
[ https://issues.jboss.org/browse/ELY-1568?page=com.atlassian.jira.plugin.s... ]
Martin Choma updated ELY-1568:
------------------------------
Description:
I am getting error in my IDE during xml validation
* {noformat}
cvc-complex-type.2.4.b: The content of element 'providers' is not complete. One of '{"urn:elytron:client:1.1":global}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{noformat}
<providers>
<use-service-loader/>
</providers>
{noformat}
* {noformat}
cvc-complex-type.2.4.b: The content of element 'configuration' is not complete. One of '{"urn:elytron:client:
1.1":set-host, "urn:elytron:client:1.1":set-port, "urn:elytron:client:1.1":set-protocol, "urn:elytron:client:
1.1":abstract-user-spec, "urn:elytron:client:1.1":set-mechanism-realm, "urn:elytron:client:1.1":rewrite-user-
name-regex, "urn:elytron:client:1.1":set-mechanism-properties, "urn:elytron:client:1.1":set-authorization-
name, "urn:elytron:client:1.1":abstract-sasl-factories}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{code:xml|title=wildfly-config.xml}
<configuration name="default">
<sasl-mechanism-selector selector="EXTERNAL"/>
<credentials>
<key-store-reference key-store-name="keystore">
<key-store-clear-password password="${password}"/>
</key-store-reference>
</credentials>
<providers>
<use-service-loader/>
</providers>
</configuration>
{noformat}
Based on [1] I think elements in xsd:all should contain minOccurs="0" explicitly. E.g. <xsd:element ref="abstract-user-spec" minOccurs="0"/>.
I see this problem in providers-type, authentication-configuration-type, key-pair-type and certificate-type
[1] https://www.w3schools.com/xml/el_all.asp
was:
I am getting error in my IDE during xml validation
*
{noformat}
cvc-complex-type.2.4.b: The content of element 'providers' is not complete. One of '{"urn:elytron:client:1.1":global}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{noformat}
<providers>
<use-service-loader/>
</providers>
{noformat}
*
{noformat}
cvc-complex-type.2.4.b: The content of element 'configuration' is not complete. One of '{"urn:elytron:client:
1.1":set-host, "urn:elytron:client:1.1":set-port, "urn:elytron:client:1.1":set-protocol, "urn:elytron:client:
1.1":abstract-user-spec, "urn:elytron:client:1.1":set-mechanism-realm, "urn:elytron:client:1.1":rewrite-user-
name-regex, "urn:elytron:client:1.1":set-mechanism-properties, "urn:elytron:client:1.1":set-authorization-
name, "urn:elytron:client:1.1":abstract-sasl-factories}' is expected.
{noformat}
While having this snippet in my wildfly-config.xml
{code:xml|title=wildfly-config.xml}
<configuration name="default">
<sasl-mechanism-selector selector="EXTERNAL"/>
<credentials>
<key-store-reference key-store-name="keystore">
<key-store-clear-password password="${password}"/>
</key-store-reference>
</credentials>
<providers>
<use-service-loader/>
</providers>
</configuration>
{noformat}
Based on [1] I think elements in xsd:all should contain minOccurs="0" explicitly. E.g. <xsd:element ref="abstract-user-spec" minOccurs="0"/>.
I see this problem in providers-type, authentication-configuration-type, key-pair-type and certificate-type
[1] https://www.w3schools.com/xml/el_all.asp
> elytron-client-1.1.xsd xsd:all minOccurs="0"
> --------------------------------------------
>
> Key: ELY-1568
> URL: https://issues.jboss.org/browse/ELY-1568
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client, XML
> Affects Versions: 1.3.0.Final
> Reporter: Martin Choma
>
> I am getting error in my IDE during xml validation
> * {noformat}
> cvc-complex-type.2.4.b: The content of element 'providers' is not complete. One of '{"urn:elytron:client:1.1":global}' is expected.
> {noformat}
> While having this snippet in my wildfly-config.xml
> {noformat}
> <providers>
> <use-service-loader/>
> </providers>
> {noformat}
> * {noformat}
> cvc-complex-type.2.4.b: The content of element 'configuration' is not complete. One of '{"urn:elytron:client:
> 1.1":set-host, "urn:elytron:client:1.1":set-port, "urn:elytron:client:1.1":set-protocol, "urn:elytron:client:
> 1.1":abstract-user-spec, "urn:elytron:client:1.1":set-mechanism-realm, "urn:elytron:client:1.1":rewrite-user-
> name-regex, "urn:elytron:client:1.1":set-mechanism-properties, "urn:elytron:client:1.1":set-authorization-
> name, "urn:elytron:client:1.1":abstract-sasl-factories}' is expected.
> {noformat}
> While having this snippet in my wildfly-config.xml
> {code:xml|title=wildfly-config.xml}
> <configuration name="default">
> <sasl-mechanism-selector selector="EXTERNAL"/>
> <credentials>
> <key-store-reference key-store-name="keystore">
> <key-store-clear-password password="${password}"/>
> </key-store-reference>
> </credentials>
> <providers>
> <use-service-loader/>
> </providers>
> </configuration>
> {noformat}
> Based on [1] I think elements in xsd:all should contain minOccurs="0" explicitly. E.g. <xsd:element ref="abstract-user-spec" minOccurs="0"/>.
> I see this problem in providers-type, authentication-configuration-type, key-pair-type and certificate-type
> [1] https://www.w3schools.com/xml/el_all.asp
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (WFLY-10256) [JDK9+] shaded client jars with MR overlays do not have defined Multi-Release in Manifest
by Rostislav Svoboda (JIRA)
[ https://issues.jboss.org/browse/WFLY-10256?page=com.atlassian.jira.plugin... ]
Rostislav Svoboda updated WFLY-10256:
-------------------------------------
Summary: [JDK9+] shaded client jars with MR overlays do not have defined Multi-Release in Manifest (was: WildFly Common and shaded jars with MR overlays do not have defined Multi-Release in Manifest)
> [JDK9+] shaded client jars with MR overlays do not have defined Multi-Release in Manifest
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10256
> URL: https://issues.jboss.org/browse/WFLY-10256
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Reporter: Rostislav Svoboda
> Assignee: David Lloyd
> Priority: Critical
>
> Several jars with MR overlays do not have defined Multi-Release in Manifest
> Results with WildFly master from 2018-04-18:
> {code}
> DistributionTestCase.checkOverlayDirectoryAndManifestEntryForExpectedMRJars:93
> The following 4 assertions failed:
> 1) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/wildfly-elytron-tool.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
> at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
> 2) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/client/jboss-cli-client.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
> at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
> 3) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/bin/client/jboss-client.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
> at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
> 4) [Artifact /Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.3.1.Final.jar is expected to be Multi-Release JAR, jar.isMultiReleaseJar() returns false] expected:<[tru]e> but was:<[fals]e>
> at DistributionTestCase.lambda$checkOverlayDirectoryAndManifestEntryForExpectedMRJars$8(DistributionTestCase.java:90) expected:<[tru]e> but was:<[fals]e>
> {code}
> According MR JAR Support in JBoss Parent proposal WildFly Common should have Manifest entry
> * modules/system/layers/base/org/wildfly/common/main/wildfly-common-1.3.1.Final.jar
> I believe shaded jars should also have Manifest entry
> * bin/wildfly-elytron-tool.jar
> * bin/client/jboss-cli-client.jar
> * bin/client/jboss-client.jar
> Using https://github.com/jboss-eap-qe/jarest/pull/3/files ++ mvn test -Djarest.input.dir=/Users/rsvoboda/git/wildfly/dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2495) NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
by Toshiya Kobayashi (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2495?page=com.atlassian.jira.plugi... ]
Toshiya Kobayashi updated DROOLS-2495:
--------------------------------------
Git Pull Request: https://github.com/kiegroup/drools/pull/1875
Sent a PR unit test & fix.
> NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
> ------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-2495
> URL: https://issues.jboss.org/browse/DROOLS-2495
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.7.0.Final
> Reporter: Toshiya Kobayashi
> Assignee: Mario Fusco
> Labels: support
>
> Under the condition:
> - A rule uses a getter method in LHS. e.g. "Cheese(type == $p.getName())"
> - A package is serialized/deserialized
> executing the rule throws NullPointerException.
> {noformat}
> java.lang.NullPointerException: null
> at org.drools.core.rule.Declaration.getHashCode(Declaration.java:267)
> at org.drools.core.util.AbstractHashTable$FieldIndex.hashCodeOf(AbstractHashTable.java:333)
> at org.drools.core.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:397)
> at org.drools.core.util.index.TupleIndexHashTable.getOrCreate(TupleIndexHashTable.java:392)
> at org.drools.core.util.index.TupleIndexHashTable.add(TupleIndexHashTable.java:358)
> at org.drools.core.phreak.PhreakJoinNode.doLeftInserts(PhreakJoinNode.java:95)
> at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:71)
> at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:552)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:538)
> at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:373)
> at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
> at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
> at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
> at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
> at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
> at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
> at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1315)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1306)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1290)
> at org.drools.compiler.integrationtests.SerializedPackageMergeTest.testBuildAndSerializePackagesWithGetterInLHS(SerializedPackageMergeTest.java:220)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (DROOLS-2495) NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
by Toshiya Kobayashi (JIRA)
Toshiya Kobayashi created DROOLS-2495:
-----------------------------------------
Summary: NullPointerException in Declaration.getHashCode() when getter in LHS and serialize/deserialize package
Key: DROOLS-2495
URL: https://issues.jboss.org/browse/DROOLS-2495
Project: Drools
Issue Type: Bug
Components: core engine
Affects Versions: 7.7.0.Final
Reporter: Toshiya Kobayashi
Assignee: Mario Fusco
Under the condition:
- A rule uses a getter method in LHS. e.g. "Cheese(type == $p.getName())"
- A package is serialized/deserialized
executing the rule throws NullPointerException.
{noformat}
java.lang.NullPointerException: null
at org.drools.core.rule.Declaration.getHashCode(Declaration.java:267)
at org.drools.core.util.AbstractHashTable$FieldIndex.hashCodeOf(AbstractHashTable.java:333)
at org.drools.core.util.AbstractHashTable$SingleIndex.hashCodeOf(AbstractHashTable.java:397)
at org.drools.core.util.index.TupleIndexHashTable.getOrCreate(TupleIndexHashTable.java:392)
at org.drools.core.util.index.TupleIndexHashTable.add(TupleIndexHashTable.java:358)
at org.drools.core.phreak.PhreakJoinNode.doLeftInserts(PhreakJoinNode.java:95)
at org.drools.core.phreak.PhreakJoinNode.doNode(PhreakJoinNode.java:71)
at org.drools.core.phreak.RuleNetworkEvaluator.switchOnDoBetaNode(RuleNetworkEvaluator.java:552)
at org.drools.core.phreak.RuleNetworkEvaluator.evalBetaNode(RuleNetworkEvaluator.java:538)
at org.drools.core.phreak.RuleNetworkEvaluator.evalNode(RuleNetworkEvaluator.java:373)
at org.drools.core.phreak.RuleNetworkEvaluator.innerEval(RuleNetworkEvaluator.java:333)
at org.drools.core.phreak.RuleNetworkEvaluator.outerEval(RuleNetworkEvaluator.java:169)
at org.drools.core.phreak.RuleNetworkEvaluator.evaluateNetwork(RuleNetworkEvaluator.java:127)
at org.drools.core.phreak.RuleExecutor.reEvaluateNetwork(RuleExecutor.java:212)
at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:87)
at org.drools.core.concurrent.AbstractRuleEvaluator.internalEvaluateAndFire(AbstractRuleEvaluator.java:34)
at org.drools.core.concurrent.SequentialRuleEvaluator.evaluateAndFire(SequentialRuleEvaluator.java:43)
at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1067)
at org.drools.core.common.DefaultAgenda.internalFireAllRules(DefaultAgenda.java:1014)
at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1006)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1315)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1306)
at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1290)
at org.drools.compiler.integrationtests.SerializedPackageMergeTest.testBuildAndSerializePackagesWithGetterInLHS(SerializedPackageMergeTest.java:220)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years
[JBoss JIRA] (SWSQE-165) Create Kiali Phase (Step 2) of Pipeline
by Hayk Hovsepyan (JIRA)
[ https://issues.jboss.org/browse/SWSQE-165?page=com.atlassian.jira.plugin.... ]
Hayk Hovsepyan updated SWSQE-165:
---------------------------------
Description:
{panel:title=
Step 2 (SWSQE-165)}
- Refactor [Istio and Kiali on Openshift |http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/]Jenkins Job
- Refactor prepare.env in just two steps
* Create a Jenkins Job to build kiali (Make optional because I think sometimes we don't want to build Kiali - but Mandatory for PRs and Nightly Jobs) using the building part of prepare env script
* Create a Jenkins Job to deploy Kiali based Mazz [Comment |https://github.com/kiali/kiali/pull/119#issuecomment-376519224]
{code:shell}
curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
| oc create -n istio-system -f -
curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
| IMAGE_NAME=kiali/kiali IMAGE_VERSION=latest NAMESPACE=istio-system VERBOSE_MODE=4 envsubst \
| oc create -n istio-system -f -
{code}
where IMAGE_NAME and IMAGE_VERSION could be changed to QE images (built on step 2.1.2) it can be deployed developers images by default
I don't know if the best configuration is two scripts (one for build or another to deploy) or just two functions on the same script but with optional parameters, so I'm leaving this one as you may you prefer to move this forward
* Make sure that Kiali installation allows to install more than one Kiali on the same cluster.
{panel}
was:
{panel:title=
Step 2 (SWSQE-165)}
- Refactor [Istio and Kiali on Openshift |http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/]Jenkins Job
- Refactor prepare.env in just two steps
* Create a Jenkins Job to build kiali (Make optional because I think sometimes we don't want to build Kiali - but Mandatory for PRs and Nightly Jobs) using the building part of prepare env script
* Create a Jenkins Job to deploy Kiali based Mazz [Comment |https://github.com/kiali/kiali/pull/119#issuecomment-376519224]
{code:shell}
curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
| oc create -n istio-system -f -
curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
| IMAGE_NAME=kiali/kiali IMAGE_VERSION=latest NAMESPACE=istio-system VERBOSE_MODE=4 envsubst \
| oc create -n istio-system -f -
{code}
where IMAGE_NAME and IMAGE_VERSION could be changed to QE images (built on step 2.1.2) it can be deployed developers images by default
I don't know if the best configuration is two scripts (one for build or another to deploy) or just two functions on the same script but with optional parameters, so I'm leaving this one as you may you prefer to move this forward
{panel}
> Create Kiali Phase (Step 2) of Pipeline
> ---------------------------------------
>
> Key: SWSQE-165
> URL: https://issues.jboss.org/browse/SWSQE-165
> Project: Kiali QE
> Issue Type: Sub-task
> Reporter: Guilherme Baufaker Rêgo
> Assignee: Hayk Hovsepyan
>
> {panel:title=
> Step 2 (SWSQE-165)}
> - Refactor [Istio and Kiali on Openshift |http://jenkins2.bc.jonqe.lab.eng.bos.redhat.com:8080/job/Istio-and-Kiali-on-Openshift/]Jenkins Job
> - Refactor prepare.env in just two steps
> * Create a Jenkins Job to build kiali (Make optional because I think sometimes we don't want to build Kiali - but Mandatory for PRs and Nightly Jobs) using the building part of prepare env script
> * Create a Jenkins Job to deploy Kiali based Mazz [Comment |https://github.com/kiali/kiali/pull/119#issuecomment-376519224]
> {code:shell}
> curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
> | oc create -n istio-system -f -
> curl https://raw.githubusercontent.com/kiali/kiali/master/deploy/openshift/kia... \
> | IMAGE_NAME=kiali/kiali IMAGE_VERSION=latest NAMESPACE=istio-system VERBOSE_MODE=4 envsubst \
> | oc create -n istio-system -f -
> {code}
> where IMAGE_NAME and IMAGE_VERSION could be changed to QE images (built on step 2.1.2) it can be deployed developers images by default
> I don't know if the best configuration is two scripts (one for build or another to deploy) or just two functions on the same script but with optional parameters, so I'm leaving this one as you may you prefer to move this forward
> * Make sure that Kiali installation allows to install more than one Kiali on the same cluster.
> {panel}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years