June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14764) Update VJET in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-14764: ------------------------------- Assignee: Nick Boldt (was: Victor Rubezhny) > Update VJET in Central > ---------------------- > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, target-platform > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Fix For: 4.1.0.Beta2 > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14764) Update VJET in Central

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14764: ---------------------------------- Summary: Update VJET in Central Key: JBIDE-14764 URL: https://issues.jboss.org/browse/JBIDE-14764 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, target-platform Affects Versions: 4.1.0.Beta1 Reporter: Victor Rubezhny Assignee: Victor Rubezhny Fix For: 4.1.0.Beta1 We should provide an ability to install VJET v.0.10 through Central The latest stable VJET Update Site: [http://download.eclipse.org/vjet/updates-0.10] - v.0.10.0, Released The following dependencies (in addition to what we already have in TP) are to be satisfied in order to run VJet: {code:title=Orbit bundles for VJET} <unit id="org.apache.xml.serializer" version="2.7.1.v201005080400"/> <unit id="org.apache.xml.resolver" version="1.2.0.v201005080400"/> <unit id="org.apache.batik.css" version="1.7.0.v201011041433"/> <unit id="org.apache.batik.css.source" version="1.7.0.v201011041433"/> <unit id="org.apache.batik.dom" version="1.7.0.v201011041433"/> <unit id="org.apache.batik.dom.source" version="1.7.0.v201011041433"/> <unit id="org.apache.batik.util" version="1.7.0.v201011041433"/> <unit id="org.apache.batik.util.source" version="1.7.0.v201011041433"/> <unit id="org.apache.xerces" version="2.9.0.v201101211617"/> <unit id="org.ccil.cowan.tagsoup" version="1.2.0.v201202211000"/> <unit id="org.w3c.css.sac" version="1.3.1.v200903091627"/> <unit id="org.w3c.css.sac.source" version="1.3.1.v200903091627"/> <unit id="org.w3c.dom.svg" version="1.1.0.v201011041433"/> <unit id="org.w3c.dom.svg.source" version="1.1.0.v201011041433"/> <unit id="javax.xml" version="1.3.4.v201005080400"/> <unit id="org.apache.commons.collections" version="3.2.0.v2013030210310"/> <unit id="org.apache.commons.io" version="2.0.1.v201105210651"/> {code} -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2636) rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio"

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2636?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2636: ----------------------------- Fix Version/s: 7.0.0.Beta2 (was: 7.0.0.Beta1) > rebrand devstudio.jboss.com pages with "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio" > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-2636 > URL: https://issues.jboss.org/browse/JBDS-2636 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 7.0.0.Beta2 > > > New requirement from MW management. Rebrand the pages to state "Red Hat JBoss Developer Studio" instead of "JBoss Developer Studio". > Similar changes should happen on jboss.org/tools pages which mention JBDS as well. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12810) Add more tests to OpenShift tooling

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12810?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-12810. -------------------------------------- Fix Version/s: 4.1.0.Beta2 (was: 4.1.x) Resolution: Done resolving since there's not much interest in general purpose issue. need to open specific issues when specific cases arise. > Add more tests to OpenShift tooling > ----------------------------------- > > Key: JBIDE-12810 > URL: https://issues.jboss.org/browse/JBIDE-12810 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Beta2 > > > There are far too few tests for OpenShift tooling (main things that are fairly good covered are the openshift-java-client, the egit utils and a few import related components. Beside this there are no tests at all): > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.0_trunk... > we should add more tests. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14763: --------------------------------------------- [~fbricon] and [~rob.stryker] can you look at this ? My concern is what happens for our download runtimes functionallity in server adapter, central maven archetype runtime selection etc. when the layered products/project start showing up ? having gatein show up as AS7 download seems wrong/bad. > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14763: ---------------------------------------- Component/s: central server > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, server > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14763?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14763: ---------------------------------------- Assignee: Rob Stryker > GateIn 3.6 goes to stacks.yaml > ------------------------------ > > Key: JBIDE-14763 > URL: https://issues.jboss.org/browse/JBIDE-14763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Reporter: Peter Palaga > Assignee: Rob Stryker > Priority: Blocker > > It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14763) GateIn 3.6 goes to stacks.yaml

by Peter Palaga (JIRA)

Peter Palaga created JBIDE-14763: ------------------------------------ Summary: GateIn 3.6 goes to stacks.yaml Key: JBIDE-14763 URL: https://issues.jboss.org/browse/JBIDE-14763 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Peter Palaga Priority: Blocker It should be checked which consequences will it have for JBoss Tools if GateIn 3.6 appears in {{stacks.yaml}}. Filling this as recommended by [~maxandersen]. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14564) Runtime detection prompt shown on every IDE start

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14564?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14564: --------------------------------------- The PR was applied to the master, but wasn't to beta1. > Runtime detection prompt shown on every IDE start > ------------------------------------------------- > > Key: JBIDE-14564 > URL: https://issues.jboss.org/browse/JBIDE-14564 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Fix For: 4.1.0.Beta2 > > Attachments: Server_RTDwindow.png > > > I installed JBDS with the universal installer (Beta1-v20130519-0601-B206) and did not set up runtime detection. > On every IDE start, the runtime detection prompt is now displayed (screen capture attached). Not sure if this is a bug or desired behavior. > If it is desired behavior, I can understand showing the prompt on the first start after an install to encourage users to use this function. But showing it on every start is annoying, particularly if a user does not want to use runtime detection. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14762) cannot install jboss tools into Kepler JavaEE

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14762?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-14762: ------------------------------------- Max, can you describe the steps to reproduce this issue? > cannot install jboss tools into Kepler JavaEE > --------------------------------------------- > > Key: JBIDE-14762 > URL: https://issues.jboss.org/browse/JBIDE-14762 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, maven > Affects Versions: 4.1.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.1.0.Beta2 > > > something is amiss in our TP seems like Kepler includes a version incompatible with our includes. > http://screencast.com/t/tyy5O8bQj > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Maven Project Examples 1.5.0.Beta1-v20130523-1233-B39 (org.jboss.tools.maven.project.examples.feature.feature.group 1.5.0.Beta1-v20130523-1233-B39) > Software currently installed: Maven Integration for WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp.feature.feature.group 0.15.3.20120830-0850) > Only one of the following can be installed at once: > This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 1.0.0.20130507-1357 (org.maven.ide.eclipse.wtp 1.0.0.20130507-1357) > Maven Integration for Eclipse WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp 0.15.3.20120830-0850) > This version of m2e-wtp cannot be installed on top of the already installed m2eclipse-wtp. Uninstall the previous version of m2eclipse-wtp and try the install again. 1.0.0.20130528-1157 (org.maven.ide.eclipse.wtp 1.0.0.20130528-1157) > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130507-1357 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130507-1357) > To: bundle org.maven.ide.eclipse.wtp [1.0.0.20130507-1357] > Cannot satisfy dependency: > From: m2e-wtp - Maven Integration for WTP (Incubation) 1.0.0.20130528-1157 (org.eclipse.m2e.wtp.feature.feature.group 1.0.0.20130528-1157) > To: bundle org.maven.ide.eclipse.wtp [1.0.0.20130528-1157] > Cannot satisfy dependency: > From: JBoss Maven Project Examples 1.5.0.Beta1-v20130523-1233-B39 (org.jboss.tools.maven.project.examples.feature.feature.group 1.5.0.Beta1-v20130523-1233-B39) > To: org.eclipse.m2e.wtp.feature.feature.group 0.16.0 > Cannot satisfy dependency: > From: Maven Integration for WTP 0.15.3.20120830-0850 (org.maven.ide.eclipse.wtp.feature.feature.group 0.15.3.20120830-0850) > To: org.maven.ide.eclipse.wtp [0.15.3.20120830-0850] -- 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, 10 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 June 2013