April 2013 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGE-657) Missing mime-mapping in web.xml

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-657?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-657: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Missing mime-mapping in web.xml > ------------------------------- > > Key: FORGE-657 > URL: https://issues.jboss.org/browse/FORGE-657 > Project: Forge > Issue Type: Bug > Components: Java EE APIs > Reporter: George Gastaldi > Labels: starter > Fix For: 2.0.0.Alpha4 > > > To eliminate the annoying log jboss server log: > {code} > 23:59:54,914 AVVERTENZA [javax.enterprise.resource.webcontainer.jsf.context] (http--127.0.0.1-8080-1) JSF1091: No mime type could be found for file favicon.ico. To resolve this, add a mime-type mapping to the applications web.xml > {code} > you should add on web.xml: > {code:xml} > <mime-mapping> > <extension>ico</extension> > <mime-type>image/x-icon</mime-type> > </mime-mapping> > {code} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-675) Testing under Weblogic 12c

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-675?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-675: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Testing under Weblogic 12c > -------------------------- > > Key: FORGE-675 > URL: https://issues.jboss.org/browse/FORGE-675 > Project: Forge > Issue Type: Feature Request > Components: Test Harness > Affects Versions: 1.0.6.Final > Reporter: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > It could be a nice thing if the Forge tests could run also in Weblogic 12c, maybe in a different profile. We must be aware of the licensing issues this may bring before doing it. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-736) Properties file Resource Addon - Potential implementation / backing library

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-736?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-736: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Properties file Resource Addon - Potential implementation / backing library > --------------------------------------------------------------------------- > > Key: FORGE-736 > URL: https://issues.jboss.org/browse/FORGE-736 > Project: Forge > Issue Type: Story > Components: Resources API > Reporter: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > > This "OWNER" library looks like something that might make a nice foundation for a properties file F2 addon. > Doesn't look like its in central or any reliable repo, though. But if its good enough, we could help that along. > http://lviggiano.github.com/owner/ -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-563) Create a class lookup index

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-563?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-563: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Create a class lookup index > --------------------------- > > Key: FORGE-563 > URL: https://issues.jboss.org/browse/FORGE-563 > Project: Forge > Issue Type: Feature Request > Components: Maven Integration > Affects Versions: 1.0.4.Final > Reporter: Jason Porter > Assignee: George Gastaldi > Fix For: 2.0.0.Alpha4 > > > We need to support an index of classes and dependencies which contain them. > This would allow us to do wildcard expansion, and also allow facets to depend on a class, not a specific dependency. I believe Lincoln has the information about wildcard support, for the facet dependency idea my thoughts are an index like this would allow a facet to declare a class, or collection of classes, which it requires to function. For example the faces facet could depend on FacesContext, or PhaseListener or some other class. When a facet checks to see if a project has the dependencies it could match multiple jars instead one specific jar. Again in the faces example it could match Mojarra, MyFaces, JBoss spec jars, Geromino spec jars, etc. > We could keep a local cache and add to it, we could also have an online cache available which users could push to and also merge into their local cache. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-688) Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-688?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-688: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Addition of the JavaEE 6 BOM should be encapsulated in a specific Facet > ----------------------------------------------------------------------- > > Key: FORGE-688 > URL: https://issues.jboss.org/browse/FORGE-688 > Project: Forge > Issue Type: Enhancement > Components: Plugin API > Affects Versions: 1.1.0.Final > Reporter: George Gastaldi > Priority: Minor > Fix For: 2.0.0.Alpha4 > > > It would be nice if we have a JavaEE6Facet, which installs the jboss bom. > Even though the BaseJavaEEFacet abstract class already does that, this behavior would not be possible if a custom Facet is created extending a specific subclass of BaseFacet and requiring the JavaEE6. > The more elegant solution would be to add: > {code:java} > @RequiresFacet(JavaEE6Facet.class) > {code} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-707) Forge 2 should support non-CDI addons / service registration via ServiceLoader

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-707?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-707: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Forge 2 should support non-CDI addons / service registration via ServiceLoader > ------------------------------------------------------------------------------ > > Key: FORGE-707 > URL: https://issues.jboss.org/browse/FORGE-707 > Project: Forge > Issue Type: Feature Request > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-757) Forge tests should delete the created folders

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-757?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-757: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Forge tests should delete the created folders > --------------------------------------------- > > Key: FORGE-757 > URL: https://issues.jboss.org/browse/FORGE-757 > Project: Forge > Issue Type: Bug > Components: Test Harness > Affects Versions: 1.2.0.Final > Reporter: George Gastaldi > Fix For: 1.2.4.Final, 2.0.0.Alpha4 > > > After running tests, Forge isn't removing the created temp folders inside the /tmp folder. That leads to insufficient disk space after some time if these files are not deleted. -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-770: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version > ------------------------------------------------------------------------------------------- > > Key: FORGE-770 > URL: https://issues.jboss.org/browse/FORGE-770 > Project: Forge > Issue Type: Story > Components: Container > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > > Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.) > {code} > (A) -> (B, v1) > -> Service 1 > (B, v2) > -> Service 1v2 > -> Service 2v1 > {code} > A should receive only the instance of Service 1 from (B, v1) -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-754) @Inject Instance<ExportedServiceBlah> instances; does not work. Infinite recursion.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-754?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-754: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > @Inject Instance<ExportedServiceBlah> instances; does not work. Infinite recursion. > ----------------------------------------------------------------------------------- > > Key: FORGE-754 > URL: https://issues.jboss.org/browse/FORGE-754 > Project: Forge > Issue Type: Bug > Components: Container > Reporter: Lincoln Baxter III > Assignee: Lincoln Baxter III > Fix For: 2.0.0.Alpha4 > > > Infinite recursion results from > {code} > @Inject > private Instance<Converter> converterInstances; > ... > for( Converter c : converterInstances ) { > // etc > } > {code} -- 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, 12 months

1
0
0 / 0

[JBoss JIRA] (FORGE-771) Result.success(message) should be displayed as a "Growl" notification after UICommand invocation in Eclipse.

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/FORGE-771?page=com.atlassian.jira.plugin.... ] George Gastaldi updated FORGE-771: ---------------------------------- Fix Version/s: 2.0.0.Alpha4 (was: 2.0.0.Alpha3) > Result.success(message) should be displayed as a "Growl" notification after UICommand invocation in Eclipse. > ------------------------------------------------------------------------------------------------------------ > > Key: FORGE-771 > URL: https://issues.jboss.org/browse/FORGE-771 > Project: Forge > Issue Type: Enhancement > Components: UI - Eclipse > Affects Versions: 2.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Fix For: 2.0.0.Alpha4 > > -- 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, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues April 2013