July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10312) Define a minimal target platform as opposed to the recommend one we have now for builds

by Max Rydahl Andersen (Created) (JIRA)

Define a minimal target platform as opposed to the recommend one we have now for builds --------------------------------------------------------------------------------------- Key: JBIDE-10312 URL: https://issues.jboss.org/browse/JBIDE-10312 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Assignee: Nick Boldt Priority: Critical Seeing JBIDE-10311 made me realize that we actually could catch these by having a *minimal* target platform to either build or test against. The problem here is that a plugin got a plugin dependency based on the target platform - but the target platform have the latest 3.7.1 version meaning those users running 3.7.0 would have problems installing it. If we had a minimal target platform (.target) we could actually install/verify these issues against it. Not necessarily every night - but like once a week run the build or install the updatesite against the minimal target platform would reveal these dependency issues. WDYT? -- 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, 8 months

6
25
0 / 0

[JBoss JIRA] (JBIDE-12219) Seam project cannot be properly removed from server

by Martin Malina (JIRA)

11 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-146) Missing doc for Hibernate Ant Code Generation

by Jiri Peterka (JIRA)

Missing doc for Hibernate Ant Code Generation --------------------------------------------- Key: TOOLSDOC-146 URL: https://issues.jboss.org/browse/TOOLSDOC-146 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Hibernate Tools Reference Guide Affects Versions: 3.2.0.Final Reporter: Jiri Peterka Hibernate documentation should contain information related to Ant Code Generation. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-227) Create update site for JBT eclipse documentation plug-ins

by Isaac Rooskov (JIRA)

Create update site for JBT eclipse documentation plug-ins --------------------------------------------------------- Key: TOOLSDOC-227 URL: https://issues.jboss.org/browse/TOOLSDOC-227 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Create an update site for Eclipse that contains the JBT documentation as Eclipse plug-ins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-226) JBDS and JBT documentation as eclipse help

by Isaac Rooskov (JIRA)

JBDS and JBT documentation as eclipse help ------------------------------------------ Key: TOOLSDOC-226 URL: https://issues.jboss.org/browse/TOOLSDOC-226 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final This bug tracks the progress of the overall initiative of having the JBT and JBDS documentation as eclipse plug-ins and help within the respective programs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-228) Create update site for JBDS documentation plug-ins

by Isaac Rooskov (JIRA)

Create update site for JBDS documentation plug-ins -------------------------------------------------- Key: TOOLSDOC-228 URL: https://issues.jboss.org/browse/TOOLSDOC-228 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: General documentation issues Reporter: Isaac Rooskov Assignee: Isaac Rooskov Fix For: 3.3.0.Final Create an update site for JBDS that contains the documentation as plug-ins -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8803) the build system need a jre5 installed

by Feng Qian (JIRA)

the build system need a jre5 installed -------------------------------------- Key: JBIDE-8803 URL: https://issues.jboss.org/browse/JBIDE-8803 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Feng Qian Assignee: Nick Boldt Fix For: 3.2.1.M1 https://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_stable_branch.tests... There are three ws junit tests failed. Because in hudson system, no jre5 location. the error is: The JRE5 location is not right I had remebered, some time ago, in 3.2-trunk codes, https://issues.jboss.org/browse/JBIDE-6581 we need a system property for jre5, I will use the codes to get it's location: System.getProperty("jbosstools.test.jre.5", ""); I think for the 3.2 branch, we don't set the jre5 for the build, right? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

5
15
0 / 0

[JBoss JIRA] (JBIDE-10287) Add support for JAX-RS Application

by Xavier Coulon (Created) (JIRA)

Add support for JAX-RS Application ---------------------------------- Key: JBIDE-10287 URL: https://issues.jboss.org/browse/JBIDE-10287 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 3.3.0.M4 Reporter: Xavier Coulon Assignee: Xavier Coulon Add support for classes annotated with @ApplicationPath If multiple classes exist in the project, a warning should be displayed -- 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, 8 months

7
16
0 / 0

[JBoss JIRA] Created: (JBIDE-4727) Support distribution defining "New Project" dependencies

by Pete Muir (JIRA)

Support distribution defining "New Project" dependencies -------------------------------------------------------- Key: JBIDE-4727 URL: https://jira.jboss.org/jira/browse/JBIDE-4727 Project: JBoss Tools Issue Type: Feature Request Components: Seam Reporter: Pete Muir Summary: Move the responsibility for defining a "New Seam Project"'s dependencies (libraries) from JBoss Tools to the Seam distribution. Use the Maven 2 POM format to define the dependencies. Use Maven POM profiles to support different use cases for Seam projects. Reason: Currently JBoss Tools defines the project dependencies which causes issues very time Seam changes either the dependency set of a new seam project, or the layout of libraries in the distribution. Use Maven 2 POM format as it is already a well defined and understood model. Use of Maven POM profiles can further increase the flexibility and support various use cases for Seam (for example, Seam with jBPM or Seam with ICEFaces). Details: JBoss Tools should be able to read these files from the seam-gen/ directory: war.pom.xml, ear.pom.xml, ejb-jar.ear.pom.xml, war.ear.pom.xml. The war.pom.xml defines the dependencies for a WAR project; the *ear.pom.xml define dependencies for the composite modules of an EAR project. The standard Maven scopes are used: compile to indicate compile/runtime dependencies of the project, test to indicate extra dependencies required in the test project. Maven profiles are used to define additional dependency sets for new seam projects, allowing the user to optionally add extra dependencies to his project. To make this extensible, and not require JBossTools to use a well-known list of profile ids, an xml namespace will be used to add additional metadata to the profile. This allows JBossTools to identify the possible profiles: <profile> <id>drools5</id> <jbt:profile> <jbt:description>Drools 5 support (Tech Preview)</jbt:description> </jbt:profile>  </profile> <profile> <id>ICEFaces</id> <jbt:profile> <jbt:description>ICEFaces</jbt:description> </jbt:profile>  </profile> JBossTools can recognize the jbt:profile element, and use the jbt:description element to as a descriptive element to present to the user: [x] ICEFaces [x] Drools 5 support (Tech Preview) displayed in the New Seam Project Wizard. We should allow for additional information to be placed in the POM and in the future beyond dependency information. For example, additional configuration files to include in the generated project, however this is not a critical feature. We should also consider allowing JBoss Tools to retrieve the POMs from a Maven repository. This would require a user to simply specify the version of Seam they require, and have JBoss Tools download the seam-gen artifact containing all templates and resources. -- 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, 8 months

5
9
0 / 0

[JBoss JIRA] (JBIDE-11264) Wrong workspace project name when the OpenShift app name != artifact id in pom file and the project location is not default

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11264: --------------------------------------- Summary: Wrong workspace project name when the OpenShift app name != artifact id in pom file and the project location is not default Key: JBIDE-11264 URL: https://issues.jboss.org/browse/JBIDE-11264 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Priority: Critical Fix For: 3.3.0.Beta1f When I have an existing OpenShift application with name different that the artifact id in pom file and I want to import it into Eclipse workspace, I get different Eclipse project names depending on the chosen location of the newly created workspace file. # when selected default value (/home/xxx/git) the project's name is the one from pom file # when selected any other value the project's name is the OpenShift application name -- 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, 8 months

4
24
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2012