June 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12047) Regression - cannot create a new email notifier attachment in ESB editor

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-12047: ----------------------------------------- Summary: Regression - cannot create a new email notifier attachment in ESB editor Key: JBIDE-12047 URL: https://issues.jboss.org/browse/JBIDE-12047 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.3.0.Beta2-SOA Reporter: Brian Fitzpatrick Assignee: Viacheslav Kabanovich Priority: Blocker Fix For: 3.3.0.Beta3-SOA This is a clone of JBDS-2167. Details and screen shots are there. -- 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

11 years, 11 months

3
7
0 / 0

[JBoss JIRA] (JBDS-2176) Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2176?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2176: ------------------------------------- we lost one more which is lucene.analysis. it is simple to get them back by telling tycho to include optional dependencies, I've just finished my local testing for it. So question is include optional bundles or not? > Audit differences between Tycho-built installer (.updatesite job) and PDE-built installer (.product job) > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-2176 > URL: https://issues.jboss.org/browse/JBDS-2176 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 5.0.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 5.0.0.CR1 > > Attachments: lucene.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png, trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png > > > Comparing the on-disk footprints for the two installers, I see some discrepancies. > !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_04.png! > Left: jarred plugins for ch.qos. org.eclipse.equinox, org.slf4j > Right: unpcked plugins > !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_03.png! > Left: javax.servlet 3.0; no org.apache.lucene > Right: no javax.servlet; org.apache.lucene 2.9.1 > !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_02.png! > Left: org.eclipse.jetty > Right: no jetty > !trunk-nightly-updatesite-installer-Tycho_vs_trunk-nightly-product-installer-PDE_01.png! > Left: org.eclipse.mylyn.commons.workbench, org.jdom > Right: no org.eclipse.mylyn.commons.workbench; no org.jdom -- 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

11 years, 11 months

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

11 years, 11 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

11 years, 11 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

11 years, 11 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-10962) Support for 'source-ref' in Project Examples

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-10962: ------------------------------------- Summary: Support for 'source-ref' in Project Examples Key: JBIDE-10962 URL: https://issues.jboss.org/browse/JBIDE-10962 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Reporter: Aslak Knutsen Assignee: Snjezana Peco In a effort to make it as painless as possible to contribute, I would like to suggest adding a source-location/reference attribute/element to the project examples description. Tools could use this to display in the examples something like: - Found a bug? or have improvements to this example? Help us develop it, source can be found at xxx.. -- 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

11 years, 11 months

4
8
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

11 years, 11 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

11 years, 11 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

11 years, 11 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

11 years, 11 months

3
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2012