[ https://issues.jboss.org/browse/JBIDE-18857?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-18857 at 12/10/14 2:34 PM: ------------------------------------------------------------------------- Batch uses annotation javax.inject.Named on Java classes. We have it processed in CDI tools, but batch project can do without CDI, as javax.inject.Named does not require CDI. It seems we may need nature/facet/builder for a Batch project. Batch tools should not depend on whether the project has or not CDI nature/facet. Batch project definitely needs its own model which should collect Batch specific objects and should be built by some builder. There is a way to avoid Batch nature/builder - use extension to KB nature/builder. KB nature now is attached to all projects that would use in full JBoss Tools capabilities. So, kb plugin may define interfaces and extension point for models that would be stored/accessed through KBModel, and had their builders called through KBBuilder. We have already used it for JSF 2 project model. Theoretically, CDI model/builder could be also implemented in this way. So, here is choice for voting. 1. New nature/builder for projects with Batch capabilities. 2. Framework that uses KB nature/builder to access and build projects with Batch capabilities (detected by Batch specific libraries). 3. Just manage Batch model through JDT's IElementChangedListener - this approach will have bad performance for large projects (but maybe Batch projects are small?) 4. ... I would prefer (1) as most straitforward and Eclipse-like, but ready to implement any of the choices. Though, on second thought, it is better to start with (2), since it includes the same implementation for project and builder, just without registering nature and builder, and later can easily be switched to (1) if needed. [~maxandersen], [~akazakov], please take a look. was (Author: scabanovich): Batch uses annotation javax.inject.Named on Java classes. We have it processed in CDI tools, but batch project can do without CDI, as javax.inject.Named does not require CDI. It seems we may need nature/facet/builder for a Batch project. Batch tools should not depend on whether the project has or not CDI nature/facet. Batch project definitely needs its own model which should collect Batch specific objects and should be built by some builder. There is a way to avoid Batch nature/builder - use extension to KB nature/builder. KB nature now is attached to all projects that would use in full JBoss Tools capabilities. So, kb plugin may define interfaces and extension point for models that would be stored/accessed through KBModel, and had their builders called through KBBuilder. We have already used it for JSF 2 project model. Theoretically, CDI model/builder could be also implemented in this way. So, here is choice for voting. 1. New nature/builder for projects with Batch capabilities. 2. Framework that uses KB nature/builder to access and build projects with Batch capabilities (detected by Batch specific libraries). 3. Just manage Batch model through JDT's IElementChangedListener - this approach will have bad performance for large projects (but maybe Batch projects are small?) 4. ... I would prefer (1) as most straitforward and Eclipse-like, but ready to implement any of the choices. [~maxandersen], [~akazakov], please take a look. -- This message was sent by Atlassian JIRA (v6.3.8#6338)