December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1447) Missing Legal Info for Plugins

by Vlado Pakan (JIRA)

Missing Legal Info for Plugins ------------------------------ Key: JBDS-1447 URL: https://jira.jboss.org/browse/JBDS-1447 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: ui/branding Affects Versions: 4.0.0.Beta2 Environment: JBDS 4.0.0.v201012021737R-H23-Beta2 Reporter: Vlado Pakan These plugins has missing Legal Info (Help > About JBoss Developer Studio > Installation Details > Plug-ins): org.jboss.ide.eclipse.freemaker.source.feature org.jboss.tools.jmx.source.feature org.teiid.* except org.teiid.designer -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-1463) Missing Legal Info for Freemaker plugin

by Vlado Pakan (JIRA)

Missing Legal Info for Freemaker plugin --------------------------------------- Key: JBDS-1463 URL: https://issues.jboss.org/browse/JBDS-1463 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Affects Versions: 4.0.0.Beta2 Environment: JBDS 4.0.0.v201012021737R-H23-Beta2 Reporter: Vlado Pakan Fix For: 4.0.0.CR1 Plugin org.jboss.ide.eclipse.freemaker.source.feature has missing Legal Info (Help > About JBoss Developer Studio > Installation Details > Plug-ins) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1462) Missing Legal Info for JMX plugin

by Vlado Pakan (JIRA)

Missing Legal Info for JMX plugin --------------------------------- Key: JBDS-1462 URL: https://issues.jboss.org/browse/JBDS-1462 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Affects Versions: 4.0.0.Beta2 Environment: JBDS 4.0.0.v201012021737R-H23-Beta2 Reporter: Vlado Pakan Fix For: 4.0.0.CR1 Plugin org.jboss.tools.jmx.source.feature has missing Legal Info (Help > About JBoss Developer Studio > Installation Details > Plug-ins) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1461) Missing Legal Info for Teiid Plugins

by Vlado Pakan (JIRA)

Missing Legal Info for Teiid Plugins ------------------------------------ Key: JBDS-1461 URL: https://issues.jboss.org/browse/JBDS-1461 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Components: teiid Environment: JBDS 4.0.0.v201012021737R-H23-Beta2 Reporter: Vlado Pakan Assignee: Barry LaFond Plugins org.teiid.* except org.teiid.designer plugins has missing Legal Info (Help > About JBoss Developer Studio > Installation Details > Plug-ins) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7937) BPMN component has no pom.xml files and therefore cannot be built w/ Tycho

by Nick Boldt (JIRA)

BPMN component has no pom.xml files and therefore cannot be built w/ Tycho -------------------------------------------------------------------------- Key: JBIDE-7937 URL: https://issues.jboss.org/browse/JBIDE-7937 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpm Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Max Andersen Fix For: LATER This component has apparently never been included in JBT 3.2 or JBDS 4.0. http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... If you want it included we can do so. Let me know. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-4809) Creating application.xml, jboss-app.xml and datasource files when importing Maven EAR project

by Snjezana Peco (JIRA)

Creating application.xml, jboss-app.xml and datasource files when importing Maven EAR project --------------------------------------------------------------------------------------------- Key: JBIDE-4809 URL: https://jira.jboss.org/jira/browse/JBIDE-4809 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: maven Affects Versions: 3.1.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco See https://jira.jboss.org/jira/browse/JBIDE-4736?focusedCommentId=12481300#a... and http://archive.codehaus.org/lists/org.codehaus.m2eclipse.user/msg/4A8A60A... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
16
0 / 0

[JBoss JIRA] Created: (JBIDE-6879) BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package

by Robert (Bob) Brodt (JIRA)

BPEL deployer should not be using PublishCopyUtili.java in JBoss as.core package -------------------------------------------------------------------------------- Key: JBIDE-6879 URL: https://jira.jboss.org/browse/JBIDE-6879 Project: Tools (JBoss Tools) Issue Type: Task Components: bpel Affects Versions: 3.2.0.M2 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.0.M2 Like the comments in PublishCopyUtili say: * This class/interface is part of an interim API that is still under development and expected to * change significantly before reaching stability. It is being made available at this early stage to solicit feedback * from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken * (repeatedly) as the API evolves. the bpel deployer package probably shouldn't be using this class, but should be using the standard WTP API instead. I've made a quick fix for now to get us through M2, but this needs to be addressed before final release. -- 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

15 years, 3 months

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-7107) Problems when creating BPEL Correlation Set

by Robert (Bob) Brodt (JIRA)

Problems when creating BPEL Correlation Set ------------------------------------------- Key: JBIDE-7107 URL: https://jira.jboss.org/browse/JBIDE-7107 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.0.CR1 I discovered several issues during testing: 1. The WSDL property is created correctly but the PropertySelectorDialog does not detect the message part. This leads to "missing "type" or "element" attribute" validation error 2. The messages.properties file in the org.eclipse.bpel.validator.vprop package (used for error message localization) is empty 3. WSDL validator does not detect duplicate definitions of <property name="foo"> 4. The message "Structure" tree widget in EditPropertyAliasDialog is only one line high - should display more of message structure 5. The overall workflow for creating correlation sets is overly complicated! This needs to be reworked. -- 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

15 years, 3 months

2
12
0 / 0

[JBoss JIRA] Created: (JBIDE-7786) Unable to associate BPEL project with SOA 5.1 runtime.

by Marek Baluch (JIRA)

Unable to associate BPEL project with SOA 5.1 runtime. ------------------------------------------------------ Key: JBIDE-7786 URL: https://jira.jboss.org/browse/JBIDE-7786 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.1.2 Reporter: Marek Baluch Assignee: Max Andersen It's not possible to associate a BPEL project with a SOA 5.1 runtime. Even if there's a usable runtime then it's greyed-out. This association should be done automatically on project creation. According to the "targeted runtimes" dialog there seem to be facets blocking it. There are following facets associated with the project: BPEL 2.0 Facet (checked) Contexts and Dependency Injection (not checked) Java (not checked) JavaScript (not checked) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

4
10
0 / 0

[JBoss JIRA] Updated: (JBIDE-7959) NPE when showing up instances view

by Libor Zoubek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7959?page=com.atlassian.jira.plugin... ] Libor Zoubek updated JBIDE-7959: -------------------------------- Attachment: .log > NPE when showing up instances view > ---------------------------------- > > Key: JBIDE-7959 > URL: https://issues.jboss.org/browse/JBIDE-7959 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: deltacloud > Affects Versions: 3.2.0.CR1 > Environment: 3.2.0.v20101210-1533-H44-CR1 > Reporter: Libor Zoubek > Attachments: .log > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 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 December 2010