May 2011 - jboss-jira - Jboss List Archives

[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

15 years, 1 month

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

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBBUILD-677) Repository not creating index directories

by Jesse Bowes (JIRA)

Repository not creating index directories ----------------------------------------- Key: JBBUILD-677 URL: https://issues.jboss.org/browse/JBBUILD-677 Project: JBoss Build System Issue Type: Bug Components: Sonatype Reporter: Jesse Bowes Assignee: Paul Gier https://repository.jboss.org/nexus/content/groups/public-jboss/.index/ and https://repository.jboss.org/nexus/content/groups/public/.index/ are currently empty, and therefore cannot be parsed by nexus using your repositories as a proxy. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-3056) Include Standard Deviation accumulate function

by Radoslav Husar (JIRA)

Include Standard Deviation accumulate function ----------------------------------------------- Key: JBRULES-3056 URL: https://issues.jboss.org/browse/JBRULES-3056 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M2 Reporter: Radoslav Husar Assignee: Mark Proctor Priority: Minor Hi guys, I think we should add the standard deviation to accumulate functions (even excel has it ;-) I went through the Jira there is no similar request, although people are asking about it on the mailing list - so why not make their lives easier? http://lists.jboss.org/pipermail/rules-users/2011-April/019494.html It can nicely reside here with others https://github.com/droolsjbpm/drools/tree/master/drools-core/src/main/jav... Edson's article on how to add custome ones http://blog.athico.com/2007/06/accumulate-functions-edson-tirelli.html If it sounds feasible assign back to me and I can try to contribute, Cheers. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
2
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

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (AS7-919) Upgrade to Mojarra 2.1 (or even 2.1.1)

by Juergen Zimmermann (JIRA)

Upgrade to Mojarra 2.1 (or even 2.1.1) -------------------------------------- Key: AS7-919 URL: https://issues.jboss.org/browse/AS7-919 Project: Application Server 7 Issue Type: Feature Request Components: JSF Reporter: Juergen Zimmermann JBoss is still using 2.0.4. Meanwhile there is 2.1.1-b04. Please see: http://java.net/projects/javaserverfaces/downloads/download/release/mojar... http://download.java.net/maven/2/com/sun/faces/jsf-api/ http://download.java.net/maven/2/com/sun/faces/jsf-impl/ There is also a comment of JBoss' JSF expert Stan Silvert at http://community.jboss.org/thread/163922 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-9395) Add JSF Configuration for Mojarra 2.1

by Frank Langelage (JIRA)

Add JSF Configuration for Mojarra 2.1 ------------------------------------- Key: JBAS-9395 URL: https://issues.jboss.org/browse/JBAS-9395 Project: Legacy JBoss Application Server 6 Issue Type: Feature Request Security Level: Public (Everyone can see) Components: JSF Affects Versions: 6.1.0 Reporter: Frank Langelage Assignee: Stan Silvert JBoss AS 6.1 contains three JSF implementations for MyFaces-2.0, Mojarra-1.2 and Mojarra-2.0. Please add another config for Mojarra-2.1 containing Mojarra 2.1.1 for the official 6.1.0 version of JBoss AS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
0
0 / 0

[JBoss JIRA] Created: (JBRULES-2940) Kowledge Agent puts all assets in just one package

by Esteban Aliverti (JIRA)

Kowledge Agent puts all assets in just one package -------------------------------------------------- Key: JBRULES-2940 URL: https://issues.jboss.org/browse/JBRULES-2940 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.M1, 5.1.1.FINAL Reporter: Esteban Aliverti Assignee: Esteban Aliverti Fix For: 5.2.0.M2 If you add different resources to kagent containing assets defined in different packages, the result is just one package (the first package created by the kgent) containing all the assets defined in all the resources. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
7
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-292) jboss-ha-server-ispn.jar contains old schemas/infinispan-config.xsd

by Paul Ferraro (JIRA)

jboss-ha-server-ispn.jar contains old schemas/infinispan-config.xsd ------------------------------------------------------------------- Key: JBCLUSTER-292 URL: https://issues.jboss.org/browse/JBCLUSTER-292 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: HA-Server-ISPN 1.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: HA-Server-ISPN 1.0.1.Final This xsd was added to the jar at some point to workaround release bugs in infinispan (where the xsd was missing or the namespace was mislabeled) - but should not be there any longer. Because the xsd is out of date, a configuration containing newer config features will not parse correctly. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

4
7
0 / 0

[JBoss JIRA] Created: (AS7-785) Setting runtime-name seems to have no effect

by Stan Silvert (JIRA)

Setting runtime-name seems to have no effect -------------------------------------------- Key: AS7-785 URL: https://issues.jboss.org/browse/AS7-785 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.0.CR1 Reporter: Stan Silvert Assignee: Jason Greene If I upload a deployment using the runtime_name argument, it seems to have no effect. Also, for consistency with internals, suggest using "runtime-name" for the argument instead of the underscored "runtime_name". [standalone@localhost:9999 /] deploy /as7trunk/as7jsf/mojarra2.0/jsfwithjsp/target/jsfwithjsp.war --runtime_name=jsfjsp 'jsfwithjsp.war' deployed successfully. [standalone@localhost:9999 /] /deployment=jsfwithjsp.war/:read-resource { "outcome" => "success", "result" => { "name" => "jsfwithjsp.war", "runtime-name" => "jsfwithjsp.war", "content" => [{ "input-stream-index" => 0, "hash" => bytes { 0xe1, 0xfb, 0xee, 0x1c, 0xed, 0x9e, 0x8e, 0x1e, 0xa0, 0x09, 0xd6, 0x47, 0xc1, 0x44, 0x5d, 0xdb, 0xca, 0x7d, 0xc0, 0x72 } }], "enabled" => true }, "compensating-operation" => undefined } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

2
3
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 May 2011