December 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6177) Failed to execute goal on project jboss-as-clustering-jgroups

by Tom Jenkinson (JIRA)

Tom Jenkinson created AS7-6177: ---------------------------------- Summary: Failed to execute goal on project jboss-as-clustering-jgroups Key: AS7-6177 URL: https://issues.jboss.org/browse/AS7-6177 Project: Application Server 7 Issue Type: Bug Reporter: Tom Jenkinson Attachments: AS7-build-failed.txt -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6177) Failed to execute goal on project jboss-as-clustering-jgroups

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/AS7-6177?page=com.atlassian.jira.plugin.s... ] Tom Jenkinson updated AS7-6177: ------------------------------- Affects Version/s: 7.2.0.Alpha1 Priority: Blocker (was: Major) Description: Failed to execute goal on project jboss-as-clustering-jgroups: Could not resolve dependencies for project org.jboss.as:jboss-as-clustering-jgroups:jar:7.2.0.Alpha1-SNAPSHOT: Failure to find org.jboss.as:jboss-as-clustering-common:jar:tests:7.2.0.Alpha1-SNAPSHOT Component/s: Clustering Steps to Reproduce: To reproduce: Clean out your .m2 folder and try to build AS, it won't work... > Failed to execute goal on project jboss-as-clustering-jgroups > ------------------------------------------------------------- > > Key: AS7-6177 > URL: https://issues.jboss.org/browse/AS7-6177 > Project: Application Server 7 > Issue Type: Bug > Components: Clustering > Affects Versions: 7.2.0.Alpha1 > Reporter: Tom Jenkinson > Priority: Blocker > Attachments: AS7-build-failed.txt > > > Failed to execute goal on project jboss-as-clustering-jgroups: Could not resolve dependencies for project org.jboss.as:jboss-as-clustering-jgroups:jar:7.2.0.Alpha1-SNAPSHOT: Failure to find org.jboss.as:jboss-as-clustering-common:jar:tests:7.2.0.Alpha1-SNAPSHOT -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6159) UserPrincipal search in RemotingLoginModule seems to be broken

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/AS7-6159?page=com.atlassian.jira.plugin.s... ] Josef Cacek resolved AS7-6159. ------------------------------ Resolution: Done > UserPrincipal search in RemotingLoginModule seems to be broken > -------------------------------------------------------------- > > Key: AS7-6159 > URL: https://issues.jboss.org/browse/AS7-6159 > Project: Application Server 7 > Issue Type: Bug > Components: Security > Affects Versions: 7.1.3.Final (EAP) > Reporter: Josef Cacek > Assignee: Josef Cacek > > The code of UserPrincipal search in RemotingLoginModule seems to be invalid. > There's > {code} > UserPrincipal up = null; > for (Principal current : con.getPrincipals()) { > if (current instanceof UserPrincipal) { > up = (UserPrincipal) current; > } > break; > } > {code} > but IMO, the correct code is: > {code} > UserPrincipal up = null; > for (Principal current : con.getPrincipals()) { > if (current instanceof UserPrincipal) { > up = (UserPrincipal) current; > break; > } > } > {code} > If the connection from RemotingContext contains more Principals, then only the first is checked. I.e. If the first Principal is not an UserPrincipal, then the RemotingLoginModule doesn't work. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6176) Setup TCK job for Enterprise OSGi WebApp

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6176: ----------------------------------- Summary: Setup TCK job for Enterprise OSGi WebApp Key: AS7-6176 URL: https://issues.jboss.org/browse/AS7-6176 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6174) Setup TCK job for Enterprise OSGi JPA

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6174: ----------------------------------- Summary: Setup TCK job for Enterprise OSGi JPA Key: AS7-6174 URL: https://issues.jboss.org/browse/AS7-6174 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6175) Setup TCK job for Enterprise OSGi HttpService

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6175: ----------------------------------- Summary: Setup TCK job for Enterprise OSGi HttpService Key: AS7-6175 URL: https://issues.jboss.org/browse/AS7-6175 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6173) Initial FrameworkFactory implementation

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6173: ----------------------------------- Summary: Initial FrameworkFactory implementation Key: AS7-6173 URL: https://issues.jboss.org/browse/AS7-6173 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.CR1 Provide an initial FrameworkFactory implementation that allows to run basic Enterprise OSGi TCK sections (i.e. httpservice) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (AS7-6172) Consolidate embedded server API

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-6172: ----------------------------------- Summary: Consolidate embedded server API Key: AS7-6172 URL: https://issues.jboss.org/browse/AS7-6172 Project: Application Server 7 Issue Type: Task Components: Server Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 There are currently a number of duplicate code paths leading up to the EmbeddedServerFactory. This should be consolidated such that it is sufficient to do this {code} StandaloneServer server = EmbeddedServerFactory.create(jbossHome, modulePath, bundlePath, syspackages...); {code} The ARQ/EJB3 embedded container as well as the future FrameworkFactory integration benefit from this -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (SECURITY-711) LdapExtAdLoginModule proposal for inclusion

by Péter Radics (JIRA)

[ https://issues.jboss.org/browse/SECURITY-711?page=com.atlassian.jira.plug... ] Péter Radics updated SECURITY-711: ---------------------------------- Attachment: picketbox-r363-LdapExtAdLoginModule-with-history.patch This patch shows the difference between the original LdapExtLoginModule and LdapExtAdLoginModule > LdapExtAdLoginModule proposal for inclusion > ------------------------------------------- > > Key: SECURITY-711 > URL: https://issues.jboss.org/browse/SECURITY-711 > Project: PicketBox > Issue Type: Patch > Security Level: Public(Everyone can see) > Components: PicketBox, Security SPI > Affects Versions: PicketBox_4_0_14.Final > Environment: jboss7, active directory authentication > Reporter: Péter Radics > Assignee: Anil Saldhana > Priority: Minor > Labels: LdapExtLoginModule, active-directory, security > Attachments: picketbox-r362-LdapExtAdLoginModule.patch, picketbox-r363-LdapExtAdLoginModule-with-history.patch > > Original Estimate: 1 week > Remaining Estimate: 1 week > > Please consider including the attached LdapExtAdLoginModule into the official release. This login module is based on r362 of LdapExtLoginModule, but it's better suited for deeply nested Active Directory domains: it only uses one search for the userDN then it's resolving the roles recursively by querying attributes on DNs only. (as a side-effect, it doesn't trigger AS7-5737) -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-30) TCLFilter fails to get correct URLs from classloader in AS-5

by Arun Kumar (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-30?page=com.atlassian.jira.plug... ] Arun Kumar commented on JBLOGGING-30: ------------------------------------- i tried to implement the TCLfilter by following the robert as per below link https://community.jboss.org/message/6616 but i got failed. is there any updated jar available for this.. Please help.. > TCLFilter fails to get correct URLs from classloader in AS-5 > -------------------------------------------------------------- > > Key: JBLOGGING-30 > URL: https://issues.jboss.org/browse/JBLOGGING-30 > Project: JBoss Logging > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: jboss-logging-log4j > Affects Versions: 2.1.0.GA-jboss-logging > Reporter: jaikiran pai > Assignee: jaikiran pai > Fix For: 2.1.1.GA-jboss-logging, 2.2.0.CR2-jboss-logging > > > As explained in JBAS-6532, the TCLFilter doesn't work in AS-5 because it never attempts to use the URLClassLoader while retrieving the Classloader URLs. A patch is attached to that JIRA (details of the patch are in the forum thread) which needs to be applied in jboss-logging-log4j component to get this working. -- 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

12 years

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 December 2012