June 2015 - jbosstools-issues - Jboss List Archives

[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 commented on LOCUS-42: --------------------------------- Hey [~kcbabo] - I'd like to use version 0.4.13 of jsonschema2pojo - looks like it came out last week. If it causes trouble we can back off of it. WDYT? > 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20063) locked up machine with "Loading descriptor" ...

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20063?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20063: ----------------------------------------------- Names like 'batch-chunk-exception' and others in the message 'Loading descriptor for ...' are maven artifact ids in pom.xml. The jobs in progress must be maven jobs stuck when resolving and downloading dependencies. > locked up machine with "Loading descriptor" ... > ----------------------------------------------- > > Key: JBIDE-20063 > URL: https://issues.jboss.org/browse/JBIDE-20063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > when loaded javaee7-samples I ended up with frozen eclipse showing this: > https://www.dropbox.com/s/ttx9ppieads5m7n/Screenshot%202015-06-13%2001.31... > its so frozen I cannot even get a stacktrace from jps. > I tried looking for "Loading descriptor" in common and batch but no luck so maybe it is not in batch this is happening but something is definitely locking up ;/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-20110: ----------------------------------------------- The attached pull request is done on top of fix for JBIDE-19995, it includes both one commit for that issue, and one commit for this issue. > Batch Diagram silently closes Palette view > ------------------------------------------ > > Key: JBIDE-20110 > URL: https://issues.jboss.org/browse/JBIDE-20110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > Case 1: > 1. Open Studio. > 2. Open Palette. > 3. Open some batch job xml file. > FAIL: Palette is silently closed. > The code that does it, is commented with > {code} > /** > * This is a workaround that ensures that the flyout pallete (inner > * composite inside the diagram editor) is used instead of a separate > * pallete view. The separate pallete view does not work with the diagram > * editor currently. > */ > {code} > This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace. > There is another case when this silent close does not work. > Case 2: > 1. Open some batch job xml file. > 2. Open Palette view. > 3. Test work with the separate palette. > 4. Close/Restart Eclipse. > 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it) > 6. Test work with the separate palette. > [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it. > Separate Palette view does not work with Batch diagram in this usecase: > 1. Open batch job editor. > 2. Open separate palette. Make sure that it works. > 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. > 4. Make sure that Palette does not work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11436) Migrate to use of o.j.t.foundation.license feature

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11436?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-11436: ------------------------------- Summary: Migrate to use of o.j.t.foundation.license feature (was: we should use license features) > Migrate to use of o.j.t.foundation.license feature > -------------------------------------------------- > > Key: JBIDE-11436 > URL: https://issues.jboss.org/browse/JBIDE-11436 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: wrong-feature-name-shown-in-p2-install-UI-when-using-license-features.png, wrong-feature-name-shown-when-using-license-features.png > > > See http://relengofthenerds.blogspot.fr/2011/01/implementing-shared-licenses-... for explanation -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19598?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19598: ------------------------------------ Until we adopt the buildchow stuff (feel free to start on that if you're comfortable "breaking" all the master jobs) we're still using the git backup of jenkins config w/ the sync mojo. Once we move to buildchow I think it's still a good idea to periodically save a snapshot of what's on the server into github, so we can more easily track things. When we're satisfied that buildchow handles all the jobs and all the permutations (including _master and _4.3.mars/_9.0.mars streams) we can drop that step and just rely on the generator templates. Sound good? > Use "Build other project (extended)" to cascade aggregation > ----------------------------------------------------------- > > Key: JBIDE-19598 > URL: https://issues.jboss.org/browse/JBIDE-19598 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta2 > > > In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes. > This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1]. > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-20110 at 6/29/15 2:56 PM: ------------------------------------------------------------------------ Alas, I have found when the separate palette stops working: 1. Open batch job editor. 2. Open separate palette. Make sure that it works. 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. 4. Make sure that Palette does not work. [~ljelinko], please check this case. All the same, I am sure that the Palette may not be silently closed. This issue should be fixed along with incorrect work of Palette view when inner flow is opened in Batch diagram. was (Author: scabanovich): Alas, I have found when the separate palette stops working: 1. Open batch job editor. 2. Open separate palette. Make sure that it works. 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. 4. Make sure that Palette does not work. [~ljelinko], please check this case. All the same, I am sure that the Palette may not be silently closed. This issue should be fixed and new issue should be created about incorrect work of Palette view when inner flow is opened in Batch diagram. > Batch Diagram silently closes Palette view > ------------------------------------------ > > Key: JBIDE-20110 > URL: https://issues.jboss.org/browse/JBIDE-20110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > Case 1: > 1. Open Studio. > 2. Open Palette. > 3. Open some batch job xml file. > FAIL: Palette is silently closed. > The code that does it, is commented with > {code} > /** > * This is a workaround that ensures that the flyout pallete (inner > * composite inside the diagram editor) is used instead of a separate > * pallete view. The separate pallete view does not work with the diagram > * editor currently. > */ > {code} > This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace. > There is another case when this silent close does not work. > Case 2: > 1. Open some batch job xml file. > 2. Open Palette view. > 3. Test work with the separate palette. > 4. Close/Restart Eclipse. > 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it) > 6. Test work with the separate palette. > [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it. > Separate Palette view does not work with Batch diagram in this usecase: > 1. Open batch job editor. > 2. Open separate palette. Make sure that it works. > 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. > 4. Make sure that Palette does not work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20110) Batch Diagram silently closes Palette view

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20110?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-20110: ------------------------------------------ Description: Case 1: 1. Open Studio. 2. Open Palette. 3. Open some batch job xml file. FAIL: Palette is silently closed. The code that does it, is commented with {code} /** * This is a workaround that ensures that the flyout pallete (inner * composite inside the diagram editor) is used instead of a separate * pallete view. The separate pallete view does not work with the diagram * editor currently. */ {code} This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace. There is another case when this silent close does not work. Case 2: 1. Open some batch job xml file. 2. Open Palette view. 3. Test work with the separate palette. 4. Close/Restart Eclipse. 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it) 6. Test work with the separate palette. [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it. Separate Palette view does not work with Batch diagram in this usecase: 1. Open batch job editor. 2. Open separate palette. Make sure that it works. 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. 4. Make sure that Palette does not work. was: Case 1: 1. Open Studio. 2. Open Palette. 3. Open some batch job xml file. FAIL: Palette is silently closed. The code that does it, is commented with {code} /** * This is a workaround that ensures that the flyout pallete (inner * composite inside the diagram editor) is used instead of a separate * pallete view. The separate pallete view does not work with the diagram * editor currently. */ {code} This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace. There is another case when this silent close does not work. Case 2: 1. Open some batch job xml file. 2. Open Palette view. 3. Test work with the separate palette. 4. Close/Restart Eclipse. 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it) 6. Test work with the separate palette. [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it. > Batch Diagram silently closes Palette view > ------------------------------------------ > > Key: JBIDE-20110 > URL: https://issues.jboss.org/browse/JBIDE-20110 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > > Case 1: > 1. Open Studio. > 2. Open Palette. > 3. Open some batch job xml file. > FAIL: Palette is silently closed. > The code that does it, is commented with > {code} > /** > * This is a workaround that ensures that the flyout pallete (inner > * composite inside the diagram editor) is used instead of a separate > * pallete view. The separate pallete view does not work with the diagram > * editor currently. > */ > {code} > This is a very bad workaround, since with other editors, e.g. for html5 files, Palette view is critical, and we even suggest in a dialog opening it, but only once for a workspace. > There is another case when this silent close does not work. > Case 2: > 1. Open some batch job xml file. > 2. Open Palette view. > 3. Test work with the separate palette. > 4. Close/Restart Eclipse. > 5. Both job xml file editor and Palette view are open. (That may be considered as a bug of the 'workaround', but now it gives the opportunity to test seprate palette without reopening it) > 6. Test work with the separate palette. > [~ljelinko], could you please study if there are differences when working with inner and separate palette instances? It is very easy to turn off the workaround, the main efforts are to find what failures may happen without it. > Separate Palette view does not work with Batch diagram in this usecase: > 1. Open batch job editor. > 2. Open separate palette. Make sure that it works. > 3. Create Flow element on Diagram. Select it and use right click action 'Open Flow'. > 4. Make sure that Palette does not work. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3460) Line numbers should be shown in text editors by default

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3460?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3460: -------------------------------- Story Points: 1 Sprint: Sprint #6 July 2015 > Line numbers should be shown in text editors by default > ------------------------------------------------------- > > Key: JBDS-3460 > URL: https://issues.jboss.org/browse/JBDS-3460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Eclipse use by default shown line numbers for text editors (e.g. Java classes). But our developer studio has line numbers hidden by default. I remember there was some questionnarie some time ago but unfortunately I do not remember results from it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3460) Line numbers should be shown in text editors by default

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3460?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3460: ------------------------------------- This should be done in plugin_customization.ini. > Line numbers should be shown in text editors by default > ------------------------------------------------------- > > Key: JBDS-3460 > URL: https://issues.jboss.org/browse/JBDS-3460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Marián Labuda > Assignee: Max Rydahl Andersen > Fix For: 9.0.0.Beta2 > > > Eclipse use by default shown line numbers for text editors (e.g. Java classes). But our developer studio has line numbers hidden by default. I remember there was some questionnarie some time ago but unfortunately I do not remember results from it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3460) Line numbers should be shown in text editors by default

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3460?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3460: ----------------------------------- Assignee: Denis Golovin (was: Max Rydahl Andersen) > Line numbers should be shown in text editors by default > ------------------------------------------------------- > > Key: JBDS-3460 > URL: https://issues.jboss.org/browse/JBDS-3460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build, installer > Affects Versions: 9.0.0.Beta1 > Reporter: Marián Labuda > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > > Eclipse use by default shown line numbers for text editors (e.g. Java classes). But our developer studio has line numbers hidden by default. I remember there was some questionnarie some time ago but unfortunately I do not remember results from it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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 June 2015