September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-19979) New Docker connection wizard is confusing when no Docker is detected

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19979?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-19979. --------------------------------- This is still working in JBDS 9.0.0.CR1 B105 like I described in my last comment, so closing. > New Docker connection wizard is confusing when no Docker is detected > -------------------------------------------------------------------- > > Key: JBIDE-19979 > URL: https://issues.jboss.org/browse/JBIDE-19979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: docker, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Xavier Coulon > Fix For: 4.3.0.CR1 > > > When I open the new Docker Connection wizard (clicking on the link in Docker Explorer) and no running Docker daemon is detected, there is no way to know this. If I know how this works, then I will know that a detected docker would result in prefilled fields in the Wizard. But if I don't know this, I can be easily confused. There is no warning or anything. And what's worse, I can even click Finish to create the connection. It should be disabled unless I select custom values in case Docker was not detected. > Upstream bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=469635 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20774?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20774. ------------------------------ Resolution: Done > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 > ------------------------------------------------- > > Key: JBIDE-20774 > URL: https://issues.jboss.org/browse/JBIDE-20774 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1: 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...] > See also: JBDS-3529 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3258. ------------------------------- Closing. The rest will be done in other jira(s). > Docker Tooling (Advanced Integration) > ------------------------------------- > > Key: JBDS-3258 > URL: https://issues.jboss.org/browse/JBDS-3258 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 9.0.0.CR1 > > > Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear. > In addition to the basic integrations of pull, run, stop, commit and push > boot2docker init > boot2docker up > boot2docker down > boot2docker ip > docker run -d > docker ps > docker rm > docker rmi > docker build > End-user steps: > 0) assumes boot2docker has been dowloaded and installed > 1) boot2docker init : required to to insure boot2docker-vm is properly initialized > 2) boot2docker up : starts the VirtualBox boot2docker-vm > 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability. > 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously > 5) docker ps : allows me to see all my currently running containers > 6) docker rm : allows me to kill a currently running container > 7) docker rmi : allows me to remove a local image > 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded > 9) docker run : this new created image > The docker build scenario can be triggered via a Maven plugin > The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install) > We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14385) Server Adapter ignores deploy-name of component projects

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14385?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-14385. --------------------------------- Verified in JBDS 9.0.0.CR1 B105. I deployed the provided ear project and then checked the deployment directory of the server and the ear included the version in the name. > Server Adapter ignores deploy-name of component projects > -------------------------------------------------------- > > Key: JBIDE-14385 > URL: https://issues.jboss.org/browse/JBIDE-14385 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Alpha2 > Environment: WTP 3.5.0 > Reporter: Fred Bricon > Assignee: Rob Stryker > Labels: respin-a > Fix For: 4.3.0.CR1 > > Attachments: ear-deploy-name-ignored.png, JBIDE-14385-ear.zip > > > After https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918 has been fixed, I expected the deploy-name of EAR projects to be honored during deployment. It's not the case. > !ear-deploy-name-ignored.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] Martin Malina closed JBDS-3256. ------------------------------- Basic docker support is done, the rest will be done in other jiras. Closing. > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: docker, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > Labels: new_and_noteworthy > Fix For: 9.0.0.CR1 > > Attachments: multiview_properties_docker_idea.bmml, multiview_properties_docker_idea.png > > > 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] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-508: -------------------------------- Assignee: Paul Leacu > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20805) For JBIDE 4.3.0.Final: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20805?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20805. ------------------------------ Resolution: Done Child tasks done. Closing. > For JBIDE 4.3.0.Final: Code Freeze + Branch > ------------------------------------------- > > Key: JBIDE-20805 > URL: https://issues.jboss.org/browse/JBIDE-20805 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3530 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20810) For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20810?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20810. ------------------------------ Resolution: Done Nothing to do in maven-plugins. Does not depend on parent pom and is versioned 0.23.2-SNAPSHOT (related to Tycho, not JBT). > For JBIDE 4.3.0.Final: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch] > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20810 > URL: https://issues.jboss.org/browse/JBIDE-20810 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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] (JBIDE-20815) For JBIDE 4.3.0.Final: Code Freeze + Branch [Playground]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20815?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20815. ------------------------------ Resolution: Done Done but not closed. https://github.com/jbosstools/jbosstools-playground/commit/9758d0bfd73a87... > For JBIDE 4.3.0.Final: Code Freeze + Branch [Playground] > -------------------------------------------------------- > > Key: JBIDE-20815 > URL: https://issues.jboss.org/browse/JBIDE-20815 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.Final > > > For JBIDE 4.3.0.Final [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Final > [Unresolved JIRAs with fixVersion = 4.3.0.Final, 9.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In your *{color:blue}jbosstools-4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.0.Final-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.Final-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.x{color}* branch, and > * *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 2. Close (do not resolve) this JIRA when done. > 3. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [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] (JBIDE-20828) Unify code for Link widget emulation via StyledText

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20828?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20828. -------------------------------------- Resolution: Done > Unify code for Link widget emulation via StyledText > --------------------------------------------------- > > Key: JBIDE-20828 > URL: https://issues.jboss.org/browse/JBIDE-20828 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.3.1.Final > > > Because of the upstream issue with link widgets that are not clickable (in dialogs only) we started emulating it via StyledText: JBIDE-20092, JBIDE-20361, https://bugs.eclipse.org/bugs/show_bug.cgi?id=471717 > We now should centralize the code that creates those StyledTexts -- 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