[JBoss JIRA] (JBDS-1993) v20120114-1832-H1633-Beta1 - conflicts installing SOA tooling
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-1993:
----------------------------------
Summary: v20120114-1832-H1633-Beta1 - conflicts installing SOA tooling
Key: JBDS-1993
URL: https://issues.jboss.org/browse/JBDS-1993
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: SOA Platform
Affects Versions: 5.0.0.M5
Environment: Version: 5.0.0.Beta1
Build id: v20120114-1832-H1633-Beta1
Build date: 20120114-1832
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... - nightly as of Jan 16
Reporter: Len DiMaggio
Assignee: Brian Fitzpatrick
Fix For: 5.0.0.Beta1
Attempting to install the "SOA abridged" plugins from:
http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_trunk.... (nightly - Jan 16 2012)
On top of the Jan 16 build:
Version: 5.0.0.Beta1
Build id: v20120114-1832-H1633-Beta1
Build date: 20120114-1832
Results in these errors:
Your original request has been modified.
"Runtime Initialization" is already installed, so an update will be performed instead.
"JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
Cannot complete the install because of a conflicting dependency.
Software being installed: Runtime Initialization 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120116-1513-H527-Beta1)
Software currently installed: JBoss Developer Studio 5.0.0.201201141342 (com.jboss.jbds.all 5.0.0.201201141342)
Only one of the following can be installed at once:
JBoss Runtime Initializer 1.3.0.v20120114-1741-H525-Beta1 (org.jboss.tools.runtime 1.3.0.v20120114-1741-H525-Beta1)
JBoss Runtime Initializer 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime 1.3.0.v20120116-1513-H527-Beta1)
Cannot satisfy dependency:
From: JBoss Developer Studio 5.0.0.201201141342 (com.jboss.jbds.all 5.0.0.201201141342)
To: org.jboss.tools.runtime.feature.feature.group [1.3.0.v20120114-1741-H525-Beta1]
Cannot satisfy dependency:
From: Runtime Initialization 1.3.0.v20120114-1741-H525-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120114-1741-H525-Beta1)
To: org.jboss.tools.runtime [1.3.0.v20120114-1741-H525-Beta1]
Cannot satisfy dependency:
From: Runtime Initialization 1.3.0.v20120116-1513-H527-Beta1 (org.jboss.tools.runtime.feature.feature.group 1.3.0.v20120116-1513-H527-Beta1)
To: org.jboss.tools.runtime [1.3.0.v20120116-1513-H527-Beta1]
--
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
14 years
[JBoss JIRA] (JBIDE-10714) Forge "rm" does not clean up Eclipse UI
by Burr Sutter (JIRA)
Burr Sutter created JBIDE-10714:
-----------------------------------
Summary: Forge "rm" does not clean up Eclipse UI
Key: JBIDE-10714
URL: https://issues.jboss.org/browse/JBIDE-10714
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Environment: Using Beta5 runtime inside of JBDS5 M5 on Mac OS X 64-bit Lion
Reporter: Burr Sutter
Assignee: Koen Aers
Attachments: Screen Shot 2012-01-25 at 2.25.55 PM.png, Screen Shot 2012-01-25 at 2.26.47 PM.png
Steps to reproduce:
- Create a Java EE Web project from JBoss Central called "myjavaeeproject"
- Command-4 to open Forge Console
- entity --named Address
adds Address.java to my project, opens the editor
- cd ..
- rm Address.java
closes the editor but leaves Address.java "ghost" in the Project Explorer
--
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
14 years, 1 month
[JBoss JIRA] (JBDS-1959) publish JBDS version of Central directory.xml file into JBDS core update site
by Nick Boldt (Created) (JIRA)
publish JBDS version of Central directory.xml file into JBDS core update site
-----------------------------------------------------------------------------
Key: JBDS-1959
URL: https://issues.jboss.org/browse/JBDS-1959
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: central, updatesite
Affects Versions: 5.0.0.M5
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 5.0.0.Beta1
Like we have for JBT, we need that:
a) the update site for JBDS core contain a jbdevstudio-directory.xml file
b) it be linked from the site's index.htmt page (to support mirrors)
c) the directory file link to a different discovery plugin, available only in JBDS
Therefore the site generator for the JBDS core site must be tweaked slightly to reference the correct discovery plugin when generating the directory file.
d) also, be sure to update the releng guide publishing instructions / email template for this new tweak.
--
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
14 years, 1 month
[JBoss JIRA] (JBIDE-10473) AS7.1 default classpath entries missing critical jboss ejb jar
by Rob Stryker (Created) (JIRA)
AS7.1 default classpath entries missing critical jboss ejb jar
--------------------------------------------------------------
Key: JBIDE-10473
URL: https://issues.jboss.org/browse/JBIDE-10473
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.3.0.M5, 3.3.0.Beta1
The as7.1 runtime type's default list of classpath jars does not include a critical folder / jar, specifically modules/org/jboss/ejb3/main/*.jar, which includes support for the @SecurityDomain annotation. Without this, users must fiddle with classpaths and search for jars manually.
A workaround, as noted in JBIDE-10463, is to add the folder / fileset to the list of default classpath entries for the runtime type. However, due to that specific bug, a workspace restart will be required for these changes to take effect.
--
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
14 years, 1 month
[JBoss JIRA] Created: (JBIDE-9716) create jboss-dmr bundle
by Andre Dietisheim (JIRA)
create jboss-dmr bundle
-----------------------
Key: JBIDE-9716
URL: https://issues.jboss.org/browse/JBIDE-9716
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.3.0.M4
We currently use jboss-dmr in org.jboss.ide.eclipse.as.management and org.jboss.ide.eclipse.as.openshift.core. We currently bundle jboss-dmr in both plugins as embedded jar. We should replace this by a bundled version of jboss-dmr
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month