November 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCL-84) Extend the ClassLoadingMetaData filtered package semantics

by Adrian Brock (JIRA)

Extend the ClassLoadingMetaData filtered package semantics ---------------------------------------------------------- Key: JBCL-84 URL: https://jira.jboss.org/jira/browse/JBCL-84 Project: JBoss ClassLoader Issue Type: Feature Request Components: MetaData Reporter: Adrian Brock Currently the ClassLoadingMetaData has some includedPackages and excludedPackages metadata. This is just a comma seperated list of explicit package names. This metadata should be extended to make it more flexible. e.g. using globing <classloader> <excluded type="glob">com.foo.*</included> or explicitly naming the filter <classloader> <excluded class="com.foo.MyClassFilter>...</excluded> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-663) Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search

by BTO Sabre (JIRA)

Some artifacts, like org.hibernate:hibernate-entitymanager:3.5.6-Final are missing in Nexus search -------------------------------------------------------------------------------------------------- Key: JBBUILD-663 URL: https://jira.jboss.org/browse/JBBUILD-663 Project: JBoss Build System Issue Type: Bug Components: Sonatype Reporter: BTO Sabre Assignee: Paul Gier Priority: Critical Some artifacts are in repo but not show up in Nexus. I guess this is index issue. For example below artifact is in repo https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibern... but not in Nexus https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.hibern... This bug is critical because we are unable to download this artifact using jboss-public repository proxied in our Nexus. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-660) extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy

by Ian Springer (JIRA)

extension of archetype jar gets changes from .jar to .maven-archetype when published to Nexus releases repo via mvn deploy --------------------------------------------------------------------------------------------------------------------------- Key: JBBUILD-660 URL: https://jira.jboss.org/browse/JBBUILD-660 Project: JBoss Build System Issue Type: Bug Components: Sonatype Affects Versions: Maven Repository Nexus Rollout Reporter: Ian Springer Assignee: Paul Gier Priority: Critical I published the following artifact using 'mvn deploy' from a project with type maven-archetype: https://repository.jboss.org/nexus/content/repositories/releases/org/rhq/... Notice the jarfile's extension got changed from .jar to .maven-archetype. I'm not sure if it was the maven deploy plugin or Nexus that did this. but I suspect it was Nexus. It needs to have the extension .jar, because the archetype:generate goal assumes all archetype artifacts will have that extension. -- 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

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBBUILD-629) Include the release comments from staged repo, in the audit.json file

by jaikiran pai (JIRA)

Include the release comments from staged repo, in the audit.json file --------------------------------------------------------------------- Key: JBBUILD-629 URL: https://jira.jboss.org/browse/JBBUILD-629 Project: JBoss Build System Issue Type: Feature Request Reporter: jaikiran pai Assignee: John Casey Right now the *.audit.json files (ex: https://repository.jboss.org/nexus/content/groups/public/org/jboss/metada...) do not include the comments that were added during the release, in the staged repo. It will be useful to have this info available in the audit file. -- 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

13 years, 7 months

3
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-608) Research repository file upload size limit

by Paul Gier (JIRA)

Research repository file upload size limit ------------------------------------------ Key: JBBUILD-608 URL: https://jira.jboss.org/jira/browse/JBBUILD-608 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assignee: Paul Gier Fix For: Repository Support 2010 It was reported during testing that the deployment fail on files greater than ~50MB. This limit is probably set in the web server configuration. The limit should be set to at least 100MB and documented in the wiki. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1135) Move generation should be described in a drl

by Geoffrey De Smet (JIRA)

Move generation should be described in a drl -------------------------------------------- Key: JBRULES-1135 URL: http://jira.jboss.com/jira/browse/JBRULES-1135 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Solver Affects Versions: 4.0.0.GA Reporter: Geoffrey De Smet Assigned To: Geoffrey De Smet Fix For: FUTURE instead of MoveFactory POJO -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2049) org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations

by Bob Shanahan (JIRA)

org.drools.runtime.rule StatefulRuleSession.fireAllRules(org.drools.runtime.rule.AgendaFilter af) has no AgendaFilter implementations ------------------------------------------------------------------------------------------------------------------------------------- Key: JBRULES-2049 URL: https://jira.jboss.org/jira/browse/JBRULES-2049 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-core Affects Versions: 5.0.0.CR1 Environment: Java 1.5 Reporter: Bob Shanahan Assignee: Mark Proctor StatefulSession.fireAllRules(org.drools.spi.AgendaFilter af) has several implementations of AgendaFilter for filtering rules. Why aren't the AgendaFilters common? Even the Activation class between them is different, so it is not simple to workaround by wrapping org.drools.spi.AgendaFilter impls. It would be handy if there were out-of-the-box AgendaFilters for implementations of StatefulRuleSession. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
8
0 / 0

[JBoss JIRA] Created: (JBRULES-2292) event feed class hangs when using fireUntilHalt

by Jeff DeLong (JIRA)

event feed class hangs when using fireUntilHalt ----------------------------------------------- Key: JBRULES-2292 URL: https://jira.jboss.org/jira/browse/JBRULES-2292 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Environment: Eclipse 3.5 with JBoss Tools JBoss Drools Core 5.1.0.truck-N200908260601-H218 using Drools Runtime drools-5.1.0.SNAPSHOT-bin from Sept 10, 2009 Reporter: Jeff DeLong Assignee: Mark Proctor I added a new test to my project: KioskRulesTwoThreadsTest that calls another class InsertEvents in a separate thread, then calls fireUntilHalt. InsertEvents inserts three facts and then three events three times, then mysteriously stops. All I see in the AuditLog is the 12 Object inserted (well and a single Object removed). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
5
0 / 0

[JBoss JIRA] Created: (JGRP-1193) Simplify RspFilter interface

by Vladimir Blagojevic (JIRA)

Simplify RspFilter interface ---------------------------- Key: JGRP-1193 URL: https://jira.jboss.org/jira/browse/JGRP-1193 Project: JGroups Issue Type: Task Affects Versions: 2.9, 2.8, 2.7 Reporter: Vladimir Blagojevic Assignee: Vladimir Blagojevic Fix For: 3.0 RspFilter interface although having only two methods in its contract has been a source of some confusion regarding the semantics of response filtering. In order to simplify and make response filtering semantics easier to understand and implement a new RspFilter has been proposed for 3.0. RspFilterResult responseReceived(Object response, Address sender); RspFilterResult is an enum with four states where each state is essentially a combination of two boolean variables: validResponse and needMoreResponses. Original discussion reference: http://sourceforge.net/mailarchive/forum.php?thread_name=4BC8943F.2000101... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
8
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2120) Tx logic doesn't take method-intf type into acount

by Carlo de Wolf (JIRA)

Tx logic doesn't take method-intf type into acount -------------------------------------------------- Key: EJBTHREE-2120 URL: https://jira.jboss.org/browse/EJBTHREE-2120 Project: EJB 3.0 Issue Type: Bug Components: transactions Reporter: Carlo de Wolf Fix For: bom-as6-0.1.3 -- 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

13 years, 7 months

2
8
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2010