April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3669: ----------------------------- Attachment: JBDS3669-new-UI.png > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3669: ---------------------------------- After recent refactorings, here's the new process: {code} hub checkout https://github.com/redhat-developer-tooling/developer-platform-install/pu... gulp; gulp package; gulp 7zip-cleanup {code} Of course the same works with a temporary version change applied into the package.json file: {code} npm --no-git-tag-version version 0.0.2-v20160404-1103-B667 gulp package; gulp 7zip-cleanup git checkout package.json # revert temporary change to the version string {code} However, in this case the appended suffix doesn't appear - only the first 3 digits: !JBDS3669-new-UI.png! > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3669) Inject version, timestamp and Jenkins build number into installer to show in installer window

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3669?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3669: ----------------------------- Attachment: JBDS3669-new-UI.png > Inject version, timestamp and Jenkins build number into installer to show in installer window > --------------------------------------------------------------------------------------------- > > Key: JBDS-3669 > URL: https://issues.jboss.org/browse/JBDS-3669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: JBDS3669-new-UI.png, version-string-in-exe-and-first-page-of-installer.png > > > Currently this information is not available in installer at execution time, we should create json or js file with this info before executing the build, include it in installer and use during installation to get required data. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22078) Error publishing war file to wildfy 10.0 on windows

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22078?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22078: ----------------------------------- Assignee: Rob Stryker > Error publishing war file to wildfy 10.0 on windows > --------------------------------------------------- > > Key: JBIDE-22078 > URL: https://issues.jboss.org/browse/JBIDE-22078 > Project: Tools (JBoss Tools) > Issue Type: Bug > 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: Rob Stryker > > 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 (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3755: ----------------------------- Fix Version/s: 9.1.0.GA > JBDS source zip: all files have 000 permissions after unzip > ----------------------------------------------------------- > > Key: JBDS-3755 > URL: https://issues.jboss.org/browse/JBDS-3755 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 9.1.0.GA > > Attachments: readme.png, readme2.png > > > While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem: > When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3755: ---------------------------------- Simplest solution for JBDS 9.1: add a note in the readme telling people they have to chmod the zip's contents before they can run the build. https://github.com/jbdevstudio/jbdevstudio-product/pull/372 For JBDS 10, we'll drop the zip entirely. > JBDS source zip: all files have 000 permissions after unzip > ----------------------------------------------------------- > > Key: JBDS-3755 > URL: https://issues.jboss.org/browse/JBDS-3755 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: readme.png, readme2.png > > > While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem: > When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3755) JBDS source zip: all files have 000 permissions after unzip

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3755?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3755: ----------------------------- Git Pull Request: https://github.com/jbdevstudio/jbdevstudio-product/pull/372 > JBDS source zip: all files have 000 permissions after unzip > ----------------------------------------------------------- > > Key: JBDS-3755 > URL: https://issues.jboss.org/browse/JBDS-3755 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: build > Affects Versions: 9.1.0.CR1 > Reporter: Martin Malina > Assignee: Nick Boldt > Attachments: readme.png, readme2.png > > > While verifying JBDS-3598 and trying to build from the latest source zip (jboss-devstudio-9.1.0.CR1-v20160326-0059-B443-src.zip), I hit a problem: > When I unzipped the zip, I could not cd to the directory. It turned out that all the files had zero permissions. So I had to do "chmod -R 777 jboss-devstudio-9.1.0.CR1-src" first. Could we fix that? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22079) Error when import a project already existing in workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22079?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-22079: ---------------------------------------- Assignee: Andre Dietisheim > Error when import a project already existing in workspace > --------------------------------------------------------- > > Key: JBIDE-22079 > URL: https://issues.jboss.org/browse/JBIDE-22079 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Labels: import_wizard, openshift_v3 > > When I am creating a new OpenShift application using an existing repo, or at least project in workspace, it throws an error upon application creation completion. This is a bit of pain, because even I have an existing git repo and checked the checkbox in Import Wizard to reuse it, it tries to import project then, but it fails. But the existing project is still usable to use it for a new OpenShift 3 server adapter and upon start of the adapter, local changes are published to OpenShift. This issue is just about error. Maybe we could display a dialog that such a project already exists in workspace and let user to choose to replace it by the one being imported or keep it as it is (if user know that the project in workspace is the correct one and he/she does not want to overwrite it and let local changes disappear). > Error: > {code}Could not import project from org.jboss.tools.openshift.internal.common.ui.application.importoperation.ImportFailedException: There was a maven related error that prevented us from importing the project. We encourage you to look into the pom in the cloned repository at /home/mlabuda/git/jboss-eap-quickstarts. > One of the possible reasons is that there is already a project in your workspace that matches the maven name of the OpenShift application. You can then rename your workspace project and start over again. > An exception stack trace is not available. > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21981) Error during rsync

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21981: --------------------------------------- So should we keep this as informative warning? > Error during rsync > ------------------ > > Key: JBIDE-21981 > URL: https://issues.jboss.org/browse/JBIDE-21981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > While testing the debugging support on the server adapter, I got the following error: > {code} > Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy > OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66) > rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9] > error: exit status 23 > {code} > The content of the {{.../deploy}} directory was: > {code} > drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./ > drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../ > -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt > drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/ > -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed > -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying > -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar > -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed > -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21981) Error during rsync

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21981?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21981: ------------------------------------------ [~rob.stryker] explains that this error is actually non-harmful, it's just pasted as an information. It lets the incremental publisher switch to full publishing and the upcoming syncup then works. {quote} [3:28:36 PM] André Dietisheim: so this error makes the publishing switch to full publish which then works, correct? [3:28:48 PM] Rob Stryker: yes, fred had other steps to replicate that involve right-clicking the app and doing build now or whatever [3:28:55 PM] Rob Stryker: this forces the server to regenerate a root.war binary [3:29:20 PM] Rob Stryker: and then the syncdown will fail the next incremental publish, so we switch to full publish and mostly ignore the syncdown failure [3:29:27 PM] Rob Stryker: the syncup works after that [3:29:32 PM] André Dietisheim: ok gotcha [3:29:39 PM] André Dietisheim: sounds non-critical, just informative {quote} > Error during rsync > ------------------ > > Key: JBIDE-21981 > URL: https://issues.jboss.org/browse/JBIDE-21981 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Xavier Coulon > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.3.1.CR1 > > > While testing the debugging support on the server adapter, I got the following error: > {code} > Could not sync all pods to folder /Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample@eap-app/deploy > OpenShiftBinaryCapability process exited: rsync: delete_file: rmdir "/Users/xcoulon/workspaces/runtime-Eclipse-mars.2/.metadata/.plugins/org.jboss.ide.eclipse.as.core/sample(a)eap-app/deploy/ROOT.war" failed: Directory not empty (66) > rsync error: some files could not be transferred (code 23) at /SourceCache/rsync/rsync-45/rsync/main.c(1400) [generator=2.6.9] > error: exit status 23 > {code} > The content of the {{.../deploy}} directory was: > {code} > drwxr-xr-x 9 xcoulon staff 306 Mar 25 12:19 ./ > drwxr-xr-x 4 xcoulon staff 136 Mar 25 11:55 ../ > -rw-r--r-- 1 xcoulon staff 9041 Mar 27 2015 README.txt > drwxr-xr-x 7 xcoulon staff 238 Mar 25 11:59 ROOT.war/ > -rw-r--r-- 1 xcoulon staff 8 Mar 23 17:59 ROOT.war.deployed > -rw-r--r-- 1 xcoulon staff 8 Mar 25 12:18 ROOT.war.isdeploying > -rw-r--r-- 1 xcoulon staff 8415373 Aug 11 2015 activemq-rar.rar > -rw-r--r-- 1 xcoulon staff 16 Aug 11 2015 activemq-rar.rar.deployed > -rw-r--r-- 1 xcoulon staff 16 Mar 25 12:18 activemq-rar.rar.isdeploying > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016