[JBoss JIRA] (JBIDE-10311) Installing abridged jboss from updatesite fails due to jaxrs
by Rob Stryker (Created) (JIRA)
Installing abridged jboss from updatesite fails due to jaxrs
------------------------------------------------------------
Key: JBIDE-10311
URL: https://issues.jboss.org/browse/JBIDE-10311
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.3.0.M5
Reporter: Rob Stryker
Assignee: Max Rydahl Andersen
Priority: Blocker
Fix For: 3.3.0.M5
clean install of eclipse with the following plugin zips:
dtp-sdk_1.9.0.zip
eclipse
eclipse-SDK-3.7-linux-gtk-x86_64.tar.gz
emf-transaction-runtime-1.5.0.zip
emf-validation-runtime-1.5.0.zip
emf-xsd-SDK-2.7.0.zip
GEF-SDK-3.7.0.zip
org.eclipse.releng.tools-3.7M7.zip
RSE-SDK-3.3.zip
wtp-sdk-R-3.3.0-20110607160810.zip
Enter the installation, try to make use of our nightly build update site, select "Abridged", the most-of-jbt selection. Try to install. Error / conflicts are as follows:
Cannot complete the install because of a conflicting dependency.
Software being installed: JBoss JAX-RS Tools 1.2.2.v20111201-2131-H636-M5 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.2.2.v20111201-2131-H636-M5)
Software currently installed: Eclipse SDK 3.7.0.I20110613-1736 (org.eclipse.sdk.ide 3.7.0.I20110613-1736)
Only one of the following can be installed at once:
Declarative Services 1.3.1.R37x_v20110701 (org.eclipse.equinox.ds 1.3.1.R37x_v20110701)
Declarative Services 1.3.0.v20110502 (org.eclipse.equinox.ds 1.3.0.v20110502)
Cannot satisfy dependency:
From: Eclipse Platform 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f (org.eclipse.platform.feature.group 3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f)
To: org.eclipse.rcp.feature.group [3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY]
Cannot satisfy dependency:
From: Eclipse RCP 3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY (org.eclipse.rcp.feature.group 3.7.0.v20110216-9DB5Fm1FpBGy_AaVz-mFamgY)
To: org.eclipse.equinox.ds [1.3.0.v20110502]
Cannot satisfy dependency:
From: Eclipse Project SDK 3.7.0.v20110426-7Q7xA7DPb31rE2_TcfD-VPkLqq8sfDmLus7XtaSo-7NHB (org.eclipse.sdk.feature.group 3.7.0.v20110426-7Q7xA7DPb31rE2_TcfD-VPkLqq8sfDmLus7XtaSo-7NHB)
To: org.eclipse.platform.feature.group [3.7.0.v20110530-9gF7UHNFFt4cwE-pkZDJ7oz-mj4OSEIlu9SEv0f]
Cannot satisfy dependency:
From: Eclipse SDK 3.7.0.I20110613-1736 (org.eclipse.sdk.ide 3.7.0.I20110613-1736)
To: org.eclipse.sdk.feature.group [3.7.0.v20110426-7Q7xA7DPb31rE2_TcfD-VPkLqq8sfDmLus7XtaSo-7NHB]
Cannot satisfy dependency:
From: JBoss JAX-RS Tools 1.2.2.v20111201-2131-H636-M5 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.2.2.v20111201-2131-H636-M5)
To: org.jboss.tools.ws.jaxrs.ui [1.2.2.v20111201-2131-H636-M5]
Cannot satisfy dependency:
From: JBoss JAX-RS Tooling (UI) 1.2.2.v20111201-2131-H636-M5 (org.jboss.tools.ws.jaxrs.ui 1.2.2.v20111201-2131-H636-M5)
To: bundle org.eclipse.equinox.ds 1.3.1
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-10314) Back out "Seam 2" changes, reverting to just "Seam"
by Max Rydahl Andersen (Updated) (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10314?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-10314:
----------------------------------------
Assignee: Alexey Kazakov
> Back out "Seam 2" changes, reverting to just "Seam"
> ---------------------------------------------------
>
> Key: JBIDE-10314
> URL: https://issues.jboss.org/browse/JBIDE-10314
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 3.3.0.M4
> Reporter: mark yarborough
> Assignee: Alexey Kazakov
> Fix For: 3.3.0.M5, 3.3.0.Beta1
>
>
> Multiple locations in the JBDS code that formerly referred to "Seam" now refer to "Seam 2". This was based on need to distinguish Seam 2 from Seam 3, which is no longer relevant. The code has already been changed to denote Seam 2, but this alters the screens and may necessitate re-shoot of many screenshots for the JBDS 5 documentation. So, a decision to be made... Which is easier and/or more appropriate? To back out the "Seam 2" code changes (and skip the need for new screenshots) or to leave the "Seam 2" label in the existing M4 code and re-shoot the screens for the docs? Personal opinion: If the need to distinguish Seam 2 from Seam 3 has gone away, then using "Seam 2" instead of "Seam" clutters things up...
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-10314) Back out "Seam 2" changes, reverting to just "Seam"
by Max Rydahl Andersen (Commented) (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10314?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-10314:
---------------------------------------------
Akazakov - if this can be done easily for M5 then great, if not wait for Beta1 is ok
> Back out "Seam 2" changes, reverting to just "Seam"
> ---------------------------------------------------
>
> Key: JBIDE-10314
> URL: https://issues.jboss.org/browse/JBIDE-10314
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 3.3.0.M4
> Reporter: mark yarborough
> Fix For: 3.3.0.M5, 3.3.0.Beta1
>
>
> Multiple locations in the JBDS code that formerly referred to "Seam" now refer to "Seam 2". This was based on need to distinguish Seam 2 from Seam 3, which is no longer relevant. The code has already been changed to denote Seam 2, but this alters the screens and may necessitate re-shoot of many screenshots for the JBDS 5 documentation. So, a decision to be made... Which is easier and/or more appropriate? To back out the "Seam 2" code changes (and skip the need for new screenshots) or to leave the "Seam 2" label in the existing M4 code and re-shoot the screens for the docs? Personal opinion: If the need to distinguish Seam 2 from Seam 3 has gone away, then using "Seam 2" instead of "Seam" clutters things up...
--
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
12 years, 6 months
[JBoss JIRA] Created: (JBIDE-9758) Seam DVD example does not work with JBoss AS 4.2
by Jaroslav Jankovič (JIRA)
Seam DVD example does not work with JBoss AS 4.2
------------------------------------------------
Key: JBIDE-9758
URL: https://issues.jboss.org/browse/JBIDE-9758
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam 2
Affects Versions: 3.2.2.M1
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 3.2.2.M1
Seam DVD Store Example should work with JBoss AS 4.2.x as written in description of this example (JBoss EAP 4.3/JBoss AS 4.2.x). However, during deploying application on JBoss AS 4.2.3, exception is thrown and deployment fails. Deployment on JBoss EAP 4.3 passes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 6 months