September 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3528) there are two reddeer and RedDeer in jbdevstudio-ci

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3528?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen closed JBDS-3528. ------------------------------------- Fix Version/s: 9.0.0.CR1 Resolution: Done resolved and closed with proper fix version. > there are two reddeer and RedDeer in jbdevstudio-ci > --------------------------------------------------- > > Key: JBDS-3528 > URL: https://issues.jboss.org/browse/JBDS-3528 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 9.0.0.CR1 > > > both > {code} > cache/https/jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/... > {code} > and > {code} > cache/https/jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/... > {code} > exist in https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/cache/https/jen... > causing it being impossible to actually to a PR against jbdevstudio-ci when you are on a case-insensitive filesystem (like OSX or Windows). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-506) Update JBDS-IS version to 8.0.3 in info box on Markeplace

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-506?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-506. ----------------------------------- Fix Version/s: 8.0.3.GA Resolution: Done Now, the displayed version is 8.0.3.GA which is the right version. Thank you! > Update JBDS-IS version to 8.0.3 in info box on Markeplace > --------------------------------------------------------- > > Key: JBTIS-506 > URL: https://issues.jboss.org/browse/JBTIS-506 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.3.GA > > > There is an old version (8.0.2) of JBDS-IS in info box on Marketplace, see > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio-in... > This old version also occurs in Eclipse IDE when trying to install JBDS-IS from markeplace. > Note that correct features are installed (those in JBDS-IS 8.0.3.GA). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20401: --------------------------------------- Shouldn't we reopen JIRA, set fix version to CR2 and modify property file to point to our getting started user doc? > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Fred Bricon > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-609) FeedHenry: Document how to change the splash screen

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-609?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-609: -------------------------------------------- Hi [~mhusnain], this issue is similar to the icon change one (JBDS-3270). I have documented the steps and got them reviewed from Pavol (instructions at: https://docs.google.com/document/d/124ptroykZasftYjSQTGCd3rSYRibWABUfqqDl...). But, since we have been unable to get the app to show on the emulator (JBDS-3454), I have not tested the steps. Thanks - Supriya > FeedHenry: Document how to change the splash screen > --------------------------------------------------- > > Key: TOOLSDOC-609 > URL: https://issues.jboss.org/browse/TOOLSDOC-609 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: Priority1, cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. > This will be added to an existing article, probably as a Did You Know? Item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20784) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Playground]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20784?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-20784. ---------------------------------- Assignee: Mickael Istria Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [Playground] > -------------------------------------------------------------- > > Key: JBIDE-20784 > URL: https://issues.jboss.org/browse/JBIDE-20784 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [Playground]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. 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 Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-609) FeedHenry: Document how to change the splash screen

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-609?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-609: ------------------------------------ Hi [~supriya.bharadwaj] - what's the status for this issue? This needs to be done for GA so please update here. > FeedHenry: Document how to change the splash screen > --------------------------------------------------- > > Key: TOOLSDOC-609 > URL: https://issues.jboss.org/browse/TOOLSDOC-609 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > Labels: Priority1, cordova, feedhenry > Fix For: 4.3.0.Final > > > As a HTML5+Cordova mobile app developer, I need to change the splash screen associated with the application launch. > This will be added to an existing article, probably as a Did You Know? Item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-606) Docker: Document basic docker tooling

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-606?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-606. -------------------------------- Resolution: Done > Docker: Document basic docker tooling > ------------------------------------- > > Key: TOOLSDOC-606 > URL: https://issues.jboss.org/browse/TOOLSDOC-606 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Priority1, docker > Fix For: 4.3.0.Final > > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-606) Docker: Document basic docker tooling

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-606?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-606: ------------------------------------ Done: https://access.redhat.com/articles/1488373 > Docker: Document basic docker tooling > ------------------------------------- > > Key: TOOLSDOC-606 > URL: https://issues.jboss.org/browse/TOOLSDOC-606 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Priority1, docker > Fix For: 4.3.0.Final > > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-602) OpenShift: Document Downloading/Importing existing OS Project

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-602?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-602: ------------------------------------ Done: https://access.redhat.com/articles/1610503#import_app > OpenShift: Document Downloading/Importing existing OS Project > ------------------------------------------------------------- > > Key: TOOLSDOC-602 > URL: https://issues.jboss.org/browse/TOOLSDOC-602 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Priority1, openshift > Fix For: 4.3.0.Final > > > Document the following use case: > Use Case #1 - Download/Import Existing OpenShift Project > a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects) > b) Assume end-user is logged in (ignore auth for now) > c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services. > d) Eclipse user will open a dialog and enter the URL from step a > e) Eclipse user will see a list of "things" associated with "projects" from step 1c > "things" > f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f] > g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets > h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files > i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com) > j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container: > docker run -it -p 8080:8080 openshift/wildfly-8-centos > [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-602) OpenShift: Document Downloading/Importing existing OS Project

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-602?page=com.atlassian.jira.plug... ] Misha Ali closed TOOLSDOC-602. ------------------------------ Resolution: Done > OpenShift: Document Downloading/Importing existing OS Project > ------------------------------------------------------------- > > Key: TOOLSDOC-602 > URL: https://issues.jboss.org/browse/TOOLSDOC-602 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Priority1, openshift > Fix For: 4.3.0.Final > > > Document the following use case: > Use Case #1 - Download/Import Existing OpenShift Project > a) Assume OpenShift is started remotely and provides an entrypoint URL (e.g. http://localhost:8080/osapi/v1beta1/projects) > b) Assume end-user is logged in (ignore auth for now) > c) Assume OpenShift already has some deployed "projects", this "project" definition includes the buildconfig, deployconfig, docker image, source git URL, routes and services. > d) Eclipse user will open a dialog and enter the URL from step a > e) Eclipse user will see a list of "things" associated with "projects" from step 1c > "things" > f) Embedded in one of those things is a Git URL - that will be displayed to the user who will agree to git clone it [1f] > g) If the downloaded items include a Maven project, the Eclipse user will see a newly configured Eclipse project based on Maven with the appropriately configured facets > h) If there is no pom.xml, the Eclipse user will see a newly configured generic Eclipse project containing the downloaded files > i) It is expected that a Maven-based Java project will build locally (leveraging Maven Central and/or maven.repository.redhat.com) > j) It is expected that a Maven-based Java project will deploy to a localhost EAP/Wildfly or a locally running Docker container: > docker run -it -p 8080:8080 openshift/wildfly-8-centos > [1f] https://github.com/openshift/origin/blob/master/examples/sample-app/appli... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 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 September 2015