August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-72) drools/jBPM - Kepler component content - JBTIS 4.1.0

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-72?page=com.atlassian.jira.plugin.s... ] Kris Verlaenen commented on JBTIS-72: ------------------------------------- Paul, I've uploaded the most recent version here: http://download.jboss.org/jbpm/release/6.0.0.201308222359/org.drools.upda... Kris > drools/jBPM - Kepler component content - JBTIS 4.1.0 > ---------------------------------------------------- > > Key: JBTIS-72 > URL: https://issues.jboss.org/browse/JBTIS-72 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools/ jBPM5 > Affects Versions: 4.1.0.Beta1 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > Fix For: 4.1.0.Beta1 > > > Welcome to Kepler. > JBTIS 4.1.0/JBDSIS 7.0.0 is now available on master/trunk. This is needed for JBDS 7.0 in SOA-P 6.0 Beta. Please specify your compatible component for Kepler and update your contribution to the integration stack. The release procedure is here: > https://community.jboss.org/wiki/IntegrationToolingReleaseProcess > The specific files to change are: > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/jb... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... > The Kepler JBTIS target platform is here: > https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > I'll process the PR and regenerate the aggregate update site. > Thanks! > --paull -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15369) Minor part of jbosstools-server/as submodule version should be incremented

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-15369: ------------------------------------- Summary: Minor part of jbosstools-server/as submodule version should be incremented Key: JBIDE-15369 URL: https://issues.jboss.org/browse/JBIDE-15369 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Alpha1 Reporter: Denis Golovin Priority: Blocker API tooling reports that minor version should be incremented for as.core plugin because new APIs have been added since previous release. In theory whole jbosstools-server/as sub-module should get new version 2.5.0 (current is 2.4.100). At the same time if master branch contains different API version in its version should be also increased. Question is which part of version should be changed to avoid conflicts in future between two streams. This version changes should take place after JBIDE-15368 is taken care of. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15368: ---------------------------------- Labels: api-compatibility (was: ) > jbosstools-server has API Compatibility problem > ----------------------------------------------- > > Key: JBIDE-15368 > URL: https://issues.jboss.org/browse/JBIDE-15368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Priority: Blocker > Labels: api-compatibility > > Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: > "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". > According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 > || Interface change || Conditions || Compatibility || > |Add API field|If interface not implementable by Clients | Binary compatible| > |Add API field|If interface implementable by Clients| Breaks compatibility (2)| > (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-15368: ------------------------------------- Summary: jbosstools-server has API Compatibility problem Key: JBIDE-15368 URL: https://issues.jboss.org/browse/JBIDE-15368 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Alpha1 Reporter: Denis Golovin Priority: Blocker Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 || Interface change || Conditions || Compatibility || |Add API field|If interface not implementable by Clients | Binary compatible| |Add API field|If interface implementable by Clients| Breaks compatibility (2)| (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15367) JBoss Knowledge Base Builder hangs up

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15367: --------------------------------------------- Summary: JBoss Knowledge Base Builder hangs up Key: JBIDE-15367 URL: https://issues.jboss.org/browse/JBIDE-15367 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 https://community.jboss.org/message/833488 The cause is thread unsafe code in org.jboss.tools.jsf.jsf2.bean.model.impl.DefinitionContext. When one thread reads from HashSet while another modifies it, sometimes reading slips into eternal cycle. That is a feature of implementation of java.util.HashSet, and the only way to avoid it is to provide thread safety. I will open an issue. -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15358) No code completion when navigating in jsp files of Spring examples

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15358?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15358: ---------------------------------------- This project is a pure Spring project. There is no JSF or CDI. We have never provided any code completion for Spring projects. So it is not a bug. > No code completion when navigating in jsp files of Spring examples > ------------------------------------------------------------------ > > Key: JBIDE-15358 > URL: https://issues.jboss.org/browse/JBIDE-15358 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.0.Final > Reporter: Jiri Peterka > Assignee: Jiri Peterka > Fix For: 4.1.1.Final > > Attachments: jboss-wfk-2.3.0-spring-demo.zip > > > There is no code completion when editing standard.jsp spring example -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2737) Archive old JBDS docs on devstudio.jboss.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2737 at 8/22/13 5:17 PM: ----------------------------------------------------------- HTML content includes some strange CSS, including a "DRAFT" watermark, which despite removing it from local copies of CSS files, persists in the HTML pages. So for now just going to post the PDFs here: https://devstudio.jboss.com/download/documentation/ was (Author: nickboldt): HTML content includes some strange CSS, including a "DRAFT" watermark, which despite removing it from local copies of CSS files, persists in the HTML pages. So for now just going to post the PDFs. > Archive old JBDS docs on devstudio.jboss.com > --------------------------------------------- > > Key: JBDS-2737 > URL: https://issues.jboss.org/browse/JBDS-2737 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh* > Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references. > _Hack: 1. Proper solution: 0._ -- 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

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

11 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013