January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1785) Enable Windows x86_64 platform configuration in tycho buildTo let install JBDS for x86_64 from JBDS Update site

by Denis Golovin (JIRA)

Enable Windows x86_64 platform configuration in tycho buildTo let install JBDS for x86_64 from JBDS Update site --------------------------------------------------------------------------------------------------------------- Key: JBDS-1785 URL: https://issues.jboss.org/browse/JBDS-1785 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 5.0.0.M3 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 5.0.0.M3 configuration below should be added to build/parent/pom.xml <environment> <os>win32</os> <ws>win32</ws> <arch>x86</arch> </environment> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9140) move to tycho 0.13 for JBT and JBDS builds

by Nick Boldt (JIRA)

move to tycho 0.13 for JBT and JBDS builds ------------------------------------------ Key: JBIDE-9140 URL: https://issues.jboss.org/browse/JBIDE-9140 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M3 After M2, move to latest Tycho 0.13 including refactoring plugin names in parent pom andelsewhere (eg., test plugin poms that override settings) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

9
27
0 / 0

[JBoss JIRA] Created: (JBIDE-8518) fix pom.xml files in JBT and JBDS repo such that only component root poms reference parent pom (all others just look up to .. for parent)

by Nick Boldt (JIRA)

fix pom.xml files in JBT and JBDS repo such that only component root poms reference parent pom (all others just look up to .. for parent) ----------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8518 URL: https://issues.jboss.org/browse/JBIDE-8518 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M1 Reporter: Nick Boldt Assignee: Nick Boldt Currently, there are many plugin pom.xml files which reference the parent pom directly. This is bad. Instead, only ~/trunk/<component>/pom.xml should reference the parent pom, which can then be pulled from nexus: Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... (383 B at 0.2 KB/sec) Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... Downloaded: http://repository.jboss.org/nexus/content/groups/public/org/jboss/tools/o... (20 KB at 21.5 KB/sec) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-8791) JBoss 6 and 7 not found

by Rob Stryker (JIRA)

JBoss 6 and 7 not found ------------------------ Key: JBIDE-8791 URL: https://issues.jboss.org/browse/JBIDE-8791 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M1 Reporter: Rob Stryker Assignee: Nick Boldt Priority: Critical Fix For: 3.3.0.M1 https://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.... Only two tests showing failing in this build are: * org.jboss.ide.eclipse.as.test.ASTestSuite.testAS60Exists * org.jboss.ide.eclipse.as.test.ASTestSuite.testAS70Exists These tests are simple and just verify the passed-in folders / locations actually exist on the host machine. They don't even really do anything else, no verification of whether its a proper server or not. Just, does the folder exist. If you dont have time to fix / check it out, tell me and i'll comment out those two tests... It seems only yesterday we were setting fire to Strong Sad's underdrawers. (that *WAS* yesterday!) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9708) project examples should resolve its path relative to the location of the projectexample.xml file by default

by Max Rydahl Andersen (JIRA)

project examples should resolve its path relative to the location of the projectexample.xml file by default ----------------------------------------------------------------------------------------------------------- Key: JBIDE-9708 URL: https://issues.jboss.org/browse/JBIDE-9708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Max Rydahl Andersen Assignee: Snjezana Peco Fix For: 3.3.0.M4, 3.3.0.Beta1 Having project examples support relative paths in the .xml declarations would allow distributions to include an example.xml with pointers to the examples relative to files on disk and also allow you to upload a set of xml + archives without having to rewire the locations. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8939) Add project name into info log messages 'The project doesn't contain the Web Module facet'

by Denis Golovin (JIRA)

Add project name into info log messages 'The project doesn't contain the Web Module facet' ------------------------------------------------------------------------------------------ Key: JBIDE-8939 URL: https://issues.jboss.org/browse/JBIDE-8939 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: maven Affects Versions: 3.3.0.M1 Reporter: Denis Golovin Assignee: Snjezana Peco Attachments: screenshot64.png Would be good to have project name in message 'The project {0} doesn't contain the Web Module facet' Now it says something is missing, but it doesn't say where !screenshot64.png' -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-10082) Add documentation for project examples custom actions

by Snjezana Peco (Created) (JIRA)

Add documentation for project examples custom actions ----------------------------------------------------- Key: JBIDE-10082 URL: https://issues.jboss.org/browse/JBIDE-10082 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M3 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.Beta1 -- 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

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9822) Allow project examples to be created in a user-defined location

by Fred Bricon (JIRA)

Allow project examples to be created in a user-defined location --------------------------------------------------------------- Key: JBIDE-9822 URL: https://issues.jboss.org/browse/JBIDE-9822 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven, project-examples Affects Versions: 3.3.0.M3 Reporter: Fred Bricon Assignee: Snjezana Peco Fix For: 3.3.0.M4 In the wake of JBIDE-9368, we want to be able to let the user kickstart new projects from Maven Archetypes (for starters). Kickstart/Quickstart projects, as opposed to project examples, are meant to be actually used by users, i.e. added to SCM, as sub modules to existing maven projects; Problem is, if we choose to use Archetype-based project examples (and I think we should), projects are generated under *<workspace>/.JBossToolsMavenProjects/* We should be able to change that location, to use the workspace root (or another directory) for example. That means we should change the IImportProjectExample interface to add setLocation(IPath path)/IPath getLocation() methods (or something else) We need to make sure these projects can be added as maven sub modules. Also, we must make sure the delete existing example stuff doesn't impede this feature (see JBIDE-9821) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-9702) Refactor project examples plugin so that it can be used inside JBoss Central

by Snjezana Peco (JIRA)

Refactor project examples plugin so that it can be used inside JBoss Central ---------------------------------------------------------------------------- Key: JBIDE-9702 URL: https://issues.jboss.org/browse/JBIDE-9702 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M4 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8867) migrate to be compatible to the latest deltacloud-core gem 0.3.0

by Andre Dietisheim (JIRA)

migrate to be compatible to the latest deltacloud-core gem 0.3.0 ---------------------------------------------------------------- Key: JBIDE-8867 URL: https://issues.jboss.org/browse/JBIDE-8867 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x the latest available binary deltacloud gem is 0.3.0. It became available on 28th of April 2011. Deltacloud should move to get compatible to it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

4
7
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 January 2012