April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17208) cannot create python app w/jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17208?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17208: ------------------------------------- Fix Version/s: 4.2.0.Beta2 > cannot create python app w/jenkins > ---------------------------------- > > Key: JBIDE-17208 > URL: https://issues.jboss.org/browse/JBIDE-17208 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.2.0.Beta2 > > > When trying to create a pyton 2.7 w/jenkins client I get this error: > Could not create application "jira" > Could not request https://openshift.redhat.com/broker/rest/domain/man/applications?include=...: An application must contain one web cartridge. None of the specified cartridges is a web cartridge. Please include one of the following cartridges: diy-0.1, jboss-dv-6.0.0, jboss-vertx-2.1, jbossas-7, jbosseap-6, jbossews-1.0, jbossews-2.0, jenkins-1, nodejs-0.10, nodejs-0.6, perl-5.10, php-5.3, php-5.4, python-2.6, python-2.7, python-3.3, ruby-1.8, ruby-1.9, zend-5.6, and zend-6.1 or supply a valid url to a custom web_framework cartridge. > -- Configuration Details -- > Product: Eclipse 4.4.0.20140301-1817 (org.eclipse.epp.package.jee.product) > Installed Features: > org.jboss.ide.eclipse.as.feature 3.0.0.Beta2-v20140421-1626-B483 -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2778) Support New Binary Deployment mode

by Eric Rich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2778?page=com.atlassian.jira.plugin.... ] Eric Rich commented on JBDS-2778: --------------------------------- This 'definition' of binary deployment is different from that of what is done with Java Artifacts. This would me more of an admin operation with your account. Example: Once the OpenShift Plugin is configured you can create an application. Then save that application with the snapshot features https://access.redhat.com/site/documentation/en-US/OpenShift_Online/2.0/h... >From there I can or should be able to use this snapshot as a binary to re-deploy or move this deployment to another gear (IE clone the gear, or moved from a non-scaled application to a scaled application). > Support New Binary Deployment mode > ---------------------------------- > > Key: JBDS-2778 > URL: https://issues.jboss.org/browse/JBDS-2778 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 8.0.0.GA > > -- 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

11 years, 11 months

1
0
0 / 0

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

by Eric Rich (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Eric Rich commented on JBDS-2864: --------------------------------- Even if using the roll back model you still need to follow: https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2... > 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17210?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17210: ---------------------------------------- I just looked at http://download.jboss.org/jbosstools/updates/nightly/core/master and it seems to be up-to-date. > where is our nightly site OR why is nightly site not actually built regularly? > ------------------------------------------------------------------------------ > > Key: JBIDE-17210 > URL: https://issues.jboss.org/browse/JBIDE-17210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > http://download.jboss.org/jbosstools/updates/nightly/core/master > our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing. > see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > Why is this ? > Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ? > p.s. i'm going to kick of a build so we get some fixes into the nightly. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Martin Malina closed JBIDE-7515. -------------------------------- Works somewhat in 4.2.0.Beta1, closing. > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Martin Malina commented on JBIDE-7515: -------------------------------------- I tend to disagree here. The point of a feature request is to add the feature AND ensure it works as expected, IMHO. But no problem, here you go: JBIDE-17212 > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta2 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Martin Malina updated JBIDE-7515: --------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Beta2) > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > Attachments: JBIDE-7515_1.png, JBIDE-7515_2.png, JBIDE-7515_3.png, JBIDE-7515_lc1.png, JBIDE-7515_lc2.png, JBIDE-7515_lc3.png > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter

by Martin Malina (JIRA)

Martin Malina created JBIDE-17212: ------------------------------------- Summary: Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter Key: JBIDE-17212 URL: https://issues.jboss.org/browse/JBIDE-17212 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.2.0.Beta1 Reporter: Martin Malina Assignee: Rob Stryker Fix For: 4.2.0.Beta2 As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case. >From JBIDE-7515: {quote} I left the shutdown script empty. You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't. In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1". {quote} The shutdown should default to process kill even if the shutdown script is empty. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17211) Inform users which deployment scanner's interval they're setting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17211?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17211: ---------------------------------- Assignee: Rob Stryker > Inform users which deployment scanner's interval they're setting > ---------------------------------------------------------------- > > Key: JBIDE-17211 > URL: https://issues.jboss.org/browse/JBIDE-17211 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR1 > > > You asked for a new JIRA in JBIDE-15287 so here you go :) > It is possible to change the interval for the custom deployment scanners that the tools add. > But the UI doesn't state this, so it seems that in fact we alter the interval even for the default deployment scanner which we don't. -- 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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17211) Inform users which deployment scanner's interval they're setting

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17211?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-17211: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Inform users which deployment scanner's interval they're setting > ---------------------------------------------------------------- > > Key: JBIDE-17211 > URL: https://issues.jboss.org/browse/JBIDE-17211 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Martin Malina > Fix For: 4.2.0.CR1 > > > You asked for a new JIRA in JBIDE-15287 so here you go :) > It is possible to change the interval for the custom deployment scanners that the tools add. > But the UI doesn't state this, so it seems that in fact we alter the interval even for the default deployment scanner which we don't. -- 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

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