[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
[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
[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
[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
[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