October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25138 at 10/3/17 1:51 PM: ------------------------------------------------------------- The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the /updates/rhamt/ folder. cc: [~manaRH] {code} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /updates/rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT updates/rhamt/composite/ folder so it reuses the ../ folder (/updates/rhamt/) instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder's composite site too [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... was (Author: nickboldt): The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the /updates/rhamt/ folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /updates/rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT updates/rhamt/composite/ folder so it reuses the ../ folder (/updates/rhamt/) instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder's composite site too [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... > RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25138 > URL: https://issues.jboss.org/browse/JBIDE-25138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site: > {code} > 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) > {code} > [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/com... > [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25138: ------------------------------------ Building new discovery site: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... then re-running install tests: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... >=1174 > RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25138 > URL: https://issues.jboss.org/browse/JBIDE-25138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site: > {code} > 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) > {code} > [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/com... > [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25138 at 10/3/17 1:49 PM: ------------------------------------------------------------- The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the /updates/rhamt/ folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /updates/rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT updates/rhamt/composite/ folder so it reuses the ../ folder (/updates/rhamt/) instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder's composite site too [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... was (Author: nickboldt): The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the rhamt folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT /composite/ folder so it reuses the ../ folder instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... > RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25138 > URL: https://issues.jboss.org/browse/JBIDE-25138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site: > {code} > 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) > {code} > [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/com... > [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25138: ------------------------------- Description: Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site: {code} 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) {code} [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/com... [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/ was: Realized today (thanks to failing install tests!) that the Windup 4.0.0.Beta2 update site [1] includes a ref to the JBT Oxygen Stable update site [2], which was causing an install test to fail: {code} 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) {code} > RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25138 > URL: https://issues.jboss.org/browse/JBIDE-25138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Realized today (thanks to failing install tests [0]) that the Windup 4.0.0.Beta2 update site [1] includes a reference to the JBT Oxygen Stable update site [2], which was causing an install conflict when trying to install everything in Central from the latest CI AND the Stable site: > {code} > 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) > {code} > [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... > [1] http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/com... > [2] http://download.jboss.org/jbosstools/oxygen/stable/updates/ -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25138: ------------------------------------ The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the rhamt folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT /composite/ folder so it reuses the ../ folder instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... > RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25138 > URL: https://issues.jboss.org/browse/JBIDE-25138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.5.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM3 > > > Realized today (thanks to failing install tests!) that the Windup 4.0.0.Beta2 update site [1] includes a ref to the JBT Oxygen Stable update site [2], which was causing an install test to fail: > {code} > 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) > 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25138) RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-25138: ---------------------------------- Summary: RHAMT composite site in Central should not re-add the JBT Stable site (especially in Devstudio Central!) Key: JBIDE-25138 URL: https://issues.jboss.org/browse/JBIDE-25138 Project: Tools (JBoss Tools) Issue Type: Bug Components: central-update Affects Versions: 4.5.1.AM3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.5.1.AM3 Realized today (thanks to failing install tests!) that the Windup 4.0.0.Beta2 update site [1] includes a ref to the JBT Oxygen Stable update site [2], which was causing an install test to fail: {code} 15:15:09 [p2.dir] !MESSAGE Only one of the following can be installed at once: 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 3.0.0 (org.tigris.subversion.subclipse.mylyn 3.0.0) 15:15:09 [p2.dir] !MESSAGE Subclipse Integration for Mylyn 3.x 4.2.0.1 (org.tigris.subversion.subclipse.mylyn 4.2.0.1) {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25136) Add OSIO related bundles/features to update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25136?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25136: ------------------------------------ PRs merged. Building: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=2095 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1730 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... >=1206 > Add OSIO related bundles/features to update site > ------------------------------------------------ > > Key: JBIDE-25136 > URL: https://issues.jboss.org/browse/JBIDE-25136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.5.1.AM3 > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: Openshift.io, site > Fix For: 4.5.1.AM3 > > > As OSIO integration brought new bundles/features, we should add them to the integrated update site. > The bundles are: > - org.jboss.tools.openshift.io.core > - org.jboss.tools.openshift.io.ui > - org.jboss.tools.openshift.io.test > The features are: > - org.jboss.tools.openshift.io.feature and .feature.source > - org.jboss.tools.openshift.io.test.feature and .feature.source -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4574) Improve naming of Karaf runtime created by installer

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4574?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4574: --------------------------------------- When using "Search" in Preferences -> Server -> Runtime environments, I reproduce it, it is using the pattern "<folderName>" for Server Runtime environments name > Improve naming of Karaf runtime created by installer > ---------------------------------------------------- > > Key: JBDS-4574 > URL: https://issues.jboss.org/browse/JBDS-4574 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: fusetools, installer, platform-installer, runtime-detection > Affects Versions: 11.0.1.GA > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 11.1.0.AM3 > > Attachments: image-2017-10-03-17-30-35-495.png > > > i used Development Suite installer 2.0.1 and installed Jboss Fuse Karaf Runtime from it, the name created for the Server adapter is "fuseplatformkaraf Runtime Server" which can be more user-friendly, what do you think of "Red Hat JBoss Fuse Runtime Server 6.3"? > !image-2017-10-03-17-30-35-495.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4574) Improve naming of Karaf runtime created by installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4574?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4574: ------------------------------------- It might be also [here |https://github.com/jbosstools/jbosstools-fuse/blob/master/servers/plugins/org.fusesource.ide.server.karaf.core/src/org/fusesource/ide/server/karaf/core/server/KarafServerLocator.java#L52]. Because after first start runtime detection kicks in and search for runtimes. In this case it seems just calls createServer method without name just server id and runtime instance. This might be the reason for using default template for server name. I've no dev env ready for this, so cannot say exactly what is going on, but hope that helps. > Improve naming of Karaf runtime created by installer > ---------------------------------------------------- > > Key: JBDS-4574 > URL: https://issues.jboss.org/browse/JBDS-4574 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer, platform-installer > Affects Versions: 11.0.1.GA > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 11.1.0.AM3 > > Attachments: image-2017-10-03-17-30-35-495.png > > > i used Development Suite installer 2.0.1 and installed Jboss Fuse Karaf Runtime from it, the name created for the Server adapter is "fuseplatformkaraf Runtime Server" which can be more user-friendly, what do you think of "Red Hat JBoss Fuse Runtime Server 6.3"? > !image-2017-10-03-17-30-35-495.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4574) Improve naming of Karaf runtime created by installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4574?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4574: -------------------------------- Component/s: runtime-detection > Improve naming of Karaf runtime created by installer > ---------------------------------------------------- > > Key: JBDS-4574 > URL: https://issues.jboss.org/browse/JBDS-4574 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: installer, platform-installer, runtime-detection > Affects Versions: 11.0.1.GA > Reporter: Aurélien Pupier > Assignee: Aurélien Pupier > Fix For: 11.1.0.AM3 > > Attachments: image-2017-10-03-17-30-35-495.png > > > i used Development Suite installer 2.0.1 and installed Jboss Fuse Karaf Runtime from it, the name created for the Server adapter is "fuseplatformkaraf Runtime Server" which can be more user-friendly, what do you think of "Red Hat JBoss Fuse Runtime Server 6.3"? > !image-2017-10-03-17-30-35-495.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 October 2017