November 2012 - jbosstools-issues

[JBoss JIRA] (JBDS-2378) Generating project from custom user site uses wrong maven archetype

by Juraj Húska (JIRA)

Juraj Húska created JBDS-2378: --------------------------------- Summary: Generating project from custom user site uses wrong maven archetype Key: JBDS-2378 URL: https://issues.jboss.org/browse/JBDS-2378 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: maven Affects Versions: 6.0.0.Beta1 Environment: JBDS 6.0.0.Beta1c Reporter: Juraj Húska The problem is that when I am generating richfaces project from custom project example site, wrong archetype version is used. The archetype with that version is however downloaded into my local maven repository while generating that project (however not used). Please see the steps to reproduce for info how I get this issue. -- 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, 5 months

4
6
0 / 0

[JBoss JIRA] (JBIDE-12926) CLONE - missing empty folders after migration of hibernatetools (svn) to jbosstools-hibernate (git)

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-12926: ---------------------------------- Summary: CLONE - missing empty folders after migration of hibernatetools (svn) to jbosstools-hibernate (git) Key: JBIDE-12926 URL: https://issues.jboss.org/browse/JBIDE-12926 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.0.0.CR1 Reporter: Nick Boldt Assignee: Max Rydahl Andersen Priority: Blocker Fix For: 4.0.0.CR1 Attachments: missing-empty-folders-after-esb-migrated-to-github.png See attached image comparing old SVN tunk sources on the left w/ new Github sources on the right: !missing-empty-folders-after-hibernatetools-migrated-to-hibernate.png! Note that differences in pom.xml are due to refactoring I did - not a problem. -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] (JBIDE-13120) Improve codegeneration test for multiple hibernate versions

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13120: ------------------------------------ Summary: Improve codegeneration test for multiple hibernate versions Key: JBIDE-13120 URL: https://issues.jboss.org/browse/JBIDE-13120 Project: Tools (JBoss Tools) Issue Type: Task Components: QA Affects Versions: 4.0.0.CR1 Reporter: Jiri Peterka Assignee: Jiri Peterka Fix For: 4.0.0.CR1 -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] (JBIDE-13108) Update Forge Embedded Runtime to 1.1.2.Final

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-13108: ---------------------------------- Summary: Update Forge Embedded Runtime to 1.1.2.Final Key: JBIDE-13108 URL: https://issues.jboss.org/browse/JBIDE-13108 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.0.0.Beta1 Reporter: Pavol Srna Assignee: Koen Aers Priority: Blocker Fix For: 4.0.0.CR1 Please update forge runtime to current 1.1.2.Final version. It will allow us to install jboss-as-7 plugin which is currently broken in forge 1.1.1.Final. https://issues.jboss.org/browse/FORGEPLUGINS-41 -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] (JBDS-2405) Inconsistency in how Mylyn is referred to in Central and Extras Site

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-2405: ---------------------------------- Summary: Inconsistency in how Mylyn is referred to in Central and Extras Site Key: JBDS-2405 URL: https://issues.jboss.org/browse/JBDS-2405 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: central Affects Versions: 6.0.0.CR1 Environment: Version: 6.0.0.CR1 Build id: CR1-v20121125-1229-B133 Build date: 20121125-1229 http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.0.CR1.extras/ Reporter: Len DiMaggio Assignee: Snjezana Peco Fix For: 6.1.x Attachments: mylyn_selected_Screenshot.png, mylyn_supported_Screenshot.png See the attached screenshots. Central refers to Mylyn as "supported", the extras site refers to it as "selected." -- 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, 5 months

1
1
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, 5 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-12462) set VERBOSE on doesn´t work on JBoss Tools

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12462?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-12462. ------------------------------ Verified in jbdevstudio 6.0.0-CR1a build. > set VERBOSE on doesn´t work on JBoss Tools > ------------------------------------------ > > Key: JBIDE-12462 > URL: https://issues.jboss.org/browse/JBIDE-12462 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.0.0.Beta1 > > > Using {code} set VERBOSE on {code} has no effect when running Forge under Forge Console (No stacktraces are shown when an error is found) -- 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, 5 months

1
0
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, 5 months

3
7
0 / 0

[JBoss JIRA] (JBDS-2396) Cannot update from JBDS 6.0.0.CR1 to CR1a

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBDS-2396: ------------------------------------ Summary: Cannot update from JBDS 6.0.0.CR1 to CR1a Key: JBDS-2396 URL: https://issues.jboss.org/browse/JBDS-2396 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 6.0.0.CR1 Reporter: Stefan Bunciak Priority: Blocker Fix For: 6.0.0.CR1 using JBoss Developer Studio Version: 6.0.0.CR1 Build id: CR1-v20121118-2035-B111 Build date: 20121118-2035 update site: http://www.qa.jboss.com/binaries/RHDS/updates/development/6.0.0.CR1a.core/ {code} Your original request has been modified. "Apache Deltaspike Tools" is already installed, so an update will be performed instead. "Context and Dependency Injection Tools" is already installed, so an update will be performed instead. "Forge Tools" is already installed, so an update will be performed instead. "FreeMarker IDE" is already installed, so an update will be performed instead. "Hibernate Tools" is already installed, so an update will be performed instead. "JBoss Archives Tools" is already installed, so an update will be performed instead. "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead. "JBoss JAX-RS Tools" is already installed, so an update will be performed instead. "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead. "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead. "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead. "JBoss Maven Integration" is already installed, so an update will be performed instead. "JBoss Maven JAX-RS Configurator" is already installed, so an update will be performed instead. "JBoss Maven JPA Configurator" is already installed, so an update will be performed instead. "JBoss Maven JSF Configurator" is already installed, so an update will be performed instead. "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead. "JBoss Maven Project Examples" is already installed, so an update will be performed instead. "JBoss Maven Seam Integration" is already installed, so an update will be performed instead. "JBoss OpenShift Tools" is already installed, so an update will be performed instead. "JBoss Portlet" is already installed, so an update will be performed instead. "JBoss Runtime Detection Core" is already installed, so an update will be performed instead. "JBoss Runtime Seam Detector" is already installed, so an update will be performed instead. "JBoss Tools EGit Integration (Experimental)" is already installed, so an update will be performed instead. "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead. "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead. "JBoss Tools JSF" is already installed, so an update will be performed instead. "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead. "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead. "JBoss Tools RichFaces" is already installed, so an update will be performed instead. "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead. "JBoss WebServices Tools" is already installed, so an update will be performed instead. "JBossAS Tools" is already installed, so an update will be performed instead. "JMX Console" is already installed, so an update will be performed instead. "Maven Integration (Selected)" is already installed, so an update will be performed instead. "Maven Integration for Eclipse JDT APT" is already present because other installed software requires it. It will be added to the installed software list. "Maven Profiles Management" is already installed, so an update will be performed instead. "Project Examples" is already installed, so an update will be performed instead. "Seam 3 Tools" is already installed, so an update will be performed instead. "Seam Tools" is already installed, so an update will be performed instead. "Struts Tools" is already installed, so an update will be performed instead. Cannot complete the install because of a conflicting dependency. Software being installed: org.jboss.tools.struts.feature.source.feature.group 3.4.0.CR1-v20121125-0708-B50 Software currently installed: JBoss Developer Studio (Branded Product) 6.0.0.CR1-v20121118-2035-B111 (com.jboss.jbds.all 6.0.0.CR1-v20121118-2035-B111) Only one of the following can be installed at once: Struts Verification 3.4.0.CR1-v20121125-0708-B50 (org.jboss.tools.struts.verification 3.4.0.CR1-v20121125-0708-B50) Struts Verification 3.4.0.CR1-v20121118-0434-B35 (org.jboss.tools.struts.verification 3.4.0.CR1-v20121118-0434-B35) Cannot satisfy dependency: From: JBoss Developer Studio (Branded Product) 6.0.0.CR1-v20121118-2035-B111 (com.jboss.jbds.all 6.0.0.CR1-v20121118-2035-B111) To: com.jboss.jbds.product.feature.feature.group [6.0.0.CR1-v20121118-2035-B111] Cannot satisfy dependency: From: JBoss Developer Studio (Core Features) 6.0.0.CR1-v20121118-2035-B111 (com.jboss.jbds.product.feature.feature.group 6.0.0.CR1-v20121118-2035-B111) To: org.jboss.tools.struts.feature.feature.group [3.4.0.CR1-v20121118-0434-B35] Cannot satisfy dependency: From: Struts Tools 3.4.0.CR1-v20121118-0434-B35 (org.jboss.tools.struts.feature.feature.group 3.4.0.CR1-v20121118-0434-B35) To: org.jboss.tools.struts.verification [3.4.0.CR1-v20121118-0434-B35] Cannot satisfy dependency: From: Struts Tools 3.4.0.CR1-v20121125-0708-B50 (org.jboss.tools.struts.feature.feature.group 3.4.0.CR1-v20121125-0708-B50) To: org.jboss.tools.struts.verification [3.4.0.CR1-v20121125-0708-B50] Cannot satisfy dependency: From: org.jboss.tools.struts.feature.source.feature.group 3.4.0.CR1-v20121125-0708-B50 To: org.jboss.tools.struts.feature.feature.group [3.4.0.CR1-v20121125-0708-B50] {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, 5 months

3
8
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, 5 months

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 November 2012