6 p.m.
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Denis Golovin
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:31 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9397) Create a separate feature for JSF Tools
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-9397:
---------------------------------
Fix Version/s: 3.3.0.M3
3.3.0.Beta1
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Denis Golovin
Labels: new_and_noteworthy
Fix For: 3.3.0.M3, 3.3.0.Beta1
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:50 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9397) Create a separate feature for JSF Tools
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-9397:
------------------------------
Fix Version/s: (was: 3.3.0.Beta1)
Assignee: Nick Boldt (was: Denis Golovin)
Component/s: JSF
(was: Build/Releng)
Rather than dumping this on the JSF component lead, I can do this if someone details for
me what you want in the new feature.
Need a list of included plugins and dependent features.
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M3
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:52 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9397) Create a separate feature for JSF Tools
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9397 at 8/18/11 9:51 AM:
------------------------------------------------------------
Rather than dumping this on the JSF component lead, I can do this if someone details for
me what you want in the new feature.
Need a list of included plugins and dependent features.
Also need to know which downstream features should contain this new feature so that it can
be invisibly installed under the covers if a larger containing or depending feature is
installed.
was (Author: nickboldt):
Rather than dumping this on the JSF component lead, I can do this if someone details
for me what you want in the new feature.
Need a list of included plugins and dependent features.
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
Labels: new_and_noteworthy
Fix For: 3.3.0.M3
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:39 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9397) Create a separate feature for JSF Tools
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Alexey Kazakov edited comment on JBIDE-9397 at 8/18/11 2:38 PM:
----------------------------------------------------------------
Actually we already have JSF feature which is up-to-date.
We just need to use get rid of RichFaces feature (includes plugins from common, JST, JSF
and VPE features).
So there is a list of feature dependencies:
# Common (o.j.t.common.all.feature)
# JST (o.j.t.jst.feature)
Depends on o.j.t.common.all.feature
# VPE (o.j.t.vpe.feature)
# JSF (o.j.t.jsf.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.vpe.feature
# Seam2 (o.j.t.seam.feature)
Depends on o.j.t.as.feature,
o.j.t.hibernate.feature,
o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.jsf.feature
# CDI (o.j.t.cdi.feature and o.j.t.cdi.seam.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature
was (Author: akazakov):
Actually we already have JSF feature which is up-to-date.
We just need to use get rid of RichFaces feature (includes plugins from common, JST, JSF
and VPE features).
So there is a list of feature dependencies:
# Common (o.j.t.common.all.feature)
# JST (o.j.t.jst.feature)
Depends on o.j.t.common.all.feature
# VPE (o.j.t.vpe.feature)
# JSF (o.j.t.jsf.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.vpe.feature
# Seam2 (o.j.t.seam.feature)
Depends on o.j.t.as.feature,
o.j.t.hibernate.feature,
o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.jsf.feature
# CDI (o.j.t.cdi.feature and o.j.t.cdi.seam.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M3
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:15 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9397) Create a separate feature for JSF Tools
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Alexey Kazakov edited comment on JBIDE-9397 at 8/19/11 7:15 PM:
----------------------------------------------------------------
Actually we already have JSF feature which is up-to-date.
We just need to use get rid of RichFaces feature (includes plugins from common, JST, JSF
and VPE features).
So there is a list of feature dependencies:
# Common (o.j.t.common.feature)
# JST (o.j.t.jst.feature)
Depends on o.j.t.common.feature
# VPE (o.j.t.vpe.feature)
# JSF (o.j.t.jsf.feature)
Depends on o.j.t.common.feature,
o.j.t.jst.feature,
o.j.t.vpe.feature
# Seam2 (o.j.t.seam.feature)
Depends on o.j.t.as.feature,
o.j.t.hibernate.feature,
o.j.t.common.feature,
o.j.t.jst.feature,
o.j.t.jsf.feature
# CDI (o.j.t.cdi.feature and o.j.t.cdi.seam.feature)
Depends on o.j.t.common.feature,
o.j.t.jst.feature
was (Author: akazakov):
Actually we already have JSF feature which is up-to-date.
We just need to use get rid of RichFaces feature (includes plugins from common, JST, JSF
and VPE features).
So there is a list of feature dependencies:
# Common (o.j.t.common.all.feature)
# JST (o.j.t.jst.feature)
Depends on o.j.t.common.all.feature
# VPE (o.j.t.vpe.feature)
# JSF (o.j.t.jsf.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.vpe.feature
# Seam2 (o.j.t.seam.feature)
Depends on o.j.t.as.feature,
o.j.t.hibernate.feature,
o.j.t.common.all.feature,
o.j.t.jst.feature,
o.j.t.jsf.feature
# CDI (o.j.t.cdi.feature and o.j.t.cdi.seam.feature)
Depends on o.j.t.common.all.feature,
o.j.t.jst.feature
Create a separate feature for JSF Tools
---------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M3
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:34 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Alexey Kazakov updated JBIDE-9397:
----------------------------------
Summary: Split RichFaces feature into separate Common, JSF, VPE, ... features (was:
Create a separate feature for JSF Tools)
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M3
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:34 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Denis Golovin updated JBIDE-9397:
---------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
2. JST feature does not currently depend on common, but swimlanes already set up for
this.
4. JSF feature does not currently depend on common, jst, or vpe, but swimlanes already set
up.
5. Seam feature
(http://anonsvn.jboss.org/repos/jbosstools/trunk/seam/features/org.jboss.t...)
does not currently depend on common, jst, or jsf -- only on as and hibernate; swimlanes do
NOT have Seam depending on Hibernate or JSF
6. cdi and cdi.seam features declare no upstream feature deps on common or jst; swimlanes
already set up.
I will attempt to fix the inter-feature deps locally and then set up the swimlanes (and
~/trunk/build/pom*.xml) so everything builds in the correct order w/ the correct
dependencies.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:40 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt edited comment on JBIDE-9397 at 9/14/11 7:39 PM:
------------------------------------------------------------
2. JST feature does not currently depend on common, but swimlanes [1] already set up for
this.
4. JSF feature does not currently depend on common, jst, or vpe, but swimlanes already set
up.
5. Seam feature
(http://anonsvn.jboss.org/repos/jbosstools/trunk/seam/features/org.jboss.t...)
does not currently depend on common, jst, or jsf -- only on as and hibernate; swimlanes do
NOT have Seam depending on Hibernate or JSF
6. cdi and cdi.seam features declare no upstream feature deps on common or jst; swimlanes
already set up.
I will attempt to fix the inter-feature deps locally and then set up the swimlanes (and
~/trunk/build/pom*.xml) so everything builds in the correct order w/ the correct
dependencies.
[1] http://download.jboss.org/jbosstools/builds/cascade/swimlanes.txt
was (Author: nickboldt):
2. JST feature does not currently depend on common, but swimlanes already set up for
this.
4. JSF feature does not currently depend on common, jst, or vpe, but swimlanes already set
up.
5. Seam feature
(http://anonsvn.jboss.org/repos/jbosstools/trunk/seam/features/org.jboss.t...)
does not currently depend on common, jst, or jsf -- only on as and hibernate; swimlanes do
NOT have Seam depending on Hibernate or JSF
6. cdi and cdi.seam features declare no upstream feature deps on common or jst; swimlanes
already set up.
I will attempt to fix the inter-feature deps locally and then set up the swimlanes (and
~/trunk/build/pom*.xml) so everything builds in the correct order w/ the correct
dependencies.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:49 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt updated JBIDE-9397:
------------------------------
Attachment: patch_JBIDE9397.txt
With my changes, 3 tests are failing. Not sure if they were failing beforehand too:
{code}
Tests run: 121, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 45.589 sec <<<
FAILURE!
testGraphValidator(org.jboss.tools.jsf.vpe.richfaces.test.RichFacesComponentContentTest)
Time elapsed: 0.277 sec <<< FAILURE!
[INFO] org.jboss.tools.jsf.vpe.richfaces.test ............ FAILURE [58.654s]
[INFO] BUILD FAILURE
Tests run: 12, Failures: 2, Errors: 0, Skipped: 0, Time elapsed: 30.303 sec <<<
FAILURE!
testInjectedProducerMethodParametersHyperlinkDetector(org.jboss.tools.cdi.text.ext.test.InjectedPointHyperlinkDetectorTest)
Time elapsed: 0.881 sec <<< FAILURE!
testObserverMethodHyperlinkDetector(org.jboss.tools.cdi.text.ext.test.EventAndObserverMethodHyperlinkDetectorTest)
Time elapsed: 3.309 sec <<< FAILURE!
[INFO] org.jboss.tools.cdi.text.ext.test ................. FAILURE [1:01.256s]
[INFO] BUILD FAILURE
{code}
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:12 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-9397:
--------------------------------------
Are common,jst,vpe and jsf features published as part of JBT aggregated update site? I
remember we included only richfaces feature into aggregated update site.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:44 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
No, they are not. But they are published to their respective component sites and
therefore available for building / resolving upstream deps.
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/site/site...
Should they be published to the aggregate site too?
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:53 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-9397:
--------------------------------------
They should be, build will work because of _composite/trunk have these features, but
install from nightly update site fails.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:42 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
Swimlanes amended for trunk and 3.3_stable branch.
3 missing features (o.j.t.common.feature, o.j.t.jst.feature, o.j.t.vpe.feature) added to
both the JBT aggregate and the JBDS aggregate (input to product build).
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Denis Golovin commented on JBIDE-9397:
--------------------------------------
I've added jsf.feature as well for consistency.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:47 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
Waiting on verification in a build:
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
(#3702 or later)
http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.updatesite/ (#1493 or later)
http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.product/ (#782 or later)
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:22 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
OK, we have a problem. By adding these extra features/dependencies, the resulting update
site (trunk aggregate) can't be built because:
{code}
[INFO] [Software being installed: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT,
Only one of the following can be installed at once: [org.jboss.tools.common.validation
3.3.0.v20110915-1555-H434-M4, org.jboss.tools.common.validation
3.3.0.v20110915-2138-H435-M4, org.jboss.tools.common.validation
3.3.0.v20110829-0518-H428-M3, org.jboss.tools.common.validation
3.3.0.v20110914-2136-H433-M4, org.jboss.tools.common.validation
3.3.0.v20110915-2155-H436-M4],
Only one of the following can be installed at once: [org.jboss.tools.jst.jsp
3.3.0.v20110915-2213-H498-M4, org.jboss.tools.jst.jsp 3.3.0.v20110915-0440-H494-M4,
org.jboss.tools.jst.jsp 3.3.0.v20110915-1645-H496-M4, org.jboss.tools.jst.jsp
3.3.0.v20110830-0158-H488-M3, org.jboss.tools.jst.jsp 3.3.0.v20110915-1954-H497-M4,
org.jboss.tools.jst.jsp 3.3.0.v20110829-0543-H487-M3],
Cannot satisfy dependency: org.jboss.tools.common.feature.feature.group
3.3.0.v20110829-0518-H428-M3 depends on: org.jboss.tools.common.validation
[3.3.0.v20110829-0518-H428-M3],
Cannot satisfy dependency: org.jboss.tools.common.feature.feature.group
3.3.0.v20110915-2138-H435-M4 depends on: org.jboss.tools.common.validation
[3.3.0.v20110915-2138-H435-M4],
Cannot satisfy dependency: org.jboss.tools.common.feature.feature.group
3.3.0.v20110915-2155-H436-M4 depends on: org.jboss.tools.common.validation
[3.3.0.v20110915-2155-H436-M4],
Cannot satisfy dependency: org.jboss.tools.jst.feature.feature.group
3.3.0.v20110830-0158-H488-M3 depends on: org.jboss.tools.jst.jsp
[3.3.0.v20110830-0158-H488-M3],
Cannot satisfy dependency: org.jboss.tools.jst.feature.feature.group
3.3.0.v20110915-1954-H497-M4 depends on: org.jboss.tools.jst.jsp
[3.3.0.v20110915-1954-H497-M4],
Cannot satisfy dependency: org.jboss.tools.jst.feature.feature.group
3.3.0.v20110915-2213-H498-M4 depends on: org.jboss.tools.jst.jsp
[3.3.0.v20110915-2213-H498-M4],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110830-0201-H414-M3 depends on: org.jboss.tools.jst.jsp
[3.3.0.v20110829-0543-H487-M3],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110915-1354-H420-M4 depends on: org.jboss.tools.jst.jsp
[3.3.0.v20110915-0440-H494-M4],
Cannot satisfy dependency: org.jboss.tools.richfaces.feature.feature.group
3.3.0.v20110915-1947-H421-M4 depends on: org.jboss.tools.common.validation
[3.3.0.v20110915-1555-H434-M4],
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.common.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.jst.feature.feature.group 0.0.0,
Cannot satisfy dependency: org.jboss.tools.site.aggregate
raw:0.0.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):0.0.1-SNAPSHOT depends on:
org.jboss.tools.richfaces.feature.feature.group 0.0.0]
{code}
So, I need to ensure we have only singular deps on org.jboss.tools.jst.jsp and
org.jboss.tools.common.validation. Seems like we have too many features which include
these 2 plugins:
{code}
org.jboss.tools.common.feature
org.jboss.tools.jst.feature
org.jboss.tools.richfaces.feature
{code}
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:50 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt commented on JBIDE-9397:
-----------------------------------
richfaces.feature now includes nothing but upstream features...
{code}
<includes id="org.jboss.tools.common.feature" version="3.3.0"
match="greaterOrEqual" />
<includes id="org.jboss.tools.common.core.feature" version="3.3.0"
match="greaterOrEqual" />
<includes id="org.jboss.tools.common.text.ext.feature"
version="3.3.0" match="greaterOrEqual" />
<includes id="org.jboss.tools.common.ui.feature" version="3.3.0"
match="greaterOrEqual" />
<includes id="org.jboss.tools.common.verification.feature"
version="3.3.0" match="greaterOrEqual" />
<includes id="org.jboss.tools.jsf.feature" version="3.3.0"
match="greaterOrEqual" />
<includes id="org.jboss.tools.jst.feature" version="3.3.0"
match="greaterOrEqual" />
<includes id="org.jboss.tools.vpe.feature" version="3.3.0"
match="greaterOrEqual" />
{code}
... and requires the xulrunner.initializer plugin (also from upstream).
Hopefully that removes the duplication and allows the agg site to build; this makes the
RichFaces feature simply a wrapper for other features. A feature of convenience, as it
were.
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
(#3711 or later)
http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.updatesite/ (#1493 or later)
http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.product/ (#781 or later)
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:01 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Nick Boldt resolved JBIDE-9397.
-------------------------------
Resolution: Done
Updated JBDS 5.0.0.M3 from 09/09 to M4 from 09/17 using
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk....
successfully. New features not previously installed were added.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 p.m.
New subject: [JBoss JIRA] (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Isaac Rooskov updated JBIDE-9397:
---------------------------------
Release Notes Docs Status: Needs More Info
Writer: irooskov
Steps to Reproduce: Components available as part of the RichFaces Tools feature
are now available individually. Common, JST, JSF and VPE are all now available as
individual components or as a RichFaces Tools bundle. For a user, if you only wish to use
JSF Tools, you no longer need to also have Common, JST and VPE tooling components
installed.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
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
12:02 a.m.
New subject: [JBoss JIRA] (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Isaac Rooskov updated JBIDE-9397:
---------------------------------
Release Notes Docs Status: Not Required (was: Needs More Info)
This issue has been found to not be required for inclusion in the release notes of JBDS 5
as it only relates to the community verison, JBT 3.3.0.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Labels: new_and_noteworthy
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
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
4:28 a.m.
New subject: [JBoss JIRA] (JBIDE-9397) Split RichFaces feature into separate Common, JSF, VPE, ... features
[
https://issues.jboss.org/browse/JBIDE-9397?page=com.atlassian.jira.plugin...
]
Vlado Pakan closed JBIDE-9397.
------------------------------
Verified with JBT 3.3.0.v20120403-0225-H4468-Beta3.
Split RichFaces feature into separate Common, JSF, VPE, ... features
--------------------------------------------------------------------
Key: JBIDE-9397
URL: https://issues.jboss.org/browse/JBIDE-9397
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.3.0.M2
Reporter: Alexey Kazakov
Assignee: Nick Boldt
Fix For: 3.3.0.M4
Attachments: patch_JBIDE9397.txt
Right now, if you need JSF tools you have to install RichFaces feature that bundles a set
of components: JST, JSF, VPE, ...
It can confuse users.
Here is the story that illustrates the possible problem:
Jose Freitas (Seam 3 team) complained that code completion is not working for seam faces
tags. It turned out that he installed CDI, Maven, AS, Hibernate tools but didn't
install RichFaces feature. He just didn't realize that the RichFaces feature is much
more than just RichFaces support. He didn't install it and as a result he didn't
get JSF Tools. So JSF code completion didn't work for his project.
It would be good to have a separate JSF Tools feature that requires only reasonable
dependencies (such as Common, JST) and doesn't require VPE.
--
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
5114
days inactive
5372
days old
jbosstools-issues@lists.jboss.org
22 comments
5 participants
participants (5)
-
Alexey Kazakov (JIRA) -
Denis Golovin (JIRA)
-
Isaac Rooskov (Updated) (JIRA)
-
Nick Boldt (JIRA)
-
Vlado Pakan (JIRA)