January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2776: ---------------------------------------- set fixVersion 8.0.0.GA according to discussion/sync with OpenShift team > Support quickstarts in OpenShift UI > ----------------------------------- > > Key: JBDS-2776 > URL: https://issues.jboss.org/browse/JBDS-2776 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 7.0.0.GA > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Fix For: 8.0.0.GA > > Attachments: new-application-2.png > > > OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI: > !new-application-2.png! > JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16214) Code Coverage jobs needs to have locally available measured plugins

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16214?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16214: ---------------------------------------- Good news is that I can reproduce it. > Code Coverage jobs needs to have locally available measured plugins > ------------------------------------------------------------------- > > Key: JBIDE-16214 > URL: https://issues.jboss.org/browse/JBIDE-16214 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.1.1.CR1 > Reporter: Vlado Pakan > Assignee: Mickael Istria > Fix For: 4.1.x > > > Code Coverage calculating via maven build returns 0% coverage because it's using source code and binary plugins installed from update site. > When these are built locally prior to build calculating code coverage it returns correct results. > Unfortunately sometimes maven build used plugins installed from update site instead of those which are locally build. > We need to find way how to fix this. > It's already reported here https://bugs.eclipse.org/bugs/show_bug.cgi?id=352560 -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2776: ----------------------------------- Fix Version/s: 8.0.0.GA (was: LATER) > Support quickstarts in OpenShift UI > ----------------------------------- > > Key: JBDS-2776 > URL: https://issues.jboss.org/browse/JBDS-2776 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 7.0.0.GA > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Fix For: 8.0.0.GA > > Attachments: new-application-2.png > > > OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI: > !new-application-2.png! > JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users. -- 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, 9 months

1
0
0 / 0

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

by Daniel McPherson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin.... ] Daniel McPherson commented on JBDS-2864: ---------------------------------------- Some details about the new deployments system: Under application: http://openshift.github.io/documentation/rest_api/rest-api-1-6.html#appli... Update application will allow you to set: auto_deploy deployment_type - git or binary deployment_branch - This is just a default. Can be overridden on each deploy. keep_deployments - Number of historical deployments to keep that you can roll back to. Then you can perform a deploy with: Deploy the application (found under application) And activate a previous deployment with: Activate a specific deployment of the application (also under application) And you can list deployments with (See list all deployments): http://openshift.github.io/documentation/rest_api/rest-api-1-6.html#deplo... > 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 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16128) Publish component sites to Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16128?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16128: ------------------------------------ If you're just adding the new `mvn deploy` section between the `publish.sh` and `mvn verify tests/pom.xml` steps, then sure. Go for it. > Publish component sites to Nexus > -------------------------------- > > Key: JBIDE-16128 > URL: https://issues.jboss.org/browse/JBIDE-16128 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > Attachments: deployWithJenkins.png > > > In order to get a first idea of how easy/difficult it would be to rely on Nexus for publication,we could simply start by configuring CI jobs to also run a "mvn deploy" to deploy the output p2 repository onto Nexus. > Then we'll see what are the pros/cons of this approach. > Current publication process and locations will be kept. These p2 repo on Nexus won't be consumed by aggregator, at least not until we are sure it's worth it. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-228) Please update target platform dependencies to .Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-228?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-228: ---------------------------------- Updated drools/jBPM in the IS to 6.0.1.Final https://github.com/jbosstools/jbosstools-integration-stack/pull/164 > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-228 > URL: https://issues.jboss.org/browse/JBTIS-228 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools/ jBPM > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16290) Bugs using SWT over GTK3

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16290?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16290: ----------------------------------- Description: This ticket is meant to list the bugs related to GTK3 affecting JBDS: * JBIDE-16280 VPE/XulRunner crashes workbench * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 * Central tests uses SWT_GTK3=0 in its pom. * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. was: This ticket is meant to list the bugs related to GTK3 affecting JBDS: * JBIDE-16280 VPE/XulRunner crashes workbench * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 * Central tests uses SWT_GTK3=0 in its pom. We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. > Bugs using SWT over GTK3 > ------------------------ > > Key: JBIDE-16290 > URL: https://issues.jboss.org/browse/JBIDE-16290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Snjezana Peco > Fix For: 4.2.x > > > This ticket is meant to list the bugs related to GTK3 affecting JBDS: > * JBIDE-16280 VPE/XulRunner crashes workbench > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=420581 > * Central tests uses SWT_GTK3=0 in its pom. > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=421127 > We should make sure all SWT issues we met are reported upstream and that we provide the necessary assistance to SWT developers to make sure everything will be stable for Luna/GA. > On Linux, most issues can be "hidden" by setting SWT_GTK3=0, but that's definitely not something we want to rely on for JBDS, as SWT over GTK2 will not be maintained in future. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- [~dgolovin] did you mean to mix com.jboss.*jbds*.core and com.jboss.*devstudio*.core in your Option D above? As to convention for "branding plugins" we also have this: {code} com.jboss.jbds.usage.branding{code} So perhaps instead of com.jboss.jbds.core we would want *com.jboss.jbds.core.branding*? > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-228) Please update target platform dependencies to .Final

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-228?page=com.atlassian.jira.plugin.... ] Kris Verlaenen resolved JBTIS-228. ---------------------------------- Resolution: Done > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-228 > URL: https://issues.jboss.org/browse/JBTIS-228 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools/ jBPM > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-228) Please update target platform dependencies to .Final

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-228?page=com.atlassian.jira.plugin.... ] Kris Verlaenen commented on JBTIS-228: -------------------------------------- New update site available on http://downloads.jboss.org/jbpm/release/6.0.1.Final/updatesite/ > Please update target platform dependencies to .Final > ---------------------------------------------------- > > Key: JBTIS-228 > URL: https://issues.jboss.org/browse/JBTIS-228 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools/ jBPM > Affects Versions: 7.0.0.Final-JBDSIS > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please respin your component to include JBTIS TP 4.1.5.Final > On Dec. 8 JBossTools released version 4.1.1.Final of core and coretests: > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.core/ > http://download.jboss.org/jbosstools/updates/JBossTools-4.1.1.Final.coret... > These (and some other) changes have been picked up by the JBTIS TP 4.1.5.Final release (also by JBTIS TP 4.1.5.CR3): > https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > Most of the aggregate components pick up the nexus version of the JBTIS target platform. We need for you to rebuild and resubmit your component built using the .Final JBTIS TP (which gets you JBDS core/coretests .Final) so we: > 1. Know as early as possible is the .Final broke anyone > 2. Establish a stable TP for subsequent kepler releases > This needs to be done for the Jan. 8 DV/FSW 6.0 tooling capture. > Thanks! -- 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, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014