April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9819) Openshift Express: provide existing system settings

by Andre Dietisheim (JIRA)

Openshift Express: provide existing system settings --------------------------------------------------- Key: JBIDE-9819 URL: https://issues.jboss.org/browse/JBIDE-9819 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Andre Dietisheim The current jboss tooling for openshift express does not read the settings that the rhc tooling would have created. We need to close this gap. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] (JBIDE-9841) Openshift Express: rename org.jboss.ide.eclipse.as.openshift.* plugins to org.jboss.tools.openshift.*

by Andre Dietisheim (Created) (JIRA)

Openshift Express: rename org.jboss.ide.eclipse.as.openshift.* plugins to org.jboss.tools.openshift.* ----------------------------------------------------------------------------------------------------- Key: JBIDE-9841 URL: https://issues.jboss.org/browse/JBIDE-9841 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 the are currently 3 plugins for openshift: * org.jboss.ide.eclipse.as.openshift.core: REST client * org.jboss.ide.eclipse.as.openshift.test: tests for the REST client * org.jboss.ide.eclipse.as.openshift.ui: UI, mainly a wizard to create a server adapter and deal with openshift apps and domains They all shall renamed to org.jboss.tools.openshift.* -- 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

14 years

5
4
0 / 0

[JBoss JIRA] (JBDS-1884) JBDS links to old Getting Started Guide in 5.0.0

by Nick Boldt (Created) (JIRA)

JBDS links to old Getting Started Guide in 5.0.0 ------------------------------------------------ Key: JBDS-1884 URL: https://issues.jboss.org/browse/JBDS-1884 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: documentation, Welcome Affects Versions: 4.1.1.M2, 5.0.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.1.1.Final, 5.0.0.M4 Fire up JBDS. Help > Welcome > Getting Started > Gettng Started with JBoss Developer Studio Note that the content looks like http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html/Getting... rather than the 4.1 or 5.0 docs. -- 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

14 years

4
3
0 / 0

[JBoss JIRA] (JBIDE-10215) Archetypes should have cheatsheets like the project examples

by Burr Sutter (Created) (JIRA)

Archetypes should have cheatsheets like the project examples ------------------------------------------------------------ Key: JBIDE-10215 URL: https://issues.jboss.org/browse/JBIDE-10215 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Reporter: Burr Sutter Assignee: Fred Bricon Attachments: Screen Shot 2011-11-22 at 11.06.56 AM.png In a recent usability exercise, the cheatsheets were popular. Can we add them to the key archetypes that are found on File New (JBoss Perspective) and on JBoss Central? -- 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

14 years

8
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9057) Update the maven plugins' manifests to use m2e 0.13/1.0

by Fred Bricon (JIRA)

Update the maven plugins' manifests to use m2e 0.13/1.0 ------------------------------------------------------- Key: JBIDE-9057 URL: https://issues.jboss.org/browse/JBIDE-9057 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.2.1.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.2.2 We need to provide integration for m2e 0.13/1.0 in JBT 3.2.x. That means backporting the current code from trunk to the 3.2.X branch. According to Snjezana, there are no dependencies on new code/features from JBT 3.3.0, so it should be pretty straightforward. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
6
0 / 0

[JBoss JIRA] (JBIDE-10430) Regression for JBossAS 7.1: configured runtime not selectable

by Juergen Zimmermann (Created) (JIRA)

Regression for JBossAS 7.1: configured runtime not selectable ------------------------------------------------------------- Key: JBIDE-10430 URL: https://issues.jboss.org/browse/JBIDE-10430 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Juergen Zimmermann Assignee: Rob Stryker I tried to upgrade from M4 to jbosstools-3.3_stable_branch.aggregate-Update-2011-12-09_00-34-40-H51 which I downloaded from http://downloads.jboss.org/jbosstools/builds/nightly/core/3.3.indigo/2011.... However, I got 2 problems: a) The targeted runtime of an EJB project is visible, but the according JARs are *NOT* appended to the classpath resp. buildpath. b) In a utility project I cannot add the server library although the server itself is configured. I'll attach 3 screenshots: 1) 1_M4_ok shows the regular behavior when using M4. 2) 2_M5_targeted_runtime_not_in_classpath shows that the server runtime is configured, but the according jars are not part of the buildpath in an ejb project. 3) 3_M5_no_selectable_runtime_for_utility_project shows that adding a server library doesn't work because the configured server runtime is not listed. -- 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

14 years

10
12
0 / 0

[JBoss JIRA] Created: (JBDS-1821) Eclipse-cs plugin on JBDS Extras Site

by Jiri Peterka (JIRA)

Eclipse-cs plugin on JBDS Extras Site ------------------------------------- Key: JBDS-1821 URL: https://issues.jboss.org/browse/JBDS-1821 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: updatesite Affects Versions: 5.0.0.M2 Reporter: Jiri Peterka Fix For: 5.0.0.M3 Eclipse-cs one of the most popular Eclipse plugin and also widely used by JBoss guys and it would be nice to have it available on JBDS Extras site. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
9
0 / 0

[JBoss JIRA] (JBIDE-11375) Runtime detection depends on SOA runtime detectors

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11375: -------------------------------------- Summary: Runtime detection depends on SOA runtime detectors Key: JBIDE-11375 URL: https://issues.jboss.org/browse/JBIDE-11375 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime detection Reporter: Mickael Istria Assignee: Snjezana Peco Priority: Critical Runtime detection for SOA were move to the SOA components (reversed dependencies make it easier and more modular). But there are still some dependencies from runtime to soa detectors. They should be moved to a more accurate place where they don't break build. -- 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

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1695) New splashscreen for JBDS 5.0

by Jiri Peterka (JIRA)

New splashscreen for JBDS 5.0 ----------------------------- Key: JBDS-1695 URL: https://issues.jboss.org/browse/JBDS-1695 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 5.0.0.M2 Environment: JBDS 5.0.m1 h657 Reporter: Jiri Peterka Fix For: 5.0.0.M2 New splash-screen should be created or at least updated big version number from 4 to 5 on the image -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
4
0 / 0

[JBoss JIRA] Created: (JBDS-1652) Setting up JBoss Dev Studio - linking to JBoss AS7

by Matt V (JIRA)

Setting up JBoss Dev Studio - linking to JBoss AS7 -------------------------------------------------- Key: JBDS-1652 URL: https://issues.jboss.org/browse/JBDS-1652 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Environment: Win7 Pro 64bit Reporter: Matt V I am trying to setup a new JBoss Dev Studio, and have it configure JBoss 7 during the install. I had previously downloaded and unzipped JBoss AS7 into a folder. When getting to step 5 of 9, "Select Platforms and Servers", I tried both "Find" and "Add" options to add the JBoss AS 7 by specifying the folder. It was not able to "find" it or configure it. For the Configure option, I selected Application Server, but version 7 was not listed in the droplist. For the find option, it was not able to find it when specifying the AS7 folder or its AS7/bin folder. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

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