September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12037) set up Jenkins for 3.4 stream builds - tweak poms, add new jobs, replace old trunk jobs

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12037: ---------------------------------- Summary: set up Jenkins for 3.4 stream builds - tweak poms, add new jobs, replace old trunk jobs Key: JBIDE-12037 URL: https://issues.jboss.org/browse/JBIDE-12037 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.4.x Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.4.x We will need to move 3.3_trunk jobs to 3.4_trunk, and add 3.4_stable_branch jobs too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
4
0 / 0

[JBoss JIRA] (JBDS-2002) could JBDS product include a range of feature versions?

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2002: -------------------------------- Summary: could JBDS product include a range of feature versions? Key: JBDS-2002 URL: https://issues.jboss.org/browse/JBDS-2002 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, installer, updatesite Affects Versions: 5.0.0.Beta1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.Beta1 Idea would be to allow the pieces under jbds.all to be updated w/o having to update the top-level feature. For example, instead of the feature including o.j.t.foo_3.3.0.vYYYYMMDDhhmm-Hxxx-Beta1, it could instead include [3.3.0,3.4.0) Might need p2.inf directions, eg: http://www.eclipse.org/forums/index.php/t/210526/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
8
0 / 0

[JBoss JIRA] (JBIDE-12448) Move ECF download and associated dialog to common area

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-12448: ----------------------------------- Summary: Move ECF download and associated dialog to common area Key: JBIDE-12448 URL: https://issues.jboss.org/browse/JBIDE-12448 Project: Tools (JBoss Tools) Issue Type: Task Components: common/jst/core, JBossAS/Servers, project-examples, runtime detection Affects Versions: 3.4.0.M1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.4.0.M1 The ability to download and expand (install) jars is a common utility that should not be at the top of a tree bundled into Project Examples. It would be better served somewhere more common and accessible by other plugins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] Created: (JBIDE-9479) Enhance custom classpath containers for additional support such as as7's modules tag

by Rob Stryker (JIRA)

Enhance custom classpath containers for additional support such as as7's modules tag ------------------------------------------------------------------------------------ Key: JBIDE-9479 URL: https://issues.jboss.org/browse/JBIDE-9479 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta2 Enhance /JBIDE-1354 to allow for additional types of filesets. 1) Add API 2) Add extension point 3) Add UI -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-12567) Change BrowserSim error message when it cannot be run on Windows with JRE 7u6/7u7

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-12567: ---------------------------------------- Summary: Change BrowserSim error message when it cannot be run on Windows with JRE 7u6/7u7 Key: JBIDE-12567 URL: https://issues.jboss.org/browse/JBIDE-12567 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Yahor Radtsevich Please see the parent issue JBIDE-12467 for full description of the problem. This bug is about the following changes witch fix this problem partially: # BrowserSim launcher should try to run BrowserSim with JDK 7 (not JRE), if it is available through the 'eclipse.vm' variable. # BrowserSim should show the following message (a more precise) if the error appears: !https://issues.jboss.org/secure/attachment/12356597/new-message-screenshot.png! *4QAs*: please ensure that: # BrowserSim shows new error message if Eclipse is run with JRE 7u6 or JRE 7u7. # BrowserSim is working properly if Eclipse is run with JDK 7u7. # BrowserSim is working if Eclipse is run with JRE 7u5 and below. Please use -vm param in eclipse.ini to run Eclipse with partial JVM. -- 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, 7 months

1
3
0 / 0

[JBoss JIRA] (JBDS-2231) restructure JBDS staging update sites so that relative paths don't break when moved to production

by Nick Boldt (JIRA)

13 years, 7 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-12564) GWT Designer missing in central

by Martin Malina (JIRA)

Martin Malina created JBIDE-12564: ------------------------------------- Summary: GWT Designer missing in central Key: JBIDE-12564 URL: https://issues.jboss.org/browse/JBIDE-12564 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, GWT Affects Versions: 4.0.0.Alpha1 Environment: JBT 4.0.0.Alpha1 B6 / JBDS 6.0.0.Alpha1 H12 Reporter: Martin Malina Assignee: Nick Boldt Fix For: 4.0.0.Alpha1 GWT Designer is not available in neither JBT nor JBDS Central. -- 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, 7 months

2
2
0 / 0

[JBoss JIRA] (JBDS-2243) JBDS 6 includes eclipse.platform 3.8 instead of 4.2

by Denis Golovin (JIRA)

Denis Golovin created JBDS-2243: ----------------------------------- Summary: JBDS 6 includes eclipse.platform 3.8 instead of 4.2 Key: JBDS-2243 URL: https://issues.jboss.org/browse/JBDS-2243 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 6.0.0.M1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 6.0.0.M1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11549) Support Juno

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11549: ------------------------------------------- Summary: Support Juno Key: JBIDE-11549 URL: https://issues.jboss.org/browse/JBIDE-11549 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Juno is coming - This year, lets see if we can stay compatible. There should be a compatibility layer so unless we use changed internal API's we should be fine. If you have a plugin that does not compile/work then we should investigate what options we got - trying to avoid having to maintain two forks! Eclipse migration tips: http://dev.eclipse.org/viewcvs/viewvc.cgi/org.eclipse.platform.doc.isv/po... (not sure that being empty can be all true) WTP help for old friends: http://wiki.eclipse.org/New_Help_for_Old_Friends_VII See JBIDE-8624 for last years Indigo move. Please link related Juno to this issue and if we find issues please outline the fix and if relevant relate eclipse bugzilla references. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

6
16
0 / 0

[JBoss JIRA] (JBIDE-12403) Cannot start a SOA-P server with JBT on eclipse Juno

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-12403: ------------------------------------ Summary: Cannot start a SOA-P server with JBT on eclipse Juno Key: JBIDE-12403 URL: https://issues.jboss.org/browse/JBIDE-12403 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.1.x Environment: RHEL6 java -version java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.3) (rhel-1.48.1.11.3.el6_2-x86_64) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode) eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0... http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ Reporter: Len DiMaggio Assignee: Rob Stryker Priority: Blocker Fix For: 3.1.2 To recreate: 1) Install eclipse Juno (eclipse-SDK-4.2RC2-linux-gtk-x86_64.tar.gz) 2) Help->Install New Software - install JBoss tools: http://download.jboss.org/jbosstools/updates/target-platform_3.4.juno.SR0... http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ 3) Create a new SOA-P 5.3 server runtime 4) Create a new SOA-P server - accept defaults for run config: "-Dprogram.name=JBossTools: JBossTools: SOA-5.3" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/redhat_svn/jbds/jbosstools/esb/tests/org.jboss.tools.esb.ui.bot.test/target/requirements/jboss-soa-p-5/jboss-as/lib/endorsed" 5) Attempt to start the server - this error is returned: JBossTools: JBossTools: SOA-5.3: invalid option -- s -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 7 months

4
13
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 September 2012