April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16957) no difference between beta1 and beta1a updatesites

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16957?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-16957: --------------------------------------- This affects both JBDS and JBoss Tools Beta1a builds. So essentially Beta1a is broken and we're looking forward to Beta1b? Or will we call the new fixed build Beta1a still? > no difference between beta1 and beta1a updatesites > -------------------------------------------------- > > Key: JBIDE-16957 > URL: https://issues.jboss.org/browse/JBIDE-16957 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.Beta1 > > > something is funky here. > eclipse doesn't give me any updates for this new beta1a site. > Thus I tried running p2diff and browse via p2browser. The binary content except the category are identical. > See difference at https://gist.github.com/maxandersen/352153881b657fbe2ecb > none of the plugins like open shift or server has changed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10546) Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10546?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10546: ---------------------------------------- Sprint: Sprint Beta2 CF > Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10546 > URL: https://issues.jboss.org/browse/JBIDE-10546 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Isaac Rooskov > Fix For: 4.2.0.Beta2 > > > The 3.3.0.M5 new and noteworthy information highlights the ability to take an application that exists in the workspace and port it to OpenShift; however it has to be done through the OpenShift application creation wizard. > A more intuitive place for this ability to be might be within the context menu of an application in the workspace. The option to 'Import to OpenShift' could sit under the 'Configure' menu item. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13938) Add support for reddeer server requirements to integration-tests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13938?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-13938. ------------------------------ > Add support for reddeer server requirements to integration-tests > ----------------------------------------------------------------- > > Key: JBIDE-13938 > URL: https://issues.jboss.org/browse/JBIDE-13938 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: qa > Affects Versions: 4.1.0.Alpha1 > Reporter: Pavol Srna > Assignee: Radoslav Rábara > Fix For: 4.2.0.Beta1 > > > * new annotations for test classes will be introduced > * server will be defined in reddeer requirement xml > * server adapter will be configured according to the xml configuration -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10546) Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10546?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10546: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10546 > URL: https://issues.jboss.org/browse/JBIDE-10546 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Isaac Rooskov > Fix For: 4.2.0.Beta2 > > > The 3.3.0.M5 new and noteworthy information highlights the ability to take an application that exists in the workspace and port it to OpenShift; however it has to be done through the OpenShift application creation wizard. > A more intuitive place for this ability to be might be within the context menu of an application in the workspace. The option to 'Import to OpenShift' could sit under the 'Configure' menu item. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-10541) Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-10541: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Labels: server_adapter > Fix For: 4.2.x > > Attachments: committed-changes-to-publish.png > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-14322) Application wizard: displays wrong cloning location

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14322?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14322: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Application wizard: displays wrong cloning location > --------------------------------------------------- > > Key: JBIDE-14322 > URL: https://issues.jboss.org/browse/JBIDE-14322 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Stefan Bunciak > Labels: application_wizard > Fix For: 4.2.x > > Attachments: clonning.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2864) Support faster turnarounds (with possibly hot deploy)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2864: -------------------------------------- Sprint: (was: Sprint Beta2 CF) > Support faster turnarounds (with possibly hot deploy) > ----------------------------------------------------- > > Key: JBDS-2864 > URL: https://issues.jboss.org/browse/JBDS-2864 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.Beta2 > > > Currently the turnarounds are far to heavy, it takes far too much time to redeploy java applications to OpenShift. > We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid builds upon git push and manually triggering (hot-deploys) deploy > There's a blog post that is discussing parts of this: https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16720) Allow easier access to openshift operations from jboss servers

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16720?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16720: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Allow easier access to openshift operations from jboss servers > -------------------------------------------------------------- > > Key: JBIDE-16720 > URL: https://issues.jboss.org/browse/JBIDE-16720 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift, server > Affects Versions: 4.1.1.Final > Reporter: Mark Drilling > Fix For: 4.2.x > > > We currently have a couple issues with connecting to an OpenShift Data Virtualization instance from the tooling. I'm aware that issues are being addressed for future release, others I'm not sure. This is intended to help guide your development to accommodate this use case. > Our expected usage with Data Virtualization is a bit different than some others. With DV we expect to deploy via a DV cartridge to OpenShift, then connect to the OpenShift DV instance as a remote server. We typically would not deploy using git push. > Currently, we connect to an OpenShift DV instance like this: > 1) Deploy DV cartridge via OpenShift web console. > 2) Port forward from command line using rhc port-forward > 3) Set up EAP server instance in the tooling, mark as externally managed and start it. From there we can connect to the DV instance and continue with modeling and deployments in Teiid Designer perspective > The issues we observed: > 1) Creation of the OpenShift 'server' forces a git repo to be copied locally. We'd like to simply create the 'OpenShift server' without cloning the repo. > 2) Can't deploy our downloadable cartridge from the wizard. I believe OpenShift is now (or will soon) allow downloadable carts to be registered, so this problem should be solved as the cart will show up in the cartridge list. > Our current method of connecting is ok for now, but a simpler usage of the OpenShift server adapter would allow us to more easily manage the instance (e.g. port-forward without going to the command line, viewing logs, etc.) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13162) Cannot deploy dynamic web project to OpenShift without a web.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13162?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13162: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Cannot deploy dynamic web project to OpenShift without a web.xml > ---------------------------------------------------------------- > > Key: JBIDE-13162 > URL: https://issues.jboss.org/browse/JBIDE-13162 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift, upstream > Affects Versions: 4.0.0.CR1 > Reporter: Stefan Bunciak > Fix For: 4.2.x > > > Dynamic web project should should be deployable to OpenShift (is visible when merging OpenShift application and the workspace project). > After publishing, following output is returned from server: > {code} > [INFO] Packaging webapp > [INFO] Assembling webapp [dw] in [/var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/target/dw] > [INFO] Processing war project > [INFO] Webapp assembled in [19 msecs] > [INFO] Building war: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/deployments/ROOT.war > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 33.330s > [INFO] Finished at: Tue Nov 27 11:27:40 EST 2012 > [INFO] Final Memory: 8M/169M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on project dw: Error assembling WAR: webxml attribute is required (or pre-existing WEB-INF/web.xml if executing in update mode) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > hot_deploy_added=false > Found 127.3.36.1:8080 listening port > /usr/libexec/openshift/cartridges/abstract/info/lib/util: line 992: /var/lib/openshift/1e6a743963104f30bdcdebdff460d42b/app-root/runtime/repo/.openshift/action_hooks/post_start_jbossas-7: Permission denied > Failed to start jbossas-7 > {code} > Shouldn't this be a part of openshift maven profile? > {code} > <failOnMissingWebXml>false</failOnMissingWebXml> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15936) Application wizard: should only show gear sizes appropriate for the selected domain

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15936?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15936: ---------------------------------------- Sprint: (was: Sprint Beta2 CF) > Application wizard: should only show gear sizes appropriate for the selected domain > ----------------------------------------------------------------------------------- > > Key: JBIDE-15936 > URL: https://issues.jboss.org/browse/JBIDE-15936 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Michelle Murray > Labels: application_wizard > Fix For: 4.2.x > > > in the openshift application wizard, I selected a domain. The gear profile field shows three sizes but only small is allowed for the domain I have. If I am a user who doesn't know this I might select medium but then only after three pages of wizard, when trying to create app, does it tell me: > {noformat}Could not create application "MyApp" > Could not request https://openshift.redhat.com/broker/rest/domain/myjbdsdomain/applications...: App gear sizes: medium is not valid for this domain. Allowed sizes: small.{noformat} > If I click Back to change the gear profile, all of the info is removed from the wizard and I have to input it all again. Frustrating. See JBIDE-14002. > The openshift application wizard could be improved to only show appropriate gear sizes for the selected domain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

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 April 2014