March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13729) Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13729?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13729: ------------------------------------------------- Lili Nader <lnader(a)redhat.com> made a comment on [bug 918501|https://bugzilla.redhat.com/show_bug.cgi?id=918501] https://github.com/openshift/origin-server/pull/1566 > Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges) > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13729 > URL: https://issues.jboss.org/browse/JBIDE-13729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: scaledeap.png > > > This is a watcher issue that keeps track of the progress in the OpenShift bugzilla: > HAProxy cartridge not displayed in OpenShift Explorer even it is already embedded during the process of creating scaled application. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13729) Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13729?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13729: ------------------------------------------------- Lili Nader <lnader(a)redhat.com> changed the Status of [bug 918501|https://bugzilla.redhat.com/show_bug.cgi?id=918501] from NEW to ON_QA > Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges) > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13729 > URL: https://issues.jboss.org/browse/JBIDE-13729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: scaledeap.png > > > This is a watcher issue that keeps track of the progress in the OpenShift bugzilla: > HAProxy cartridge not displayed in OpenShift Explorer even it is already embedded during the process of creating scaled application. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13729) Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13729?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13729: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 918501|https://bugzilla.redhat.com/show_bug.cgi?id=918501] What matters to JBDS is not the ability to get removed or not, it's the type: embedded/standalone. What breaks JBDS is when standalone cartridges get reported. If HAProxy (which is afaik an embedded cartridge) cannot be removed, then this doesn't hurt JBDS as long as the REST service errors on removal. What breaks JBDS is if standalone cartridges get reported where it only expects embeddded cartridges. > Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges) > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13729 > URL: https://issues.jboss.org/browse/JBIDE-13729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: scaledeap.png > > > This is a watcher issue that keeps track of the progress in the OpenShift bugzilla: > HAProxy cartridge not displayed in OpenShift Explorer even it is already embedded during the process of creating scaled application. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13729) Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13729?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13729: ------------------------------------------------- Lili Nader <lnader(a)redhat.com> made a comment on [bug 918501|https://bugzilla.redhat.com/show_bug.cgi?id=918501] As part of bug https://bugzilla.redhat.com/show_bug.cgi?id=911322, I put in a fix so that in the version 1.0 of the API returns only embedded cartridges. Now this bug is saying that it is not showing the haproxy cartridge. Please clarify. > Error trying to embed HAProxy into scaled application: HAProxy not listed in embedded cartridges (OpenShift Explorer, Add/Remove embedded cartridges) > ----------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13729 > URL: https://issues.jboss.org/browse/JBIDE-13729 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.x > > Attachments: scaledeap.png > > > This is a watcher issue that keeps track of the progress in the OpenShift bugzilla: > HAProxy cartridge not displayed in OpenShift Explorer even it is already embedded during the process of creating scaled application. -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13671 at 3/6/13 1:40 PM: ------------------------------------------------------------ One proposal that might solve the question of "was this built locally" or "was this built in Jenkins" and ensure that locally built always has a newer timestamp than that in Jenkins CI: a) profile for Jenkins needs to be updated to use "-CI" instead of "-B$\{BUILD_NUMBER\}" b) profile for Jenkins uses jgit timestamp provider c) default profile omits the "-CI" and "-Bxxxx" suffix, as it does today d) default profile uses the default timestamp provider, as it does today Therefore the change proposed should now ONLY be made to the existing jenkins profile, and PR https://github.com/jbosstools/jbosstools-build/pull/72 should be rejected. New PR: https://github.com/jbosstools/jbosstools-build/pull/73 was (Author: nickboldt): One proposal that might solve the question of "was this built locally" or "was this built in Jenkins" and ensure that locally built always has a newer timestamp than that in Jenkins CI: a) profile for Jenkins needs to be updated to use "-CI" instead of "-B${BUILD_NUMBER}" b) profile for Jenkins uses jgit timestamp provider c) default profile omits the "-CI" and "-Bxxxx" suffix, as it does today d) default profile uses the default timestamp provider, as it does today Therefore the change proposed should now ONLY be made to the existing jenkins profile, and PR https://github.com/jbosstools/jbosstools-build/pull/72 should be rejected. > parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13671: ------------------------------------ One proposal that might solve the question of "was this built locally" or "was this built in Jenkins" and ensure that locally built always has a newer timestamp than that in Jenkins CI: a) profile for Jenkins needs to be updated to use "-CI" instead of "-B${BUILD_NUMBER}" b) profile for Jenkins uses jgit timestamp provider c) default profile omits the "-CI" and "-Bxxxx" suffix, as it does today d) default profile uses the default timestamp provider, as it does today Therefore the change proposed should now ONLY be made to the existing jenkins profile, and PR https://github.com/jbosstools/jbosstools-build/pull/72 should be rejected. > parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13737) Provide Restart for Application as the Web-UI does

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13737?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13737: ------------------------------------------ Restarting an application is an important enhancement we need to provide. Once you add markers (like the debug marker) you have to restart the application. > Provide Restart for Application as the Web-UI does > -------------------------------------------------- > > Key: JBIDE-13737 > URL: https://issues.jboss.org/browse/JBIDE-13737 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > We need at least a way to restart an application as the web-UI does: > !application-restart.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13737) Provide Restart for Application as the Web-UI does

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13737: ---------------------------------------- Summary: Provide Restart for Application as the Web-UI does Key: JBIDE-13737 URL: https://issues.jboss.org/browse/JBIDE-13737 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 We need at least a way to restart an application as the web-UI does: !application-restart.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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13682) Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-13682: -------------------------------------- Assignee: Victor Rubezhny (was: Alexey Kazakov) > Investigate use of Atlassian 3.0.7 or 3.2 in JBoss Central > ---------------------------------------------------------- > > Key: JBIDE-13682 > URL: https://issues.jboss.org/browse/JBIDE-13682 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Fix For: 4.1.0.Alpha2 > > > Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno. > There is also a 3.2 available: > https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo... > available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/ -- 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

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13732) Firebug doesn't run from Btrowsersimm for some web page

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13732?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13732: ----------------------------------- Component/s: Visual Page Editor core (was: jsp/jsf/xml/html source editing) > Firebug doesn't run from Btrowsersimm for some web page > ------------------------------------------------------- > > Key: JBIDE-13732 > URL: https://issues.jboss.org/browse/JBIDE-13732 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 4.1.0.Alpha1 > Environment: Linux and JBDS Alpha1-v20130306-0101-B124 > Reporter: Vlado Pakan > Assignee: Yahor Radtsevich > Priority: Critical > Fix For: 4.1.0.Beta1 > > > 1. Open Browsersimm > 2. Open url www.google.com > 3. Run Firebug Lite from context menu of BrowserSimm > ASSERT: Debug window is opened and working > 4. Open url www.sme.sk > 5. Run Firebug Lite from context menu of BrowserSimm > ERROR: No debug window is opened -- 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

13 years, 1 month

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 March 2013