February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19137) FeedHenry Import Wizard doesn't list any projects to import

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19137?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19137: -------------------------------------- I do not envision that we need specific import wizard for every FH application type. However importing is not simply a matter of ability to clone an application, we need to create a corresponding eclipse project type, and configure it, make sure that the related eclipse plugins are installed and test different scenarios. This is all extra work on dev, doc and QE and the agreed scope of the requirement was Cordova only. However when we decide to enhance the scope we can actually use the current wizard. The current wizard uses filters to avoid unsupported application types, so all the data and selection logic is there, it just lacks the application type specific import logic. > FeedHenry Import Wizard doesn't list any projects to import > ----------------------------------------------------------- > > Key: JBIDE-19137 > URL: https://issues.jboss.org/browse/JBIDE-19137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Pavol Srna > Priority: Blocker > Fix For: 4.2.3.Beta1 > > Attachments: fh-preferences.png, fh-site.png, nothing-to-import.png > > > The FeedHenry import wizard can't find any projects to import. > There is no stacktrace in error log. > Please look at the attached screenshots for demonstration. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- So to sum up, what you'd like would be: * sha1 as 1st element in revision * then localBranch (if applicable, I don't even know whether Jenkins actually creates a branch or works on a detached head) * then knownReferences ? > Attach metadata during assembly instead of publish time > ------------------------------------------------------- > > Key: JBIDE-15135 > URL: https://issues.jboss.org/browse/JBIDE-15135 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site. > Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-3338. -------------------------------- Resolution: Done > JBDS Build fails with Tycho 0.22 > -------------------------------- > > Key: JBDS-3338 > URL: https://issues.jboss.org/browse/JBDS-3338 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 9.0.0.Alpha1 > > > JBDS build is failing with Tycho 0.22 > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer: > Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed: > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at > file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/. > No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19146: ------------------------------------- Fix Version/s: 4.3.0.Beta1 > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19146?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19146: ------------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.3.0.Beta1) > Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final > ----------------------------------------------------------------------------------- > > Key: JBIDE-19146 > URL: https://issues.jboss.org/browse/JBIDE-19146 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: > - restore opened views (explorer) > - restore connections > - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-387) Incorporate new version for 4.2.0.CR2/ 8.0.0.CR2

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-387: -------------------------------- Summary: Incorporate new version for 4.2.0.CR2/ 8.0.0.CR2 Key: JBTIS-387 URL: https://issues.jboss.org/browse/JBTIS-387 Project: JBoss Tools Integration Stack Issue Type: Task Components: distribution Affects Versions: 4.2.0.CR2, 8.0.0.CR2 Reporter: Paul Leacu Assignee: Paul Leacu new teiid designer -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19146) Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-19146: ---------------------------------------- Summary: Make sure new tooling can restore a workspace that was created with JBT 4.2.0.Final Key: JBIDE-19146 URL: https://issues.jboss.org/browse/JBIDE-19146 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Alpha1 Reporter: Andre Dietisheim We have to make sure that the new tooling (with the new plugins and the code reorg in JBIDE-19048) can restore a workspace that was created with JBT 4.2.0.Final / JBDS 8.0.0: - restore opened views (explorer) - restore connections - restore server editor(s) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3338) JBDS Build fails with Tycho 0.22

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3338?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3338: -------------------------------------- Should be resolved with patch https://github.com/jbdevstudio/jbdevstudio-product/commit/78923ed6d3bf078... CI build in progress. > JBDS Build fails with Tycho 0.22 > -------------------------------- > > Key: JBDS-3338 > URL: https://issues.jboss.org/browse/JBDS-3338 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 9.0.0.Alpha1 > > > JBDS build is failing with Tycho 0.22 > {code} > [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products (default-publish-products) on project installer: > Execution default-publish-products of goal org.eclipse.tycho:tycho-p2-publisher-plugin:0.22.0:publish-products failed: > org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at > file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/. > No repository found at file:/qa/hudson_workspace/workspace/devstudio.product_master/sources/product/installer/target/jbds/. > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19125) For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19125?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19125: ------------------------------------ [~gercan] Please also remember to push https://github.com/jbosstools/jbosstools-aerogear/pull/108 into your 4.2.x branch so you can build against the latest upstream Thym 0.1 site [1]. [1] http://downloads.jboss.org/jbosstools/updates/integration/luna/core/thym/ > For JBIDE 4.2.3.Beta1: Prepare for JBT 4.2.3 / JBDS 8.1.0 [Aerogear] > -------------------------------------------------------------------- > > Key: JBIDE-19125 > URL: https://issues.jboss.org/browse/JBIDE-19125 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, cordovasim > Reporter: Nick Boldt > Assignee: Gorkem Ercan > Priority: Blocker > Labels: task > Fix For: 4.2.3.Beta1 > > > For JBIDE 4.2.3.Beta1 [Aerogear]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.1 to 1.0.2 or from 1.0.2 to 1.0.3. > Please also ensure that the version of your plugins in the master (4.3.x) branch is a LARGER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT > {code} > 2. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Beta1-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Beta1-SNAPSHOT > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19045) Update Tern.java (TP) and AngularJS (Central) IDE v.0.7

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19045?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19045: ------------------------------------ Any user who's running JBT 4.2.0 to 4.2.2 needs 0.6. Builds run against the 4.40.x target platform to ensure that we can build and install against the baseline Eclipse Luna R 4.4.0, not SR1 or SR2 4.4.x. And the latest 4.40.0.Final TP contain 0.6, not 0.7. So [as you suggest], we could leave 0.6 in the JBT/JBDS TPs, and put 0.7 into Central (or even into the JBT/JBDS update site, if that's better?). That would allow them to BOTH exist in the composite site that is JBT+TP+Central or JBDS+TP+Central, but would also save us from having to have TWO versions in the same TP (which breaks TP validation because both versions can't be co-installed). IMHO, even if the JST plugins in 4.2.3 will run with [0.6,0.7], we need both versions there for users who might install JBDS 8.0 instead of 8.1. ---- Alternatively, we could start building w/ Luna SR2 instead of R, and force everyone to upgrade to SR2 / 8.1, dropping support for Eclipse Luna R and SR1 entirely. > Update Tern.java (TP) and AngularJS (Central) IDE v.0.7 > ------------------------------------------------------- > > Key: JBIDE-19045 > URL: https://issues.jboss.org/browse/JBIDE-19045 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, jsp/jsf/xml/html source editing, target-platform > Reporter: Alexey Kazakov > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.3.Beta1 > > > We are going to update Tern to v0.7.0 for 4.2.x. > Master will be updated to the latest 0.8.0 (see the corresponding issue JBIDE-19002) > p2diff output: > {code} > ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... > < tern.eclipse.ide.tools.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.ui [0.7.0.201412012159] > < tern.eclipse.ide.tools.ui [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.7.0.201412012159] > < tern-jsdt-feature.feature.jar [0.7.0.201412012159] > < tern.server.nodejs [0.7.0.201412012159] > < tern-server-nodejs-feature.feature.jar [0.7.0.201412012159] > < tern.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.7.0.201412012159] > < tern.eclipse.ide.core [0.7.0.201412012159] > < tern-server-nodejs-feature.feature.group [0.7.0.201412012159] > < tern-feature.feature.group [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.core [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.ui [0.7.0.201412012159] > < tern.eclipse.ide.tools.feature.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.7.0.201412012159] > < tern-jsdt-feature.feature.group [0.7.0.201412012159] > < tern-feature.feature.jar [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.7.0.201412012159] > < tern.eclipse.ide.server.nodejs.embed.feature.group [0.7.0.201412012159] > < tern.eclipse.ide.jsdt [0.7.0.201412012159] > < tern.eclipse.ide.tools.feature.feature.group [0.7.0.201412012159] > < tern.eclipse [0.7.0.201412012159] > > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 [0.6.0.201409231610] > > tern.eclipse.ide.core [0.6.0.201409231610] > > tern-feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.tools.feature.feature.group [0.6.0.201409231610] > > tern.server.nodejs [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 [0.6.0.201409231610] > > tern-jsdt-feature.feature.jar [0.6.0.201409231610] > > tern-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.tools.ui [0.6.0.201409231610] > > tern-jsdt-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.ui [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 [0.6.0.201409231610] > > tern-server-nodejs-feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.feature.group [0.6.0.201409231610] > > tern.eclipse [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.core [0.6.0.201409231610] > > tern.eclipse.ide.ui [0.6.0.201409231610] > > tern.core [0.6.0.201409231610] > > tern-server-nodejs-feature.feature.group [0.6.0.201409231610] > > tern.eclipse.ide.tools.core [0.6.0.201409231610] > > tern.eclipse.ide.jsdt [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 [0.6.0.201409231610] > > tern.eclipse.ide.tools.feature.feature.jar [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 [0.6.0.201409231610] > > tern.eclipse.ide.server.nodejs.embed.feature.jar [0.6.0.201409231610] > === Summary === > ./jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 25 unique IUs > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... contains 25 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2015