[JBoss JIRA] (FORGE-368) Return list of properties based on higher-level understanding
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/FORGE-368?page=com.atlassian.jira.plugin.... ]
George Gastaldi updated FORGE-368:
----------------------------------
Fix Version/s: 2.0.0.Alpha3
(was: 2.0.0.Alpha2)
> Return list of properties based on higher-level understanding
> -------------------------------------------------------------
>
> Key: FORGE-368
> URL: https://issues.jboss.org/browse/FORGE-368
> Project: Forge
> Issue Type: Feature Request
> Components: Parsers / File Manipulation
> Reporter: Richard Kennard
> Fix For: 2.0.0.Alpha3
>
>
> Hi guys,
> As I understand it, Forge has an understanding of your project that transcends Java's own understanding. So for example if I say...
> field string --named foo
> ...Forge knows I'm creating a property, and it creates getters and setters for that property. But later if I do...
> org.jboss.forge.parser.java.JavaClass.getMethods()
> ...then I get back just normal methods. I'll have to check their signature for 'get' or 'set' to see if they're properties. Equally if I do...
> org.jboss.forge.parser.java.JavaClass.getFields()
> ...I get back just normal fields. I don't know if these are property fields (and if so, what their corresponding getter/setter methods are) or whether they're just internal fields (and should be ignored).
> Is there a recommended way to 'get back out' the list of properties for a class? Something that tells me a) the field; b) the getter; c) the setter?
> If it helps, for now I am using a rough implementation at: https://github.com/kennardconsulting/forge/blob/master/scaffold-metawidge...
--
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
11 years, 8 months
[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.Alpha3
(was: 2.0.0.Alpha2)
> 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.Alpha3
>
>
> 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
11 years, 8 months
[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.Alpha3
(was: 2.0.0.Alpha2)
> 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.Alpha3
>
>
> 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
11 years, 8 months
[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.Alpha3
(was: 2.0.0.Alpha2)
> 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.Alpha3
>
>
> 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
11 years, 8 months