August 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-500) JBoss Tools (nightly) Prevents any Eclipse Plug-in Update

by Todd Flinders (JIRA)

JBoss Tools (nightly) Prevents any Eclipse Plug-in Update --------------------------------------------------------- Key: JBIDE-500 URL: http://jira.jboss.com/jira/browse/JBIDE-500 Project: JBoss Tools Issue Type: Bug Components: EJB3 plugin Environment: Eclipse Europa 3..3 (stable) JBossTools-200706290355-nightly-ALL-linux-gtk java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Client VM (build 1.5.0_10-b03, mixed mode, sharing) openSUSE 10.2 Linux HQISB-7Y2GF61 2.6.18.8-0.3-default #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 i686 i386 GNU/Linux Reporter: Todd Flinders Assigned To: Max Andersen After installing the nightly JBoss Tools nightly build on Eclipse 3.3 stable, updates are prevented due to the following error: org.jboss.ide.eclipse.ejb3.feature (1.0.0.200706290355-nightly) requires plug-in "org.eclipse.wst.server.core". It should be noted I'm referring to JBoss Tools nightly build installed by unpacking the zip file downloaded from http://download.jboss.org/jbosstools/builds/nightly/200706290355-nightly/.... This is not to be confused with the JBossIDE Beta 2. The problem can be demonstrated by attempting to install subclipse (for example). The steps to recreate the problem are: 1. Install a fresh Eclipse 3.3. 2. Unzip JBossTools-200706290355-nightly-ALL-linux-gtk to the Eclipse 3.3 directory 3. In Eclipse: Help | Software Updates | Find and Install | Search for new features to install 4. Add a new remote site. In my case I added Subclipse with the update URL of http://subclipse.tigris.org/update_1.2.x 5. Select a feature to install, in my case Subclipse | Subclipse Plugin 6. The error is displayed at the top of the Updates window: org.jboss.ide.eclipse.ejb3.feature (1.0.0.200706290355-nightly) requires plug-in "org.eclipse.wst.server.core". -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

5
16
0 / 0

[JBoss JIRA] Assigned: (RHDS-72) RHDS menu items on Fedora 7

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/RHDS-72?page=all ] Max Andersen reassigned RHDS-72: -------------------------------- Assignee: Vladimir Ralev > RHDS menu items on Fedora 7 > --------------------------- > > Key: RHDS-72 > URL: http://jira.jboss.com/jira/browse/RHDS-72 > Project: Red Hat Developer Studio > Issue Type: Bug > Affects Versions: 1.0.0.beta1 > Environment: Fedora 7, RHDS nightly 200708080004 > Reporter: Manik Surtani > Assigned To: Vladimir Ralev > Fix For: 1.0.0.beta2 > > Attachments: installer_on_kde, Screenshot.png > > > Using the installer was nice and easy, but when it prompted me to install RHDS in my menu, I opted for it to create it's own group. And it didn't. So here are the list of my gripes with this: > 1) The default (at least on F7) should be in the "Programming" group, with other dev tools - not it's own RHDS group. > 2) When it does try and create the RHDS group ( as I opted for) it created a group called "Other" and dumped the menu items in there. > 3) There were 2 copies of each menu item. > See screen shot for details of all 3 above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (RHDS-72) RHDS menu items on Fedora 7

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/RHDS-72?page=all ] Max Andersen updated RHDS-72: ----------------------------- Fix Version/s: 1.0.0.beta2 Affects Version/s: 1.0.0.beta1 > RHDS menu items on Fedora 7 > --------------------------- > > Key: RHDS-72 > URL: http://jira.jboss.com/jira/browse/RHDS-72 > Project: Red Hat Developer Studio > Issue Type: Bug > Affects Versions: 1.0.0.beta1 > Environment: Fedora 7, RHDS nightly 200708080004 > Reporter: Manik Surtani > Assigned To: Vladimir Ralev > Fix For: 1.0.0.beta2 > > Attachments: installer_on_kde, Screenshot.png > > > Using the installer was nice and easy, but when it prompted me to install RHDS in my menu, I opted for it to create it's own group. And it didn't. So here are the list of my gripes with this: > 1) The default (at least on F7) should be in the "Programming" group, with other dev tools - not it's own RHDS group. > 2) When it does try and create the RHDS group ( as I opted for) it created a group called "Other" and dumped the menu items in there. > 3) There were 2 copies of each menu item. > See screen shot for details of all 3 above. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-759) Problem with "add project" to jboss server.

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-759?page=comments#action_12372433 ] Rob Stryker commented on JBIDE-759: ----------------------------------- judging by the icons on the two sides, it's trying to allow you to add a module of one type, and is then interpreting it as a module of another (dynamic web it seems). Can you please attach the project so that this can be investigated? Thanks. > Problem with "add project" to jboss server. > ------------------------------------------- > > Key: JBIDE-759 > URL: http://jira.jboss.com/jira/browse/JBIDE-759 > Project: JBoss Tools > Issue Type: Bug > Components: JBossAS > Environment: windows xp, RHDS beta 1, jdk 1.5_0.12 > Reporter: Adrian Mitev > Attachments: add project.jpg > > > There is something wrong with "add project" window. When i add the project and then open add/remove project window again, i can add the same project again and again. I'm providing a screen shot to the issue. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by R Firoz (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12372360 ] R Firoz commented on JBIDE-322: ------------------------------- I actually ran the update manager to download the plugin and install it so I had to exclude ' org.jboss.ide.eclipse.ejb3.feature 1.0.2.GA' from the update in order to go ahead with the plugin installation. So my question is more in line with what happens if I exclude this component from plugin. I have ran my application and am able to debug. What I am trying to understand is the side effects of excluding a component from the plugin. Thanks, RF > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by Gerhard Schuster (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12372358 ] Gerhard Schuster commented on JBIDE-322: ---------------------------------------- What I saied before applies if you already have downloaded the plugins as zip and have unzipped it into your eclipse directory. The eclipse update manager will not download the faulty part of the JBoss package and if you have installed JBoss as zip, the update manager will not work again until you have fixed the problem as described. > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by Gerhard Schuster (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12372357 ] Gerhard Schuster commented on JBIDE-322: ---------------------------------------- a) Get JBossIDE-2.0.0.Beta2-Bundle-win32.zip b) Edit your plugins\org.jboss.ide.eclipse.ejb3.wizards.ui_1.1.0.Beta2\META-INF\MANIFEST.MF and all other files where org.eclipse.jdt.source is refferenced (Only the ones Eclipse complaines about) c) Delete all JBoss plugins and work without Did this help? > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBIDE-322) Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source

by R Firoz (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-322?page=comments#action_12372353 ] R Firoz commented on JBIDE-322: ------------------------------- Is there any workaround to this in eclipse version Europa? I have JBoss 4.0.4 and just recently installed the plugin for eclipse IDE and when I went through the installation I faced the dependency error referenced here. What should I do at this point? > Unused plugin dependency in org.jboss.ide.eclipse.ejb3.wizards.ui on org.eclipse.jdt.source > -------------------------------------------------------------------------------------------- > > Key: JBIDE-322 > URL: http://jira.jboss.com/jira/browse/JBIDE-322 > Project: JBoss Tools > Issue Type: Bug > Components: ejb3 > Affects Versions: 1.5 Final > Reporter: Francois Granade > Assigned To: Marshall Culpepper > Priority: Minor > Fix For: 2.0.0.Alpha > > > The plugin org.jboss.ide.eclipse.ejb3.wizards.ui declare a dependency on org.eclipse.jdt.source. You can see that in the Manifest file: > http://fisheye.labs.jboss.com/viewrep/JBoss/jbosside/ejb3/plugins/org.jbo... > Unless I'm mistaken, this dependency is not needed (why would the wizard have a dependency on JDT source code ???) > It's innocuous, but this causes an error to appear in Eclipse error log. > Also, for us at http://www.easyeclipse.org, it means that we have to patch the manifest when we build it. It's small, but useless -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-785) Red Hat XML editor does not work for tiles definitions xml

by Viacheslav Kabanovich (JIRA)

Red Hat XML editor does not work for tiles definitions xml ---------------------------------------------------------- Key: JBIDE-785 URL: http://jira.jboss.com/jira/browse/JBIDE-785 Project: JBoss Tools Issue Type: Bug Reporter: Viacheslav Kabanovich Assigned To: Viacheslav Kabanovich Create tiles definitions file (in Web Projects View, right click node Tiles under project and select New->Tiles...). Open editor and make sure that Tree tab looks ok. Add definition named 'd1'. Switch to Source tab. Modify name 'd1' to 'd2'. Switch back to Tree tab. Now it shows error in xml. Explanation - There is incorrect reference to tiles-config_1_1.dtd file in plugin.xml. Hence in runtime, the reference is resolved so that model is notified that this kind of file can be validated with dtd, but validation files because dtd file is not found. By the way, it is better to move registration of the dtd to from struts plugin to tiles plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
1
0 / 0

[JBoss JIRA] Updated: (RHDS-71) GCJ is getting used by default in installer and for servers

by Max Andersen (JIRA)

[ http://jira.jboss.com/jira/browse/RHDS-71?page=all ] Max Andersen updated RHDS-71: ----------------------------- Summary: GCJ is getting used by default in installer and for servers (was: RHDS crashes when I try and create a new instance of the JBoss app server) Component/s: installer changed title to reflect what is the issue. We should at least change the installer to allow users optionally to set the vm (and definitly warn against usage of gcj if the installer is running with gcj) The installer should try and look/scan for vm's (if doable) the other issue is how we avoid to launch jboss with gcj as default vm....I think that issue will be solved if eclipse is started with a decent vm. the settings could be stored in the eclipse.ini file (remember to keep the memory settings too) > GCJ is getting used by default in installer and for servers > ----------------------------------------------------------- > > Key: RHDS-71 > URL: http://jira.jboss.com/jira/browse/RHDS-71 > Project: Red Hat Developer Studio > Issue Type: Bug > Components: servers, installer > Environment: Fedora 7, Intel-based hardware, using RHDS nightly build 200708080004, gcj 1.5.0 > Reporter: Manik Surtani > Attachments: rhds.txt > > > 1) Start RHDS > 2) Statr Server -> Start -> New Server > 3) Bang! RHDS gone! > Although I do have Sun Java 5 and 6 installed on this system (and used Sun Java 5 when installing RHDS), RHDS chooses gcj when starting up using the shortcuts provided. See config information (obtained using Help -> About ... -> Config Details) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2007