May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20937: -------------------------------- Story Points: 20 > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha2 > > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22190) Application wizard: Support "URL" templates to create a new application

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22190?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22190: -------------------------------- Story Points: 14 > Application wizard: Support "URL" templates to create a new application > ----------------------------------------------------------------------- > > Key: JBIDE-22190 > URL: https://issues.jboss.org/browse/JBIDE-22190 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > Currently, we can choose on the server template or to use a local template. it would be nice to be able to use an URL template too. > My current use case: I want to create a Fuse Integration Service application based on a template which is available on github at https://raw.githubusercontent.com/jboss-fuse/application-templates/master... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22187: -------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > Connection wizard: Should not be able to create duplicate Openshift connections > ------------------------------------------------------------------------------- > > Key: JBIDE-22187 > URL: https://issues.jboss.org/browse/JBIDE-22187 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff MAURY > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.0.Alpha2 > > > It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3850) Test code coverage console report for platform installer unit tests

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3850?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3850: -------------------------------- Sprint: (was: devex #113 April 2016) > Test code coverage console report for platform installer unit tests > ------------------------------------------------------------------- > > Key: JBDS-3850 > URL: https://issues.jboss.org/browse/JBDS-3850 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Denis Golovin > Assignee: Pavol Pitonak > Labels: Havoc > Fix For: 10.0.0.Alpha2 > > Attachments: code_coverage_unit.png > > > Would be good to have code coverage report for unit tests to see how reliable tests are -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22177) Docker Image host is missing from Deployment Config when deploying from a private registry

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22177?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22177: -------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > Docker Image host is missing from Deployment Config when deploying from a private registry > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22177 > URL: https://issues.jboss.org/browse/JBIDE-22177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Fix For: 4.4.0.Alpha1 > > > If you deploy a docker image from myregistry:5000/example/myimage, the deployment config is generated with only example/myimage, so can't find the image to deploy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22066) Server adapter: Stopping debugging of OpenShift application should get application back to normal state.

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22066?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22066: -------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > Server adapter: Stopping debugging of OpenShift application should get application back to normal state. > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22066 > URL: https://issues.jboss.org/browse/JBIDE-22066 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha2 > > > When user stop or delete Server Adapter where debugging has been enabled, application should be able to get back to normal state - remove environment variable for debugging and remove ports for debugging from deployment config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22157: -------------------------------- Sprint: devex #114 May 2017 (was: devex #113 April 2016) > On deployoment, utility JAR projects are being exploded on WEB-INF/LIB > ---------------------------------------------------------------------- > > Key: JBIDE-22157 > URL: https://issues.jboss.org/browse/JBIDE-22157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Eclipse: Mars, latest version. > Webserver: Wilfly 10.0.0 > Maven: 3.3.3 > JBoss Tools: Latest version. > Reporter: Tiago Matias > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > Attachments: JBIDE22157.zip > > > Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside. > After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project. > An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below: > org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado) > org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151) > org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) > org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) > org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456) > org.apache.jasper.compiler.Parser.parse(Parser.java:143) > A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built. > I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment. > Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3875) Split gulpfile.js to multiple modules to simplify maintenance

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3875?page=com.atlassian.jira.plugin.... ] Pavol Pitonak commented on JBDS-3875: ------------------------------------- [Test tasks|https://github.com/redhat-developer-tooling/developer-platform-inst... moved to separate file some time ago. Now we should do the same for build-related tasks (and clean-up tasks if it makes sense) I also suggest that we use some naming convention for Gulp tasks, what about prefixing _test:_ for everything in test tasks and _build:_ for build-related tasks? We already have _transpile:app_. The only tasks that stay in gulpfile.js are high-level tasks that should also have 1:1 mapping to npm scripts (i.e. npm run package-simple calls gulp package-simple)... not sure about naming conventions for these scripts/tasks. > Split gulpfile.js to multiple modules to simplify maintenance > ------------------------------------------------------------- > > Key: JBDS-3875 > URL: https://issues.jboss.org/browse/JBDS-3875 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Jan Richter > Assignee: Pavol Pitonak > Labels: havoc > > Following up from JBDS-3851. Split the gulpfile into separate modules. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3859) Use SHA256sums to intelligently download latest CI builds into DP installer

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3859?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3859: ----------------------------------- [~nickboldt], so the approach of choice is the first bullet + using latest devstudio url, right? > Use SHA256sums to intelligently download latest CI builds into DP installer > --------------------------------------------------------------------------- > > Key: JBDS-3859 > URL: https://issues.jboss.org/browse/JBDS-3859 > Project: Red Hat Developer Studio (DevStudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 10.0.0.Alpha1 > > > Per discussion with Denis today, we could: > * check REMOTE sha256sum before pulling down a new JBDS jar; this will allow us to only fetch a new jbds.jar if the SHAs don't match because a new CI build is available > * re-enable creation of sha256sum after a download (so that we don't have to create them every time we want to compare to a remote one > * switch json to use nightly for CDK, vbox, jbds, so builds will use the latest CI > * add cmdline flag to use the values in requirements.json vs. nightly latest CI, so it's easy to switch between a CI-based build and a statically-defined list of deps > * add url-latest in requirements.json so that for requirements that have a CI or latest URL, we know where to pull the nightly; this would obviate the need to pass in the URLs via commandline, or to have to toggle between stable/staging and snapshot/CI every time we want to run one type of build or the other -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-688) Rebuild JBDS-IS build to include new Drools/jBPM plugin

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-688?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-688: ----------------------------------------- [~bbrodt] please do not forget on the version format (JBTIS-471) > Rebuild JBDS-IS build to include new Drools/jBPM plugin > ------------------------------------------------------- > > Key: JBTIS-688 > URL: https://issues.jboss.org/browse/JBTIS-688 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 9.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > Currently, there is Drools 6.4.0.Final. Bug Bob and Kris want to include some bug fixes (see JBTIS-686) and ask for including the version 6.4.1.Final. > QE is now verifying the bug fixes and found some issues. Here we will discuss whether we include version 6.4.1.Final into JBDS-IS 9.0.0.GA or not. > Note that we cannot include Drools 6.3.1.Final since this version wasn't tested with JBDS 9.1.0.GA. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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