[JBoss JIRA] (JBIDE-18093) Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18093?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18093.
---------------------------------
Verified in JBDS 8.0.0.CR1 build ID B201.
> Explorer: Special character "®" in manifest.yml --> Description leads to errors when accessing OSE from JBDS/Explorer
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18093
> URL: https://issues.jboss.org/browse/JBIDE-18093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Final
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Labels: explorer
> Fix For: 4.2.0.CR1
>
> Attachments: illegal-character.png, mock1b.png, special-character-mock-cartridges.png
>
>
> Description of problem:
> I have developed a custom cartridge for OSE and placed the special character "®" (registered trademark) in the description field within my "manifest.yml". The cartridge could be installed correctly via WebUI and was also working fine from a technical point of view.
> However, when trying to access the OSE instance from JBDS via the Openshift Explorer plugin, I always got the following error:
> Invalid value for input string: "00ae"
> The string "00ae" is the unicode representation of my special character. After removing everything worked fine again. The OpenShift Explorer was completely unusable in this scenario! So only one installed cartridge with this special character can poison a whole installation and affect ALL users!!!
> Version-Release number of selected component (if applicable):
> OSE 2.2 (Developer Image)
> How reproducible:
> Yes.
> Steps to Reproduce:
> 1. Create a custom cartridge and add a "®" to the description field of your manifest.yml.
> 2. Install the cartridge according to doc.
> 3. Start JBDS and try to work with your OSE instance via the OpenShift Explorer plugin (e.g. try to add an application)
> Result:
> !illegal-character.png!
> The Eclipse log shows the following snippet:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2014-08-28 03:02:54.101
> !MESSAGE An internal error occurred during: "Loading OpenShift information...".
> !STACK 0
> java.lang.NumberFormatException: For input string: "00ae"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Integer.parseInt(Integer.java:492)
> at java.lang.Integer.parseInt(Integer.java:527)
> at org.jboss.dmr.JSONParserImpl.parseStringValue(JSONParserImpl.java:109)
> at org.jboss.dmr.JSONParser.yyLex(JSONParser.java:574)
> at org.jboss.dmr.JSONParser.yyParse(JSONParser.java:650)
> at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1184)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.getModelNode(OpenShiftJsonDTOFactory.java:207)
> at com.openshift.internal.client.response.OpenShiftJsonDTOFactory.get(OpenShiftJsonDTOFactory.java:94)
> at com.openshift.internal.client.RestService.request(RestService.java:124)
> at com.openshift.internal.client.RestService.request(RestService.java:103)
> at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:155)
> at com.openshift.internal.client.DomainResource$ListApplicationsRequest.execute(DomainResource.java:446)
> at com.openshift.internal.client.DomainResource.updateApplications(DomainResource.java:297)
> at com.openshift.internal.client.DomainResource.refresh(DomainResource.java:381)
> at org.jboss.tools.openshift.express.internal.ui.command.RefreshResourceHandler$1.doRun(RefreshResourceHandler.java:69)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
> To create the cartridge with the illegal character do the following as stated in the bugzilla:
> {quote}
> 1. Modify the official EAP Cartridge by adding a '®' to the description: (I've attached my manifest.yml)
> vi /usr/libexec/openshift/cartridges/jbosseap/metadata/manifest.yml
> 2. Reinstall cartridge with the following commands:
> cd /usr/libexec/openshift/cartridges
> oo-admin-cartridge --action install --recursive --source /usr/libexec/openshift/cartridges
> oo-admin-ctl-cartridge --activate -c import-node --obsolete
> oo-admin-broker-cache --clear && oo-admin-console-cache --clear
> 3. Create a new gear based on EAP cartridge.
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18128:
---------------------------------------------
so i've now imported the latest project, and deployed it and test.jsp is responding.
What is it that should be missing ?
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: jboss-test.zip, TestJboss-2014-09-03.zip
>
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3034) add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3034?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3034:
-------------------------------------------
Since this is urgent, already done in jbosstools and should have been done a while ago I suggest apply and then inform.
> add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3034
> URL: https://issues.jboss.org/browse/JBDS-3034
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> When we added tern to the JBT target platform, we forgot to add it to the JBDS one... because initially, it was just there to build JST, but wasn't needed at install time.
> Now, it's required to build the JBDS update site, which includes jst.jsdt, because jst.jsdt requires it. Without it, I get this:
> {code}
> [ERROR] Software being installed: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta2-v20140523-2229 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta3-v20140523-1909-B631 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT depends on: org.jboss.tools.aerogear.hybrid.feature.feature.group 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.core 1.1.0.Beta2-v20140523-1436-B253 depends on: bundle org.jboss.tools.jst.jsdt 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.feature.feature.group 1.1.0.Beta2-v20140523-1436-B253 depends on: org.jboss.tools.aerogear.hybrid.core [1.1.0.Beta2-v20140523-1436-B253]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18014) For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Server]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18014?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18014.
---------------------------------
Won's fix - nothing to check here. Closing.
> For JBIDE 4.2.0.CR1: Ensure copyrights and provider names are correct in all plugins and features [Server]
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18014
> URL: https://issues.jboss.org/browse/JBIDE-18014
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Server]: Please perform the following *2* tasks:
> 1. Verify that all your plugin and feature copyright dates end in 2014, and that the copyright holder is *{color:red}Red Hat, Inc.{color}* or a variation similar to the examples below.
> Be sure to also include *translated* files, where they exist.
> *java files*
> {code:title=*.java}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> *html files*
> {code:title=about.html}
> © 2014 Red Hat, Inc. All rights reserved
> {code}
> *properties files*
> {code:title=about.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. All rights reserved
> {code}
> {code:title=about_fr.properties}
> Copyright (c) Red Hat, Inc., contributors and others 2004 - 2014. Tous droits r\u00E9serv\u00E9s.
> {code}
> {code:title=feature.properties}
> Copyright (c) 2010-2014 Red Hat, Inc. and others.
> {code}
> {code:title=Messages.properties}
> # Copyright (c) 2014 Red Hat, Inc. and others.
> {code}
> *xsd files*
> {code:title=jboss-as-naming_1_3.xsd}
> Copyright 2014, Red Hat, Inc., and individual contributors
> {code}
> 2. Verify that all your plugin and feature provider names are *{color:red}JBoss by Red Hat{color}*.
> Be sure to also include *translated* files, where they exist.
> *This step is particularly important for new plugins and features that have been added recently.*
> Depending on how your plugin is configured you should see something like this in your *plugin.properties* files:
> {code}BundleName = JMX Resources Bundle
> BundleProvider = JBoss by Red Hat{code}
> or
> {code}Bundle-Name.0 = JBossTools Archives Core Plugin
> Bundle-Vendor.0 = JBoss by Red Hat{code}
> Then in your MANIFEST.MF files, you will reference these variables like this.
> *Bundle-Localization* is required or your plugin won't see the values in your *plugin.properties* file!
> {code}Bundle-Localization: plugin
> Bundle-Name: %BundleName
> Bundle-Vendor: %BundleProvider{code}
> or
> {code}Bundle-Localization: plugin
> Bundle-Name: %Bundle-Name.0
> Bundle-Vendor: %Bundle-Vendor.0{code}
> For features, check that your *feature.properties* file contains good values too:
> {code}featureName=JMX Console
> featureProvider=JBoss by Red Hat{code}
> or
> {code}featureName=JBoss Archives Tools
> providerName=JBoss by Red Hat{code}
> Then in your feature.xml files, you will reference these variables like this:
> {code}<feature label="%featureName" provider-name="%featureProvider" ...>{code}
> or
> {code}<feature label="%featureName" provider-name="%providerName" ...>{code}
> 3. If you would like QE to review your changes, please *Resolve* this JIRA when done.
> 4. If you do not require QE to review your changes, please *Close* this JIRA when done.
> 5. If you have any questions, please contact [~nickboldt].
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17743) SSH Keys wizard: columns are incorrectly aligned
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17743?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-17743:
---------------------------------------
My bad, incorrect desciption. I lost orientation in the sides. Reopening and fixing description.
> SSH Keys wizard: columns are incorrectly aligned
> ------------------------------------------------
>
> Key: JBIDE-17743
> URL: https://issues.jboss.org/browse/JBIDE-17743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: problems-view.png, properties-view.png, ssh-keys.png, ssh_alignement.png
>
>
> Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center. See Type or Content columns.
> !ssh_alignement.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17743) SSH Keys wizard: columns are incorrectly aligned
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17743?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17743:
----------------------------------
Description:
Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the right. It should be aligned to the left or the best to the center. See Type or Content columns.
!ssh_alignement.png!
was:
Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the left. It should be aligned to the right or the best to the center. See Type or Content columns.
!ssh_alignement.png!
> SSH Keys wizard: columns are incorrectly aligned
> ------------------------------------------------
>
> Key: JBIDE-17743
> URL: https://issues.jboss.org/browse/JBIDE-17743
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.0.CR1
>
> Attachments: problems-view.png, properties-view.png, ssh-keys.png, ssh_alignement.png
>
>
> Specific SSH keys data in the table containing SSH keys in Manage SSH Keys are aligned to the right. It should be aligned to the left or the best to the center. See Type or Content columns.
> !ssh_alignement.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18141) Include latest Tern 0.5.0.201408272110 and Angular JS 0.5.0.201408281218 into jbosstools TPs
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18141?page=com.atlassian.jira.plugi... ]
Denis Golovin closed JBIDE-18141.
---------------------------------
Release Notes Text: Vlado, in PR build.xml is for 0.5.0 and build-0.4.xml references 0.4.0. Everything looks good. Closing.
Resolution: Done
> Include latest Tern 0.5.0.201408272110 and Angular JS 0.5.0.201408281218 into jbosstools TPs
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18141
> URL: https://issues.jboss.org/browse/JBIDE-18141
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.CR1
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
> Attachments: tern-version.png
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.5.0. It contains the important fixes required for JBIDE-17992:
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:* http://oss.opensagres.fr/tern.repository/0.5.0-SNAPSHOT/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/tern/0.5.0.2014...
> *Sources:* https://github.com/angelozerr/tern.java
> *Affected projects:* jbosstools-jst, jbosstools-aerogear
> *Include in JBDS:* No
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.tools.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.group [0.4.0.201408101311]
> < tern-jsdt-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.4.0.201408101311]
> < tern.server.nodejs [0.4.0.201408101311]
> < tern-feature.feature.group [0.4.0.201408101311]
> < tern.core [0.4.0.201408101311]
> < tern.eclipse.ide.jsdt [0.4.0.201408101311]
> < tern-jsdt-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.ui [0.4.0.201408101311]
> < tern.eclipse.ide.tools.feature.feature.jar [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.jar [0.4.0.201408101311]
> < tern-feature.feature.jar [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.core [0.4.0.201408101311]
> < tern.eclipse.ide.tools.ui [0.4.0.201408101311]
> < tern-server-nodejs-feature.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.ui [0.4.0.201408101311]
> < tern.eclipse.ide.core [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.feature.group [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.4.0.201408101311]
> < tern.eclipse [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.4.0.201408101311]
> < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.4.0.201408101311]
> > tern.eclipse.ide.tools.feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.group [0.5.0.201408272110]
> > tern-feature.feature.group [0.5.0.201408272110]
> > tern.server.nodejs [0.5.0.201408272110]
> > tern.core [0.5.0.201408272110]
> > tern.eclipse.ide.jsdt [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.feature.group [0.5.0.201408272110]
> > tern.eclipse [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.5.0.201408272110]
> > tern.eclipse.ide.tools.ui [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.ui [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.group [0.5.0.201408272110]
> > tern.eclipse.ide.core [0.5.0.201408272110]
> > tern-jsdt-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.tools.feature.feature.jar [0.5.0.201408272110]
> > tern-server-nodejs-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.core [0.5.0.201408272110]
> > tern.eclipse.ide.ui [0.5.0.201408272110]
> > tern-feature.feature.jar [0.5.0.201408272110]
> > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.5.0.201408272110]
> === Summary ===
> http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs
> file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 25 unique IUs
> {code}
> Verification Steps:
> # EXEC: Open Installation Details dialog
> # EXEC: Go to Plugins tab
> # EXEC: Filter 'tern."
> # ASSERT: Dialog contains
> !tern-version.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3034) add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-3034?page=com.atlassian.jira.plugin.... ]
Mickael Istria commented on JBDS-3034:
--------------------------------------
[~maxandersen] What process should we follow here? ask for feedback from rest of the team or merge it and send to notify?
> add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3034
> URL: https://issues.jboss.org/browse/JBDS-3034
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 8.0.0.CR1
>
>
> When we added tern to the JBT target platform, we forgot to add it to the JBDS one... because initially, it was just there to build JST, but wasn't needed at install time.
> Now, it's required to build the JBDS update site, which includes jst.jsdt, because jst.jsdt requires it. Without it, I get this:
> {code}
> [ERROR] Software being installed: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta2-v20140523-2229 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Missing requirement: org.jboss.tools.jst.jsdt 3.6.0.Beta3-v20140523-1909-B631 requires 'bundle tern.core 0.2.0' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.site raw:8.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):8.0.0-SNAPSHOT depends on: org.jboss.tools.aerogear.hybrid.feature.feature.group 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.core 1.1.0.Beta2-v20140523-1436-B253 depends on: bundle org.jboss.tools.jst.jsdt 0.0.0
> [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.hybrid.feature.feature.group 1.1.0.Beta2-v20140523-1436-B253 depends on: org.jboss.tools.aerogear.hybrid.core [1.1.0.Beta2-v20140523-1436-B253]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months