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 commented on JBIDE-15384: ---------------------------------------- >From JBIDE-15349: Content assist works for full path and for file names: http://www.screenr.com/rQOH It works for: {code} <script src="*.js"> <link rel="stylesheet" href="*.css"> <img src="image files"> <video src="video files"> <audio src="audio filse"> <source src="video or audio depending on the parent element"> <a href="html files"> {code} > 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

11 years, 3 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: ---------------------------------- The "TP + aggregate" zip is now overwriting the Tycho-generated one since having both artifacts seems unnecessary. Build and promote jobs should work even if we decide we want to have both artifacts after all. > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2623: ---------------------------------- Also gives us the option to provide a zip of the 3rd party Central content for offline install (except for Android and JRebel). > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2715) provide script & instructions for performing headless commandline installations of JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2715?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2715: ---------------------------------- Offline users sometimes want to be able to script installation of JBDS and roll it out to many users. Combine that with a desire to install other third party plugins (eg., JBoss Tools into Eclipse, JBDS into Eclipse, or other stuff into JBDS), which we've already scripted [1], [2], and you get a lot of power in being able to administer JBDS installations within a company. [1] https://www.jboss.org/tools/download/installation/update_4_1#fromscript [2] http://download.jboss.org/jbosstools/updates/scripted-installation/README... > provide script & instructions for performing headless commandline installations of JBDS > --------------------------------------------------------------------------------------- > > Key: JBDS-2715 > URL: https://issues.jboss.org/browse/JBDS-2715 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > > Script for linux: > https://gist.github.com/nickboldt/6041754 > Need a windows version & then to provide this somewhere along w/ the JBDS installer, perhaps on the CSP / EA pages? -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14531) Error 'Pack must be specified'

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14531?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14531: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Error 'Pack must be specified' > ------------------------------ > > Key: JBIDE-14531 > URL: https://issues.jboss.org/browse/JBIDE-14531 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > {code} > @RunWith(Arquillian.class) > public class ManagerTest > { > @Deployment > public static Archive<?> createDeployment() > { > JavaArchive archive = ShrinkWrap.create(JavaArchive.class, "test.jar") > .addPackage(ManagerTest.class.getPackage()); > return archive; > } > } > {code} > Warning from ShrinkWrap: Packt must be specified > Probably something wrong with the context the deployment method is executed in. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14779) 'Generate deployment method' add Archive Type 'rar'

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14779?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14779: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > 'Generate deployment method' add Archive Type 'rar' > --------------------------------------------------- > > Key: JBIDE-14779 > URL: https://issues.jboss.org/browse/JBIDE-14779 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > *Given* > Generate Deployment Method Dialog > *When* > Selecting Archive Type > *Then* > Show all known EE Archive types > *Expected* > JavaArchive, WebArchive, EnterpriseArchive and ResourceAdapterArchive > *Actual* > ResourceAdapterArchive is missing -- 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

11 years, 3 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: --------------------------------------- {quote} A) please add steps on how this can be tested. B) provide info on how it looks (screenshot or descripton) {quote} - create an Arquillian JUnit test without a deployment method - click the quick fix on the test class There is also the GenerateDeploymenMethodMarkerResolutionTest JUnit test See http://screencast.com/t/xENx8b6sn {quote} C) 4.1.x pushes should get peer reviewed. {quote} I have already pushed several PRs/jiras to the jbosstools-4.1.x branch: https://issues.jboss.org/browse/JBIDE-14527 https://issues.jboss.org/browse/JBIDE-14779 https://issues.jboss.org/browse/JBIDE-14430 https://issues.jboss.org/browse/JBIDE-15328 https://issues.jboss.org/browse/JBIDE-14531 Each PR includes a JUnit test. I have changed the fix version from 4.1.1.Final to 4.1.1.Alpha1. > 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.Alpha1, 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2746) On a Full Publish LiveReload refreshes the browser before the application is fully restarted

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2746?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2746: ---------------------------------- [~pmuir] Please provide more information, details, version of JBDS used, screenshot, etc. Also, did you really mean to set this to target JBDS 3.0.2.GA? Pretty sure there was no LiveReload before JBDS 7. > On a Full Publish LiveReload refreshes the browser before the application is fully restarted > -------------------------------------------------------------------------------------------- > > Key: JBDS-2746 > URL: https://issues.jboss.org/browse/JBDS-2746 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build > Reporter: Pete Muir > > I can't quite tell if the same problem exists for Incremental Publish. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15328) Fixing Arquillian tests

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15328?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-15328: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Fixing Arquillian tests > ----------------------- > > Key: JBIDE-15328 > URL: https://issues.jboss.org/browse/JBIDE-15328 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.0.Final > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > There are two issues: > 1) The CreateDeploymentMethodTest test, introduced by JBIDE-14779, isn't included into the build > 2) The CheckArquillianModificationsTest test, introduced by JBIDE-15030, creates, but doesn't remove a project. The project can't be removed because the test opens, but doesn't close an inputstream. -- 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14430) Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ?

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14430?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14430: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > Run as arquillian seem to *always* ask for there being exactly one implementation of DeploymentContainer - can't it detect it ? > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14430 > URL: https://issues.jboss.org/browse/JBIDE-14430 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > can't we detect if there is more than one DeploymentContainer for Run As > Arquillian test or is that too slow ? > Or at least show which profile is enabled or something to give user an idea what he is currently running with. -- 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

11 years, 3 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