August 2013 - jbosstools-issues - Jboss List Archives

[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

12 years, 8 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

12 years, 8 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

12 years, 8 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

12 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-158: ---------------------------------- https://github.com/jbosstools/jbosstools-integration-stack/pull/109 merged > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-158: ---------------------------------- Ok - looks good - i installed core first: https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/ then my local standalone into a clean eclipse and all went well. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-158: ---------------------------------- +1 to JBDS IS requiring JBDS. Options for an end user are therefore: 1. Install JBDS or JBDS BYOE from Marketplace 2. Launch JBDS or Eclipse 3. Help > Install > Work With > browse for downloaded JBDS IS zip 4. Install OR 1. Launch Eclipse 2. Help > Install > Work With > browse for downloaded JBDS installer jar or just enter https://devstudio.jboss.com/updates/7.0/ 3. Help > Install > Work With > browse to downloaded JBDS IS zip 4. Install > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install

by Rob Cernich (JIRA)

[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ] Rob Cernich commented on JBTIS-158: ----------------------------------- Paul, the standalone zip has a requirement on JBDS, so for a BYOE install, you'll need to add a site for JBDS core (i.e. you need to add the JBDS core and JBDS IS sites). HTH. > create composite site zip containing JBDS IS + dependencies for easier offline install > -------------------------------------------------------------------------------------- > > Key: JBTIS-158 > URL: https://issues.jboss.org/browse/JBTIS-158 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Rob Cernich > > Suggested by [~rcernich]: > {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like: > {code}./compositeContent.xml > ./compositeArtifacts.xml > ./7.1.0/7.1.0.Beta1-jbds-is/ > ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code} > {quote} > This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site. > If we did a similar thing for JBT IS, it would need to contain these sites: > {code} > JBT webtools aggregate site (not the full JBT aggregate site) > JBT TP > JBT IS > JBT IS TP > {code} > Or, if we assume that users will already have JBT (or some part of it) installed, then we need only: > {code} > JBT IS > JBT IS TP > {code} -- 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, 8 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. was:If class is anotated @Vetoed or if its package is annotated @Vetoed, then it > 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. -- 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, 8 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 > 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 -- 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, 8 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