October 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBBUILD-649) Cannot browse org.hibernate index in Sonatype Nexus releases repository

by Paul Gier (JIRA)

[ https://jira.jboss.org/browse/JBBUILD-649?page=com.atlassian.jira.plugin.... ] Paul Gier commented on JBBUILD-649: ----------------------------------- The repository has been regenerated, and the search seems to be working fine now. According to Sonatype, there is a 60 second timeout in the web UI when browsing a repository index. The same timeout occurs when browsing org.jboss for example. Sonatype is going to look into this timeout issue further. I will close this issue since the index seems to be working ok now. > Cannot browse org.hibernate index in Sonatype Nexus releases repository > ----------------------------------------------------------------------- > > Key: JBBUILD-649 > URL: https://jira.jboss.org/browse/JBBUILD-649 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Environment: Windows XP, > Firefox 3.6.6 > Reporter: Alex Jboss > Assignee: Paul Gier > Fix For: Repository Support 2010 > > > 1. Navigate to `https://repository.jboss.org/nexus/index.html#view-repositories;releases` > 2. Click `Browse Index` tab > 3. Expand org > 4. Try to expand org/hibernate > BUG >> > System shows a wait cursor next to `hibernate` for a while, after which it shows an error message: > Nexus returned an error: ERROR -1: transaction aborted. > Out of curiosity I tried to expand some other directories and some of them display a similar problem ( drools, jboss ), and others work ( e.g. hornetq ) > I suspect that repository's index is corrupt. The other tell-tail sign of it is that proxy repository on my local nexus can only see hibernate-core-3.5.2-Final, although the latest version is hibernate-core-3.5.3-Final ( which is what I am after ), and which is clearly available in your repository. You can verify this fact by clicking 'Browse Storage' tab and navigating to /org/hibernate/hibernate-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-649) Cannot browse org.hibernate index in Sonatype Nexus releases repository

by Paul Gier (JIRA)

[ https://jira.jboss.org/browse/JBBUILD-649?page=com.atlassian.jira.plugin.... ] Paul Gier updated JBBUILD-649: ------------------------------ Assignee: Paul Gier Fix Version/s: Repository Support 2010 > Cannot browse org.hibernate index in Sonatype Nexus releases repository > ----------------------------------------------------------------------- > > Key: JBBUILD-649 > URL: https://jira.jboss.org/browse/JBBUILD-649 > Project: JBoss Build System > Issue Type: Bug > Components: Artifact Repositories > Environment: Windows XP, > Firefox 3.6.6 > Reporter: Alex Jboss > Assignee: Paul Gier > Fix For: Repository Support 2010 > > > 1. Navigate to `https://repository.jboss.org/nexus/index.html#view-repositories;releases` > 2. Click `Browse Index` tab > 3. Expand org > 4. Try to expand org/hibernate > BUG >> > System shows a wait cursor next to `hibernate` for a while, after which it shows an error message: > Nexus returned an error: ERROR -1: transaction aborted. > Out of curiosity I tried to expand some other directories and some of them display a similar problem ( drools, jboss ), and others work ( e.g. hornetq ) > I suspect that repository's index is corrupt. The other tell-tail sign of it is that proxy repository on my local nexus can only see hibernate-core-3.5.2-Final, although the latest version is hibernate-core-3.5.3-Final ( which is what I am after ), and which is clearly available in your repository. You can verify this fact by clicking 'Browse Storage' tab and navigating to /org/hibernate/hibernate-core. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-8505) Miss configuration of jgroups "udp-async" in jgroups-channelfactory-stacks.xml

by Naoki Nishihara (JIRA)

Miss configuration of jgroups "udp-async" in jgroups-channelfactory-stacks.xml ------------------------------------------------------------------------------- Key: JBAS-8505 URL: https://jira.jboss.org/browse/JBAS-8505 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Affects Versions: JBossAS-5.1.0.GA Reporter: Naoki Nishihara Assignee: Brian Stansberry In jgroups-channelfactory-stacks.xml, "enable_bundling=false" is default in "udp-async". The description of the "udp-async" stack is "message bundling is enabled ". Is this miss configuration. Please confirm it. Thanks in advance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-8508) map metadata classes to root element names

by Alexey Loubyansky (JIRA)

map metadata classes to root element names ------------------------------------------ Key: JBAS-8508 URL: https://jira.jboss.org/browse/JBAS-8508 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 6.0.0.CR1 When schemaLocation attribute is not included in the XML deployment descriptor there needs to be a way to determine the schema and the JAXB-annotated class by the root XML element name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8464) Preload OSGi Resolver with selected bootstrap modules

by Thomas Diesler (JIRA)

Preload OSGi Resolver with selected bootstrap modules ----------------------------------------------------- Key: JBAS-8464 URL: https://jira.jboss.org/browse/JBAS-8464 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.M2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8431) Provide ServerEnvironment lookup

by Thomas Diesler (JIRA)

Provide ServerEnvironment lookup -------------------------------- Key: JBAS-8431 URL: https://jira.jboss.org/browse/JBAS-8431 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Thomas Diesler Assignee: Brian Stansberry Fix For: 7.0.0.M1 The OSGi subsystem requires access to the ServerEnvironment. Please document (in javadoc) how that can be done. We currently use a very naive ServerEnvironmentLocator that likely needs improvement. http://github.com/jbosgi/jboss-as/blob/fe484fab032d134d2fcb5f84bee7575b50... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBAS-8498) Support hot-deployment of bundles through deployments folder

by Thomas Diesler (JIRA)

Support hot-deployment of bundles through deployments folder ------------------------------------------------------------ Key: JBAS-8498 URL: https://jira.jboss.org/browse/JBAS-8498 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: OSGi integration Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.0.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2726) Missing "g" xml namespace

by Kris Verlaenen (JIRA)

Missing "g" xml namespace ------------------------- Key: JBRULES-2726 URL: https://jira.jboss.org/browse/JBRULES-2726 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (flow) Environment: When using the latest BPMN2 version, the "g" namespace, for example used for ruleFlowGroup attribute in the rule task, can be missing Reporter: Kris Verlaenen Assignee: Kris Verlaenen Fix For: 5.2.0.M1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBXB-253) resolve schemas by element QName

by Alexey Loubyansky (JIRA)

resolve schemas by element QName -------------------------------- Key: JBXB-253 URL: https://jira.jboss.org/browse/JBXB-253 Project: JBoss XML Binding (JBossXB) Issue Type: Feature Request Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: JBossXB-2.0.2.GA When schema location is not available and multiple schemas share the same namespace there needs to be a way to identify specific schema by the root element name. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8504) <any-address/> interface specification lost in translation from DomainModel to ServerModel

by Brian Stansberry (JIRA)

<any-address/> interface specification lost in translation from DomainModel to ServerModel ------------------------------------------------------------------------------------------ Key: JBAS-8504 URL: https://jira.jboss.org/browse/JBAS-8504 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 7.0.0.M1 Creating a ServerInterfaceElement from an InterfaceElement loses the "anyLocal..." values, resulting in sockets being bound to a semi-random IP address. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2010