May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-6608) Ability to remove drools nature from project

by Libor Zoubek (JIRA)

Ability to remove drools nature from project -------------------------------------------- Key: JBIDE-6608 URL: https://jira.jboss.org/browse/JBIDE-6608 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: drools Affects Versions: 3.1.0.GA Reporter: Libor Zoubek Assignee: Kris Verlaenen Regarding to http://community.jboss.org/message/552490 at this time, there is no possibility to remove drools "nature" (as it is probably not the nature in sense of eclipse nature) We should be able to remove drools from project. Menu item 'Convert to drools project' should be called 'Add drools nature' and when a project has a drools nature it should be called 'Remove drools nature'. Maybe it would be good, not to have 'Convert to drools project' menu item in main context menu, but move it into 'Configure' submenu -- 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

13 years, 10 months

7
17
0 / 0

[JBoss JIRA] Created: (JBIDE-9646) org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name

by Nick Boldt (JIRA)

org.eclipse.bpel.apache.ode.deploy.ui has no provider or plugin name -------------------------------------------------------------------- Key: JBIDE-9646 URL: https://issues.jboss.org/browse/JBIDE-9646 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Robert (Bob) Brodt Priority: Minor Fix For: 3.3.0.M4 Attachments: snapshot7.png Minor nitpick -- the providerName and pluginName are not being displayed correctly. This is either due to a missing directive in the manifest.mf telling Eclipse this is a plugin, or your build.properties doesn't include mention of your plugin.properties (and license.html) files. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

7
14
0 / 0

[JBoss JIRA] (JBIDE-10183) BPEL - cannot change the fixed value generated by variable initializer.

by Marek Baluch (Created) (JIRA)

BPEL - cannot change the fixed value generated by variable initializer. ----------------------------------------------------------------------- Key: JBIDE-10183 URL: https://issues.jboss.org/browse/JBIDE-10183 Project: Tools (JBoss Tools) Issue Type: Bug Components: BPEL Affects Versions: 3.2.2.Final Environment: JBT version 3.2.2.CR4 inside JBDS 4.1.1.GA Reporter: Marek Baluch Assignee: Robert (Bob) Brodt The fixed value generated by BPEL variable initializer cannot be changed using the UI. I attempt to change the assigned value but saving the changes does not have any effect. To make the save work it's required to close/open the .bpel process document. -- 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, 10 months

5
5
0 / 0

[JBoss JIRA] Created: (JBIDE-6958) Restore build results index.html page

by Denis Golovin (JIRA)

Restore build results index.html page ------------------------------------- Key: JBIDE-6958 URL: https://jira.jboss.org/browse/JBIDE-6958 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.2.0.M2 Reporter: Denis Golovin Assignee: Nick Boldt Priority: Critical Fix For: 3.2.0.Beta Build results page should look the same as we had in 3.1.X releases. Probably we need to mention not just required drivers here but update sites. It should contain zipped update sites for separate components and aggregated update site. -- 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

13 years, 10 months

4
14
0 / 0

[JBoss JIRA] Created: (JBDS-1810) Push BPEL editor development back upstream to eclipse.org

by Robert (Bob) Brodt (JIRA)

Push BPEL editor development back upstream to eclipse.org --------------------------------------------------------- Key: JBDS-1810 URL: https://issues.jboss.org/browse/JBDS-1810 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: integration, SOA Platform Reporter: Robert (Bob) Brodt Assignee: Nick Boldt Fix For: 5.0.0.M3 The BPEL editor development will be moved back to eclipse.org - JBT/JBDS and SOA builds should include the plugins from the eclipse update site at http://download.eclipse.org/bpel/update-site/ -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

9
19
0 / 0

[JBoss JIRA] (JBIDE-11049) [ESB Dependency Tool] Link to ESB editor - change to use Eclipse frameworks, not XModel code directly

by Brian Fitzpatrick (JIRA)

Brian Fitzpatrick created JBIDE-11049: ----------------------------------------- Summary: [ESB Dependency Tool] Link to ESB editor - change to use Eclipse frameworks, not XModel code directly Key: JBIDE-11049 URL: https://issues.jboss.org/browse/JBIDE-11049 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.3.0.Beta1 Reporter: Brian Fitzpatrick Assignee: Brian Fitzpatrick Fix For: 3.3.0.CR1 While developing the new ESB Dependency Visualizer tool, we added functionality to double-click on a node and have it open the ESB editor. In beta1 we used XModel code to do this, but Slava added some code that allows us to do the same thing by using Eclipse Frameworks and some XModel magic implemented in the background. It simplifies the dependencies a bit and is cleaner down the line. This is not a change that will be visible to the user in the UI. And it doesn't affect the beta1 functionality. We're just changing underneath how this functionality is implemented. -- 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, 10 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-10097) ESB project properties does not contain 'ESB Validator' page

by Viacheslav Kabanovich (Created) (JIRA)

ESB project properties does not contain 'ESB Validator' page ------------------------------------------------------------ Key: JBIDE-10097 URL: https://issues.jboss.org/browse/JBIDE-10097 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich 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, 10 months

4
3
0 / 0

[JBoss JIRA] Created: (JBDS-1516) Navigation between links on welcome screen should be uninterrupted

by Lukas Jungmann (JIRA)

Navigation between links on welcome screen should be uninterrupted ------------------------------------------------------------------ Key: JBDS-1516 URL: https://issues.jboss.org/browse/JBDS-1516 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 4.0.0.CR1 Reporter: Lukas Jungmann Attachments: test-0000.mpeg -shrink the JBDS window a bit and click on links on the welcome screen I can see two issues here: -the loading of the link should be uninterrupted, as of now one can see white/empty page between clicking on the link and displaying the contents of the link -the white strip (the one containing the RH and JBoss logos) does not have fixed position at the bottom of the window, ie if one needs to scroll, he may not be able to follow link hidden by the strip video from ubuntu 10.10 is attached -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
12
0 / 0

[JBoss JIRA] (JBDS-1917) timestamp & build type qualifier (R) on JBDS Core update site generated by PDE (Installer build) should use same convention as Tycho-generated sites

by Nick Boldt (Created) (JIRA)

timestamp & build type qualifier (R) on JBDS Core update site generated by PDE (Installer build) should use same convention as Tycho-generated sites ---------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBDS-1917 URL: https://issues.jboss.org/browse/JBDS-1917 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Build, updatesite Affects Versions: 5.0.0.M4 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.Beta1 http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M4a_core/ > Latest Build: 5.0.0.v201110271830R-H42-M4 > This is the Stable Release Update Site for JBoss Developer Studio, including upstream features from Eclipse.org. http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M4a_extras/ > Latest Build 5.0.0.v20111027-1656-H37-M4.extras > This is the Development Milestone Update Site for JBoss Developer Studio - Extras. http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.0.M4a.soa-t... > Latest Build 5.0.0.v20111027-2344-H67-M4.soa-tooling > This is the Development Milestone Update Site for JBoss Developer Studio - SOA Tooling. -- 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, 10 months

7
7
0 / 0

[JBoss JIRA] (JBIDE-10295) Using eGit in JBoss Tools - The selected wizard could not be started.

by Burr Sutter (Created) (JIRA)

Using eGit in JBoss Tools - The selected wizard could not be started. --------------------------------------------------------------------- Key: JBIDE-10295 URL: https://issues.jboss.org/browse/JBIDE-10295 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Mac OS X Lion - JBoss Tools http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ Reporter: Burr Sutter I was not sure how to clone a github-based project to start a new project inside of eclipse/JBoss Tools so I tried the following steps. Steps: 1) File-New-Other (or Ctrl/Command N) 2) Git Repository 3) Next Error message... The selected wizard could not be started. Plug-in "org.eclipse.egit.ui" was unable to instantiate class "org.eclipse.egit.ui.internal.repository.NewRepositoryWizard". org.eclipse.egit.ui.internal.repository.NewRepositoryWizard Are those the correct steps? -- 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, 10 months

5
4
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 May 2012