August 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15386) Resolve values in annotations given by expressions

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15386: --------------------------------------------- Summary: Resolve values in annotations given by expressions Key: JBIDE-15386 URL: https://issues.jboss.org/browse/JBIDE-15386 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: CDI Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 Currently supported are references to constants, class names, strings and numerals. For annotation Priority, CDI specification suggests predefined constants as well as pattern for usage: {code} @Priority(APPLICATION+100) {code} We have to support such simple expressions. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15385) Support annotation @Priority

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-15385: --------------------------------------------- Summary: Support annotation @Priority Key: JBIDE-15385 URL: https://issues.jboss.org/browse/JBIDE-15385 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: CDI Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.2.0.Alpha1 An alternative can be annotated with Priority. {code} @Alternative @Priority(APPLICATION+100) public class MockAsynchronousService extends AsynchronousService { ... } {code} That makes it enabled without declaring it in beans.xml. Value of Priority is used to resolve ambiguous dependencies. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2737) Archive old JBDS docs on devstudio.jboss.com

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2737?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2737: --------------------------------------- Looks good. Thanks for fixing that [~nickboldt]. > Archive old JBDS docs on devstudio.jboss.com > --------------------------------------------- > > Key: JBDS-2737 > URL: https://issues.jboss.org/browse/JBDS-2737 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: documentation > Affects Versions: 3.0.1.GA, 4.0.1.GA, 4.1.3.GA, 5.0.2.GA, 6.0.0.GA, 7.0.0.GA > Reporter: Nick Boldt > Assignee: Michelle Murray > Fix For: 7.0.0.GA > > Attachments: JBDS2737_draft-css.png, JBDS2737_final.png > > > This is a workaround for https://bugzilla.redhat.com/show_bug.cgi?id=983934 because it's easier to download the internet (apparently) than to fix portal code. *sigh* > Docs will be posted to devstudio.jboss.com/site/documentation/ as they include absolute path references. > _Hack: 1. Proper solution: 0._ -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15381: ------------------------------------------ Description: If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. Test with archive. 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest 2. Open class test.a.Test 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed. 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that). Test with sources. 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed. 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java). 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package. 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class. was: If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. Test with archive. 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest 2. Open class test.a.Test 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed. 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that). Test with sources. 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed. 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed. 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package. 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class. > Support annotation @Vetoed > -------------------------- > > Key: JBIDE-15381 > URL: https://issues.jboss.org/browse/JBIDE-15381 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: CDI > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. > Test with archive. > 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest > 2. Open class test.a.Test > 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed. > 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that). > Test with sources. > 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1 > 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections > 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed. > 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java). > 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package. > 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15381: ------------------------------------------ Description: If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. Test with archive. 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest 2. Open class test.a.Test 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed. 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that). Test with sources. 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed. 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed. 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package. 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class. was: If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. > Support annotation @Vetoed > -------------------------- > > Key: JBIDE-15381 > URL: https://issues.jboss.org/browse/JBIDE-15381 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: CDI > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans. > Test with archive. > 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest > 2. Open class test.a.Test > 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed. > 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that). > Test with sources. > 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1 > 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections > 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed. > 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed. > 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package. > 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15384) CLONE - content assist for filenames in html

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-15384: -------------------------------------- Summary: CLONE - content assist for filenames in html Key: JBIDE-15384 URL: https://issues.jboss.org/browse/JBIDE-15384 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml/html source editing Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.Alpha1 given <script type="text/javascript" src="|"></script> and app.js, lib/angular.js exists relative to the file being edited. then content assist at | should offer app.js and lib/angular.js as options. given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15384) CLONE - content assist for filenames in html

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15384?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-15384: ----------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.2.0.Alpha1) > CLONE - content assist for filenames in html > -------------------------------------------- > > Key: JBIDE-15384 > URL: https://issues.jboss.org/browse/JBIDE-15384 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.1.1.Alpha1 > > > given > <script type="text/javascript" src="|"></script> > and app.js, lib/angular.js exists relative to the file being edited. > then content assist at | should offer app.js and lib/angular.js as options. > given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15368) jbosstools-server has API Compatibility problem

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15368: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 > jbosstools-server has API Compatibility problem > ----------------------------------------------- > > Key: JBIDE-15368 > URL: https://issues.jboss.org/browse/JBIDE-15368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Priority: Blocker > Labels: api-compatibility > Fix For: 4.1.1.Alpha1 > > > Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: > "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". > According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 > || Interface change || Conditions || Compatibility || > |Add API field|If interface not implementable by Clients | Binary compatible| > |Add API field|If interface implementable by Clients| Breaks compatibility (2)| > (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14526) Add 'quick fix' to 'warning missing deployment method'

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14526?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14526: --------------------------------------- The PR applied to the master and jbosstols-4.1.x branch. > Add 'quick fix' to 'warning missing deployment method' > ------------------------------------------------------ > > Key: JBIDE-14526 > URL: https://issues.jboss.org/browse/JBIDE-14526 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Given no deployment method > When 'warning missing deployment method' > Then add 'quick fix' open to 'generate deployment method' -- 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

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14526) Add 'quick fix' to 'warning missing deployment method'

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14526?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14526: ---------------------------------- Fix Version/s: 4.1.1.Final 4.2.0.Alpha1 (was: 4.1.x) (was: 4.2.x) > Add 'quick fix' to 'warning missing deployment method' > ------------------------------------------------------ > > Key: JBIDE-14526 > URL: https://issues.jboss.org/browse/JBIDE-14526 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > Given no deployment method > When 'warning missing deployment method' > Then add 'quick fix' open to 'generate deployment method' -- 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

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2013