August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4391) [DMN Designer] Search overlays constraint dialogue

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-4391?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-4391: ------------------------------------ Sprint: 2019 Week 32-34 (was: 2019 Week 32-34, 2019 Week 35-37) > [DMN Designer] Search overlays constraint dialogue > --------------------------------------------------- > > Key: DROOLS-4391 > URL: https://issues.jboss.org/browse/DROOLS-4391 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.25.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-08-02 10-43-15.png > > > In the attached screenshot is shown state of having search element present when constraint dialogue was invoked. It overlays the constraint dialogue and makes it not usable. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12448) pgrade jboss-transaction-api_1.2_spec to 2.0.0.CR1

by Thomas Jenkinson (Jira)

Thomas Jenkinson created WFLY-12448: --------------------------------------- Summary: pgrade jboss-transaction-api_1.2_spec to 2.0.0.CR1 Key: WFLY-12448 URL: https://issues.jboss.org/browse/WFLY-12448 Project: WildFly Issue Type: Component Upgrade Components: Transactions Reporter: Thomas Jenkinson Assignee: Thomas Jenkinson Available here: https://repository.jboss.org/nexus/content/groups/public/org/jboss/spec/j... Commits are here https://github.com/jboss/jboss-jakarta-jta-api/commits/2.0.0.CR1 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12387) Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.0.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12387?page=com.atlassian.jira.plugin... ] Brian Stansberry reopened WFLY-12387: ------------------------------------- [~yersan] Reopened. Sorry, I'd resolved another one that said .CR1 in the title and didn't notice this one said .Final. Most of them say .Final so I stopped resolving them. > Upgrade org.jboss.spec.javax.annotation from 1.0.1.Final to 2.0.0.Final > ----------------------------------------------------------------------- > > Key: WFLY-12387 > URL: https://issues.jboss.org/browse/WFLY-12387 > Project: WildFly > Issue Type: Sub-task > Components: EE > Reporter: Yeray Borges > Assignee: Yeray Borges > Priority: Critical > Fix For: 18.0.0.Beta1 > > > Upgrade Common Annotations JSR-250 to Jakarta EE > Fork: https://github.com/jboss/jboss-jakarta-annotations-api_spec > Working branch: [JBEE-207 | https://github.com/jboss/jboss-jakarta-annotations-api_spec/tree/JBEE-207] -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-223) Release JBoss / Jakarta JASPI 2.0.0.CR1

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-223?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-223. ----------------------------------- Resolution: Done > Release JBoss / Jakarta JASPI 2.0.0.CR1 > --------------------------------------- > > Key: JBEE-223 > URL: https://issues.jboss.org/browse/JBEE-223 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-223) Release JBoss / Jakarta JASPI 2.0.0.CR1

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-223?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated JBEE-223: ---------------------------------- Fix Version/s: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > Release JBoss / Jakarta JASPI 2.0.0.CR1 > --------------------------------------- > > Key: JBEE-223 > URL: https://issues.jboss.org/browse/JBEE-223 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-212) Port PicketBox integration changes to JBoss / Jakarta JASPI Form

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-212?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-212. ----------------------------------- Fix Version/s: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 Resolution: Done > Port PicketBox integration changes to JBoss / Jakarta JASPI Form > ---------------------------------------------------------------- > > Key: JBEE-212 > URL: https://issues.jboss.org/browse/JBEE-212 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-210) Correct the JASPI build so it builds

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-210?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-210. ----------------------------------- Fix Version/s: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 Resolution: Done > Correct the JASPI build so it builds > ------------------------------------ > > Key: JBEE-210 > URL: https://issues.jboss.org/browse/JBEE-210 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > > {noformat} > darranl@Flame ~/src/jakartaee/jaspic (EE4J_8) $ mvn clean install > [INFO] Scanning for projects... > Downloading from jboss-public-repository-group: https://repository.jboss.org/nexus/content/groups/public-jboss/%7BgroupId... > Downloading from jboss-public-repository-group: https://repository.jboss.org/nexus/content/groups/public-jboss/%7BgroupId... > [ERROR] [ERROR] Some problems were encountered while processing the POMs: > [WARNING] 'parent.relativePath' of POM {groupId}:authentication-spec:[unknown-version] (/home/darranl/src/jakartaee/jaspic/spec/pom.xml) points at org.eclipse.ee4j.security.auth.message-api:security.auth.message-api-parent instead of {groupId}:{parentArtifactId}, please verify your project structure @ line 20, column 13 > [FATAL] Non-resolvable parent POM for {groupId}:authentication-spec:[unknown-version]: Could not find artifact {groupId}:{parentArtifactId}:pom:1.1.2-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) and 'parent.relativePath' points at wrong local POM @ line 20, column 13 > @ > [ERROR] The build could not read 1 project -> [Help 1] > [ERROR] > [ERROR] The project {groupId}:authentication-spec:[unknown-version] (/home/darranl/src/jakartaee/jaspic/spec/pom.xml) has 1 error > [ERROR] Non-resolvable parent POM for {groupId}:authentication-spec:[unknown-version]: Could not find artifact {groupId}:{parentArtifactId}:pom:1.1.2-SNAPSHOT in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) and 'parent.relativePath' points at wrong local POM @ line 20, column 13 -> [Help 2] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException > [ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-214) Update Jaspi to use JBoss parent

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-214?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-214. ----------------------------------- Fix Version/s: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 Resolution: Done > Update Jaspi to use JBoss parent > -------------------------------- > > Key: JBEE-214 > URL: https://issues.jboss.org/browse/JBEE-214 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > > This is required to be able to publish artefacts to the JBoss repo. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-211) Update GAV for next JASPI Release

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-211?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-211. ----------------------------------- Fix Version/s: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 Resolution: Done > Update GAV for next JASPI Release > --------------------------------- > > Key: JBEE-211 > URL: https://issues.jboss.org/browse/JBEE-211 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.CR1 > > > Current pom of Java EE fork: - > <groupId>org.jboss.spec.javax.security.auth.message</groupId> > <artifactId>jboss-jaspi-api_1.1_spec</artifactId> > <version>1.0.3.Final-SNAPSHOT</version> > So will match but set version to 2.0.0.CR1-SNAPSHOT -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1829) Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1829?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1829: ---------------------------- Fix Version/s: 1.10.0.CR6 > Need to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm > ------------------------------------------------------------------------------------------------------------ > > Key: ELY-1829 > URL: https://issues.jboss.org/browse/ELY-1829 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: Ashley Abdel-Sayed > Assignee: Ashley Abdel-Sayed > Priority: Major > Fix For: 1.10.0.CR6 > > > It is requirement to use principal-transformer in aggregate-realm in between authentication-realm and authorization-realm . > -------------------------------------- > <security-domain name="TestDomain" default-realm="TestAggRealm" permission-mapper="default-permission-mapper" pre-realm-principal-transformer="test-transformer" security-event-listener="local-audit"> > <realm name="TestAggRealm" role-decoder="from-roles-attribute"/> > </security-domain> > . > . > <aggregate-realm name="TestAggRealm" authentication-realm="TestLdapRealm" authorization-realm="Test_Auth_LdapRealm"/> > -------------------------------------- > I think to achieve this there need to be something like "mid-realm-principal-transformer" in <aggregate-realm> only . -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2019