[
https://issues.jboss.org/browse/JBIDE-9120?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9120:
----------------------------------------------
I have tried what I have suggested above, and it works but without auto incremental build,
because changes in Java project ProjectJAR-B have no way to kick KB builder on KB project
ProjectWeb-A. Full rebuild of ProjectWeb-A helps, until next change in project
ProjectJAR-B.
Let us consider all possible solutions with advantages and drawbacks.
1. Add KB nature and builder automatically without user's control wherever it is
required by tools.
Advantage: Everything will work perfectly (with bugs to fix, of course).
Drawback: User will have no way to get rid of our tool interference which may be
annoying.
2. Create automatically non-updating KB model, and add marker with quick-fix adding kb
nature, or other nature that incorporates kb. We do that now, but only for some
old-fashioned projects that have some JBoss tools nature but have no kb nature or builder,
case of this issue is not covered but might be.
Advantage: Everything is under user's control.
Drawback: User has to read his manual very carefully, before he understands why some
features are not enabled in his workspace.
3. Parse src's of used Java project by kb builder of dependent kb project (which I
discussed in previous comment).
Advantage: No need to add kb builder to a Java project, if only user agrees to rebuild
manually his dependent project after changes to the Java project.
Disadvantages: It is grossly against Eclipse practices. No solution for true incremental
build.
4. Add enablement/disablement of KB to Preferences and project Properties. Under general
check-box, we can place more options that allow to adjust project's kb features to be
enabled, e.g. enable/disable building (a) facelets (b) composite components, etc. Also, we
can have preference 'Auto enable kb capabilities when needed by tools' - that will
cover Solution 1 above while providing user with control.
Advantages: covers all advantages of previous solutions.
Disadvantages: Same as in solution 2.
jboss should be able to code complete a composite component and its
attributes.
-------------------------------------------------------------------------------
Key: JBIDE-9120
URL:
https://issues.jboss.org/browse/JBIDE-9120
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF, jsp/jsf/xml source editing
Affects Versions: 3.2.1.M1
Environment: JSF2.0, maven 3.
Reporter: José Freitas
Assignee: Viacheslav Kabanovich
Labels: code_completion, composite_component, jsf
Fix For: 3.3.0.M3
I have a composite component in a jars META-INF folder, it has been stored on
META-INF/resouces/components/seamfaces (nested directories).
adding this jar as a dependency it should be possible to use this component on a JSF2
application.
In this version jbosstools validates the composite components existense but it does not
provide code completion to it.
related to:
https://issues.jboss.org/browse/JBIDE-8275
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira