November 2012 - forge-issues - Jboss List Archives

[JBoss JIRA] (FORGEPLUGINS-98) Create a plugin for JSR-107 (caching API)

by Dan Allen (JIRA)

Dan Allen created FORGEPLUGINS-98: ------------------------------------- Summary: Create a plugin for JSR-107 (caching API) Key: FORGEPLUGINS-98 URL: https://issues.jboss.org/browse/FORGEPLUGINS-98 Project: Forge Plugins Issue Type: Feature Request Reporter: Dan Allen Priority: Minor At long last, JSR-107 (http://jcp.org/en/jsr/detail?id=107) is moving again and has a functional impl (as in it runs). This would be a great candidate for a starter Forge plugin, if someone is interested. Aside from being a simple use case, the strategy here for Forge is that it could become the recommended way to experiment with the spec as it matures towards final draft, rather than developers messing with Maven Archetypes or copy-paste. Here's a nice short overview of the spec status from @myfear: http://blog.eisele.net/2012/10/java-temporary-caching-api-test-driving.ht... Red Hat is also on this spec EG. Integration with CDI will be happening soon (lots of design discussions about it have been long underway). -- 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, 5 months

4
5
0 / 0

[JBoss JIRA] (FORGE-583) Include Forge JavaDoc in Distribution download.

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-583: ---------------------------------------- Summary: Include Forge JavaDoc in Distribution download. Key: FORGE-583 URL: https://issues.jboss.org/browse/FORGE-583 Project: Forge Issue Type: Task Components: Documentation, Forge Build Affects Versions: 1.0.5.Final Reporter: Lincoln Baxter III The Forge API JavaDocs should be included in the Forge Distribution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

5
14
0 / 0

[JBoss JIRA] (FORGE-226) Support for Facets construct on Resources

by Ken Finnigan (JIRA)

[ https://issues.jboss.org/browse/FORGE-226?page=com.atlassian.jira.plugin.... ] Ken Finnigan commented on FORGE-226: ------------------------------------ Discussion on irc: (03:38:13 PM) lincolnthree: imagine you have a PomXmlResource (there is such a thing in Forge 1) (03:38:16 PM) lincolnthree: you could say: (03:38:31 PM) lincolnthree: pomResource.getFacet(ProfilesFacet.class) (03:38:53 PM) lincolnthree: So in a sense, a project would just be a Resource! (03:39:32 PM) kenfinnigan: so if I understand it.. (03:39:34 PM) lincolnthree: webXmlResource.getFacet(ServletsFacet.class) (03:39:46 PM) kenfinnigan: JavaSourceResource.getFacet(EJBFacet.class).isBeanType(Type.MESSAGE_DRIVEN_BEAN) (03:39:55 PM) lincolnthree: webXmlResource.hasFacet(ContextParamsFacet.class) (03:39:56 PM) kenfinnigan: would return an EJB that was an MDB? (03:40:01 PM) lincolnthree: right (03:40:05 PM) kenfinnigan: ie the java source of the class that is (03:40:10 PM) lincolnthree: well (03:40:17 PM) lincolnthree: based on what you've written, i'd expect it to return a boolean (03:40:18 PM) lincolnthree: but (03:40:19 PM) lincolnthree: yes (03:40:42 PM) lincolnthree: javaResource.hasFacet(ArquillianFacet.class) (03:40:44 PM) lincolnthree: etc (03:41:22 PM) kenfinnigan: ok, I was reading JavaSourceResource as a static, but from what you're saying in that example it would actually be an instance (03:41:26 PM) kenfinnigan: correct? (03:41:44 PM) kenfinnigan: so asking that java source instance if it's an MDB (03:41:47 PM) lincolnthree: javaResource.getFacet(TransactionInterceptorFacet.class).getPropagationType(); (03:41:56 PM) lincolnthree: it would be an instance (03:41:57 PM) lincolnthree: yes (03:42:04 PM) kenfinnigan: ok (03:42:21 PM) lincolnthree: so the facet would be able to inspect/install/remove certain pieces of information from java code in this case (03:42:30 PM) lincolnthree: in a very granular/controlled manner (03:42:55 PM) kenfinnigan: hmm, so where would that control lie, in the Facet or Resource, or bit of both? (03:44:42 PM) lincolnthree: the resource would have no knowledge of the facets contained within (03:44:54 PM) lincolnthree: facets would be responsible for inspecting the resource and determining their own installation sate (03:44:56 PM) lincolnthree: state (03:44:59 PM) lincolnthree: just like Project facets (03:45:07 PM) aslak: kenfinnigan, what am i saying? :) (03:45:24 PM) kenfinnigan: ok, so Resource just needs to provide the means that Facet can do the kinds of things aslak wants? (03:45:29 PM) kenfinnigan: aslak: FORGE-226 (03:45:30 PM) jbossbot: jira [FORGE-226] Support for Facets construct on Resources [Open (Unresolved) Feature Request, Major, Unassigned] https://issues.jboss.org/browse/FORGE-226 (03:45:39 PM) lincolnthree: resource needs to provide a generic Facet API (03:45:47 PM) lincolnthree: like the Project class in forge 1.x does (03:45:47 PM) kenfinnigan: lincolnthree: ok (03:46:18 PM) lincolnthree: https://github.com/forge/core/blob/master/shell-api/src/main/java/org/jbo... (03:46:31 PM) lincolnthree: something like that (03:46:39 PM) aslak: kenfinnigan, aa.. the basic idea is.. you have Facets on a Project (capabilities for a given project), the similar thing you would have on Resource level (03:47:15 PM) aslak: new XMLResource("arquillian.xml").getFacet(ArquillianFacet.class).addContainer() (03:47:51 PM) kenfinnigan: aslak: ok, so then the ArquillianFacet "knows" the correct XML to add back to the resource for addContainer()? (03:48:00 PM) aslak: yes (03:48:30 PM) kenfinnigan: ok, so Facets do all the work of modifying Resource, but Resource needs to know what kind of Facet it can deal with (03:48:33 PM) aslak: you need a 'supports(Facet)" or similar in ther ea swell (03:48:47 PM) aslak: it's basically a way to share code on resource level instead of just project level (03:48:59 PM) lincolnthree: yea (03:48:59 PM) kenfinnigan: ok, think that makes sense (03:49:18 PM) aslak: the EJB addon should know 'stuff' about a Class to determine if it's a EJB.. possible add EJB related annotations > Support for Facets construct on Resources > ----------------------------------------- > > Key: FORGE-226 > URL: https://issues.jboss.org/browse/FORGE-226 > Project: Forge > Issue Type: Feature Request > Reporter: Aslak Knutsen > Fix For: 2.0.0.Alpha1 > > > It would be handy to have Facets support for Resources so logic on recognizing/handling common resource related operations in one place. > e.g. > {code} > JavaSourceResource.getFacet(EJBFacet.class) > .isBeanType(Type.MESSAGE_DRIVEN_BEAN) > JavaSourceResource.getFacet(ArquillianFacet.class) > .addToDeployment(Class) > .getDeployments() > {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, 5 months

1
0
0 / 0

[JBoss JIRA] (FORGE-705) Migrate Resources API to Forge 2.0 AddOn

by Ken Finnigan (JIRA)

Ken Finnigan created FORGE-705: ---------------------------------- Summary: Migrate Resources API to Forge 2.0 AddOn Key: FORGE-705 URL: https://issues.jboss.org/browse/FORGE-705 Project: Forge Issue Type: Feature Request Components: Resources API Reporter: Ken Finnigan Assignee: Ken Finnigan Fix For: 2.0.0.Alpha1 -- 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, 5 months

1
1
0 / 0

[JBoss JIRA] (FORGE-575) Upgrade Maven Integration APIs to 3.0.4

by George Gastaldi (JIRA)

George Gastaldi created FORGE-575: ------------------------------------- Summary: Upgrade Maven Integration APIs to 3.0.4 Key: FORGE-575 URL: https://issues.jboss.org/browse/FORGE-575 Project: Forge Issue Type: Library Upgrade Reporter: George Gastaldi Priority: Minor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
3
0 / 0

[JBoss JIRA] (FORGE-630) Remove Solder from Forge

by George Gastaldi (JIRA)

George Gastaldi created FORGE-630: ------------------------------------- Summary: Remove Solder from Forge Key: FORGE-630 URL: https://issues.jboss.org/browse/FORGE-630 Project: Forge Issue Type: Patch Reporter: George Gastaldi Solder features should be integrated in Forge and the dependency should be removed -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
4
0 / 0

[JBoss JIRA] (FORGE-534) Separate forge core from built in plugins - resulting in a basic shell

by Lincoln Baxter III (JIRA)

Lincoln Baxter III created FORGE-534: ---------------------------------------- Summary: Separate forge core from built in plugins - resulting in a basic shell Key: FORGE-534 URL: https://issues.jboss.org/browse/FORGE-534 Project: Forge Issue Type: Feature Request Components: Shell Reporter: Lincoln Baxter III Fix For: 2.0.0.Alpha1 Forge should be completely de-coupled from the built-in plugins, and runnable as a standalone shell with plugin support. This means that the "Current Project" construct will need to be moved. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

1
1
0 / 0

[JBoss JIRA] (FORGE-364) Allow Plugins to Reference Facets from other Plugins

by Lincoln Baxter III (Created) (JIRA)

Allow Plugins to Reference Facets from other Plugins ---------------------------------------------------- Key: FORGE-364 URL: https://issues.jboss.org/browse/FORGE-364 Project: Forge Issue Type: Enhancement Components: Shell Affects Versions: 1.0.0.Beta3 Reporter: Lincoln Baxter III Assignee: Lincoln Baxter III Currently, it is impossible to reference Facets defined in a separate plugin, due to Modularity constraints. We need a way to expose this information between plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFORGE-289) Scan plugins for potential problematic dependencies

by Paul Bakker (JIRA)

Scan plugins for potential problematic dependencies --------------------------------------------------- Key: SEAMFORGE-289 URL: https://issues.jboss.org/browse/SEAMFORGE-289 Project: Seam Forge Issue Type: Enhancement Components: Plugin API Reporter: Paul Bakker Due to JBM some dependencies can brake Forge. Most problems have to do with the way Weld currently works. If a class is reimported that is used by the core Weld sees two classes for a injection point. If the cdi api is imported as a compile scoped dependency, this will brake injection in the plugin all together. Forge should scan for these kind of dependencies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
2
0 / 0

[JBoss JIRA] (FORGE-542) Create service provider plugin

by George Gastaldi (JIRA)

George Gastaldi created FORGE-542: ------------------------------------- Summary: Create service provider plugin Key: FORGE-542 URL: https://issues.jboss.org/browse/FORGE-542 Project: Forge Issue Type: Feature Request Reporter: George Gastaldi Create a plugin to create a new ServiceLoader service registration in META-INF/services, based on an interface and class implementation -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

forge-issues November 2012