August 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12326) After Eclipse updates, constantly get error dialogs and some features (refactor) fail

by George Policello (JIRA)

George Policello created JBIDE-12326: ---------------------------------------- Summary: After Eclipse updates, constantly get error dialogs and some features (refactor) fail Key: JBIDE-12326 URL: https://issues.jboss.org/browse/JBIDE-12326 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.Final Environment: Eclipse (Indigo, update 2012/07/12 and earlier), Java 6.1 (update check 2012/07/06), JBoss (update, part of Eclipse update), Windows 7 (update ~2012/07/10), Dell Studio. All worked fine until update errors occurred on JBoss components. Reporter: George Policello Assignee: Alexey Kazakov After all recent updates, constantly throws error dialogs. Some Eclipse features no longer work, refactor. Error logs always are headed by JBoss issue. Eclipse folks looked at error logs and said JBoss is likely cause. I have quite a few JBoss ZIP files created by JBoss Eclipse menu "Help => Report Problem" I want to attach. There does not seem to be any way to describe a "recreate action" as it is just a recurring system failure. Tried "Create Issue" quite a few times and "Create" click or "Alt-Shift-s" all failed. -- 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

11 years, 6 months

4
9
0 / 0

[JBoss JIRA] (JBIDE-12208) clean up update sites on download.jboss.org

by Nick Boldt (JIRA)

11 years, 6 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-11217) Forge: present verbose mode functionality in Forge JBT/JBDS Tooling

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-11217: ---------------------------------- Summary: Forge: present verbose mode functionality in Forge JBT/JBDS Tooling Key: JBIDE-11217 URL: https://issues.jboss.org/browse/JBIDE-11217 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Pavol Srna Assignee: Koen Aers Fix For: 3.3.0.CR1 You can run the command: 'set VERBOSE true' in forge running from standard command line. This is not possible/working in JBDS/JBT Forge console. It would be very helpful to have some preference option where you can turn ON/OFF the verbose mode and probably log all the exceptions to the Eclipse Error log. What do you think? -- 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

11 years, 6 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-12094) Add the JBoss Nexus catalog to the maven core plugin

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12094: ----------------------------------- Summary: Add the JBoss Nexus catalog to the maven core plugin Key: JBIDE-12094 URL: https://issues.jboss.org/browse/JBIDE-12094 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.3.0.CR1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.1 We should add the JBoss catalog to mitigate the loss of functionality caused by JBIDE-12066 : even though jars won't be found anymore, archetypes will still be usable. We need to add the following to our plugin.xml: {code:xml} <extension point="org.eclipse.m2e.core.archetypeCatalogs"> <remote url="https://repository.jboss.org/nexus/content/repositories/releases/archetyp..." description="JBoss Releases Catalog"/> </extension> {code} But that depends on the catalog being available. It's currently broken : JBBUILD-718 -- 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

11 years, 6 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-12475) Split JBoss Tools into several functional groups of components for migration to Github

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12475: ---------------------------------- Summary: Split JBoss Tools into several functional groups of components for migration to Github Key: JBIDE-12475 URL: https://issues.jboss.org/browse/JBIDE-12475 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.0.0.M1 As part of the planned migration to git [0] it's been suggested that we combine some of the existing components into larger groups [1] so that it's more manageable in terms of checking out sources and tagging/branching [2]. Because 25 is a large number, and 1 is a small number, and we need some happy compromise. Here's my proposal for how to divide the JBT 4.0 sources into 7 github repos (chunks), comprising 4 tiers of dependency. This is akin to the +0, +1, +2, +3 labels assigned to projects within the annual Eclipse release trains [3], used to define delivery times based on dependencies between projects. == TIER 0: no upstream JBoss.org chunks == Base = tests + common + usage == TIER 1: 1 upstream chunk, Base == AppServer = openshift + as + archives + jmx -> depends on Base Hibernate/Birt/Freemarker = hibernate + birt + freemarker -> depends on Base Visual Editing = vpe + xulrunner + gwt + struts + jsf + jst + cdi -> depends on Base Web Services = WS + Forge -> Depends on Base == TIER 2: 4 upstream chunks == Seam/Runtime = Seam + Runtime -> depends on Hib + Vis + AppServer + Base == TIER 3: 5 upstream chunks == Central/Examples/Maven/Portlet = central + examples + maven + portlet -> depends on Seam/Runtime + Hib + Vis + AppServer + Base I'm not thrilled with the names of the chunks, as something like "Central/Examples/Maven/Portlet" doesn't exactly roll off the tongue. If you have better names for the chunks, please suggest them. But regardless of name, I think the above separation of concerns, and the implied build sequence workflow makes a lot of sense. [0] http://tinyurl.com/git-migration-plan [1] http://ether-man.rhcloud.com/p/build.next [2] http://ether-man.rhcloud.com/p/jbosstools-2012-08-23 [3] http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#Milestones_and_Rel... - "These delivery times are based on the dependencies between projects. They are labeled +0, +1, +2, and +3, with +0 coming first (the Platform) and +3 coming last (EPP). Projects themselves decide if they are +0, +1, +2, or +3." -- 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

11 years, 6 months

6
100
0 / 0

[JBoss JIRA] (JBIDE-12127) Provide aggregated report for tests

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-12127: -------------------------------------- Summary: Provide aggregated report for tests Key: JBIDE-12127 URL: https://issues.jboss.org/browse/JBIDE-12127 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Mickael Istria Fix For: 3.4.x As requested per JBIDE-11784 , we need to see an aggregated view of the test trend for all components, in order to have a view of how quality evolves. This can be achieved by a Dashboard chart on Jenkins, but it has some limitations. See https://issues.jenkins-ci.org/browse/JENKINS-14045 . -- 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

11 years, 6 months

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-2720) Need 64-bit windows support

by Samuel Mendenhall (JIRA)

Need 64-bit windows support --------------------------- Key: JBIDE-2720 URL: https://jira.jboss.org/jira/browse/JBIDE-2720 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Samuel Mendenhall Fix For: 3.0.0.alpha, 2.1.2, 2.1.1, 2.1.0.GA JBoss Tools is not usable on a 64-bit Windows machine. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

15
54
0 / 0

[JBoss JIRA] (JBIDE-10537) Support Code Coverage with Jacoco

by Mickael Istria (Created) (JIRA)

Support Code Coverage with Jacoco --------------------------------- Key: JBIDE-10537 URL: https://issues.jboss.org/browse/JBIDE-10537 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Affects Versions: 3.3.0.M4 Environment: any Reporter: Mickael Istria Assignee: Nick Boldt Jacoco Maven plugin allows to add very seamlessly code coverage while executing tests. Build should leverage this and get rid of additional build steps configured for emma plugin. -- 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

11 years, 6 months

11
39
0 / 0

[JBoss JIRA] Created: (JBIDE-7870) Several Properties view does not work synchronously

by Vitali Yemialyanchyk (JIRA)

Several Properties view does not work synchronously --------------------------------------------------- Key: JBIDE-7870 URL: https://issues.jboss.org/browse/JBIDE-7870 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml source editing Affects Versions: 3.2.0.Beta2 Reporter: Vitali Yemialyanchyk Assignee: Alexey Kazakov Priority: Minor Properties View -> View Menu -> New Properties View; in both should be one content for one selected item if no pin - but this is not true, or better to say - it is not always a true - try to open one more properties view for "Web Page Editor", switch between VPE and WPE... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 6 months

6
8
0 / 0

[JBoss JIRA] (JBIDE-11592) SIGSEGV when tried JBT 3.3.0.Beta2 on Juno

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11592: ------------------------------------ Summary: SIGSEGV when tried JBT 3.3.0.Beta2 on Juno Key: JBIDE-11592 URL: https://issues.jboss.org/browse/JBIDE-11592 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta2 Environment: JBT 3.3.0.Beta2, Eclipse Juno 4.2.M6 JEE Package, Linux 64, JDK 1.6_31 Reporter: Jiri Peterka Assignee: Nick Boldt Priority: Blocker Fix For: 3.3.0.Beta3 SIGSEGV when tried JBT 3.3.0.Beta2 (withon Juno JEE M6). It's not supported configuration so feel free to lower priority and postpone Fix version. # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f779563f830, pid=2460, tid=140152133580544 # # JRE version: 6.0_31-b04 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.6-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libmozjs.so+0x73830] unsigned+0xc20 # # An error report file with more information is saved as: # /home/jpeterka/ide/test/jbttrunk-juno/eclipse/hs_err_pid2460.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # -- 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

11 years, 6 months

8
26
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2012