July 2010 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6463) JBT tests should (re)use shared requirements dir OUTSIDE hudson workspace

by Nick Boldt (JIRA)

JBT tests should (re)use shared requirements dir OUTSIDE hudson workspace ------------------------------------------------------------------------- Key: JBIDE-6463 URL: https://jira.jboss.org/browse/JBIDE-6463 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.2.0.M1 Reporter: Nick Boldt Assignee: Denis Golovin Per request of JBQA-3313, we did the following to start using /home/hudson/static_build_env/jbds/requirements as the dir into which requirements are downloaded:  <if> <available file="/home/hudson/static_build_env/jbds" type="dir" /> <then> <var name="requirement.build.root" unset="true" /> <property name="requirement.build.root" value="/home/hudson/static_build_env/jbds/requirements" /> <mkdir dir="${requirement.build.root}" /> </then> </if> <echo level="debug">requirement.build.root = ${requirement.build.root}</echo> https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.... Can the new harness in http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/ use the same shared dir? Currently it writes into the part of the workspace which contains SVN sources, which means it will most likely be overwritten every time SVN is refreshed (and have to be downloaded for every slave on which we build). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-6625) [Designer] Model Editor "Table Editor" tab unclear what to do

by Brian Fitzpatrick (JIRA)

[Designer] Model Editor "Table Editor" tab unclear what to do -------------------------------------------------------------- Key: JBIDE-6625 URL: https://jira.jboss.org/browse/JBIDE-6625 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: teiid Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Barry LaFond Fix For: 3.2.x In the Model Editor, with a new model the Table Editor tab shows as a completely gray, solid control. It might be good to add a label or tooltip that suggests that the user needs to add a table to the Package Diagram? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6356) Hibernate mapping file editor sometime shows old content

by Jiri Peterka (JIRA)

Hibernate mapping file editor sometime shows old content -------------------------------------------------------- Key: JBIDE-6356 URL: https://jira.jboss.org/browse/JBIDE-6356 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.1.1 Reporter: Jiri Peterka Fix For: 3.2.next Sometimes old hbm.xml file is shown in Hibernate editor after class modification and hbm.xml regenerating (even after close all, and refresh). I don't know if it's Eclipse problem or some Hibernate Tools problem but I've noticed that several times. After restart content is ok. It's question of editor content refresh, hbm.xml generation is ok and file system has proper file content. Steps: 1. Create some POJOs 2. Create hbml.xml mapping file 3. Open hbm.xml 4. Update created POJOs 5. Delete hbml.mxl files 6. Generate hbm.xml again 7. Open generated hbm.xml -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6343) Create a "sanity check plugin/feature" tool for running on integration builds

by Max Rydahl Andersen (JIRA)

Create a "sanity check plugin/feature" tool for running on integration builds ----------------------------------------------------------------------------- Key: JBIDE-6343 URL: https://jira.jboss.org/browse/JBIDE-6343 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Max Rydahl Andersen Fix For: LATER I keep seeing the following antipatterns or oversights happening in our codebase, most of them I believe we could mechanically check for. No duplicate names in .project since it makes it impossible to import into Eclipse bin folders should be svn:ignored and not be committed (causes problems when doing svn synchronization and all the .class files are showing up and some even commits it) things in svn:ignore should be committed (either someone overrode svn:ignore or the svn:ignore were added later) if pom.xml file exists target should be svn:ignored too. Execution environment should be specified in manifest.mf's -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
5
0 / 0

[JBoss JIRA] Created: (JBDS-1241) 3rd party updatesite

by Max Rydahl Andersen (JIRA)

3rd party updatesite -------------------- Key: JBDS-1241 URL: https://jira.jboss.org/browse/JBDS-1241 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Reporter: Max Rydahl Andersen -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-1420) Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc.

by Alexander Chabatar (JIRA)

Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc. ----------------------------------------------------------------------------------------------------------- Key: JBIDE-1420 URL: http://jira.jboss.com/jira/browse/JBIDE-1420 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: LATER Reporter: Alexander Chabatar Assigned To: Alexander Chabatar Priority: Minor Fix For: LATER 1) add Test Connection button - should be helpful. 2) Finish button is always enabled. For example if Database dialect is selected but no driver class, no URL, user. Validation might show a warning. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

5
47
0 / 0

[JBoss JIRA] Created: (JBDS-1230) JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu

by Jim Tyrrell (JIRA)

JBoss Developer 3.0 Installing in a a newly installed RHEL 5.4 does not show up in the applications menu -------------------------------------------------------------------------------------------------------- Key: JBDS-1230 URL: https://jira.jboss.org/browse/JBDS-1230 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Affects Versions: 3.0.0.GA Environment: RHEL 5.4 with Sun JDK 5.4 Reporter: Jim Tyrrell When going through the installer on a clean RHEL 5.4 system, the Programming Tools Listing under the Applications in the main menu bar does not show up until a reboot. Once it has been installed at least once, this does not seem to be a problem -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6588) BPEL deployment to ODE running in Tomcat

by Gary Brown (JIRA)

BPEL deployment to ODE running in Tomcat ---------------------------------------- Key: JBIDE-6588 URL: https://jira.jboss.org/browse/JBIDE-6588 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: bpel Reporter: Gary Brown Currently the BPEL plugins in JBoss Tools support deployment of a BPEL process and ODE deployment descriptor to RiftSaw (ODE running in JBossAS). It may be useful to allow users to also deploy the same processes to ODE running inside Tomcat. This would enable existing ODE/Tomcat users to benefit from a supported version of the BPEL editor, and easily switch to using RiftSaw if they wanted. The Eclipse BPEL project already provides a deploy for ODE in Tomcat. The only change that would be required is to change the bpel-deploy.xml to deploy.xml during deployment, as ODE does not recognize bpel-deploy.xml. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

6
18
0 / 0

[JBoss JIRA] Created: (JBIDE-5829) Update BPEL deployment plug-ins with JBoss-specific IDs

by Brian Fitzpatrick (JIRA)

Update BPEL deployment plug-ins with JBoss-specific IDs ------------------------------------------------------- Key: JBIDE-5829 URL: https://jira.jboss.org/jira/browse/JBIDE-5829 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Reporter: Brian Fitzpatrick Assignee: Max Rydahl Andersen Priority: Critical Fix For: 3.1.0.CR2 While reviewing the state of the BPEL editor, it came up that the deployment plug-ins (the o.e.bpel.apache.ode.* plugins), though they included JBoss Riftsaw-specific code, were still the same plug-in IDs & project names as were in the BPEL project at Eclipse.org. These need to change so we don't run into conflicts with the Eclipse project. -- 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

15 years, 4 months

4
22
0 / 0

[JBoss JIRA] Created: (JBIDE-6450) Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester

by Brian Fitzpatrick (JIRA)

Classloader incompatibilities between javax.xml.soap (1.2) and javax.xml.soap (1.3) when running WS Tester ---------------------------------------------------------------------------------------------------------- Key: JBIDE-6450 URL: https://jira.jboss.org/browse/JBIDE-6450 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.2.0.M1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Priority: Critical Fix For: 3.2.0.M1 Finally got to the heart of the java.lang.VerifyError issue I've been running into with the WS Tester. javax.xml.soap (1.2) is an old-school plug-in jar wrapper that takes saaj.jar and exposes it in Eclipse. javax.xml.soap (1.3) is a new-school OSGI-compatible wrapper that builds the individual saaj classes and wraps them to expose them in Eclipse. As Nick said in a recent IRC chat - ".jar!/org/whatever/*.class is better than .jar!foo.jar". But in my case, it causes the lovely java.lang.VerifyError when I try to use a utility class that takes advantage of classes from javax.xml.soap. After doing some digging, it turns out the javax.xml.soap (1.3) plug-in is coming from the Atlassian update site for the latest & greatest version of their JIRA/Mylyn plug-ins. Without Atlassian JIRA connectors installed, it runs just fine. So this presents an issue... If we're meant to certify against Atlassian JIRA connectors, this is going to come up again. So how do we work around it? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 4 months

4
29
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 July 2010