[
https://jira.jboss.org/jira/browse/JBIDE-3455?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-3455:
--------------------------------------
I have tried to reproduce your case in the following way:
- downloaded Ganymede Eclipse IDE for Java EE Developers from
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...
- unpacked it to some directory (<ECLIPSE_HOME>)
- created the jbosstools directory in <ECLIPSE_HOME>/dropins
- downloaded JBoss Tools 3.0.0RC1
(
http://downloads.sourceforge.net/jboss/JBossTools-3.0.0.CR1-R200812191611...)
- unpacked JBoss Tools to <ECLIPSE_HOME>/dropins/jbosstools
- started Eclipse
- created a new Seam Web Project
- opened components.xml
All JBoss Seam plugins are started correctly.
The content assist works as well as OpenOn for
http://jboss.com/products/seam/components-2.0.xsd or
http://jboss.com/products/seam/components-2.1.xsd
I get a warning that BIRT and tptp aren't started because of unsatisfied dependencies
and P2 reconciler error you have mentioned in the forum, but these messages don't
have any effect on the Seam feature.
Could you tell me if I need to do anything else to reproduce this issue?
Missing BIRT and TPTP dependency causing Seam Tools not to start when
dropins folder is used
--------------------------------------------------------------------------------------------
Key: JBIDE-3455
URL:
https://jira.jboss.org/jira/browse/JBIDE-3455
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.cr1
Environment: Ganymede 3.4.1, JDK6, JBoss Tools Nightly 20/12/2008
Reporter: Dirk Pitt
If I deploy the JBoss Tools with dropins functionality Seam
Tools(org.jboss.tools.seam.feature.feature.group) is not initializing because of the
missing BIRT and TPTP dependencies...
If I deploy these dependencies manually then it initialize it...
If Seam Tools doesn't initialize, content assist is not availible for Seam
Components.xml, missing BIRT should not effect the content assist for Seam...
--
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