[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
[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
[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
[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
[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