September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-11601) outdated DOCTYPE used in Hibernate Mapping file

by Simon Lo (JIRA)

Simon Lo created JBIDE-11601: -------------------------------- Summary: outdated DOCTYPE used in Hibernate Mapping file Key: JBIDE-11601 URL: https://issues.jboss.org/browse/JBIDE-11601 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Windows 7, Eclipse Indigo SR2, JBoss Tools 3.3 beta Reporter: Simon Lo Priority: Optional The generated hbm file using http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd as dtd location, which was giving a warning log when using along with Hibernate 3.6. However, I can't find any options that I could choose which DTD location to use, or anywhere I can modify this template. -- 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, 1 month

6
21
0 / 0

[JBoss JIRA] Created: (JBIDE-9106) Adding SQLServerMetaDataDialect to support auto discovery of Identity and guid strategy

by Derk Dukker (JIRA)

Adding SQLServerMetaDataDialect to support auto discovery of Identity and guid strategy --------------------------------------------------------------------------------------- Key: JBIDE-9106 URL: https://issues.jboss.org/browse/JBIDE-9106 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Hibernate Affects Versions: 3.3.0.M1, LATER Reporter: Derk Dukker Assignee: Max Rydahl Andersen Reverse engineering the MS SQLServer database with hibernate tools does not auto discover the identity fields and uniqueidentifier (guid) fields. So when generated the entities the only annotation you will see is @id. I created a new meta data dialect to discover identity and guid fields. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

7
19
0 / 0

[JBoss JIRA] (JBIDE-12489) Maven dependencies not exported in exploded war

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-12489: ---------------------------------- Summary: Maven dependencies not exported in exploded war Key: JBIDE-12489 URL: https://issues.jboss.org/browse/JBIDE-12489 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.0.0.M1 Environment: Eclipse Juno / Nightly build 4.0.0.v20120824-1014-H5503-M1 Reporter: Cody Lerum After updating to todays nightly maven is showing the following error Classpath entry org.eclipse.m2e.MAVEN2_CLASSPATH_CONTAINER will not be exported or published. Runtime ClassNotFoundExceptions may result. And none of my expected dependencies are showing up in the built exploded war. This was working on the previous days nightly. -- 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, 1 month

4
6
0 / 0

[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

13 years, 1 month

4
9
0 / 0

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

by Nick Boldt (JIRA)

13 years, 1 month

4
13
0 / 0

[JBoss JIRA] (JBIDE-12742) make code coverage reports easier to find & aggregate them into a simpler all-in-one view?

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12742: ---------------------------------- Summary: make code coverage reports easier to find & aggregate them into a simpler all-in-one view? Key: JBIDE-12742 URL: https://issues.jboss.org/browse/JBIDE-12742 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, testing Affects Versions: 4.0.0.Alpha2 Reporter: Nick Boldt Assignee: Mickael Istria Could we... * archive artifacts in the jobs, eg., to make it easier to find this page [1] ? * ensure the coverage report stuff is published to download.jboss.org, eg., in here [2] ? * collect all the coverage reports from the various jobs [2] into a single place [3] ? [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... [2] http://download.jboss.org/jbosstools/builds/staging/jbosstools-4.0_trunk.... [3] http://download.jboss.org/jbosstools/builds/staging/_coverage-reports_/ -- 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

4
19
0 / 0

[JBoss JIRA] (JBDS-2280) Investigate use of SpringIDE 3 in JBoss Central & JBDS Extras sites

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2280: -------------------------------- Summary: Investigate use of SpringIDE 3 in JBoss Central & JBDS Extras sites Key: JBDS-2280 URL: https://issues.jboss.org/browse/JBDS-2280 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, central Affects Versions: 6.0.0.Alpha1 Reporter: Nick Boldt Assignee: Len DiMaggio Fix For: 6.0.0.Beta1 Spring IDE update site (http://dist.springsource.com/release/TOOLS/update/e4.2) contains this version: Spring IDE Core (required) 3.0.0.201208090952-RELEASE Bits are mirrored here: http://download.jboss.org/jbosstools/updates/requirements/springide/3.0.0... -- 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

5
27
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

13 years, 1 month

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

13 years, 1 month

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

13 years, 1 month

6
100
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