October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (SWSQE-970) Create Jenkins Job for Quay Operator Source

by Guilherme Baufaker Rêgo (Jira)

[ https://issues.jboss.org/browse/SWSQE-970?page=com.atlassian.jira.plugin.... ] Guilherme Baufaker Rêgo resolved SWSQE-970. ------------------------------------------- Resolution: Done > Create Jenkins Job for Quay Operator Source > -------------------------------------------- > > Key: SWSQE-970 > URL: https://issues.jboss.org/browse/SWSQE-970 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Guilherme Baufaker Rêgo > Assignee: Guilherme Baufaker Rêgo > Priority: Major > > We need to deploy from different operator sources for OLM. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Keep file permissions when modifying an existing credential store

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/ELY-1890?page=com.atlassian.jira.plugin.s... ] Ingo Weiss updated ELY-1890: ---------------------------- Summary: Keep file permissions when modifying an existing credential store (was: Keep file permissions when modifying the credential store) > Keep file permissions when modifying an existing credential store > ----------------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.jboss.org/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Command-Line Tool > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Keep file permissions when modifying the credential store

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/ELY-1890?page=com.atlassian.jira.plugin.s... ] Ingo Weiss updated ELY-1890: ---------------------------- Component/s: (was: Credential Store) > Keep file permissions when modifying the credential store > --------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.jboss.org/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Command-Line Tool > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12666) JPA jipijapa use optional dependencies instead of modifying the system module

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12666?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12666: ------------------------------------- +1 for this idea! > JPA jipijapa use optional dependencies instead of modifying the system module > ----------------------------------------------------------------------------- > > Key: WFLY-12666 > URL: https://issues.jboss.org/browse/WFLY-12666 > Project: WildFly > Issue Type: Enhancement > Components: JPA / Hibernate > Affects Versions: 18.0.0.Final > Reporter: Brad Maxwell > Assignee: Scott Marlow > Priority: Major > > As per [1] it requires modifying the modules under system/layers/base, these are system modules which users really should not modify. When applying patches it will complain because the module has been modified. > It would be better if these modules depended on an optional module which would not exist unless the user configured this. So for example a user could create modules/org/eclipse/persistence/impl/main/module.xml > modules/system/layers/base/org/eclipse/persistence/main/module.xml > It looks like this almost works with just adding the optional dependency, except there is an exception where it looks like the classloader may not be set correctly for some reason when the module is split into 2. > {code} > <module name="org.eclipse.persistence" xmlns="urn:jboss:module:1.5"> > ... > <module name="org.eclipse.persistence.impl" optional="true" services="import"/> > {code} > {code} > <?xml version="1.0" encoding="UTF-8"?> > <module xmlns="urn:jboss:module:1.5" name="org.eclipse.persistence.impl"> > <resources> >  > <resource-root path="eclipselink.jar"> > <filter> > <exclude path="javax/**"/> > </filter> > </resource-root> > </resources> > <dependencies> > <module name="javax.api"/> > <module name="javax.annotation.api"/> > <module name="javax.enterprise.api"/> > <module name="javax.persistence.api"/> > <module name="javax.transaction.api"/> > <module name="javax.validation.api"/> > <module name="javax.xml.bind.api"/> > <module name="org.antlr"/> > <module name="org.dom4j"/> > <module name="org.jboss.as.jpa.spi"/> > <module name="org.jboss.logging"/> > <module name="org.jboss.vfs"/> > <module name="org.eclipse.persistence"/>  > </dependencies> > </module> > {code} > {code} > Caused by: java.lang.IllegalArgumentException: Object: com.jboss.examples.jpa.model.User@4fbcb157 is not a known Entity type. > at org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.registerNewObjectForPersist(UnitOfWorkImpl.java:4326) > at org.eclipse.persistence.internal.jpa.EntityManagerImpl.persist(EntityManagerImpl.java:596) > at org.jboss.as.jpa.container.AbstractEntityManager.persist(AbstractEntityManager.java:580) > at com.jboss.examples.jpa.TestSingleton.test(TestSingleton.java:29) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.jboss.as.ee.component.ManagedReferenceLifecycleMethodInterceptor.processInvocation(ManagedReferenceLifecycleMethodInterceptor.java:96) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.delegateInterception(Jsr299BindingsInterceptor.java:79) > at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.doLifecycleInterception(Jsr299BindingsInterceptor.java:126) > at org.jboss.as.weld.interceptors.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:112) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) > at org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) > at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.weld.injection.WeldInjectionInterceptor.processInvocation(WeldInjectionInterceptor.java:53) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) > at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:112) > {code} > [1] https://docs.jboss.org/author/display/WFLY10/JPA+Reference+Guide#JPARefer... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Keep file permissions when modifying the credential store

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/ELY-1890?page=com.atlassian.jira.plugin.s... ] Ingo Weiss updated ELY-1890: ---------------------------- Summary: Keep file permissions when modifying the credential store (was: Adding to the credential store changes the file mode of the credential store) > Keep file permissions when modifying the credential store > --------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.jboss.org/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Keep file permissions when modifying the credential store

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/ELY-1890?page=com.atlassian.jira.plugin.s... ] Ingo Weiss updated ELY-1890: ---------------------------- Component/s: Command-Line Tool > Keep file permissions when modifying the credential store > --------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.jboss.org/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Command-Line Tool, Credential Store > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1890) Adding to the credential store changes the file mode of the credential store

by Ingo Weiss (Jira)

[ https://issues.jboss.org/browse/ELY-1890?page=com.atlassian.jira.plugin.s... ] Ingo Weiss moved JBEAP-17788 to ELY-1890: ----------------------------------------- Project: WildFly Elytron (was: JBoss Enterprise Application Platform) Key: ELY-1890 (was: JBEAP-17788) Issue Type: Feature Request (was: Bug) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Credential Store (was: Security) Affects Version/s: 1.11.0.CR1 (was: 7.1.5.GA) > Adding to the credential store changes the file mode of the credential store > ---------------------------------------------------------------------------- > > Key: ELY-1890 > URL: https://issues.jboss.org/browse/ELY-1890 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Credential Store > Affects Versions: 1.11.0.CR1 > Reporter: Ingo Weiss > Assignee: Ingo Weiss > Priority: Major > > Using the offline elytron.sh tool, after creating the credential store I changed the mode to 600. Using the elytron.sh tool to add credentials changes the mode back to 644. Is that intentional for it to automatically do that? I would either expect it to not change and update or not change and error out. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4644) Restore SONAR analysis on drools-wb PR

by Gabriele Cardosi (Jira)

Gabriele Cardosi created DROOLS-4644: ---------------------------------------- Summary: Restore SONAR analysis on drools-wb PR Key: DROOLS-4644 URL: https://issues.jboss.org/browse/DROOLS-4644 Project: Drools Issue Type: Task Reporter: Gabriele Cardosi Assignee: Gabriele Cardosi Fix repository configuration inside pr_jobs.groovy -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4638) A user without write permission is able to make changes in test scenario assets via settings

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-4638?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-4638: ---------------------------------- Priority: Critical (was: Blocker) > A user without write permission is able to make changes in test scenario assets via settings > -------------------------------------------------------------------------------------------- > > Key: DROOLS-4638 > URL: https://issues.jboss.org/browse/DROOLS-4638 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Guilherme Caponetto > Assignee: Gabriele Cardosi > Priority: Critical > Labels: ScenarioSimulation > Attachments: Screenshot from 2019-10-10 15-00-58.png > > > A user without write permission is able to make changes in test scenario assets via settings > Check the code ScenarioEditorPresenter#makeMenuBar in drools-wb. The save button in the menu bar is only added if the user can update the project. Similarly, it should be done for the save button in the settings dock as well. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4697) Upgrade WildFly Elytron to 1.11.0.Final

by Ivo Studensky (Jira)

[ https://issues.jboss.org/browse/WFCORE-4697?page=com.atlassian.jira.plugi... ] Ivo Studensky updated WFCORE-4697: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.11.0.Final (was: Upgrade WildFly Elytron to 1.10.4.Final) > Upgrade WildFly Elytron to 1.11.0.Final > --------------------------------------- > > Key: WFCORE-4697 > URL: https://issues.jboss.org/browse/WFCORE-4697 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Ivo Studensky > Priority: Major > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019