September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20685: ------------------------------------- Summary: Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation (was: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation) > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.3.x > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20685) Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20685?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20685: ------------------------------------- Labels: openshift_v3 preferences (was: ) > Preferences: oc location text field in OpenShift 3 preferences should be uneditable or there should be on fly validation > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-20685 > URL: https://issues.jboss.org/browse/JBIDE-20685 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: openshift_v3, preferences > Fix For: 4.3.x > > > It would be nice to have oc location in OpenShift 3 preference page uneditable (to have better overview/control over chosen file) or at least text widget containing this location should have been validation "on fly", because it is not happening all the time at the moment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19654) Application wizard: Opening the wizard on an account without SSH key opens broken wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19654: ------------------------------------- Labels: application_wizard openshift_v2 (was: application_wizard) > Application wizard: Opening the wizard on an account without SSH key opens broken wizard > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19654 > URL: https://issues.jboss.org/browse/JBIDE-19654 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v2 > Fix For: 4.3.x > > Attachments: new_app_wizard.png, prompt-to-upload-keys.png > > > If user is opening a New application wizard from domain (context menu on domain item in OpenShift explorer) or shell menu (File - New - OpenShift Application) and there is no SSH key related to v2 account, the wizard is opened directly and cartridge/quickstart selection is empty > !new_app_wizard.png! > There should be at first opened SSH Key wizard/dialog to let the user add a SSH key to the account and then it should proceed to New application wizard (this is how it worked. Currently it's working like this only on New application wizard opened via context menu of a connection). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20686) Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20686?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20686: ------------------------------------- Summary: Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences (was: No OpenShift Client binary warning dialog is shown upon restoring default preferences) > Preferences: No OpenShift Client binary warning dialog is shown upon restoring default preferences > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-20686 > URL: https://issues.jboss.org/browse/JBIDE-20686 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.3.x > > > In OpenShift 3 workbench preference page restoring default setting by clicking on a button Restore Defaults pops up a warning dialog with title "No OpenShift Client binary" and text "Could not find the OpenShift binary "oc" on your path". I would expect that choosing default settings would just clear text field with oc binary location and no dialog is shown. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18866) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18866?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18866: ------------------------------------- Labels: new_and_noteworthy openshift_v2 (was: new_and_noteworthy) > allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18866 > URL: https://issues.jboss.org/browse/JBIDE-18866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v2 > Fix For: 4.3.x > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git(a)github.com: or ssh://git@github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18866) Application wizard: allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18866?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18866: ------------------------------------- Summary: Application wizard: allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges (was: allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges) > Application wizard: allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > --------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18866 > URL: https://issues.jboss.org/browse/JBIDE-18866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: new_and_noteworthy, openshift_v2 > Fix For: 4.3.x > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges > The exact form is documented in the github (and general purpose git-) documentation: https://gist.github.com/grawity/4392747 > {quote} > SSH, aka git(a)github.com: or ssh://git@github.com/ > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-510) did JBDS IS 8.0.3 never graduate from Early Access?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-510?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBTIS-510: ------------------------------------------- [~nickboldt] I hoped we were pass getting back to discussing merging EA content into GA content site. It should simply not happen. But to iterate again: A) Earlyaccess should not become available to users without them actually opting in - if we add EA to GA site then it will be available from "Help > Install" with no indication of it being earlyaccess before actually installed. B) Check for updates should not bring in EA content - EA could have overlapping/new versions of bundles that is not GA (we have not done this yet, but it is designed to allow for that), if we add EA to GA site then check for updates does this Also see: 26. Sep. 2014: https://issues.jboss.org/browse/JBIDE-18239?focusedCommentId=13006365&pag... {quote} And no, early access and central updatesites CANNOT be in the same updatesite - that have been discussed ad libitum before how that is not okey since: A) Earlyaccess IS NOT central B) if you add earlyaccess into central then users running Help > Check for updates (or install) will get earlyaccess content even though they have not enabled it. I would really appreciate if we stop having to return to that item again - central IS NOT earlyaccess and vice versa thus they cannot be intermingled. {quote} > did JBDS IS 8.0.3 never graduate from Early Access? > --------------------------------------------------- > > Key: JBTIS-510 > URL: https://issues.jboss.org/browse/JBTIS-510 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Nick Boldt > Attachments: jbdsis803-still-ea.png > > > On Aug 27, [~pleacu] sent a note to jbds-is-pm-list(a)redhat.com, > soa-tools-list(a)redhat.com, > jbosstools-dev(a)lists.jboss.org, > jboss-qe-leads(a)redhat.com announcing, "JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final now live". > But when I look at https://devstudio.redhat.com/updates/8.0/ I see no JBDS 8.0.3 content. Instead, this content remains on https://devstudio.redhat.com/earlyaccess/8.0/ > Is that what we intended to happen? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20152: --------------------------------------- [~akazakov], my question for you was whether or not you omitted tagging of integration-tests intentionally. I agree with Max's summary. > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20687: --------------------------------------------- How about fixing it in Mars.2 too ? > 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.Final > > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20769) Add JBoss DV 6.2 to Download Runtimes Wizard

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20769?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-20769: ------------------------------------ Rafael's patch was merged almost week ago and DV 6.2 is still not in JBT/JBDS. Is there anything to be done on our side? > Add JBoss DV 6.2 to Download Runtimes Wizard > -------------------------------------------- > > Key: JBIDE-20769 > URL: https://issues.jboss.org/browse/JBIDE-20769 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.3.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.1.Final > > > JBoss DV 6.2 was released 5 days ago. I guess it should be downloadable from Download Runtimes Wizard. > I've also created JDF-852. -- 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