February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3605. ---------------------------- Resolution: Done Should have closed this out a while ago. I've moved out the last two issues as they're now set with fixversion = LATER (or "may never get done, more important things to do"). > Rebranding to developers.redhat.com > ----------------------------------- > > Key: JBDS-3605 > URL: https://issues.jboss.org/browse/JBDS-3605 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: installer, product > Reporter: Max Rydahl Andersen > Assignee: Catherine Robson > Priority: Blocker > Fix For: 10.0.0.Alpha1 > > Attachments: Additional_RHDS_Branding.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, RedHatDevelopersStudio_SplashScreen.zip, RevisedIcons.zip, about-jbds10.png, edit-eap-icon-in-ds10-installer.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, new-eap-icon-in-ds10-installer.png, splash-jbds10.png > > > Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com. > The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms) > Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary. > > This jira will be the epic where we add related issues. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23889: ------------------------------------ Job's back to blue so assigning to you to provide more feedback or close this issue. :D > jbosstools-composite-install_master is a spam bomb > -------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.3.Final > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23889: ---------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > jbosstools-composite-install_master is a spam bomb > -------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.4.3.Final > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22145: -------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.2.AM3) > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22145: ------------------------------------- This probably won't be verified until we start using java9... so I'll just keep pushing it off. > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3951) Installer needs to add the VirtualBox install directory to the PATH

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3951: -------------------------------- Sprint: devex #127 February 2017 (was: devex #126 January 2017) > Installer needs to add the VirtualBox install directory to the PATH > ------------------------------------------------------------------- > > Key: JBDS-3951 > URL: https://issues.jboss.org/browse/JBDS-3951 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Critical > Fix For: 10.3.0.GA > > > The installer does not seem to add the VirtualBox install directory to the PATH variable (at least not with the CDK 2.0 installer). This means the executables in this directory cannot be found. > As part of Windows network setup, I want to call {{VBoxManage.exe}}, but it currently cannot be found. I first have to manually modify the PATH. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1040) Update the logic for checking all available quickstarts in RH Central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1040?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1040: ----------------------------------- Hey [~apodhrad] - sorry - still confused. I do this: 1. Install Devstudio 10.2.0.GA 2. Add the following vm args to devstudio.ini -Djboss.discovery.directory.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/devstudio-directory.xml -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/10.0/staging/updates/integration-stack/discovery/10.1.0.CR2/ 3. Start the Devstudio and open Red Hat Central 4. Type 'fuse' into the text field in the middle of the RH Central (nothing is found) 5. Switch to the tab 'Software/Update' 6. Check 'Enable Early Access' 7. Switch back to the tab 'Getting Started' (now you can see the fuse quickstart) new steps 6. Select 'JBoss Fuse Development' 7. Install it 8. When it restarts into the 'Getting Started' tab - the Fuse quickstarts are available. In your scenario, JBoss Fuse Development still isn't installed, I don't see the Fuse quickstart. I still get nothing found when I perform step 7. If I select 'JBoss Fuse Development' and install it - then go back to 'Getting Started', I see the Fuse quickstarts (without EA enabled). This behavior is as I would expect. Are you using a new workspace? > Update the logic for checking all available quickstarts in RH Central > --------------------------------------------------------------------- > > Key: JBTIS-1040 > URL: https://issues.jboss.org/browse/JBTIS-1040 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 10.1.0.CR1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: rh3.png, rhc1.png, rhc2.png > > > There is again a problem with the Fuse quickstart. Currently, the quickstart is available only if we enable Early Access in RH Central. At the first sight it looks like the behavior is hard coded. > Please update the logic for checking all available quickstarts so that it will detect Fuse quickstart without just checking if the Early Access is enabled or not. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23863) Upgrade Forge Runtime to 3.5.1.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23863?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-23863. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 3.5.1.Final > ------------------------------------ > > Key: JBIDE-23863 > URL: https://issues.jboss.org/browse/JBIDE-23863 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.4.3.AM1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Fix For: 4.4.4.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23889: ------------------------------------ Problem was likely that the Eclipse runtime tar.gz wasn't being found so the job was firing more often to get someone's attention. I've removed the email notifications and reinstated the sleep timer. I don't see more than one email every 3 hours... can you provide details on this 'multiple mails per minutes' event? > jbosstools-composite-install_master is a spam bomb > -------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.3.Final > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master is a spam bomb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23889: ------------------------------- Fix Version/s: 4.4.3.Final (was: 4.4.4.AM1) > jbosstools-composite-install_master is a spam bomb > -------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.3.Final > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017