July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20226) jst/jsf New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20226?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20226: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Beta2 > ------------------------------------------ > > Key: JBIDE-20226 > URL: https://issues.jboss.org/browse/JBIDE-20226 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] 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 jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20241) Usage Analytics New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20241?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20241. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected No N&N for Beta2 > Usage Analytics New and Noteworthy for 4.3.0.Beta2 > -------------------------------------------------- > > Key: JBIDE-20241 > URL: https://issues.jboss.org/browse/JBIDE-20241 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] 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 Usage Analytics is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Usage Analytics 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20235) CDI New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20235?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20235. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected No N&N for Beta2 > CDI New and Noteworthy for 4.3.0.Beta2 > -------------------------------------- > > Key: JBIDE-20235 > URL: https://issues.jboss.org/browse/JBIDE-20235 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] 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 CDI is not listed here check if there are issues that should be added and add them. > Document the ones relevant for CDI 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20230) Seam New and Noteworthy for 4.3.0.Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20230?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20230. ---------------------------------- Assignee: Alexey Kazakov Resolution: Rejected No N&N for Beta2 > Seam New and Noteworthy for 4.3.0.Beta2 > --------------------------------------- > > Key: JBIDE-20230 > URL: https://issues.jboss.org/browse/JBIDE-20230 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: seam2 > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Beta2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] 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 Seam is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Seam 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20222: ---------------------------------- Fix Version/s: 4.3.0.CR1 > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.0.CR1 > > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. > !inner_type_issue.png! > In this case Type is a Enum in Target: > {code} > public class Target { > public static enum Type { > Remote, Managed, Embedded > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20222: ---------------------------------- Affects Version/s: 4.3.0.Beta1 > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.0.CR1 > > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. > !inner_type_issue.png! > In this case Type is a Enum in Target: > {code} > public class Target { > public static enum Type { > Remote, Managed, Embedded > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-42?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-42: ---------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-locus/pull/43 (was: 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20222) "Create Deployment Method" gets confused when dependent is a Inner Type

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20222?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20222: ------------------------------------- Assignee: Snjezana Peco > "Create Deployment Method" gets confused when dependent is a Inner Type > ----------------------------------------------------------------------- > > Key: JBIDE-20222 > URL: https://issues.jboss.org/browse/JBIDE-20222 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Attachments: inner_type_issue.png > > > When adding a class that depends on a Inner Class the generate deployment logic tries to add it twice; > * Once as the parent Type > * Once as the Inner Type > But it still warns that the Inner Type is not included in the Deployment. > !inner_type_issue.png! > In this case Type is a Enum in Target: > {code} > public class Target { > public static enum Type { > Remote, Managed, Embedded > } > } > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20220) Arquillian Cruiser: Support Working Sets as top level

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20220?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-20220: ------------------------------------- Assignee: Snjezana Peco > Arquillian Cruiser: Support Working Sets as top level > ----------------------------------------------------- > > Key: JBIDE-20220 > URL: https://issues.jboss.org/browse/JBIDE-20220 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.0.CR1 > > > Currently Cruiser will only scan current Project and children for Arquillian Test Classes. In some cases it would be useful, where multiple Project are logically bound to a single Working Set, to show all Projects within that set when current selected context is the Working Set. This would make it easy to browse all Arquillian Tests and their deployments within a multi module project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20220) Arquillian Cruiser: Support Working Sets as top level

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20220?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20220: ---------------------------------- Fix Version/s: 4.3.0.CR1 > Arquillian Cruiser: Support Working Sets as top level > ----------------------------------------------------- > > Key: JBIDE-20220 > URL: https://issues.jboss.org/browse/JBIDE-20220 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Affects Versions: 4.3.0.Beta1 > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.0.CR1 > > > Currently Cruiser will only scan current Project and children for Arquillian Test Classes. In some cases it would be useful, where multiple Project are logically bound to a single Working Set, to show all Projects within that set when current selected context is the Working Set. This would make it easy to browse all Arquillian Tests and their deployments within a multi module project. -- 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 July 2015