July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20253) javascript New and Noteworthy for 4.3.0.Beta2

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20253?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20253: ------------------------------------- PR was sent > javascript New and Noteworthy for 4.3.0.Beta2 > --------------------------------------------- > > Key: JBIDE-20253 > URL: https://issues.jboss.org/browse/JBIDE-20253 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=((project%20in%20(JBDS)%20and%...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If javascript is not listed here check if there are issues that should be added and add them. > Document the ones relevant for javascript by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20264: ---------------------------------------- Anything in Eclipse log? > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > Attachments: video.ogv > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20274) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Hibernate]

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20274?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-20274. ----------------------------- Assignee: Koen Aers Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Hibernate] > ------------------------------------------------------- > > Key: JBIDE-20274 > URL: https://issues.jboss.org/browse/JBIDE-20274 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Hibernate]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. 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 Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-42) Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/LOCUS-42?page=com.atlassian.jira.plugin.s... ] Paul Leacu updated LOCUS-42: ---------------------------- Comment: was deleted (was: [~mickael_istria] - PR sent - please consider for 1.3.0-SNAPSHOT https://github.com/jbosstools/jbosstools-locus/pull/42 ) > Update locus to include jsonschema2pojo-core jar, jaxb-xjc.jar and jaxb-impl.jar. > --------------------------------------------------------------------------------- > > Key: LOCUS-42 > URL: https://issues.jboss.org/browse/LOCUS-42 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.2.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 1.3.0 > > > Request three new jars in Locus 1.3.0: > jsonschema2pojo-core jar > jaxb-xjc jar > jaxb-impl jar > Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. Need to capture the jar in locus for inclusion into JBTIS target platform and ultimately Data Transformation tooling (Fuse). > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > This is needed for Mars/ 9.0.x JBDSIS target platform inclusion. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20292) Remove MaxPermSize from server scripts when Java 9 is used

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20292?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20292: --------------------------------------- It's true that the WildFly team don't seem to care about this themselves - their standalone script always puts the perm gen parameter there. > Remove MaxPermSize from server scripts when Java 9 is used > ---------------------------------------------------------- > > Key: JBIDE-20292 > URL: https://issues.jboss.org/browse/JBIDE-20292 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > > I'm not sure how easy this will be, but I think we need some way to do this. > Right now when you set up your WildFly 9 to use JDK 9, it will not start because MaxPermSize is no longer allowed as an argument. > The server will fail to start with this: > {code} > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > In JBIDE-19049 we concluded that for now the workaround is to remove that parameter from Launch config manually if needed. This still works, but it would be best if we could somehow detect which version of Java is to be used and adjust the script accordingly. I know it can be tricky, especially when you use an exec env with the server and not a specific JVM directly. > One option would be to check for permgen support beforehand. But a problem I can see is that the exec env can change between server setup and server start, so we would need to check right before the start. Something like what they do here - via a script: > https://answers.atlassian.com/questions/17903656/java-warning-ignoring-op... > Maybe checking this at the time of server setup would still be better than nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-662) Add edited Advanced Install Task instructions to related docs

by Supriya Bharadwaj (JIRA)

Supriya Bharadwaj created TOOLSDOC-662: ------------------------------------------ Summary: Add edited Advanced Install Task instructions to related docs Key: TOOLSDOC-662 URL: https://issues.jboss.org/browse/TOOLSDOC-662 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Reporter: Supriya Bharadwaj Assignee: Supriya Bharadwaj Add edited Advanced Install Task instructions to following related docs: 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/cu... 2. https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-20264: ------------------------------------ Attachment: video.ogv > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > Attachments: video.ogv > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20264) Suggestion dialog is not updated correctly for ref elements

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20264?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-20264: ----------------------------------------- I tried it today on nightly build and the behaviour was slightly different. In the last step, when I clicked the info button I was navigated again to the New Batch Artifact wizard. I am attaching screencast to make things more clear. I am also using Linux, Ubuntu 14.04. > Suggestion dialog is not updated correctly for ref elements > ----------------------------------------------------------- > > Key: JBIDE-20264 > URL: https://issues.jboss.org/browse/JBIDE-20264 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.CR1 > > > In JBIDE-20005, there was added a new navigation feature from Properties to diagram. However, the suggestion box is not always updated correctly. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20292) Remove MaxPermSize from server scripts when Java 9 is used

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20292?page=com.atlassian.jira.plugi... ] Martin Malina updated JBIDE-20292: ---------------------------------- Labels: Java9 (was: ) > Remove MaxPermSize from server scripts when Java 9 is used > ---------------------------------------------------------- > > Key: JBIDE-20292 > URL: https://issues.jboss.org/browse/JBIDE-20292 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Labels: Java9 > > I'm not sure how easy this will be, but I think we need some way to do this. > Right now when you set up your WildFly 9 to use JDK 9, it will not start because MaxPermSize is no longer allowed as an argument. > The server will fail to start with this: > {code} > Unrecognized VM option 'MaxPermSize=256m' > Error: Could not create the Java Virtual Machine. > Error: A fatal exception has occurred. Program will exit. > {code} > In JBIDE-19049 we concluded that for now the workaround is to remove that parameter from Launch config manually if needed. This still works, but it would be best if we could somehow detect which version of Java is to be used and adjust the script accordingly. I know it can be tricky, especially when you use an exec env with the server and not a specific JVM directly. > One option would be to check for permgen support beforehand. But a problem I can see is that the exec env can change between server setup and server start, so we would need to check right before the start. Something like what they do here - via a script: > https://answers.atlassian.com/questions/17903656/java-warning-ignoring-op... > Maybe checking this at the time of server setup would still be better than nothing. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20277) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Playground]

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20277?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-20277. ---------------------------------- Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Playground] > -------------------------------------------------------- > > Key: JBIDE-20277 > URL: https://issues.jboss.org/browse/JBIDE-20277 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: playground > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Playground]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. 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 Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 July 2015