March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-13335. -------------------------------- Resolution: Done Done but not YET verified in JBT 4.0.1.CR1a, only in JBDS 6.0.1.CR > remove Juno SR1+ performance fix from Central > ---------------------------------------------- > > Key: JBIDE-13335 > URL: https://issues.jboss.org/browse/JBIDE-13335 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.0.1.Final > > Attachments: JBIDE13335.patch.JBDS6.0.1.txt > > > For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars. > Need to therefore, for JBT 4.0.1 and JBDS 6.0.1: > a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places) > b) remove the connector from discovery plugins' plugin.xml (2 files) -- 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-13382) 'Server Behaviour' title in Server Editor should use American spelling

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13382?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13382. --------------------------------- Verified in JBDS 7.0.0.Alpha1c. > 'Server Behaviour' title in Server Editor should use American spelling > ---------------------------------------------------------------------- > > Key: JBIDE-13382 > URL: https://issues.jboss.org/browse/JBIDE-13382 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Reporter: Michelle Murray > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.1.0.Alpha1 > > > One of the section titles on the Overview page of the Server Editor is misspelled: Server Behavi*our* should be Server Behavi*or* > American spellings should be followed, as you have with Application Reload Behavi*or* on the same page. -- 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-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13603: ------------------------------- Labels: respin-a (was: ) > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Labels: respin-a > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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-13335) remove Juno SR1+ performance fix from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13335: ------------------------------- Labels: respin-a (was: ) > remove Juno SR1+ performance fix from Central > ---------------------------------------------- > > Key: JBIDE-13335 > URL: https://issues.jboss.org/browse/JBIDE-13335 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Denis Golovin > Labels: respin-a > Fix For: 4.0.1.Final > > Attachments: JBIDE13335.patch.JBDS6.0.1.txt > > > For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars. > Need to therefore, for JBT 4.0.1 and JBDS 6.0.1: > a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places) > b) remove the connector from discovery plugins' plugin.xml (2 files) -- 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-13371) test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13371?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13371. --------------------------------- Closing this as there are no extra failures in the testsuite in master currently other than these two: JBIDE-13750 > test failure in org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) : The XPath File has not been created. Xpaths will be lost on workspace restart > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13371 > URL: https://issues.jboss.org/browse/JBIDE-13371 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 3.3.2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_5.0.indigo/job/jbosstools-3.3_stable_branch.component--as/lastCompletedBuild/testReport/org.jboss.ide.eclipse.as.test.server/XPathModelTest/testEap60Mock/} > Regression > org.jboss.ide.eclipse.as.test.server.XPathModelTest.testEap60Mock (from org.jboss.ide.eclipse.as.test.ASTestSuite) > Failing for the past 1 build (Since Unstable#152 ) > Took 30 ms. > add description > Error Message > The XPath File has not been created. Xpaths will be lost on workspace restart > Stacktrace > junit.framework.AssertionFailedError: The XPath File has not been created. Xpaths will be lost on workspace restart > at junit.framework.Assert.fail(Assert.java:47) > at org.jboss.ide.eclipse.as.test.server.XPathModelTest.serverTestImpl(XPathModelTest.java:31) > at org.jboss.ide.eclipse.as.test.server.SimpleServerImplTest.testEap60Mock(SimpleServerImplTest.java:61){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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13441) Changing vm for runtime from default to jdk1.7, then back to default, fails

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13441?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13441. --------------------------------- This works correctly in JBDS 7.0.0.Alpha1c. Closing. > Changing vm for runtime from default to jdk1.7, then back to default, fails > --------------------------------------------------------------------------- > > Key: JBIDE-13441 > URL: https://issues.jboss.org/browse/JBIDE-13441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha1 > > > 0) In workspace, ensure workspace has 1.7 jre, then add a 1.6 jre > 1) Create a web app with simple servlet, doGet() has logic: System.out.println(System.getProperty("java.version")); > 2) Create server and runtime, keep vm at default for exec env > 3) Start server, deploy web app, verify 1.6 > 4) Shutdown server > 5) Switch runtime to use 1.7 jre, finish, then save server editor > 6) Start server, verify webapp prints to console 1.7 > 7) Stop server > 8) Edit runtime to use default for 1.6 again > 9) finish wizard, save server editor > 10) start server, run webapp, verify text says 1.6 > FAIL > Step 10 fails, the 1.7 server is still chosen. This is a bug in the UI which is not properly clearing the vm flag, and is only setting it when one is chosen. -- 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-13408) investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13408?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13408: ---------------------------------------- Guys, can you please review the proposed process for releasing target-platfroms suggested here: https://github.com/jbosstools/jbosstools-target-platforms/wiki before we go ahead with using non-SNAPSHOT TP? > investigate using mvn deploy of non-SNAPSHOT target platforms to JBoss Public Nexus > ----------------------------------------------------------------------------------- > > Key: JBIDE-13408 > URL: https://issues.jboss.org/browse/JBIDE-13408 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha2 > > > investigate using `mvn deploy` from Jenkins CI job of non-SNAPSHOT target platforms to JBoss Public Nexus so that we can have *final* versions rather than ongoing snapshots. > Last time I attempted to deploy something without a -SNAPSHOT suffix in its version, I got this error: > {quote} > {code:title=https://github.com/nickboldt/jbosstools-target-platforms/tree/d14d79e71d62b77f73d19d96e6bb1a03db90d5f1} > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy (default-deploy) on project multiple: Failed to deploy artifacts: Could not transfer artifact org.jboss.tools.target-platforms.jbdevstudio:multiple:pom:4.21.3.Final from/to jboss-releases-repository (https://repository.jboss.org/nexus/content/repositories/releases/): Failed to transfer file: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos.... Return code is: 502, ReasonPhrase:Proxy Error. -> [Help 1] > {code} > {quote} -- 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) BrowserSim: Firebug doesn't run for some web pages

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13732?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13732: ------------------------------------- Summary: BrowserSim: Firebug doesn't run for some web pages (was: Firebug doesn't run from Btrowsersimm for some web page) > BrowserSim: Firebug doesn't run for some web pages > -------------------------------------------------- > > 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

[JBoss JIRA] (JBIDE-13747) [cleanup] expand org.jboss.ide.eclipse.as.ui.DeployMethodUI extension pt, allow for browse behavior, explore behavior, and launch tabs

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13747?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13747. --------------------------------- Resolution: Done pushed into master for a2. As this was a task, it primarily involves only internal implementation details. Nothing to note here for user. Nothing for release notes. > [cleanup] expand org.jboss.ide.eclipse.as.ui.DeployMethodUI extension pt, allow for browse behavior, explore behavior, and launch tabs > -------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13747 > URL: https://issues.jboss.org/browse/JBIDE-13747 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > current browse behavior is embedded inside a specific internal class and the rse plugin reaches inside. This is a bad dynamic. > Several differnet pieces of code were similarly hard-coded in this fashion. The list is: > 1) browse behavior for each server mode > 2) explore behavior for each server mode > 3) launch tabs for each server mode / server type combination -- 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-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- actually, according to dmlloyd: ${foo,bar:default value} would work. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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