[JBoss JIRA] (JBIDE-18495) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18495?page=com.atlassian.jira.plugi... ]
Len DiMaggio updated JBIDE-18495:
---------------------------------
Fix Version/s: 4.2.x
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18495
> URL: https://issues.jboss.org/browse/JBIDE-18495
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.2.0.Final, 4.2.x
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3189) AngularJS for Web Tools cannot be installed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3189?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen resolved JBDS-3189.
---------------------------------------
Resolution: Done
force update the release flag. now resolved.
> AngularJS for Web Tools cannot be installed
> -------------------------------------------
>
> Key: JBDS-3189
> URL: https://issues.jboss.org/browse/JBDS-3189
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.CR2
> Environment: JBDS 8.0.0.CR2b
> Reporter: Rastislav Wagner
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: respin-c
> Fix For: 8.0.0.CR2
>
>
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt 3.6.0.Final-v20141016-0045-B76)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt 3.6.0.CR2-v20141003-2041-B74)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141017-1111-B314)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.Final-v20141016-0045-B76]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141017-1111-B314]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.Final-v20141016-0045-B76)
> To: org.jboss.tools.jst.jsdt [3.6.0.Final-v20141016-0045-B76]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3189) AngularJS for Web Tools cannot be installed
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3189?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3189:
--------------------------------------
CDW release: + (was: ?)
> AngularJS for Web Tools cannot be installed
> -------------------------------------------
>
> Key: JBDS-3189
> URL: https://issues.jboss.org/browse/JBDS-3189
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.CR2
> Environment: JBDS 8.0.0.CR2b
> Reporter: Rastislav Wagner
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: respin-c
> Fix For: 8.0.0.CR2
>
>
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt 3.6.0.Final-v20141016-0045-B76)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt 3.6.0.CR2-v20141003-2041-B74)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.feature.feature.group 8.0.0.GA-v20141017-1111-B314)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.Final-v20141016-0045-B76]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.GA-v20141017-1111-B314 (com.jboss.devstudio.core.package 8.0.0.GA-v20141017-1111-B314)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.GA-v20141017-1111-B314]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.angularjs.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.CR2-v20141003-2041-B74 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.CR2-v20141003-2041-B74)
> To: org.jboss.tools.jst.jsdt [3.6.0.CR2-v20141003-2041-B74]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.6.0.Final-v20141016-0045-B76 (org.jboss.tools.jst.jsdt.feature.feature.group 3.6.0.Final-v20141016-0045-B76)
> To: org.jboss.tools.jst.jsdt [3.6.0.Final-v20141016-0045-B76]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (TOOLSDOC-538) If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-538?page=com.atlassian.jira.plug... ]
Vlado Pakan closed TOOLSDOC-538.
--------------------------------
> If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-538
> URL: https://issues.jboss.org/browse/TOOLSDOC-538
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Affects Versions: 4.2.0.CR2
> Reporter: Len DiMaggio
> Assignee: Michelle Murray
> Priority: Critical
> Fix For: 4.2.0.Final
>
>
> If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
> The issue is that if a RHEL user installs these packages:
> java-1.7.0-oracle-1.7.0
> java-1.7.0-oracle-devel-1.7.0
> It may appear as though the full JDK has been installed as the "devel" package installs javac - however, the JavaFx libraries are not installed. As a result, the user cannot specify JavaFx as the browser engine in the BrowserSim preferences. (See attached screenshot.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (TOOLSDOC-538) If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-538?page=com.atlassian.jira.plug... ]
Vlado Pakan resolved TOOLSDOC-538.
----------------------------------
Resolution: Done
> If a linux user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TOOLSDOC-538
> URL: https://issues.jboss.org/browse/TOOLSDOC-538
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Affects Versions: 4.2.0.CR2
> Reporter: Len DiMaggio
> Assignee: Michelle Murray
> Priority: Critical
> Fix For: 4.2.0.Final
>
>
> If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine
> The issue is that if a RHEL user installs these packages:
> java-1.7.0-oracle-1.7.0
> java-1.7.0-oracle-devel-1.7.0
> It may appear as though the full JDK has been installed as the "devel" package installs javac - however, the JavaFx libraries are not installed. As a result, the user cannot specify JavaFx as the browser engine in the BrowserSim preferences. (See attached screenshot.)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months
[JBoss JIRA] (JBDS-3191) Improve the way we switch between development and GA
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3191?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3191:
-------------------------------------------
Clarification - It is Michaels proposed flow (which is very close to what I like too ;)
In the proposed flow you do not need a manual change on the ide.properties file for released and the p2.inf stays the same.
There is no p2.inf instructions needed to remove any refs.
And the changing or rather *add* of updatesite would be a dynamic thing which yes I believe can be done just fine programmatically while eclipse/jbds is running. that is what p2 UI already do when you do it manually. We of course need to be careful about not changing/removing updatesites in a way that confuses/edits things users might rely on.
i.e. if you are JBDS-IS user of JBDS then having development in the site might still make sense.
> Improve the way we switch between development and GA
> ----------------------------------------------------
>
> Key: JBDS-3191
> URL: https://issues.jboss.org/browse/JBDS-3191
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Components: build
> Reporter: Mickael Istria
>
> JBDS-3190 has shown that there are too many changes to perform when willing to create a GA candidate, and it's almost certain that we'll forever forget to change one or some of them when switching between GA and development stream.
> We need to improve that.
> Changes are necessary in:
> * features/com.jboss.devstudio.core/feature/p2.inf
> * site/associate.properties
> * results/pom.xml
> As an alternative, I suggest that the final site be ALWAYS added to the referenced site, even if it's empty. This has no cost for build nor user, and this would simplify a few things here and there.
> Also, instead of a p2.inf, we could think a a "startup" extension that would add reference to development site in case qualifier for the feature doesn't contain GA.
> The property to the "current site" (GA or development) could be factorized in JBDS parent pom. so that both results/pom.xml and site/pom.xml could use it (instead of associateSites.properties).
> CC [~nickboldt] [~maxandersen]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 5 months