July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4464) Fuse Platform does not get added to runtime detection after installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4464?page=com.atlassian.jira.plugin.... ] Jan Richter edited comment on JBDS-4464 at 7/19/17 5:39 AM: ------------------------------------------------------------ The answer to my question is here: JBDS-4469. Also closing this in favor of the aforementioned issue. was (Author: jrichter1): The answer to my question is here: JBDS-4464. Also closing this in favor of the aforementioned issue. > Fuse Platform does not get added to runtime detection after installation > ------------------------------------------------------------------------ > > Key: JBDS-4464 > URL: https://issues.jboss.org/browse/JBDS-4464 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Both Fuse Platform installations on JBoss EAP and Apache Karaf are not getting added to runtime detection. This is happening because runtime detection configuration is configured to happen after devstudio installation finished. Then Fuse Tools installation is taking place and overwrites runtime detection config properties file with default one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4464) Fuse Platform does not get added to runtime detection after installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4464?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4464. ----------------------------- Resolution: Done > Fuse Platform does not get added to runtime detection after installation > ------------------------------------------------------------------------ > > Key: JBDS-4464 > URL: https://issues.jboss.org/browse/JBDS-4464 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Both Fuse Platform installations on JBoss EAP and Apache Karaf are not getting added to runtime detection. This is happening because runtime detection configuration is configured to happen after devstudio installation finished. Then Fuse Tools installation is taking place and overwrites runtime detection config properties file with default one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4464) Fuse Platform does not get added to runtime detection after installation

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-4464?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-4464. ----------------------------- The answer to my question is here: JBDS-4464. Also closing this in favor of the aforementioned issue. > Fuse Platform does not get added to runtime detection after installation > ------------------------------------------------------------------------ > > Key: JBDS-4464 > URL: https://issues.jboss.org/browse/JBDS-4464 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 11.0.0.AM2 > > > Both Fuse Platform installations on JBoss EAP and Apache Karaf are not getting added to runtime detection. This is happening because runtime detection configuration is configured to happen after devstudio installation finished. Then Fuse Tools installation is taking place and overwrites runtime detection config properties file with default one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4469) Some servers are only added to runtime detection when fuse tooling is installed/not installed

by Jan Richter (JIRA)

Jan Richter created JBDS-4469: --------------------------------- Summary: Some servers are only added to runtime detection when fuse tooling is installed/not installed Key: JBDS-4469 URL: https://issues.jboss.org/browse/JBDS-4469 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 11.0.0.AM2 Reporter: Jan Richter Assignee: Denis Golovin Namely: - EAP is only added if fuse tooling is not installed - Fuse runtimes are only added if fuse tooling is installed -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24661) Incorporates console output into cdk3 integration tests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24661?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24661: ---------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Incorporates console output into cdk3 integration tests > ------------------------------------------------------- > > Key: JBIDE-24661 > URL: https://issues.jboss.org/browse/JBIDE-24661 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk > Fix For: 4.5.x > > > After https://issues.jboss.org/browse/JBIDE-24587 is merged, existing cdk intergration tests should incorporates new feature. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24702) Refactor usage of AbstractWait.sleep in CDK3ServerEditorTest with async saving of editor

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24702?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24702: ---------------------------------- Fix Version/s: 4.5.x (was: 4.5.0.Final) > Refactor usage of AbstractWait.sleep in CDK3ServerEditorTest with async saving of editor > ---------------------------------------------------------------------------------------- > > Key: JBIDE-24702 > URL: https://issues.jboss.org/browse/JBIDE-24702 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24704) Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24704?page=com.atlassian.jira.plugi... ] Ondrej Dockal updated JBIDE-24704: ---------------------------------- Sprint: devex #135 July 2017 > Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing > -------------------------------------------------------------------------------- > > Key: JBIDE-24704 > URL: https://issues.jboss.org/browse/JBIDE-24704 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: integration-tests, qa > Affects Versions: 4.5.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Labels: cdk, central-ci, jenkins > Fix For: 4.5.0.Final > > > It was found out, that cdk3 can be started in CLI on win7-x64 slave with pre-installed virtualbox in central ci env. and so, I am planning to: > * prepare machine as a new snapshot in openstack images section, tune possible bugs > * create new template/label in jenkins for this machine > * create a job in jenkins that would test cdk3 start up on this slave -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24704) Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing

by Ondrej Dockal (JIRA)

Ondrej Dockal created JBIDE-24704: ------------------------------------- Summary: Add Win7 with pre-installed virtualbox as template into jenkins for cdk3 testing Key: JBIDE-24704 URL: https://issues.jboss.org/browse/JBIDE-24704 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: integration-tests, qa Affects Versions: 4.5.0.AM2 Reporter: Ondrej Dockal Assignee: Ondrej Dockal Fix For: 4.5.0.Final It was found out, that cdk3 can be started in CLI on win7-x64 slave with pre-installed virtualbox in central ci env. and so, I am planning to: * prepare machine as a new snapshot in openstack images section, tune possible bugs * create new template/label in jenkins for this machine * create a job in jenkins that would test cdk3 start up on this slave -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24703) Remove Integration Stack related target platform from Fuse Tooling codebase

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24703?page=com.atlassian.jira.plugi... ] Aurélien Pupier updated JBIDE-24703: ------------------------------------ Summary: Remove Integration Stack related target platform from Fuse Tooling codebase (was: Remove Integration Stack related target platform from Fuse Tooling) > Remove Integration Stack related target platform from Fuse Tooling codebase > --------------------------------------------------------------------------- > > Key: JBIDE-24703 > URL: https://issues.jboss.org/browse/JBIDE-24703 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 4.5.0.Final > > > The Tp ued when being in Integration Stack is still available in the source code. it is using SNAPSHOT values and is blocking the correct build of FINAL-SNAPSHOT version -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24689) For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools]

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24689?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24689: ----------------------------------------- this step is currently failing {code} mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT {code} {quote}[INFO] ------------------------------------------------------------------------ [INFO] Building JBoss Fuse Tooling 10.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.6.1:clean (default-clean) @ project --- [INFO] Deleting C:\git\fuseide\target [INFO] [INFO] --- build-helper-maven-plugin:1.7:regex-property (regex-property) @ project --- [INFO] Setting property 'skipTestsOrITests' to ''. [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) @ project --- [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (warn-no-snapshots-AMx) @ project --- [ERROR] Found property jbtis.version = 4.5.0.AM1d-SNAPSHOT [INFO] [INFO] --- maven-enforcer-plugin:1.4.1:enforce (enforce-no-snapshots-Final) @ project --- [ERROR] Found property jbtis.version = 4.5.0.AM1d-SNAPSHOT [WARNING] Rule 0: org.jboss.tools.releng.NoSnapshotsAllowed failed with message: When buildAlias (Final) matches /Final|GA/, cannot include SNAPSHOT dependencies.{quote} it is due to the fact that the old target platform has been left in the code. I cannot find a JIRA issue related to fix that. The move to the new TP has been done with this JIRA: [JBIDE-24246] I created a new JIRA task for it [JBIDE-24703] > For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-24689 > URL: https://issues.jboss.org/browse/JBIDE-24689 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Aurélien Pupier > Priority: Blocker > Labels: task > Fix For: 4.5.0.Final > > > For JBIDE 4.5.0.Final [fusetools]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for fusetools task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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 July 2017