February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19336) To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19336: ------------------------------------ Link to JBDS-3086. > To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18846: --------------------------------------------- tools.jboss.org could be hosting it yes - but tools.jboss.org could also read metadata from somewhere else if makes sense. > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19336: --------------------------------------------- just so I don't forget this jira again - JBDS-3086 about having central and IS etc. in the root updatesite was done for allowing exactly that: not having to duplicate content (AND to just have one updatesite exposed to users) > To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3359: ------------------------------------------- [~mmalina] if thats not been tested before then that is something we definitely need to do since the whole point of central is to encourage and drive updates so core and integration-stack will continue work smoothly together. > Cannot install Hybrid Mobile tools onto 8.0.0 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) Cannot install Hybrid Mobile tools onto 8.0.0 without triggering p2 remediation

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3359: ------------------------------------------- [~nickboldt] am I reading the suggested remediation wrong - I do not see it suggest up update the overall product. I see it suggest to uninstall parts of the product and install JBoss Tools Thym integration. If the p2 remediation was being logical it should have suggested to update the product not uninstall parts of it and then install JBoss Tools Thym. > Cannot install Hybrid Mobile tools onto 8.0.0 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-3285) Git: Easy Import

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3285: ------------------------------------------- which jbosstools-playground bundles ? IMO we should move them out of playground if to be part of release. > Git: Easy Import > ---------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.x > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): > {quote} > Easymport framework has been contributed to e4 (Platform Incubator): in http://git.eclipse.org/c/e4/org.eclipse.e4.ui.git/tree/bundles , see all org.eclipse.e4.ui.importer* . You can install it in your IDE from http://download.eclipse.org/e4/snapshots/org.eclipse.e4.ui . The entry-points are either the new menu "File > Import projects from folder..." or from legacy import wizard under "General > Local folder(s) as project into workspace". > We have working extensions that allow to import Java EE & Maven: https://github.com/jbosstools/jbosstools-playground/tree/master/plugins (install from http://download.jboss.org/jbosstools/builds/staging/jbosstools-playground... ) , that we plan to contribute upstream when projects such as m2e and WTP when the framework seems mature enough. > There is not yet an easy link from the EGit wizard to the Easymport one, nor an easy link from SVN wizard to Easymport. > There is almost no chance that this can be included in Eclipse IDE for Mars release in June. But we could already think about including it in next JBoss Tools and JBoss Developer Studio milestones, so that we'd get more feedback. At this point, feedback from users and adopters is the key point. > I invite you to give it a try, and to report issues here. > {quote} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

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

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3359?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3359: ----------------------------------- [~ldimaggio] One reason I see this is more (rather than less) problematic is that, as of this past weekend, when you download JBDS 8 from jboss.org/products (a very common place to grab the bits), you get 8.0.0. You then click on "Hybrid Mobile Project" in JBoss Central - and you then run into the problem demonstrated in my screenshots. > Cannot install Hybrid Mobile tools onto 8.0.0 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-2864) Support explicit deployments

by Rodney Russ (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Rodney Russ updated JBDS-2864: ------------------------------ CDW pm_ack: - (was: +) > Support explicit deployments > ---------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.x > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support explicit deployments

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2864: ----------------------------- CDW release: - (was: ?) > Support explicit deployments > ---------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.x > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3271) Cordova App Splash Screen Support

by Rodney Russ (JIRA)

[ https://issues.jboss.org/browse/JBDS-3271?page=com.atlassian.jira.plugin.... ] Rodney Russ commented on JBDS-3271: ----------------------------------- [~gercan] are you familiar with the FH release cycle? When would (could) this be added? > Cordova App Splash Screen Support > --------------------------------- > > Key: JBDS-3271 > URL: https://issues.jboss.org/browse/JBDS-3271 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.CR1 > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. -- 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