[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2710:
---------------------------------------
[Docs] No impact on docs.
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: respin-a
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.2.1.v20130402 - JBIDE-13682
> * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
> * pmd/4.0.0.v20130510-1000 - JBIDE-14902
> * SpringSource's Quick Search - JBDS-2686 *TBD*
> * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ - JBDS-2415
> * VJET 0.10 - JBIDE-14764
> These are currently unchanged since December when we released JBDS 6.0.0:
> * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
> * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
> Additionally (Target Platform):
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues do not block the release of JBDS 7.0.1.GA.
--
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
[JBoss JIRA] (JBDS-2457) Mirror stable content on Akamai
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2457?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2457:
---------------------------------------
Docs Q: I am assuming this will have no impact on users. Please correct me if I am wrong.
> Mirror stable content on Akamai
> -------------------------------
>
> Key: JBDS-2457
> URL: https://issues.jboss.org/browse/JBDS-2457
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: updatesite
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 7.1.0.Alpha1
>
>
> In order to improve installation time (for both end-users and internal build/test usage), we should use Akamai on the stable folders if devstudio downloas site.
--
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
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Michelle Murray commented on JBDS-2623:
---------------------------------------
Docs Q: Is this going to change what users need to do in any way? Or is it all behind the scenes improvements?
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Central, updatesite, Upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.x
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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
[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
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months
[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
12 years, 7 months