September 2016 - jbosstools-issues

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016 (was: devex #118 July 2016, devex #120 September 2016, RHDEVDOCS Sprint 121, > Oct 19) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #120 September 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016, RHDEVDOCS Sprint 121, > Oct 19 (was: devex #118 July 2016, devex #120 September 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3257) Basic FeedHenry Support

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3257?page=com.atlassian.jira.plugin.... ] Gorkem Ercan closed JBDS-3257. ------------------------------ > Basic FeedHenry Support > ----------------------- > > Key: JBDS-3257 > URL: https://issues.jboss.org/browse/JBDS-3257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 9.1.0.GA > > > as feedhenry user I would like to be able to easily import my existing feedhenry application into developer studio and allow me to edit and commit code back to feedhenry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3247) Hybrid Mobile Tooling covering base Apache Cordova

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3247?page=com.atlassian.jira.plugin.... ] Gorkem Ercan closed JBDS-3247. ------------------------------ Resolution: Done > Hybrid Mobile Tooling covering base Apache Cordova > -------------------------------------------------- > > Key: JBDS-3247 > URL: https://issues.jboss.org/browse/JBDS-3247 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, cordovasim, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ add support for second template - when only tweaking root poms, but not also branching > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ Job now tells user via email to run using github::JIRA mappings... {code} ./util/getProjectRootPomParents.sh -updateRootPom -createBranch -b jbosstools-4.4.2.x -b2 master -pv 4.4.2.Final-SNAPSHOT -w1 /tmp/jbt.github -vjbt 4.4.2.Final -vds 10.2.0.GA -tpmin 4.60.1.Final -tpmax 4.60.1.Final -jirahost https://issues.stage.jboss.org -jirauser jiralint -jirapwd drauc3er -p1 "aerogear::aerogear-hybrid arquillian base::foundation browsersim central forge freemarker hibernate javaee::jsf jst livereload openshift server vpe::visual-page-editor-core webservices webservices integration-tests" -p2 "build build-sites::updatesite discovery::central-update devdoc download.jboss.org maven-plugins:build versionwatch" -p3 "artwork ci::build devdoc product::installer qa website" {code} ... and you end up with this a commit message containing a JIRA ID, #comment, and #close: {code} # >>> jbosstools-integration-tests <<< # Commit change to https://github.com/jbosstools/jbosstools-integration-tests/blob/master/po... pushd /tmp/jbt.github/jbosstools-integration-tests >/dev/null && perl -0777 -i.orig -pe \ 's#(<artifactId>parent</artifactId>)[\r\n\ \t]+(<version>)([\d.]+[^<>]+)(</version>)#\1\n\t\t<version>'4.4.2.Final-SNAPSHOT'\4#igs' \ pom.xml && git commit -m "JBIDE-22819 #comment bump up to parent pom version = 4.4.2.Final-SNAPSHOT #close" . && git push origin master && popd >/dev/null; echo ">>> https://github.com/jbosstools/jbosstools-integration-tests/commits/master" # >>> jbdevstudio-product <<< # Commit change to https://github.com/jbdevstudio/jbdevstudio-product/blob/master/pom.xml pushd /tmp/jbt.github/jbdevstudio-product >/dev/null && perl -0777 -i.orig -pe \ 's#(<artifactId>parent</artifactId>)[\r\n\ \t]+(<version>)([\d.]+[^<>]+)(</version>)#\1\n\t\t<version>'4.4.2.Final-SNAPSHOT'\4#igs' \ pom.xml && git commit -m "JBDS-3955 #comment bump up to parent pom version = 4.4.2.Final-SNAPSHOT #close" . && git push origin master && popd >/dev/null; echo ">>> https://github.com/jbdevstudio/jbdevstudio-product/commits/master" {code} I also created a pair of new components in JBIDE/JBDS called "integration-tests" since there was no obvious place to map jbosstools-integration-tests in github to a matching component in JIRA. [~mmalina] is the new component's owner/default assignee. > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ implement github project :: jira component mappings for all the mismatched project/component pairs > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23127: ------------------------------------- FYI, blog "JavaScript Tools - what is new in Neon.1?" has been published - http://tools.jboss.org/blog/2016-09-29-javascript-development-tools-neon1... I also got in touch with Roxanne from Eclipse Foundation - the article would also be shared or republished on the eclipse.org > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23128) Eclipse Neon.1 JSDT Blog

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23128?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-23128: ------------------------------------- gist with html & adoc versions of the blog https://gist.github.com/ibuziuk/c1ede8af4140e4dea1be88eaced88f7b Eclipse Foundation is going to republish it > Eclipse Neon.1 JSDT Blog > ------------------------- > > Key: JBIDE-23128 > URL: https://issues.jboss.org/browse/JBIDE-23128 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript, upstream, website > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.2.AM2 > > > Need to write blog about Neon.1 JSDT improvements. Tentative structure: > - Node.js Debugger improvements > - New JavaScript Debugger > - npm scripts support > - OMPH installer support > - Important bug fixes (provide a query with all Neon.1 bug fixes) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 2016