December 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3489) Publishing existing eclipse project to OpenShift

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3489?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-3489. ------------------------------- Resolution: Done > Publishing existing eclipse project to OpenShift > ------------------------------------------------ > > Key: JBDS-3489 > URL: https://issues.jboss.org/browse/JBDS-3489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Critical > Labels: openshift_v3 > Fix For: 9.1.0.Beta1 > > Attachments: project-selection.bmml, project-selection.png > > > As a developer I would like to take an existing eclipse web project and deploy to my existing openshift v3 connection. > * This is equivalent to 'oc new-app' -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3279) Screencasts: Maven

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3279: ------------------------------ Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.Beta1) > Screencasts: Maven > ------------------ > > Key: JBDS-3279 > URL: https://issues.jboss.org/browse/JBDS-3279 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, maven, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Fix For: 9.1.0.Beta2 > > > As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow. > Use cases include: > - creation of a new project and its pom.xml, with the pom.xml editor > - dependencies adds/removes > - Import maven projects - from a SVN or Git repo > - multi-module maven projects > - run on server > - package vs install > - update - the magic "update project" that helps get Eclipse and Maven back into agreement > - adjust profiles - address the Arquillian profile -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3282) Screencasts: OpenShift v3

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3282?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3282: ------------------------------ Fix Version/s: 9.1.0.Beta2 (was: 9.1.0.Beta1) > Screencasts: OpenShift v3 > ------------------------- > > Key: JBDS-3282 > URL: https://issues.jboss.org/browse/JBDS-3282 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: documentation, openshift, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Priority: Minor > Labels: screencast > Fix For: 9.1.0.Beta2 > > > A series of short (5 minutes), educational videos to illustrate the new capabilities of JBDS associated with OpenShift. > Including: > - OpenShift's new web UI > - OpenShift Explorer in the context of v3 > - perhaps an overview of Kubernetes, depends on how "pods" become visible to our end-user > - an overview of Docker, depends on how 'containers" become visible to our end-user > and all the typical start, stop, add, delete/remove, view logs, set env vars, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21183) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21183?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21183: ------------------------------------- I believe the bulk of the work for this is done, but I'm unsure of the entrypoints where it was erroring, so it would be worth having someone verify that it's fixed now. > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21183 > URL: https://issues.jboss.org/browse/JBIDE-21183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20687: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Deployed war is NOT the specified war name > ------------------------------------------ > > Key: JBIDE-20687 > URL: https://issues.jboss.org/browse/JBIDE-20687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Beta2 > > > The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*. > Sample pom.xml which exibits the issue > {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.glassfish-samples</groupId> > <artifactId>auction</artifactId> > <version>4.0-SNAPSHOT</version> > <packaging>war</packaging> > <name>WebSocket Auction Sample Application</name> > > <dependencies> > <dependency> > <groupId>javax</groupId> > <artifactId>javaee-api</artifactId> > <version>7.0</version> > <scope>provided</scope> > </dependency> > </dependencies> > > <build> > <finalName>websocket-auction</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-war-plugin</artifactId> > <version>2.3</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > <warName>websocket-auction</warName> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20508) Makes workflow to modify application based on OS v3 templates user friendly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20508?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20508: ------------------------------------- [~mlabuda] does JBDS-3489 cover what you need (deploy existing git-shared projects from templates)? > Makes workflow to modify application based on OS v3 templates user friendly > --------------------------------------------------------------------------- > > Key: JBIDE-20508 > URL: https://issues.jboss.org/browse/JBIDE-20508 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Critical > Fix For: 4.3.1.Beta1 > > > Currently if user wants to modify an existing application based on a template with source code, user has to fork a repo containing source code, copy URL of a fork and paste it into template parameter SOURCE_CODE_URL. This is a bit unfriendly work flow from my point of view, because it requires several steps: > 1) At first user has to know an URL of a source code for a template. Intuitively user would go through New Application Wizard to Template Parameters wizard page and check value of SOURCE_CODE_URL parameter. > 2) Fork a repository containing source code - it requires switching to browser and go to the repository web page and fork repo. > 3) Copy a URL of user's source code repo (its easier to use SSH url git@github.com:user/repo.git to avoid filling in credentials for a github account) > plus importing an application, making changes, commit and push. > Would it be possible to create a fork and use user specific URL automatically? E.g. show a dialog to enter github username and tooling would via git API fork the repo and put the user specific source code URL into wizard page as template parameter. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21072) Application wizard: Server templates tree is not rendered

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21072?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21072: ------------------------------------- [~adietish] what's the status on that one? > Application wizard: Server templates tree is not rendered > --------------------------------------------------------- > > Key: JBIDE-21072 > URL: https://issues.jboss.org/browse/JBIDE-21072 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3, upstream > Fix For: 4.3.1.Beta1 > > Attachments: wizard.png > > > When I select at first a local template then proceed to next wizard page in a New OpenShift Application wizard and hit back button then tree containing server templates is not rendered correctly. Only search text field is shown but the tree with templates is missing there. > !wizard.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21184) Deploy docker: "Resource Name" should not error (but "*" required) if empty

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21184?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21184: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > Deploy docker: "Resource Name" should not error (but "*" required) if empty > --------------------------------------------------------------------------- > > Key: JBIDE-21184 > URL: https://issues.jboss.org/browse/JBIDE-21184 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > Attachments: resource-name-empty.png > > > how to reproduce: > # EXEC: in explroer: open up context menu on an openshift 3 project and choose "Deploy Docker Image..." > # ASSERT: Deploy Docker Image wizard pops up empty > Result: > The "Resource Name" field is decorated with an error marker, it should be decorated with a "*" which is used all across OpenShift when required values are missing/empty > !resource-name-empty.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21183) OC binary should be looked up on $PATH if the user doesnt provide a specific location

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21183?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21183: ------------------------------------- [~rob.stryker] was this covered in the stuff you've done around binary lookup already? > OC binary should be looked up on $PATH if the user doesnt provide a specific location > ------------------------------------------------------------------------------------- > > Key: JBIDE-21183 > URL: https://issues.jboss.org/browse/JBIDE-21183 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Labels: openshift_v3 > Fix For: 4.3.1.Beta1 > > > For port forwarding, log streming and rsyinc the tooling requires an oc binary to be installed on the local machine. The user is asked to to set the location of this binary in the OpenShift 3 preferences. He can do this either manually by browsing and pointing to the binary or by hitting "Restore Defaults" which looks it up in the $PATH. > We should lookup the binary in $PATH if the user doesnt provide anything, we should not error and tell the user to set the location as we do currently. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20576) OpenShift Explorer: Add filter of resources by label

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20576?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20576: -------------------------------- Fix Version/s: 4.3.1.Beta2 (was: 4.3.1.Beta1) > OpenShift Explorer: Add filter of resources by label > ---------------------------------------------------- > > Key: JBIDE-20576 > URL: https://issues.jboss.org/browse/JBIDE-20576 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Fix For: 4.3.1.Beta2 > > > The upcoming version of the OpenShift Explorer (JBIDE-19178) should allow filtering of resources by label -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015