[
https://jira.jboss.org/jira/browse/JBIDE-3321?page=com.atlassian.jira.plu...
]
Sean Flanigan commented on JBIDE-3321:
--------------------------------------
Looks like JIRA doesn't pick up email replies as comments, so I'll repeat my reply
here:
Max Rydahl Andersen (JIRA) wrote:
Sean, when you refer to not showing up in about dialog is that on
the
first dialog with branding icons or simply the list of plugin/features
shown when you click the button(s) on the about dialog ?
Help/About/Feature Details. Not the branding icons.
I just looked at Help/About/Configuration Details, which has a "***
Features:" section and similar contents to the Feature Details window.
Actually, for the JBT features that do show up, does anyone else get
them twice, eg two copies of -
org.jboss.tools.seam.feature (3.0.0.Beta1-R200810310645) "Seam Core Plug-in"
- or have I messed up my install somehow?
Late update: I noticed a minor problem with org.jboss.ide.eclipse.as.test.feature, but it
seems to be a problem with svn itself: ORG-70
Bad metadata for various features
---------------------------------
Key: JBIDE-3321
URL:
https://jira.jboss.org/jira/browse/JBIDE-3321
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Cleanup
Affects Versions: 3.0.0.beta1
Reporter: Sean Flanigan
Priority: Critical
Fix For: 3.0.0.cr1, 3.0.0.GA
[1. I see Nick Boldt has fixed the badly-formed feature.xml for
org.jboss.tools.birt.integration.wtp.feature for JBIDE-3216]
2. org.jboss.tools.common.feature depends on org.jboss.tools.common.text.ext_feature.
This feature appears not to exist, but org.jboss.tools.common.text.ext.feature does.
3. Eclipse's feature manifest editor shows a warning in the Dependencies tab for
org.jboss.tools.common.text.ext.feature, because it has a hard-coded dependency on
org.jboss.tools.common.core.feature 1.0.0. Changing it to greaterOrEqual seems to fix the
warning.
4. org.jboss.tools.common.ui.feature and org.jboss.tools.seam.feature have dependency
warnings, similar to #3
5. Several of JBT's features don't show up in JBDS's About Features. For
instance, org.jboss.tools.ws.feature. It looks as if the WS plugins are being activated,
but not the features. Perhaps a dependency problem like
https://bugs.eclipse.org/bugs/show_bug.cgi?id=236111 ?
(I'm not sure yet, but I think problem #5 might be the reason some of my JBT langpack
features refuse to install into JBDS 3.0.0.beta1.)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira