February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3359) Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3359: -------------------------------------- Summary: Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation (was: CordovaSim Gone) > Cannot install Hybrid Mobile tools onto 8.0.2 without triggering p2 remediation > ------------------------------------------------------------------------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3359) CordovaSim Gone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3359: -------------------------------------- Project: Developer Studio (JBoss Developer Studio) (was: Tools (JBoss Tools)) Key: JBDS-3359 (was: JBIDE-19347) Workflow: CDW v1 (was: GIT Pull Request workflow ) Affects Version/s: (was: 4.2.0.Final) Component/s: aerogear-hybrid browsersim (was: browsersim) Fix Version/s: 8.1.0.Beta1 8.1.0.CR1 (was: 4.2.2.Final) Docs QE Status: NEW > CordovaSim Gone > --------------- > > Key: JBDS-3359 > URL: https://issues.jboss.org/browse/JBDS-3359 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aerogear-hybrid, browsersim > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.1.0.Beta1, 8.1.0.CR1 > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19347) CordovaSim Gone

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19347?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19347: --------------------------------------------- [~nickboldt] something is wrong in our p2 metadata/dependencies if the out-of-box setup won't let us install/update the pieces we've put on central. No ordinary user would expect this behavior (no matter how right it is based on the p2 medatadata). The p2 remediation here should have been to update the devstudio feature but seems another (worse) solution was found. As if Thym is having very specific includes instead of requirements. [~burrsutter] what you are seeing is p2 trying to compensate for conflicting install paths (piecemal install vs one big install) and it does that by what is called p2 remediation where it is trying to figure out the best way to get to your wanted state (installing cordova). If you see these in future do attach the screenshot you made here but also attach what is in the box if you select "Show original error and build my own solution". Then a text box should be shown with the low-level technical details on what is causing the problem. > CordovaSim Gone > --------------- > > Key: JBIDE-19347 > URL: https://issues.jboss.org/browse/JBIDE-19347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Final > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.2.Final > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19331) Links to JBDS release notes broken

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19331?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-19331: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Feel free to resolve or assign back to me once you push this to production so I can verify. > Links to JBDS release notes broken > ---------------------------------- > > Key: JBIDE-19331 > URL: https://issues.jboss.org/browse/JBIDE-19331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > > This page has a link to release notes which is broken: > http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html > It points to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > The same problem happens for JBDS 8.0.1 and 8.0.0. > The correct link is e.g.: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > So it seems we just need to trim off the trailing index.html . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19331) Links to JBDS release notes broken

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19331?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-19331: --------------------------------------- OK, thanks for the update, Michelle. [~maxandersen], you said applied in the PR, but the issue is not fixed: http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html still contains the wrong link. I checked and it's only in master, not in production. Can you fix that? Thanks. > Links to JBDS release notes broken > ---------------------------------- > > Key: JBIDE-19331 > URL: https://issues.jboss.org/browse/JBIDE-19331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Xavier Coulon > > This page has a link to release notes which is broken: > http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html > It points to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > The same problem happens for JBDS 8.0.1 and 8.0.0. > The correct link is e.g.: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > So it seems we just need to trim off the trailing index.html . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19347) CordovaSim Gone

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19347?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-19347: ------------------------------------- This is confusing for the end-user - why is the default option to essentially disable/hide/remove CordovaSim? I had to re-install JBDS and pick the 2nd bullet option to workaround the issue. > CordovaSim Gone > --------------- > > Key: JBIDE-19347 > URL: https://issues.jboss.org/browse/JBIDE-19347 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Final > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.2.Final > > > The updatesite for JBDS 8.0.0 seems to have removed CordovaSim. When I go to install the Hybrid Mobile tools (clicking on Hybrid Mobile Project of JBoss Central), then the default action is to "not install CordovaSim". > Windows > http://www.screencast.com/t/Wk8js7zf6kec > Mac OSX > http://www.screencast.com/t/1Jz7BTwzo8P -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18772: ------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-14642: ---------------------------------- Assignee: Denis Golovin (was: Max Rydahl Andersen) > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Labels: versioning > Fix For: 4.3.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14642?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-14642: ------------------------------------ Assign to Denis to comment / close. > How to automate process of bumping version for changed modules/submodules for every release > ------------------------------------------------------------------------------------------- > > Key: JBIDE-14642 > URL: https://issues.jboss.org/browse/JBIDE-14642 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.0.Beta1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Labels: versioning > Fix For: 4.3.x > > > The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped. > We need two things: > A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing) > B) document/automate a process which every affected lead can follow to make this happen and if not See #A -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19346: --------------------------------------------- to be clear, the old versions still make them earlyaccess. sounds like tern should be removed since it was never earlyacces, neither have jetty been. Not sure how/why that was ever added? sound like it was autogenerated using the full TP instead of only listing the specific features that actually is EA. i'll suggest that we go back to what earlyaccess properties should be - manually edited and then verified against the TP to detect the version ranges are correct. this verificaiton could filter out any content already found in base TP (like jetty) > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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