August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15351) Implement bean discovery in explicit and implicit archives

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15351?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15351: ------------------------------------------ Description: http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive 1. Create CDI 1.1 project. 2. Create other CDI 1.1 projects and export them to jars or to class folders, these projects may vary in beans.xml: - no beans.xml - empty beans.xml - beans.xml with 1.0 schema - beans.xml with 1.1 schema and all possible values of bean-discovery-mode attribute ("annotated"/"none"/"all") and have classes with and without scope declaration. 3. Add these archives to classpath of project (1). 4. Create a bean with injections to types defined in the archives. 5. Check that injection is satisfied or not according to bean discovery rules given by specification. Examples: - Archive has no beans.xml: only annotated beans will be resolved; - Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved; - Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute. was: http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive 1. Create CDI 1.1 project. 2. Create other CDI 1.1 projects and export them to jars or to class folders, these projects may vary in beans.xml: - no beans.xml - empty beans.xml - beans.xml with 1.0 schema - beans.xml with 1.1 schema and all possible values of bean-discovery-mode attribute ("annotated"/"none"/"all") and have classes with and without scope declaration. 3. Add these archives to classpath of project (1). 4. Create a bean with injections to types defined in the archives. 5. Check that injection is satisfied or not according to bean discovery rules given by specification. Examples: - Archive has no beans.xml: only annotated beans will be resolved; - Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved; - Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute. > Implement bean discovery in explicit and implicit archives > ----------------------------------------------------------- > > Key: JBIDE-15351 > URL: https://issues.jboss.org/browse/JBIDE-15351 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: CDI > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.Alpha1 > > > http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive > 1. Create CDI 1.1 project. > 2. Create other CDI 1.1 projects and export them to jars or to class folders, > these projects may vary in beans.xml: > - no beans.xml > - empty beans.xml > - beans.xml with 1.0 schema > - beans.xml with 1.1 schema and all possible values > of bean-discovery-mode attribute ("annotated"/"none"/"all") > and have classes with and without scope declaration. > 3. Add these archives to classpath of project (1). > 4. Create a bean with injections to types defined in the archives. > 5. Check that injection is satisfied or not according to bean discovery rules given by specification. > Examples: > - Archive has no beans.xml: only annotated beans will be resolved; > - Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved; > - Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15351) Implement bean discovery in explicit and implicit archives

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15351: --------------------------------------------- Summary: Implement bean discovery in explicit and implicit archives Key: JBIDE-15351 URL: https://issues.jboss.org/browse/JBIDE-15351 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: CDI Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 http://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#bean_archive 1. Create CDI 1.1 project. 2. Create other CDI 1.1 projects and export them to jars or to class folders, these projects may vary in beans.xml: - no beans.xml - empty beans.xml - beans.xml with 1.0 schema - beans.xml with 1.1 schema and all possible values of bean-discovery-mode attribute ("annotated"/"none"/"all") and have classes with and without scope declaration. 3. Add these archives to classpath of project (1). 4. Create a bean with injections to types defined in the archives. 5. Check that injection is satisfied or not according to bean discovery rules given by specification. Examples: - Archive has no beans.xml: only annotated beans will be resolved; - Archive has empty beans.xml, or beans.xml with 1.0 schema: all beans will be resolved; - Archive has beans.xml with version 1.1: beans will be resolved according to the value of bean-discovery-attribute. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15350) Using JBoss Tools Properties Editor, breaks the format (or removes) multiline property value

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15350?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-15350 at 8/16/13 6:55 PM: ------------------------------------------------------------------------ Yes, JBoss Tools Properties editor is currently based on java.util.Properties. It does not support multiple values and it does not support the kind of comments presented in the first snippet in description. JBIDE-3833 was not about multiple values, but only about multiline value, and it was resolved with supporting all reasonable cases of splitting value to several lines that we could think of. Still, it can be tricked as in your example. If you rewrite the entry as {code} # # # JQuery scripts # javascript.files=\ jquery.js,\ j2browse.js,\ livequery.js {code} it will be preserved even if you edit/add/remove other properties. But, ok, we will continue the work on preventing damage to any file. was (Author: scabanovich): Yes, JBoss Tools Properties editor is currently based on java.util.Properties. It does not support multiple values and it does not support the kind of comments presented in the first snippet in description. JBIDE-3833 was not about multiple values, but only about multiline value, and it was resolved with supporting all reasonable cases of splitting value to several lines that we could think of. Still, it can be tricked as in your example. If you rewrite you entry as {code} # # # JQuery scripts # javascript.files=\ jquery.js,\ j2browse.js,\ livequery.js {code} it will be preserved even if you edit/add/remove other properties. But, ok, we will continue the work on preventing damage to any file. > Using JBoss Tools Properties Editor, breaks the format (or removes) multiline property value > -------------------------------------------------------------------------------------------- > > Key: JBIDE-15350 > URL: https://issues.jboss.org/browse/JBIDE-15350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Final > Reporter: thiago andrade > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > In eclipse juno with JbossTools installed and jboss tools property editor opening my .properties files > when I write in the file some something like > javascript.files=\ > # > # JQuery scripts > # > \ > jquery.js,\ > j2browse.js,\ > livequery.js,\ > it saves the file correctly BUT when I close this file and open it again the jboss tools properties editor parses the file and it becames something like this > javascript.files=\# > # JQuery scripts > # > \ > jquery.js,\ > j2browse.js,\ > livequery.js,\ > That's it. > another error that I've identified is already reported at this link https://issues.jboss.org/browse/JBIDE-3833 BUT this issue is marked as resolved but it is not resolved.. the jboss tools properties editor still removes multiplie values variables from the file when it OPENS the file. > so this: > js.files = util.js > js.files = jquery.meiomask.js > js.files = json2.0.js > becames this: > js.files = json2.0.js > I think that the jboss tools parses the file and removes the multiple.. if the user dont modified the file and save the original file is not changed, but if any change is made to the file it is saved with the modifications made by jboss tools properties editor -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-119) http://download.jboss.org/jbosstools/updates/*/soa-tooling/ should be a symlink to /updates/*/integration-stack/

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-119?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-119: ---------------------------------- http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdsistarget/7.0.0.... is the correct location for the 7.0.0.Final JBDSIS TP. The 6.0.0.GA has been cleaned up. > http://download.jboss.org/jbosstools/updates/*/soa-tooling/ should be a symlink to /updates/*/integration-stack/ > ----------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-119 > URL: https://issues.jboss.org/browse/JBTIS-119 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution, releng > Affects Versions: 4.0.0, 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.1.1 > > > Some vast inconsistencies here: > http://download.jboss.org/jbosstools/updates/stable/juno/soa-tooling/swit... exists > http://download.jboss.org/jbosstools/updates/stable/juno/integration-stac... does not exist > http://download.jboss.org/jbosstools/updates/stable/juno/soa-tooling/ exists but is empty > http://download.jboss.org/jbosstools/updates/stable/juno/integration-stack exists and has content > http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... contains esb and aggregate > http://download.jboss.org/jbosstools/updates/integration/kepler/soa-tooling/ contains fuse > http://download.jboss.org/jbosstools/updates/development/kepler/soa-tooling/ contains teiid > http://download.jboss.org/jbosstools/updates/development/kepler/integrati... contains aggregate -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-138) wrong target name attribute in core-base.target

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-138?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-138: ----------------------------- Assignee: Paul Leacu > wrong target name attribute in core-base.target > ----------------------------------------------- > > Key: JBTIS-138 > URL: https://issues.jboss.org/browse/JBTIS-138 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Priority: Trivial > > Both of these files [1], [2] use the same name attribute, which might confuse a user when they import the .target files into Eclipse. > {code}<target name="integration-stack-base-target">{code} > [1] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-139) ensure that shared categories in JBTIS/JBDSIS update sites / Central discovery plugin use same categories as in JBT/JBDS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-139?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-139: ----------------------------- Assignee: Paul Leacu > ensure that shared categories in JBTIS/JBDSIS update sites / Central discovery plugin use same categories as in JBT/JBDS > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-139 > URL: https://issues.jboss.org/browse/JBTIS-139 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Per discussion today, we need to ensure that any features in JBTIS or JBDSIS which need to be categorized into existing JBT or JBDS categories (update site + Central) will appear correctly, and in the existing JBT / JBDS categories. > To make sure this is the case, you'll want to diff your aggregate update site's category.xml (look for matching <category-def>) and discovery plugin's plugin.xml (look for <connectorCategory>) files with these equivalent files from JBT/JBDS: > Master branch: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/categ... > https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools... > https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... > 4.1.x branch: > https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.... > https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.1.x/... > https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.x/... > https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.x/... -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-144) change discovery labels to match core (+ JBoss Business Process and Rules Development, etc)

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-144?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-144. ---------------------------- Resolution: Duplicate Issue dupl 139 > change discovery labels to match core (+ JBoss Business Process and Rules Development, etc) > ------------------------------------------------------------------------------------------- > > Key: JBTIS-144 > URL: https://issues.jboss.org/browse/JBTIS-144 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.1.2 > Reporter: Paul Leacu > Assignee: Paul Leacu > > check what the current core labels are -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-144) change discovery labels to match core (+ JBoss Business Process and Rules Development, etc)

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-144: -------------------------------- Summary: change discovery labels to match core (+ JBoss Business Process and Rules Development, etc) Key: JBTIS-144 URL: https://issues.jboss.org/browse/JBTIS-144 Project: JBoss Tools Integration Stack Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 4.1.2 Reporter: Paul Leacu Assignee: Paul Leacu check what the current core labels are -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15350) Using JBoss Tools Properties Editor, breaks the format (or removes) multiline property value

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15350?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15350: ----------------------------------------------- Yes, JBoss Tools Properties editor is currently based on java.util.Properties. It does not support multiple values and it does not support the kind of comments presented in the first snippet in description. JBIDE-3833 was not about multiple values, but only about multiline value, and it was resolved with supporting all reasonable cases of splitting value to several lines that we could think of. Still, it can be tricked as in your example. If you rewrite you entry as {code} # # # JQuery scripts # javascript.files=\ jquery.js,\ j2browse.js,\ livequery.js {code} it will be preserved even if you edit/add/remove other properties. But, ok, we will continue the work on preventing damage to any file. > Using JBoss Tools Properties Editor, breaks the format (or removes) multiline property value > -------------------------------------------------------------------------------------------- > > Key: JBIDE-15350 > URL: https://issues.jboss.org/browse/JBIDE-15350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.1.0.Final > Reporter: thiago andrade > Assignee: Viacheslav Kabanovich > Fix For: 4.2.x > > > In eclipse juno with JbossTools installed and jboss tools property editor opening my .properties files > when I write in the file some something like > javascript.files=\ > # > # JQuery scripts > # > \ > jquery.js,\ > j2browse.js,\ > livequery.js,\ > it saves the file correctly BUT when I close this file and open it again the jboss tools properties editor parses the file and it becames something like this > javascript.files=\# > # JQuery scripts > # > \ > jquery.js,\ > j2browse.js,\ > livequery.js,\ > That's it. > another error that I've identified is already reported at this link https://issues.jboss.org/browse/JBIDE-3833 BUT this issue is marked as resolved but it is not resolved.. the jboss tools properties editor still removes multiplie values variables from the file when it OPENS the file. > so this: > js.files = util.js > js.files = jquery.meiomask.js > js.files = json2.0.js > becames this: > js.files = json2.0.js > I think that the jboss tools parses the file and removes the multiple.. if the user dont modified the file and save the original file is not changed, but if any change is made to the file it is saved with the modifications made by jboss tools properties editor -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-143) restore fuseide features

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-143?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-143. ------------------------------ Fix Version/s: 4.1.2 Resolution: Done > restore fuseide features > ------------------------ > > Key: JBTIS-143 > URL: https://issues.jboss.org/browse/JBTIS-143 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 4.1.2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.1.2 > > -- 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

12 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 2013