October 2013 - overlord-issues - Jboss List Archives

[JBoss JIRA] (RTGOV-308) Maven build failure due to a typo in kie-parent-with-dependencies version 6.0.0.CR3

by Eric Wittmann (JIRA)

Eric Wittmann created RTGOV-308: ----------------------------------- Summary: Maven build failure due to a typo in kie-parent-with-dependencies version 6.0.0.CR3 Key: RTGOV-308 URL: https://issues.jboss.org/browse/RTGOV-308 Project: RTGov (Run Time Governance) Issue Type: Bug Reporter: Eric Wittmann Assignee: Gary Brown When building ep-drools in rtgov, I get the following error (using a clean .m2): {code} [INFO] ------------------------------------------------------------------------ [INFO] Building Overlord RTGov::Modules::Event Processor::EP Drools 2.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.272s [INFO] Finished at: Thu Oct 31 10:10:43 EDT 2013 [INFO] Final Memory: 6M/147M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project ep-drools: Could not resolve dependencies for project org.overlord.rtgov.event-processor:ep-drools:jar:2.0.0-SNAPSHOT: Failed to collect dependencies for [org.overlord.rtgov.common:rtgov-common:jar:2.0.0-SNAPSHOT (provided), org.overlord.rtgov.event-processor:ep-core:jar:2.0.0- SNAPSHOT (provided), org.drools:drools-core:jar:6.0.0.CR3 (provided), org.drools:drools-compiler:jar:6.0.0.CR3 (provided), org.kie:kie-api:jar:6.0.0.CR3 (provid ed), org.kie:kie-internal:jar:6.0.0.CR3 (provided), org.codehaus.jackson:jackson-core-asl:jar:1.9.9 (provided), org.codehaus.jackson:jackson-mapper-asl:jar:1.9. 9 (provided), org.hibernate.javax.persistence:hibernate-jpa-2.0-api:jar:1.0.1.Final (provided), org.overlord.rtgov.activity-management:activity:jar:2.0.0-SNAPSH OT (test), junit:junit:jar:4.11 (test)]: Failed to read artifact descriptor for org.drools:drools-core:jar:6.0.0.CR3: Failure to find org.jboss.integrationplatf orm:jboss-integration-platform-bom:pom:6.0.0-20130823.165815-2 in https://repository.jboss.org/nexus/content/groups/public/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1] {code} Notice this part of the above error: {code} Failed to read artifact descriptor for org.drools:drools-core:jar:6.0.0.CR3: Failure to find org.jboss.intregrationplatform:jboss-integration-platform-bom:pom:6.0.0-20130823.165815-2 {code} And then notice that the groupId is "intregration". This was fixed in the drools codebase, but obviously after CR3 was released. The reference to "org.jboss.intregration" can be found in kie-parent-with-dependencies version 6.0.0.CR3. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-246) Deleted derived artifact are still available

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-246?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-246: ----------------------------------------------- Kurt T Stam <kurt.stam(a)redhat.com> changed the Status of [bug 1011937|https://bugzilla.redhat.com/show_bug.cgi?id=1011937] from ASSIGNED to MODIFIED > Deleted derived artifact are still available > -------------------------------------------- > > Key: SRAMP-246 > URL: https://issues.jboss.org/browse/SRAMP-246 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-246) Deleted derived artifact are still available

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-246?page=com.atlassian.jira.plugin.... ] Kurt Stam resolved SRAMP-246. ----------------------------- Resolution: Done > Deleted derived artifact are still available > -------------------------------------------- > > Key: SRAMP-246 > URL: https://issues.jboss.org/browse/SRAMP-246 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-246) Deleted derived artifact are still available

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-246?page=com.atlassian.jira.plugin.... ] Kurt Stam closed SRAMP-246. --------------------------- > Deleted derived artifact are still available > -------------------------------------------- > > Key: SRAMP-246 > URL: https://issues.jboss.org/browse/SRAMP-246 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-246) Deleted derived artifact are still available

by Kurt Stam (JIRA)

[ https://issues.jboss.org/browse/SRAMP-246?page=com.atlassian.jira.plugin.... ] Kurt Stam updated SRAMP-246: ---------------------------- Git Pull Request: https://github.com/Governance/s-ramp/pull/351 > Deleted derived artifact are still available > -------------------------------------------- > > Key: SRAMP-246 > URL: https://issues.jboss.org/browse/SRAMP-246 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Persistence > Reporter: Kurt Stam > Assignee: Kurt Stam > Fix For: 0.3.1 - jBPM - bugfix 1 > > > When a primary artifact is deleted the JCR node is moved from being rooted in '/s-ramp' to '/s-ramp-trash'. It's derived nodes are children and are moved as well. The JCR filter by '/s-ramp' still brings back the derived nodes, so they don't appear as being deleted. Opened a discussion with the ModeShape guys about this: https://community.jboss.org/message/840238#840238 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-259) Remove modeshape BOM once modeshape is synched with integration platform bom

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-259: ----------------------------------- Summary: Remove modeshape BOM once modeshape is synched with integration platform bom Key: SRAMP-259 URL: https://issues.jboss.org/browse/SRAMP-259 Project: S-RAMP Issue Type: Task Security Level: Public (Everyone can see) Reporter: Eric Wittmann Assignee: Kurt Stam Fix For: 0.5.0 - Future All the projects should be aligning with the jboss integration platform BOM, which should force all projects to use common versions of libraries. Once modeshape has been aligned with the BOM, s-ramp won't need to import the modeshape BOM anymore. Note: s-ramp imports the modeshape BOM in the root pom.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-258) Create a tomcat compatible deployment/package

by Eric Wittmann (JIRA)

[ https://issues.jboss.org/browse/SRAMP-258?page=com.atlassian.jira.plugin.... ] Work on SRAMP-258 started by Eric Wittmann. > Create a tomcat compatible deployment/package > --------------------------------------------- > > Key: SRAMP-258 > URL: https://issues.jboss.org/browse/SRAMP-258 > Project: S-RAMP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1. We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-258) Create a tomcat compatible deployment/package

by Eric Wittmann (JIRA)

Eric Wittmann created SRAMP-258: ----------------------------------- Summary: Create a tomcat compatible deployment/package Key: SRAMP-258 URL: https://issues.jboss.org/browse/SRAMP-258 Project: S-RAMP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Core Reporter: Eric Wittmann Assignee: Eric Wittmann Fix For: 0.3.1 - jBPM - bugfix 1 Currently s-ramp is only built to deploy successfully on JBoss 7 and JBoss EAP 6.1. We need a version that runs on Tomcat so that community users can more easily get started (both running and contributing). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-255: ----------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com> changed the Status of [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] from NEW to MODIFIED > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SRAMP-255) Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/SRAMP-255?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on SRAMP-255: ----------------------------------------------- Eric Wittmann <eric.wittmann(a)redhat.com> made a comment on [bug 1016591|https://bugzilla.redhat.com/show_bug.cgi?id=1016591] A workaround as described above has been implemented. The login module now looks for the Request first in the thread local variable. If not found there, it will attempt to find the Request in the PolicyContext. The former will only work if the application is configured to use the valve. The following BZ exists to fix the PolicyContext bug: https://bugzilla.redhat.com/show_bug.cgi?id=1022069 Once that bug is fixed, then the PolicyContext approach will always work and the thread local valve will not be required. In either case, the overlord apps should now have the valve configured, and thus should work in all cases. > Undeployment of *any* web app in JBoss 7/EAP 6 results in broken authentication in Overlord apps > ------------------------------------------------------------------------------------------------ > > Key: SRAMP-255 > URL: https://issues.jboss.org/browse/SRAMP-255 > Project: S-RAMP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 0.3.0 - JBPM6 Integration > Reporter: Eric Wittmann > Assignee: Eric Wittmann > Fix For: 0.3.1 - jBPM - bugfix 1 > > > This is actually an EAP bug: > https://bugzilla.redhat.com/show_bug.cgi?id=1016591 > This JIRA issue tracks the workaround used in Overlord. The workaround is only necessary until the EAP bug is fixed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

overlord-issues October 2013