August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-300) JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-300?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-300. ------------------------------ Fix Version/s: 4.2.0.Alpha2 8.0.0.Alpha2 Resolution: Done BPMN2 modeler updated: https://github.com/jbosstools/jbosstools-integration-stack/commit/a2c0936... will be available in Alpha2. > JBDS-IS 8.0.0.Alpha1 contains old version of bpmn2 modeler > ---------------------------------------------------------- > > Key: JBTIS-300 > URL: https://issues.jboss.org/browse/JBTIS-300 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Environment: JBDS 8.0.0.Beta3 > Reporter: Jozef Marko > Assignee: Paul Leacu > Priority: Critical > Fix For: 4.2.0.Alpha2, 8.0.0.Alpha2 > > > Current version of bpmn2 modeler is 1.0.2. Desired version is 1.1.0 [1] which works well with eclipse luna. > [1] http://download.eclipse.org/bpmn2-modeler/updates/luna/1.1.0/ -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17906) remove dependency on internal jdt compiler class

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17906?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-17906: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > remove dependency on internal jdt compiler class > ------------------------------------------------ > > Key: JBIDE-17906 > URL: https://issues.jboss.org/browse/JBIDE-17906 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a, L64, Fedora 19, JDK 1.8 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.x > > > JBIDE-17026 was fixed but we were still left with reference to internal jdt compiler class. This should be fixed to avoid possible future breakage. > maybe suggest this becomes public api in upcoming JDT ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17906) remove dependency on internal jdt compiler class

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17906?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-17906: ----------------------------------- This will have to wait until post GA. > remove dependency on internal jdt compiler class > ------------------------------------------------ > > Key: JBIDE-17906 > URL: https://issues.jboss.org/browse/JBIDE-17906 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a, L64, Fedora 19, JDK 1.8 > Reporter: Jiri Peterka > Assignee: Koen Aers > Fix For: 4.2.x > > > JBIDE-17026 was fixed but we were still left with reference to internal jdt compiler class. This should be fixed to avoid possible future breakage. > maybe suggest this becomes public api in upcoming JDT ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-299) Cannot install JBDS-IS 8.0.0.Alpha1 from JBoss Central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-299?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-299. ------------------------------ Resolution: Cannot Reproduce Bug Please try the following command - you must specify the jboss.discovery.site.url: ./jbdevstudio -data tmp -clean -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Alpha1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Alpha1 > Cannot install JBDS-IS 8.0.0.Alpha1 from JBoss Central > ------------------------------------------------------ > > Key: JBTIS-299 > URL: https://issues.jboss.org/browse/JBTIS-299 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: jbdsis800aplha1_central.png, jbsis800alpha1_central.log > > > I tried to install JBDS-IS from JBoss Central using the following command > ./jbdevstudio/jbdevstudio -data tmp -clean -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.0.Alpha1/devstudio-integration-stack-directory.xml > At first, when I switched to Software/Update I saw errors (see the attached log file). A then when I tried to install the tooling a warning occurd (see the attached screenshot) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16261) Investigate failing HibernateConsoleTests on OSX

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16261?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-16261: ------------------------------ Fix Version/s: 4.2.x (was: 4.2.0.CR1) > Investigate failing HibernateConsoleTests on OSX > ------------------------------------------------ > > Key: JBIDE-16261 > URL: https://issues.jboss.org/browse/JBIDE-16261 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16261) Investigate failing HibernateConsoleTests on OSX

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16261?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-16261: ----------------------------------- This will need to happen later. > Investigate failing HibernateConsoleTests on OSX > ------------------------------------------------ > > Key: JBIDE-16261 > URL: https://issues.jboss.org/browse/JBIDE-16261 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.2.x > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17704) JPA: Generate Entities From Tables wizard should tell people when something has gone wrong

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17704?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17704: ---------------------------------------- "Assign them to me - I'll kill them" - George G. > JPA: Generate Entities From Tables wizard should tell people when something has gone wrong > ------------------------------------------------------------------------------------------- > > Key: JBIDE-17704 > URL: https://issues.jboss.org/browse/JBIDE-17704 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Priority: Critical > Fix For: 4.2.0.CR1 > > > I'm opening this jira based on experience from https://issues.jboss.org/browse/JBIDE-17702 > As you can see in the screencast here: http://youtu.be/BPagtMpfZM0, the user has no idea why the operation has failed. The error log is empty. The UI was frozen for several seconds. > UI wizard should be enhanced to tell the error on wizard page. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17070) code completion for session in criteriaeditor is not working

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17070?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-17070. ------------------------------- Resolution: Done > code completion for session in criteriaeditor is not working > ------------------------------------------------------------ > > Key: JBIDE-17070 > URL: https://issues.jboss.org/browse/JBIDE-17070 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.0.CR1 > > > open criteria editor on a type > try do content assist for "session." > It should see it as a hibernate session variable but it does not work. > what is weird that the code does work when actually running the query. > so some context must be set up wrong ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18004) Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18004?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18004: ---------------------------------------- "Assign them to me - I'll kill them" - George G. > Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets > -------------------------------------------------------------------------------------------- > > Key: JBIDE-18004 > URL: https://issues.jboss.org/browse/JBIDE-18004 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Vineet Reynolds > Priority: Critical > Fix For: 4.2.0.CR1 > > > The name of the command to be executed should be accepted as a parameter so that it can be directly launched from an Eclipse cheatsheet, instead of merely guiding the user to the quick access menu. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18161) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Forge]

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18161?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18161: ---------------------------------------- "Assign them to me - I'll kill them" - George G. > For JBIDE 4.2.0.CR1: Code Freeze + Branch [Forge] > ------------------------------------------------- > > Key: JBIDE-18161 > URL: https://issues.jboss.org/browse/JBIDE-18161 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.2.0.CR1 > > > For JBIDE 4.2.0.CR1 [Forge]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1 > [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch; > {code} > git fetch origin master > git checkout FETCH_HEAD > git checkout -b jbosstools-4.2.x > git push origin jbosstools-4.2.x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.CR2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and > * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

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