March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16519) Environment Variables wizard: use the updated openshift-java-client API for manipulating env vars

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16519?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16519: ------------------------------------- Fix Version/s: 4.2.x > Environment Variables wizard: use the updated openshift-java-client API for manipulating env vars > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-16519 > URL: https://issues.jboss.org/browse/JBIDE-16519 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Fix For: 4.2.x > > > In OSJC-53 we're changing the API for env vars in the openshift-java-client. Once this change is done we have to make sure the Eclipse tooling is using the latest API -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16509) Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16509?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16509: ------------------------------------- Fix Version/s: 4.2.0.CR1 > Application wizard: Embedded cartridges should get checked when I select "Enable Scaling" AFTER I selected them > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16509 > URL: https://issues.jboss.org/browse/JBIDE-16509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Priority: Minor > Labels: application_wizard > Fix For: 4.2.0.CR1 > > > We currently only check the validity of embedded cartridges when you check/uncheck them. Since there are cartridges which are not valid in scaled apps (ex. phpmyadmin), we should also check the embedded cartridges when one hits the "Enable Scaling" checkbox. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16714) OpenShift Cartridge: Embed same cartridge with different version should show warning

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16714?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16714: ------------------------------------- Fix Version/s: 4.2.x > OpenShift Cartridge: Embed same cartridge with different version should show warning > ------------------------------------------------------------------------------------ > > Key: JBIDE-16714 > URL: https://issues.jboss.org/browse/JBIDE-16714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.2.x > > > Nowadays, when on OpenShift Online are available multiple cartridges differentiated only by version (e.g. PostgreSQL 8.4 and 9.2) there should be some kind of warning about embedding both (what could happen accidentally or by ignorance...). > How it works now? If user choose 2 cartridges of the same type, then just the first one is embedded and while trying to embed second cartridge user get error that application has already embedded that kind of cartridge (that they cannot coexist). > I suggest to have similar dialog as in embedding e.g. Jenkins cartridge to application without having Jenkins Application (server) etc. -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2943) Add m2eclipse-egit to JBDS installer

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-2943?page=com.atlassian.jira.plugin.... ] Rastislav Wagner closed JBDS-2943. ---------------------------------- m2e-egit is in JBDS 8.0.0.Beta1a by default, i was also able to install it to JBT 4.2.0.Beta1a. Git autoshare works without any issues. > Add m2eclipse-egit to JBDS installer > ------------------------------------ > > Key: JBDS-2943 > URL: https://issues.jboss.org/browse/JBDS-2943 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer, maven > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Denis Golovin > Priority: Critical > Fix For: 8.0.0.Beta1 > > > Since [m2eclipse-egit|https://github.com/tesla/m2eclipse-egit] (nor any other m2e SCM connector) is installed by default with JBDS, the Maven SCM import wizard is useless (see JBIDE-16574) > I propose we add m2eclipse-egit to the JBDS installer, as we already have m2e and egit in there, so the use case described in JBIDE-16574 can work OOTB. > Other, less ideal solution would be to add m2eclipse-egit to JBoss Central, but that would add little value over the existing m2e discovery mechanism. > Latest m2eclipse-egit build is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-egit/0.14.0/N/0.1... -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2919) Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2919?page=com.atlassian.jira.plugin.... ] Xavier Coulon updated JBDS-2919: -------------------------------- Fix Version/s: 8.0.0.Beta2 > Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8 > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2919 > URL: https://issues.jboss.org/browse/JBDS-2919 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: server > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 8.0.0.Beta2 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16580) jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16580?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-16580: ---------------------------------- Fix Version/s: 4.2.0.Beta1 Affects Version/s: 4.1.1.Final > jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16580 > URL: https://issues.jboss.org/browse/JBIDE-16580 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16800) Add usage tracking for server creation

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16800?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-16800. ------------------------------ Verified in JBDS 8.0.0.Beta1 > Add usage tracking for server creation > -------------------------------------- > > Key: JBIDE-16800 > URL: https://issues.jboss.org/browse/JBIDE-16800 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, usage > Reporter: Alexey Kazakov > Assignee: Max Rydahl Andersen > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > Attachments: action.png, category.png, label.png, preferences.png > > > Usage tracks "Perform Finish" (value=1) and "Perform Cancel" (value=0) events for New JBoss Servers. > This event type in Preferences: > !preferences.png! > A few examples in google analytics: > !category.png! > !action.png! > !label.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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Beta" stuff

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16375: --------------------------------------------- We will *NEVER* have supported and never non-supported stuff of the same content on same site. That will mess up p2 install experience anyway. What is important is that we consider what happens when the user removes "allow early access" - should/could we remove the earlyaccess sites so he wont get it via normal p2 usage "by accident" > Allow to extend Central extensions catalog with "Beta" stuff > ------------------------------------------------------------ > > Key: JBIDE-16375 > URL: https://issues.jboss.org/browse/JBIDE-16375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, discovery > Reporter: Mickael Istria > Fix For: 4.2.0.Beta2 > > > In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries. > Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels. > The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...). -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Beta" stuff

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-16375: --------------------------------------------- and I do not understand why you think installing just by id sounds very weak - that is *exactly* what we want here. The connector id looks up in the relevant catalog and find the updatesite + list of IU's to install from. All the code that referes to ID's should not care wether he gets a specific version - that is for the user to decide wether he wants the supported or the early access content. > Allow to extend Central extensions catalog with "Beta" stuff > ------------------------------------------------------------ > > Key: JBIDE-16375 > URL: https://issues.jboss.org/browse/JBIDE-16375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, discovery > Reporter: Mickael Istria > Fix For: 4.2.0.Beta2 > > > In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries. > Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels. > The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...). -- 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

12 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16592: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/216, https://github.com/jbosstools/jbosstools-central/pull/228 (was: https://github.com/jbosstools/jbosstools-central/pull/216) The second PR ( https://github.com/jbosstools/jbosstools-central/pull/228 ) includes a commit allowing update of a connector. > Allow to update/remove software installed from Central > ------------------------------------------------------ > > Key: JBIDE-16592 > URL: https://issues.jboss.org/browse/JBIDE-16592 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta2 > > Attachments: JBIDE-16592-remove.jpeg, JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg > > > Central software page should allow user to update or uninstall some modules. -- 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

12 years

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 2014