September 2013 - jbosstools-issues

[JBoss JIRA] (JBTIS-124) Create SY bot test for file gateway

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-124?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-124: ------------------------------------ Summary: Create SY bot test for file gateway (was: Create bot test for file gateway) > Create SY bot test for file gateway > ----------------------------------- > > Key: JBTIS-124 > URL: https://issues.jboss.org/browse/JBTIS-124 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Affects Versions: 4.1.0.Final > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > > Create a bot test form SY service with file binding -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-163: --------------------------------------- Summary: Failed to resolve target definition Key: JBTIS-163 URL: https://issues.jboss.org/browse/JBTIS-163 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: target-platform Affects Versions: 4.1.2, 4.1.3 Reporter: Andrej Podhradsky Priority: Blocker During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2749) Update screen captures in docs that explicitly reference JBDS 7.0

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2749?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2749: ----------------------------- CDW pm_ack: ? CDW release: ? > Update screen captures in docs that explicitly reference JBDS 7.0 > ----------------------------------------------------------------- > > Key: JBDS-2749 > URL: https://issues.jboss.org/browse/JBDS-2749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Michelle Murray > Assignee: Michelle Murray > > Screen captures that will need updating for 7.1 docs > *Installation Guide* > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal > * Figure 3.2. Installation Step 3: Select Target Folder > * Figure 3.3. Installation Step 4: Select Java VM > * Figure 3.5. Installation Step 7: Installation Progress in Finished State > * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace > * Figure 3.7. Confirm Selected Features Window > * Figure 3.10. Work from an Online Website > * Figure 3.11. work from a Local Copy of the Update .zip File > * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse > * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace > * Figure 6.3. Confirm Selected Features Window > *Migration Guide* > * Figure 3.1. jbdevstudio.ini File Open in a Text Editor > *Getting Started Guide* (all Fig. shared with Installation Guide) > * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal > * Figure 3.2. Installation Step 3: Select Target Folder > * Figure 3.3. Installation Step 4: Select Java VM > * Figure 3.5. Installation Step 7: Installation Progress in Finished State > *User Guide* > * Figure 2.4. JBoss Buzz > * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2749) Update screen captures in docs that explicitly reference JBDS 7.0

by Michelle Murray (JIRA)

Michelle Murray created JBDS-2749: ------------------------------------- Summary: Update screen captures in docs that explicitly reference JBDS 7.0 Key: JBDS-2749 URL: https://issues.jboss.org/browse/JBDS-2749 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Michelle Murray Assignee: Michelle Murray Screen captures that will need updating for 7.1 docs *Installation Guide* * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal * Figure 3.2. Installation Step 3: Select Target Folder * Figure 3.3. Installation Step 4: Select Java VM * Figure 3.5. Installation Step 7: Installation Progress in Finished State * Figure 3.6. Install JBoss Developer Studio BYOE via Eclipse Marketplace * Figure 3.7. Confirm Selected Features Window * Figure 3.10. Work from an Online Website * Figure 3.11. work from a Local Copy of the Update .zip File * Figure 3.12. Available Software Window Listing JBoss Developer Studio 7.0 - Bring Your Own Eclipse * Figure 6.2. Uninstall JBoss Developer Studio via Eclipse Marketplace * Figure 6.3. Confirm Selected Features Window *Migration Guide* * Figure 3.1. jbdevstudio.ini File Open in a Text Editor *Getting Started Guide* (all Fig. shared with Installation Guide) * Figure 3.1. JBoss Developer Studio Downloads Listed on the Customer Portal * Figure 3.2. Installation Step 3: Select Target Folder * Figure 3.3. Installation Step 4: Select Java VM * Figure 3.5. Installation Step 7: Installation Progress in Finished State *User Guide* * Figure 2.4. JBoss Buzz * Figure 2.22. Set Cheat Sheet Behavior in Project Examples Pane of Preferences Window -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2748) Fix bugs in 7.0 documentation

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2748?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2748: ---------------------------------- Assignee: Michelle Murray > Fix bugs in 7.0 documentation > ----------------------------- > > Key: JBDS-2748 > URL: https://issues.jboss.org/browse/JBDS-2748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michelle Murray > Assignee: Michelle Murray > > We should include essential but trivial fixes for the bugs in docs that have been found by docs/QE/users. > All those should be linked to this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2748) Fix bugs in 7.0 documentation

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2748?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2748: ----------------------------- CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? CDW release: ? > Fix bugs in 7.0 documentation > ----------------------------- > > Key: JBDS-2748 > URL: https://issues.jboss.org/browse/JBDS-2748 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michelle Murray > > We should include essential but trivial fixes for the bugs in docs that have been found by docs/QE/users. > All those should be linked to this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2748) Fix bugs in 7.0 documentation

by Michelle Murray (JIRA)

Michelle Murray created JBDS-2748: ------------------------------------- Summary: Fix bugs in 7.0 documentation Key: JBDS-2748 URL: https://issues.jboss.org/browse/JBDS-2748 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Michelle Murray We should include essential but trivial fixes for the bugs in docs that have been found by docs/QE/users. All those should be linked to this jira. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2733) Make Cordova tooling and CordovaSim available from software/update tab

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2733?page=com.atlassian.jira.plugin.... ] Michelle Murray edited comment on JBDS-2733 at 9/3/13 12:06 AM: ---------------------------------------------------------------- [Docs] This will needs documenting in: User Guide, CordovaSim chapter Docs Q: * Is there a distinction between Cordova tooling and CordovaSim? * So users will need to install CordovaSim from JBoss Central Software/Update tab? is it not being packaged with JBDS like all of the other tools? is it being treated differently because it is tech preview? * Where can I find info on the tasks user will be able to complete with CordovaSim? I only have [1] and [2], which state these features are functional in JBT 4.1 but I couldn't actually find when I installed JBT 4.1. [1] http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.Bet... [2] http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.CR1... was (Author: mmurray): [Docs] This will needs documenting in: User Guide, CordovaSim chapter Docs Q: * So users will need to install CordovaSim from JBoss Central Software/Update tab? is it not being packaged with JBDS like all of the other tools? is it being treated differently because it is tech preview? * Where can I find info on the tasks user will be able to complete with CordovaSim? I only have [1] and [2], which state these features are functional in JBT 4.1 but I couldn't actually find when I installed JBT 4.1. [1] http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.Bet... [2] http://docs.jboss.org/tools/whatsnew/browsersim/browsersim-news-4.1.0.CR1... > Make Cordova tooling and CordovaSim available from software/update tab > ----------------------------------------------------------------------- > > Key: JBDS-2733 > URL: https://issues.jboss.org/browse/JBDS-2733 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > Cordova should be available from JBDS, but it is not fully supported tech yet thus should be included/marked as a Technology Preview -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15392: --------------------------------------- I need the following method: public String[] getJarsAndFolders() and propose we to add it to JBossServerType. It would return jars and/or the directories jars are placed. Currently, it should return: modules, bundles, jboss-modules.jar for AS >= 7.0 and common, lib, server , server/default/lib, server/default/deploy/lib, server/default/deployers, server/default/deploy/jbossweb.sar for AS <= 6.x. > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-15392: ------------------------------------- Assignee: Rob Stryker (was: Snjezana Peco) > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
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 September 2013