August 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet resolved DROOLS-1689. -------------------------------------- Resolution: Rejected > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet edited comment on DROOLS-1689 at 8/2/17 3:36 PM: ------------------------------------------------------------------ Agreed, I see it in jboss-parent on line 276. I also see the version in "mvn help:effective-pom" of optaplanner. Must be a bug in the versions plugin? It should be reporting it. was (Author: ge0ffrey): Agreed, I see it in jboss-parent on line 276. Must be a bug in the versions plugin? > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Geoffrey De Smet commented on DROOLS-1689: ------------------------------------------ Agreed, I see it in jboss-parent on line 276. Must be a bug in the versions plugin? > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1689) maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible

by Karel Suta (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1689?page=com.atlassian.jira.plugi... ] Karel Suta commented on DROOLS-1689: ------------------------------------ [~ge0ffrey] I have tried to check it in droolsjbpm-integration pom and I found out that maven-checkstyle-plugin has already defined its version. It is defined in org.jboss:jboss-parent:22, which is parent of org.jboss.integration-platform:jboss-integration-platform-parent:7.0.0.CR9. That one is a parent of org.jboss.integration-platform:jboss-integration-platform-bom. > maven-checkstyle-plugin does not have a version specified, so the build is non-reproducible > ------------------------------------------------------------------------------------------- > > Key: DROOLS-1689 > URL: https://issues.jboss.org/browse/DROOLS-1689 > Project: Drools > Issue Type: Task > Components: build > Reporter: Geoffrey De Smet > Assignee: Karel Suta > Priority: Minor > > {code} > $ mvn versions:display-plugin-updates > ... > [INFO] ------------------------------------------------------------------------ > [INFO] Building OptaPlanner multiproject parent 8.0.0-SNAPSHOT > [INFO] ------------------------------------------------------------------------ > [INFO] > [INFO] --- versions-maven-plugin:2.1:display-plugin-updates (default-cli) @ optaplanner --- > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from central > [INFO] artifact org.apache.maven.plugins:maven-checkstyle-plugin: checking for updates from jboss-public-repository-group > [INFO] > [INFO] All plugins with a version specified are using the latest versions. > [INFO] > [WARNING] The following plugins do not have their version specified: > [WARNING] maven-checkstyle-plugin ..................................... 2.17 > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9160) ChunkPartitionTestCase fails with security manager

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9160?page=com.atlassian.jira.plugin.... ] James Perkins commented on WFLY-9160: ------------------------------------- Any test that uses a {{ModelControllerClient}} is going to have this issue. > ChunkPartitionTestCase fails with security manager > -------------------------------------------------- > > Key: WFLY-9160 > URL: https://issues.jboss.org/browse/WFLY-9160 > Project: WildFly > Issue Type: Bug > Components: Batch, Test Suite > Reporter: Hynek Švábek > Assignee: James Perkins > > ChunkPartitionTestCase fails with security manager > {code} > Suppressed: java.security.AccessControlException: WFSM000001: Permission check failed (permission "("java.io.FilePermission" "/home/hsvabek/securityworkspace/VERIFICATION/2017_08_02_BEAP-7584/jboss-eap-7.1.0.ER3-src/testsuite/integration/basic/target/jbossas/standalone/tmp/auth/local1937539592015998438.challenge" "read")" in code source "(vfs:/content/batch-chunk-partition.war/WEB-INF/classes <no signer certificates>)" of "ModuleClassLoader for Module "deployment.batch-chunk-partition.war" from Service Module Loader") > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:278) > at org.wildfly.security.manager.WildFlySecurityManager.checkPermission(WildFlySecurityManager.java:175) > at java.lang.SecurityManager.checkRead(SecurityManager.java:888) > at org.wildfly.security.manager.WildFlySecurityManager.checkRead(WildFlySecurityManager.java:350) > at java.io.FileInputStream.<init>(FileInputStream.java:127) > at org.wildfly.security.sasl.localuser.LocalUserClient.evaluateMessage(LocalUserClient.java:93) > at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:180) > at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:59) > at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55) > at java.security.AccessController.doPrivileged(Native Method) > at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.lambda$handleEvent$0(ClientConnectionOpenListener.java:644) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:898) > ... 3 more > Suppressed: javax.security.sasl.SaslException: DIGEST-MD5: Server rejected authentication > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:730) > at org.jboss.remoting3.remote.ClientConnectionOpenListener$Authentication.handleEvent(ClientConnectionOpenListener.java:572) > at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) > at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66) > at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89) > at org.xnio.nio.WorkerThread.run(WorkerThread.java:571) > ... > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9166) Fix OtpSaslTestCase to reflect OTP related changes in model

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9166?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-9166: --------------------------------- Assignee: Josef Cacek > Fix OtpSaslTestCase to reflect OTP related changes in model > ----------------------------------------------------------- > > Key: WFLY-9166 > URL: https://issues.jboss.org/browse/WFLY-9166 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Follow up to JBEAP-12140. > The {{OtpSaslTestCase}} has to be updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9166) Fix OtpSaslTestCase to reflect OTP related changes in model

by Josef Cacek (JIRA)

Josef Cacek created WFLY-9166: --------------------------------- Summary: Fix OtpSaslTestCase to reflect OTP related changes in model Key: WFLY-9166 URL: https://issues.jboss.org/browse/WFLY-9166 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Josef Cacek Follow up to JBEAP-12140. The {{OtpSaslTestCase}} has to be updated. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1316) Elytron - unable to use OTP SASL mechanism

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-1316?page=com.atlassian.jira.plugin.s... ] Josef Cacek moved WFCORE-3045 to ELY-1316: ------------------------------------------ Project: WildFly Elytron (was: WildFly Core) Key: ELY-1316 (was: WFCORE-3045) Component/s: SASL (was: Security) > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: ELY-1316 > URL: https://issues.jboss.org/browse/ELY-1316 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: Josef Cacek > Assignee: Darran Lofthouse > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1316) Elytron - unable to use OTP SASL mechanism

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/ELY-1316?page=com.atlassian.jira.plugin.s... ] Josef Cacek reassigned ELY-1316: -------------------------------- Assignee: Josef Cacek (was: Darran Lofthouse) > Elytron - unable to use OTP SASL mechanism > ------------------------------------------ > > Key: ELY-1316 > URL: https://issues.jboss.org/browse/ELY-1316 > Project: WildFly Elytron > Issue Type: Bug > Components: SASL > Reporter: Josef Cacek > Assignee: Josef Cacek > Labels: eap7.1-rfe-failure > > I'm not able to use the new OTP SASL mechanism in WildFly (introduced as part of EAP7-530). > It seems the only security-realm which has subsystem support for OTP is the {{ldap-realm}} now. Nevertheless the name filtering in {{AbstractMechanismAuthenticationFactory.getMechanismNames()}} doesn't return OTP as supported in ldap-realm. Neither the {{PasswordGuessEvidence}} nor {{PasswordCredential}} checked in the method seems to be supported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3136) Add Generic type CLI commands into docs (CLI guide)

by Vikas Dadhich (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3136?page=com.atlassian.jira.plugi... ] Vikas Dadhich updated WFCORE-3136: ---------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2684 > Add Generic type CLI commands into docs (CLI guide) > --------------------------------------------------- > > Key: WFCORE-3136 > URL: https://issues.jboss.org/browse/WFCORE-3136 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Vikas Dadhich > > Documentation for generic type CLI commands is missing. > references > - https://developer.jboss.org/wiki/GenericTypeCLICommands > - https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/resource... > Related issue: https://issues.jboss.org/browse/JBEAP-5042 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2017