March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10080) Embedded property should be highligted on Open Mapping action.

by Dmitry Geraskov (Created) (JIRA)

Embedded property should be highligted on Open Mapping action. -------------------------------------------------------------- Key: JBIDE-10080 URL: https://issues.jboss.org/browse/JBIDE-10080 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.M4 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.Final This work for core hbm.xml mapping(composite-id), but because of a different syntax doesn't work for orm.xml mapping (embedded-id and embedded). See test result for MappingTestsJpa JUnit and jpa.springframework.samples.petclinic package: Highlighted region for property id is empty. (package jpa.springframework.samples.petclinic) The property is a property of class TestId. Would be good to improve the message also. -- 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, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6178) releng update site, feature naming conventions

by Darryl Miles (JIRA)

releng update site, feature naming conventions ---------------------------------------------- Key: JBIDE-6178 URL: https://jira.jboss.org/jira/browse/JBIDE-6178 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: updatesite Affects Versions: 3.1.0.GA Reporter: Darryl Miles Priority: Minor Please consider the impact of users using the "All Update Site" view when installing JBoss plugins. Some rules to consider: 1) If JBoss creates a new top-level group (which consists entirely of JBoss features) then that top-level name should begin with the word "JBoss". 2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name of the outside vendor, but ensure your features underneath are prefixed with the word "JBoss"." In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following the above rules, but "Maven Support" is not (and also "Data Services" top level group is not). The "All in one JBoss" top-level group doesn't really need to follow this convention, since the top level group clearly indicates it is from JBoss and entirely contains JBoss features and those features are a duplicated entrypoint for installation (i.e. each feature also exist somewhere else in the "features to install" tree view). The ambigiouty is over such names as "Maven Support" and "Data Services" in the context of the "all update site view" from the drop-down filter at the top of the page. -- 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

13 years, 9 months

10
26
0 / 0

[JBoss JIRA] (JBIDE-9851) Get JBossTools added to wtp 3.3's list of server adapters :: Indigo

by Nick Boldt (Created) (JIRA)

Get JBossTools added to wtp 3.3's list of server adapters :: Indigo ------------------------------------------------------------------- Key: JBIDE-9851 URL: https://issues.jboss.org/browse/JBIDE-9851 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: UpStream Affects Versions: 3.2.0.Final Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.2.Final, 3.3.0.M4 It seems what happens is you must make use of the org.eclipse.wst.server.discovery plugin. This plugin has a file (discovery.xml) which has "sites", and those sites (such as http://public.dhe.ibm.com/software/websphere/wasce/updates/) seem to be an eclipse update site. The entry point for this wizard is in the New Runtime wizard. At the top is a hyperlink that reads "Download other adapters" (or something similar). It then queries these sites, and allows you to select one of those available. It seems the objects are then downloaded as IInstallableUnit's, which is in the org.eclipse.equinox.p2.metadata package. I kinda lose track of it here, but, I suspect that after this it is downloaded as an actual eclipse bundle and added into the eclipse installation. But I guess I could trace through further Changes to our site would require adding the category and adding it to certain features in our site.xml. -- 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, 9 months

6
6
0 / 0

[JBoss JIRA] (JBDS-1979) Add error handling for p2Director errors in universal installer

by Denis Golovin (Created) (JIRA)

Add error handling for p2Director errors in universal installer --------------------------------------------------------------- Key: JBDS-1979 URL: https://issues.jboss.org/browse/JBDS-1979 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 5.0.0.M5 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 5.0.0.Beta1 -- 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, 9 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-10221) Resorce leak problems in JBossTools

by Vitali Yemialyanchyk (Created) (JIRA)

Resorce leak problems in JBossTools ----------------------------------- Key: JBIDE-10221 URL: https://issues.jboss.org/browse/JBIDE-10221 Project: Tools (JBoss Tools) Issue Type: Bug Components: Cleanup Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Max Rydahl Andersen I've find several places in several components, which I've check - I'll create separate issues for this. There is a chance what there are leak in other components, which I did not inspect. -- 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, 9 months

8
11
0 / 0

[JBoss JIRA] Created: (JBDS-1577) using JBDS as updatesite on eclipse works, but causes outofmemory because of name change

by Max Rydahl Andersen (JIRA)

using JBDS as updatesite on eclipse works, but causes outofmemory because of name change ---------------------------------------------------------------------------------------- Key: JBDS-1577 URL: https://issues.jboss.org/browse/JBDS-1577 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: updatesite Affects Versions: 4.0.0.GA Reporter: Max Rydahl Andersen Not sure if this qualifies as a bug or a feature request but I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great until you restart (possible on the second restart) since then it suddenly has zero extra memory allocated. It only started working properly when using the jbdevstudio.app; thus my assumption is that eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere to be found (except inside jbdevstudio.app) Would be good if we could handle this situation more gracefully since the shortcuts users uses still points to eclipse thus they will see it as JBDS running out of memory since when launching it says JBDS. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

5
22
0 / 0

[JBoss JIRA] (JBIDE-10535) 12 tests skipped in org.jboss.tools.ws.jaxrs.core

by Nick Boldt (Created) (JIRA)

12 tests skipped in org.jboss.tools.ws.jaxrs.core ------------------------------------------------- Key: JBIDE-10535 URL: https://issues.jboss.org/browse/JBIDE-10535 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick Fix For: 3.3.0.Beta1 After switching to newer target platform (JBIDE-10289), 12 tests are being skipped: https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo... {code} shoudCreateEndpointWhenAddingSubresourceLocatorMethodInSubresource shouldAddResourceFieldWhenAddingFieldAnnotatedWithQueryParam shouldDoNothingMethodWhenAddingAnotherAnnotationOnParameter shouldDoNothingMethodWhenChangingAnotherAnnotationOnParameter shouldDoNothingMethodWhenRemovingAnotherAnnotationOnParameter shouldRemoveResourceWhenRemovingBinaryLib shouldUpdateResourceMethodWhenAddingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenAddingThrowsException shouldUpdateResourceMethodWhenChangingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenChangingThrowsException shouldUpdateResourceMethodWhenRemovingMatrixParamAnnotationOnParameter shouldUpdateResourceMethodWhenRemovingThrowsException {code} -- 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, 9 months

6
8
0 / 0

[JBoss JIRA] (JBDS-2019) Remove or Update http://www.redhat.com/developer_studio/Getting_Started_Single/

by Burr Sutter (JIRA)

Burr Sutter created JBDS-2019: --------------------------------- Summary: Remove or Update http://www.redhat.com/developer_studio/Getting_Started_Single/ Key: JBDS-2019 URL: https://issues.jboss.org/browse/JBDS-2019 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Burr Sutter This content shows up via Google "JBoss Getting Started" - and it is very dated -- 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, 9 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-11124) Removing project via forge is not working properly

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11124: ----------------------------------------- Summary: Removing project via forge is not working properly Key: JBIDE-11124 URL: https://issues.jboss.org/browse/JBIDE-11124 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 3.3.0.Beta1 Environment: Eclipse Java EE v.3.7.2, JBoss Tools 3.3.0 Beta1b Reporter: Jaroslav Jankovič Assignee: Koen Aers Priority: Critical Fix For: 3.3.0.Beta1 There are actually two issues when trying to remove the project. The first issue is exception thrown in Error Log. The second is the fact the project is not completely removed - the project folder remains and contains empty bin folder. -- 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, 9 months

5
27
0 / 0

by Pavol Srna (JIRA)

Pavol Srna created JBDS-2045: -------------------------------- Summary: 2011 copyright year should be replaced by 2012 Key: JBDS-2045 URL: https://issues.jboss.org/browse/JBDS-2045 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build Affects Versions: 5.0.0.Beta1 Reporter: Pavol Srna Assignee: Nick Boldt Fix For: 5.0.0.Beta1 Attachments: screenshot.png Copyright (c) 2004-2011 Red Hat, Inc., contributors and others. All rights reserved. The Copyright year should be 2004 - 2012. -- 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, 9 months

3
5
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 2012