February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13456) Move palette implementation from vpe module to jst module

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13456?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-13456: ------------------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/40, https://github.com/jbosstools/jbosstools-jst/pull/32, https://github.com/jbosstools/jbosstools-javaee/pull/42, https://github.com/jbosstools/jbosstools-vpe/pull/27 (was: https://github.com/jbosstools/jbosstools-base/pull/40, https://github.com/jbosstools/jbosstools-jst/pull/32, https://github.com/jbosstools/jbosstools-javaee/pull/42) > Move palette implementation from vpe module to jst module > --------------------------------------------------------- > > Key: JBIDE-13456 > URL: https://issues.jboss.org/browse/JBIDE-13456 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.0.0.Final > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.Alpha1 > > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13363) Cannot create Server adapter for OpenShift application: Internal Error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13363?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-13363. -------------------------------------- Resolution: Cannot Reproduce Bug Tried in current master branch and cannot reproduce it. Closing as "Cannot reproduce" > Cannot create Server adapter for OpenShift application: Internal Error > ---------------------------------------------------------------------- > > Key: JBIDE-13363 > URL: https://issues.jboss.org/browse/JBIDE-13363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.1.0.Alpha1 > > Attachments: internal-error.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11558) Repositories are missing source feature titles

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11558?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11558: ---------------------------------------- Tested version 0.17.0-SNAPSHOT of Tycho which is working fine, but has a small bug regarding feature labels and feature.properties files: https://bugs.eclipse.org/bugs/show_bug.cgi?id=399722 > Repositories are missing source feature titles > ---------------------------------------------- > > Key: JBIDE-11558 > URL: https://issues.jboss.org/browse/JBIDE-11558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite, UpStream > Affects Versions: 3.3.0.Beta3 > Environment: jbt33beta3-trunk,L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: LATER > > Attachments: empty-list.png, JBIDE-11558_empty_names.png, missing-names.png, missing-titles.png > > > While updating JBT 3.3. trunk there are missing titles in dialog (see screenshot) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13459) 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13459?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13459. --------------------------------- Resolution: Done These were all small issues, mostly had to do with tests that needed to be slightly updated. One issue (the ejb3 verifier) was that a classpath container had not been updated for eap6. This is all fixed now. > 64 test failures in org.jboss.tools.as.test.core since switching to build w/ Kepler M4 target platform > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13459 > URL: https://issues.jboss.org/browse/JBIDE-13459 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--server/165/testReport/} > Failing for 6 builds (age = 6): > Test Name Duration Age > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[60] 3.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[61] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[62] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[63] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[64] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[65] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[66] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[67] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[68] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[69] 2.9 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[70] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[71] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[72] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[73] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[74] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[75] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[76] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[77] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[78] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[79] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[80] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[81] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[82] 2.3 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[83] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[84] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[85] 2.9 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[86] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[87] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[88] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[89] 2.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[60] 3.4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[61] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[62] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[63] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[64] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[65] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[66] 4.1 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[67] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[68] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[69] 4.7 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[70] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[71] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[72] 4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[73] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[74] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[75] 4.1 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[76] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[77] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[78] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[79] 4 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[80] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[81] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[82] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[83] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[84] 3.5 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[85] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[86] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[87] 3.6 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[88] 4.2 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[89] 3.7 sec 6 > >>> org.jboss.tools.as.test.core.parametized.server.XPathModelTest.serverTestImpl[0] 15 ms 6 > >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 2 ms 6 > >>> org.jboss.tools.as.test.core.launch.MockArgsTests.initializationError 1 ms 6 > >>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[11] 20 ms 6 > {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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-13316 at 2/1/13 5:15 AM: ---------------------------------------------------------------- The URL to push to staging was incorrect. Here is a suggested change: https://github.com/mickaelistria/jbosstools-target-platforms/commit/2f62a... Can someone give me a +1 to push this change, on all branches? I did successfully push some tests artifacts to staging using this URL. was (Author: mickael_istria): The URL to push to staging was incorrect. Here is a suggested change: https://github.com/mickaelistria/jbosstools-target-platforms/commit/2f62a... Can someone give me a +1 to push this change, on all branches? > Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) > ------------------------------------------------------------------------------------ > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13316) Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13316?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13316: ---------------------------------------- The URL to push to staging was incorrect. Here is a suggested change: https://github.com/mickaelistria/jbosstools-target-platforms/commit/2f62a... Can someone give me a +1 to push this change, on all branches? > Improve versioning for TP using standard Maven way (no SNAPSHOT for stable and tags) > ------------------------------------------------------------------------------------ > > Key: JBIDE-13316 > URL: https://issues.jboss.org/browse/JBIDE-13316 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Currently, we deal with explicit versions in folder names that make it confusing to understand how target-platforms are versioned. > Instead, we should use usual Maven way and Git branches: one Git branch for each version of TPs. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13462) Given a .target file materialize it with sources for use for dev

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13462?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13462: --------------------------------------------- Great if it could install into existing location too and avoid redownloading already present IU's > Given a .target file materialize it with sources for use for dev > ---------------------------------------------------------------- > > Key: JBIDE-13462 > URL: https://issues.jboss.org/browse/JBIDE-13462 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13462) Given a .target file materialize it with sources for use for dev

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13462: ------------------------------------------- Summary: Given a .target file materialize it with sources for use for dev Key: JBIDE-13462 URL: https://issues.jboss.org/browse/JBIDE-13462 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Assignee: Mickael Istria -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13460) test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project)

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13460?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13460: ------------------------------------------ Yes, we have: http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_Trunk/job/... (bad) vs. http://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_Trunk/job/... (good) [~nickboldt], they are the same, right? > test failures (2, was 7) and skipped/failed tests (-171) in Seam and JSF (JavaEE project) > ----------------------------------------------------------------------------------------- > > Key: JBIDE-13460 > URL: https://issues.jboss.org/browse/JBIDE-13460 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, Seam 2 > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Victor Kukharchuk > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk.component--javaee/275/testReport/} > Test Result > 2 failures (-7) > 2,118 tests (-171) > Took 53 min. > add description > All Failed Tests > Test Name Duration Age > >>> org.jboss.tools.seam.ui.test.ca.SeamELContentAssistTestCase.testSeamELContentAssist 36 sec 4 > >>> org.jboss.tools.jsf.text.ext.test.JSF2CSSStylesheetOpenOnTest.testJSF2CSSClassOpenOn 0.19 sec 25 > {code} > Note that we've had considerably more tests complete in the past: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 14, 2383 tests, 1 failure) > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... (Jan 10, 2383 tests, 0 failure) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10780) Gnome Shell crash when editing wsdl file

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10780?page=com.atlassian.jira.plugi... ] Andrej Podhradsky commented on JBIDE-10780: ------------------------------------------- the problem is still present > Gnome Shell crash when editing wsdl file > ---------------------------------------- > > Key: JBIDE-10780 > URL: https://issues.jboss.org/browse/JBIDE-10780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL, UpStream > Affects Versions: 3.3.0.M5, 3.3.0.Beta2-SOA > Reporter: Pavol Srna > Assignee: Andrej Podhradsky > Priority: Blocker > Labels: UX > Fix For: 4.0.x > > Attachments: bpel-screen1.png > > > This jira was found during the JBDS TestDay. Gnome Shell will crash when you edit some wsdl file. I saw this issues couple of times but cannot always reproduce. -- 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, 2 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 February 2013