April 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17210) where is our nightly site OR why is nightly site not actually built regularly?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17210?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17210: ---------------------------------------- [I can access VPN easily right now...] So http://download.jboss.org/jbosstools/updates/nightly/core/master is up-to-date or not? If so, it is probably an optimization of the publish script (that I believe tries to avoid republishing stuff when there is no actual change in the various sites) that detected that the last 6 aggregations didn't contain any new artifact and weren't worth being published. However, the publish scripts are mainly maintained by [~nickboldt] so he may have a more precise answer. {quote}build 8748 was back in March 31 and build is now at build 8754 - there have only been 6 builds for close to a month.{quote} 6 builds in a month for aggregator may not be a mistake. Indeed, if most changed were pushed in a tight timeframe, then they only trigger a single aggregation. I don't think 6 builds in a month are a symptom of something bad. But maybe I'm missing something. > where is our nightly site OR why is nightly site not actually built regularly? > ------------------------------------------------------------------------------ > > Key: JBIDE-17210 > URL: https://issues.jboss.org/browse/JBIDE-17210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > > http://download.jboss.org/jbosstools/updates/nightly/core/master > our official "nightly" updatesite has not been rebuilt for ~6 days at the time of writing. > see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > Why is this ? > Is there another site that can be used as "nightly" ? i.e. one that just composites instead of aggregates ? > p.s. i'm going to kick of a build so we get some fixes into the nightly. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16885: ------------------------------------- Steps to Reproduce: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url !wrong_button_accessibility.png! # EXEC: check another cartridge (ex. mysql-5.5) Result: *Finish* is enabled even though the *Code Anything* cartridge is missing the url !wrong_button_accessibility2.png! Also: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a *(star) to show that the user has to provide an url # EXEC: uncheck *Code Anything* Result: *Finish* should get enabled since we're not adding the *Code Anything* cartridge was: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a * to show that the user has to provide an url # EXEC: check another cartridge (ex. mysql-5.5) Result: *Finish* is enabled even though the *Code Anything* cartridge is missing the url Also: # ASSERT: have an application running on OpenShift # EXEC: OpenShift Explorer: select "Edit Embedded Cartridges" from the context menu # EXEC: check "Code Anything" # ASSERT: "Finish" is disabled, URL text field is decorated with a * to show that the user has to provide an url # EXEC: uncheck *Code Anything* Result: *Finish* should get enabled since we're not adding the *Code Anything* cartridge > Embed wizard: Can provide "Code Anything" without url, should not be able to > ---------------------------------------------------------------------------- > > Key: JBIDE-16885 > URL: https://issues.jboss.org/browse/JBIDE-16885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: embed_wizard > Fix For: 4.2.0.Beta2 > > Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png > > > In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). > Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16885: ------------------------------------- Attachment: wrong_button_accessibility2.png > Embed wizard: Can provide "Code Anything" without url, should not be able to > ---------------------------------------------------------------------------- > > Key: JBIDE-16885 > URL: https://issues.jboss.org/browse/JBIDE-16885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: embed_wizard > Fix For: 4.2.0.Beta2 > > Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png, wrong_button_accessibility2.png > > > In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). > Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16626: ------------------------------------------ Since this seems not utterly urgent and tons of things to do for the "other" binary deployment (snapshot, deploy) I'll postpone this to 4.2.x > OpenShift Server Adapter: Binary deployment > ------------------------------------------- > > Key: JBIDE-16626 > URL: https://issues.jboss.org/browse/JBIDE-16626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final, 4.2.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment. > Current workflow is following: > PRESTEPS: > 1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application) > 2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers... > 3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge). > 4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index) > 5. Push application to OpenShift (e.g. context menu of application - Team - Commit...) > BINARY DEPLOYMENT > 1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title). > 2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is built in deployment folder as ROOT.war. > 3. Add ROOT.war to git index (context menu - Team - Add to index) > 4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter. > 5. Confirm push. > My idea of binary deployment is: > 1. User change something in application > 2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index. > 3. Confirm to push. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16626) OpenShift Server Adapter: Binary deployment

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16626: ------------------------------------- Fix Version/s: 4.2.x > OpenShift Server Adapter: Binary deployment > ------------------------------------------- > > Key: JBIDE-16626 > URL: https://issues.jboss.org/browse/JBIDE-16626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final, 4.2.0.Alpha2 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > At first, I am not sure whether this is bug or desired behaviour (in that case this issue is Enhancement). There is a problem with binary deployment. > Current workflow is following: > PRESTEPS: > 1. Create OpenShift application (e.g. EAP through OpenShift explorer, context menu, new application) > 2. Open Project Explorer, select application and open context menu OpenShift - Configure Markers... > 3. Select disable maven build marker. You can select also Hot deploy to improve deploying speed (no need to restart cartridge). > 4. Open Navigator - .openshift - markers and select new markers and add them to Index (context menu - Team - Add to Index) > 5. Push application to OpenShift (e.g. context menu of application - Team - Commit...) > BINARY DEPLOYMENT > 1. Now imagine, you want to binary deploy. Let's say, user change something in index.html (for example title). > 2. Then it's required to locally build application (context menu of application - Run as - Maven build and set goal "clean package -Popenshift"). Result - application is built in deployment folder as ROOT.war. > 3. Add ROOT.war to git index (context menu - Team - Add to index) > 4. Drag and drop application from Project Explorer to Servers view adapter onto the given OpenShift adapter. > 5. Confirm push. > My idea of binary deployment is: > 1. User change something in application > 2. Drag and drop application from Project Explorer to Servers view onto OpenShift adapter - this step build application, add ROOT.war to index. > 3. Confirm to push. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17032) Ability to configure jQuery / jQuery Mobile versions injected by Palette

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17032?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-17032: ----------------------------------------- [~maxandersen], yes, you're right. I must admit I got carried away with the idea of managing JS dependencies in a build system, just like in Maven. We should still support users who won't use Bower with Maven. > Ability to configure jQuery / jQuery Mobile versions injected by Palette > ------------------------------------------------------------------------ > > Key: JBIDE-17032 > URL: https://issues.jboss.org/browse/JBIDE-17032 > 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.2.0.Beta2 > > Attachments: 2014-04-25 17.02.bmml, 2014-04-25 17.02.bmml, 2014-04-25 17.02.png, SeparateDialog.bmml, SeparateDialog.png > > > Currently the following versions are injected for JQM 1.4: > {code} > <script src="http://code.jquery.com/jquery-1.10.2.min.js"></script> > <script src="http://code.jquery.com/mobile/1.4.2/jquery.mobile-1.4.2.min.js"></script> > {code} > And for JQM 1.3: > {code} > <script src="http://code.jquery.com/jquery-1.9.1.min.js"></script> > <script src="http://code.jquery.com/mobile/1.3.2/jquery.mobile-1.3.2.min.js"></script> > {code} > It would be good if we have a place where users can configure what versions of JQ and JQM they want to inject. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-273) Fix blog link for JBTIS 4.1.4.Final in jbosstools-website

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-273?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-273: ---------------------------------- This corrects the blog urls https://github.com/jbosstools/jbosstools-website/pull/124 > Fix blog link for JBTIS 4.1.4.Final in jbosstools-website > --------------------------------------------------------- > > Key: JBTIS-273 > URL: https://issues.jboss.org/browse/JBTIS-273 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 4.1.4.Final > Reporter: Paul Leacu > Assignee: Paul Leacu > > Fix blog link for JBTIS 4.1.4.Final in jbosstools-website -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17215) DownloadRuntime cannot discover root of tar.gz or .tar files

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17215?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-17215. --------------------------------- Assignee: Rob Stryker Release Notes Text: pushed to master. Fix Version/s: 4.2.0.Beta2 Resolution: Done > DownloadRuntime cannot discover root of tar.gz or .tar files > ------------------------------------------------------------ > > Key: JBIDE-17215 > URL: https://issues.jboss.org/browse/JBIDE-17215 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta2 > > > Now that downloadruntimes can download and unzip .tar.gz files, it also needs to be able to properly point to the new root folder of the unzipped location. So if a .tar.gz file is /home/rob/tmp/some.tar.gz, and it expands to /home/rob/tmp/my-app-version-2.3.0/ with all files under that, it should correctly identify that new folder as the root of the unzipped archive. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2778) Support New Binary Deployment mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2778?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2778: ---------------------------------------- [~edrich] according to Andy Goldstein there are actually 2 different types of snapshots: Mail from Andy Goldstein on the 29th of April (subject: OpenShift Plugin *Binary Deployment Workflow*) {quote} There are 2 types of snapshots: full gear snapshots, and binary deployment snapshots. Full gear snapshots are created using 'rhc snapshot save' and they include additional things such as the contents of app-root/data. Binary deployment snapshots are created using 'rhc snapshot save --deployment'. This form creates a tarball suitable for binary deployments. {quote} So it looks like what you're after is JBIDE-10456 > Support New Binary Deployment mode > ---------------------------------- > > Key: JBDS-2778 > URL: https://issues.jboss.org/browse/JBDS-2778 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 8.0.0.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

11 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16885) Embed wizard: Can provide "Code Anything" without url, should not be able to

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16885?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16885: ------------------------------------- Attachment: wrong_button_accessibility.png > Embed wizard: Can provide "Code Anything" without url, should not be able to > ---------------------------------------------------------------------------- > > Key: JBIDE-16885 > URL: https://issues.jboss.org/browse/JBIDE-16885 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: embed_wizard > Fix For: 4.2.0.Beta2 > > Attachments: wrong_button_accessibility.png, wrong_button_accessibility.png, wrong_button_accessibility2.png > > > In the wizard to edit the embeddable cartridges there is "Code Anything" cartridge which requires URL of cartridge. If user just selects and does not check this cartridge, it is not possible to hit the OK button (see attached screen wrong_button_accessibility). > Also if user check this cartridge but select another one without providing URL to the Code anything cartridge, it is possible to hit the OK button (it should not be - see attached screenshot wrong_button_accessibility2.) -- 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, 11 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 April 2014