July 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (TOOLSDOC-158) Separate Getting Started Guide

by Jiri Peterka (JIRA)

Separate Getting Started Guide ------------------------------ Key: TOOLSDOC-158 URL: https://issues.jboss.org/browse/TOOLSDOC-158 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Getting Started Guide Affects Versions: 3.2.0.Final Reporter: Jiri Peterka Assignee: Isaac Rooskov I would rather see separation of Getting Started Guide into JBT Installation Guide, JBDS Installation Guide (where BPEL installation steps or other tech previews should be listed) and Getting Started Guide with the rest of its content. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-121) JBDS40_006 Smooks: Direct Source to Target

by Isaac Rooskov (JIRA)

JBDS40_006 Smooks: Direct Source to Target ------------------------------------------ Key: TOOLSDOC-121 URL: https://jira.jboss.org/browse/TOOLSDOC-121 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Tracker for docs on this issue. Current status: Uncommitted -- 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

14 years, 8 months

3
9
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-190) References to "JBoss Portal" should be replace with, (Or expanded to include "JBoss Enterprise Portal Platform").

by Isaac Rooskov (JIRA)

References to "JBoss Portal" should be replace with, (Or expanded to include "JBoss Enterprise Portal Platform"). ----------------------------------------------------------------------------------------------------------------- Key: TOOLSDOC-190 URL: https://issues.jboss.org/browse/TOOLSDOC-190 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Portlet Tools User Guide Affects Versions: 3.2.0.Final Reporter: Scott Mumford Assignee: Isaac Rooskov Fix For: 3.3.0.Final References to "JBoss Portal" should be replace with, (Or expanded to include 'JBoss Enterprise Portal Platform"). Waiting for confirmation from EPP, GateIn and JBDS (JBT) individuals concerning the level of support within JBDS and JBT for EPP, GateIn and JBoss Portal. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9125) Add support for jboss-packaging-maven-plugin

by Fred Bricon (JIRA)

Add support for jboss-packaging-maven-plugin -------------------------------------------- Key: JBIDE-9125 URL: https://issues.jboss.org/browse/JBIDE-9125 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.2.0.Final Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 3.3.0.M3 The original feature request was created in m2e-wtp (https://issues.sonatype.org/browse/MECLIPSEWTP-46) The idea is to create a set of configurators, to handle jboss packages packages (http://mojo.codehaus.org/jboss-packaging-maven-plugin/). The configurators would work pretty much the same as the Connector configurator : - read the jboss-packaging-maven-plugin - all dependencies would have to be declared in .component - the project woul have to have the utility facet, in order to be deployed in an EAR First configurator would support sar projects -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9260) Update versions of all the plugins from Common/JSF/CDI/Seam modules to the highest version of each plugin.

by Alexey Kazakov (JIRA)

Update versions of all the plugins from Common/JSF/CDI/Seam modules to the highest version of each plugin. ---------------------------------------------------------------------------------------------------------- Key: JBIDE-9260 URL: https://issues.jboss.org/browse/JBIDE-9260 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi (jsr-299), common, JSF, Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.3.0.M3 For example the highest version of CDI plug-ins is 1.2.0. So every plug-in from CDI module should have the same version - 1.2.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-167) Release Notes doc is twice on docs.redhat.com

by Jiri Peterka (JIRA)

Release Notes doc is twice on docs.redhat.com --------------------------------------------- Key: TOOLSDOC-167 URL: https://issues.jboss.org/browse/TOOLSDOC-167 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Release Notes Affects Versions: 3.2.0.Final Reporter: Jiri Peterka Assignee: Matthew Casperson Same JBDS4.0 document on docs.redhat.com 4.0.0 Release Notes Release Notes resp. http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html/Release... http://docs.redhat.com/docs/en-US/JBoss_Developer_Studio/4.0/html/4.0.0_R... Please remove the second one -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-166) Automated Installation for JBoss Developer Studio

by Isaac Rooskov (JIRA)

Automated Installation for JBoss Developer Studio ------------------------------------------------- Key: TOOLSDOC-166 URL: https://issues.jboss.org/browse/TOOLSDOC-166 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Getting Started Guide Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Critical Fix For: 3.2.1.Final Add documentation about automating JBDS installation. See this wiki post for information: http://community.jboss.org/wiki/AutomatedInstallationforJBossDeveloperStudio -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
5
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-75) Incorrect ESB versions and/or examples in ESB Guide

by Libor Zoubek (JIRA)

Incorrect ESB versions and/or examples in ESB Guide ---------------------------------------------------- Key: TOOLSDOC-75 URL: https://jira.jboss.org/jira/browse/TOOLSDOC-75 Project: Documentation for JBoss Tools/Developer Studio Issue Type: Bug Security Level: Public (Everyone can see) Components: Documentation , esb Affects Versions: 3.0.0.GA Reporter: Libor Zoubek I followed ESB Tools Reference guide http://docs.jboss.org/tools/3.1.0.GA/en/esb_ref_guide/html_single/index.html. I set up Jboss AS 4.2 with ESB 4.7 and tried to run HelloWorld Example (and client) as written in section 2.3. The problem is, that helloWorld examples did not work. ESB archive did not deploy at all. So I tried to install ESB 4.7 into EAP 5. Archive was deployed, but the client worked only partly. Then I figured out, that I was using bad examples. Because ESB 4.7 is part of SOA-P 5, examples found in wizard in tree 'ESB -> JBoss ESB HelloWorld Example' are not expected to work with it. Guide should update Figure 2.7 and change the screenshot selecting from 'ESB for SOA-P 5.0 -> Jboss ESB HelloWorld Example' which works fine. These are same examples, but 'written' and hopefully verified on ESB 4.7. Also there should be some note about which examples to select with which versions. -- 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

14 years, 8 months

3
5
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-170) Document Teiid 7.1.1 install process for JBDS 4.1

by Isaac Rooskov (JIRA)

Document Teiid 7.1.1 install process for JBDS 4.1 ------------------------------------------------- Key: TOOLSDOC-170 URL: https://issues.jboss.org/browse/TOOLSDOC-170 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 3.2.0.Final Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Blocker Fix For: 3.2.1.Final >From Nick: a) Install JBDS 4.0.0.GA from installer jar (ie., downloaded from Customer Portal) for their respective platform. b) Download the Teiid 7.1.1 update site zip from here: http://download.jboss.org/jbosstools/builds/release/3.2.0.GA-Teiid-Design... http://download.jboss.org/jbosstools/builds/release/3.2.0.GA-Teiid-Design... c) Point JBDS at the zip and install updated Teiid 7.1.1 from there. If they need assistance w/ the whole "use a zip to provide an update" process you can use/modify these instructions here [1], which explain the process for installing JBT into Eclipse (same gist, different site): [1] https://www.jboss.org/tools/download/installation/update_3_2.html#fromzip -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9234) Refactor the forge plugin in a core and ui part to enhance the testing possibilities

by Koen Aers (JIRA)

Refactor the forge plugin in a core and ui part to enhance the testing possibilities ------------------------------------------------------------------------------------ Key: JBIDE-9234 URL: https://issues.jboss.org/browse/JBIDE-9234 Project: Tools (JBoss Tools) Issue Type: Task Components: forge Affects Versions: 3.3.0.M1, 3.3.0.M2 Reporter: Koen Aers Assignee: Koen Aers Priority: Critical Fix For: 3.3.0.M3 Currently the code of the forge plugin resides in one single plugin. This will be refactored so that: - there is a separate plugin that contains the embedded runtime; this will make it easier to upgrade the runtime - the non-ui related code will be put in a 'core' plugin to make testing easier - the ui related code will be put in a 'ui' plugin -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
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 2011