June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20010) JBT 4.3.0.beta1/JBDS 9.0.beta1 require Java8 - but examples once installed raise warnings as Java6 is not found

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-20010: ------------------------------------ Summary: JBT 4.3.0.beta1/JBDS 9.0.beta1 require Java8 - but examples once installed raise warnings as Java6 is not found Key: JBIDE-20010 URL: https://issues.jboss.org/browse/JBIDE-20010 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.3.0.Beta1 Reporter: Len DiMaggio See the attached screenshot - this is not a new issue, but seeing as how we now require Java 8 (http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Beta1.html...) - the examples should no longer reference Java6. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20010) JBT 4.3.0.beta1/JBDS 9.0.beta1 require Java8 - but examples once installed raise warnings as Java6 is not found

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20010?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-20010: ------------------------------------ Assignee: Fred Bricon > JBT 4.3.0.beta1/JBDS 9.0.beta1 require Java8 - but examples once installed raise warnings as Java6 is not found > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20010 > URL: https://issues.jboss.org/browse/JBIDE-20010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Len DiMaggio > Assignee: Fred Bricon > > See the attached screenshot - this is not a new issue, but seeing as how we now require Java 8 (http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Beta1.html...) - the examples should no longer reference Java6. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19641) Big war deployment via management API gets stuck

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19641?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19641: ------------------------------------- [~brian.stansberry] So, what actions should we take here? The first thing I need to know is if this error is occurring on the client side or the server side? Also, if you introduce a new set of jars and I update the jars in our plugins (aka the client), are they likely to be able to communicate fully with all eap-6.x installations? Thanks for all the help on this issue. > Big war deployment via management API gets stuck > ------------------------------------------------ > > Key: JBIDE-19641 > URL: https://issues.jboss.org/browse/JBIDE-19641 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: stuck-deploy-eap-jstack-osx.log, stuck-deploy-eap-jstack-rhel.log, stuck-deploy-jstack-osx.log, stuck-deploy-jstack-rhel.log > > > When you try to deploy some really big war (~500 MB) to EAP 6.3 via management api, it will not go through. > This is a follow-up of JBIDE-19350 which previously reported this, but Rob eventually used that JIRA to fix a side issue - the stuck operation could not be canceled. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19467) repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19467?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19467: ------------------------------------ PR: https://github.com/jbosstools/jbosstools-maven-plugins/pull/46 Results when it fails: {code} mvn verify -Pmaximum -Pfetch-source-zips -e -X [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! [ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools-github-master/jbosstools-build-sites/aggregate/site/target/buildinfo/buildinfo_jbosstools-browsersim.json [ERROR] contains 3b22a4bbe6610e35401bfccc461cb329e8b806b0, but upstream project's MANIFEST.MF has Eclipse-SourceReferences [ERROR] commitId 9255a5b7c04fb10768c14942e60092e860881d6b. [ERROR] If you have locally built projects which are aggregated here, [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. [ERROR] Or, use -DskipCheckSHAs=true to bypass this check. {code} To bypass: {code}mvn verify -Pmaximum -Pfetch-source-zips -e -X -DskipCheckSHAs=true{code} To make it fail, you just need to build something locally (like jbosstools-browsersim from https://github.com/nickboldt/jbosstools-browsersim/commit/9255a5b7c04fb10... ), then rebuilt jbosstools-build-sites/aggregate/site/pom.xml. > repository-utils :: FetchSourcesFromManifests should create its own source zip, not rely on publish.sh > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-19467 > URL: https://issues.jboss.org/browse/JBIDE-19467 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.3.0.Beta2 > > > In repository-utils, FetchSourcesFromManifests should create its own source zip, not rely on publish.sh. Because we no longer use publish.sh and don't want to have rsync.sh produce artifacts, only rsync them. > Here's what publish.sh does: > {code} > # collect component zips from upstream aggregated build jobs > if [[ ${JOB_NAME/.aggregate} != ${JOB_NAME} ]] && [[ -d ${WORKSPACE}/sources/aggregate/site/zips ]]; then > mkdir -p ${STAGINGDIR}/components > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*updatesite-*.zip"); do > # generate MD5 sum for zip (file contains only the hash, not the hash + filename) > for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > mv $z ${z}.MD5 ${STAGINGDIR}/components > done > # TODO :: JBIDE-9870 When we have a -Update-Sources- zip, this can be removed > mkdir -p ${STAGINGDIR}/all/sources > # OLD: unpack component source zips like jbosstools-pi4soa-3.1_trunk-Sources-SNAPSHOT.zip or jbosstools-3.2_trunk.component--ws-Sources-SNAPSHOT.zip > # NEW: JBIDE-16632: unpack component source zips like jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4_sources.zip > for z in $(find ${WORKSPACE}/sources/aggregate/site/zips -name "*Sources*.zip" -o -name "*_sources.zip" -o -name "*-src.zip"); do > zn=${z%*-Sources*.zip}; zn=${zn%*_sources.zip}; zn=${zn%*-src.zip}; zn=${zn#*--}; zn=${zn##*/}; zn=${zn#jbosstools-}; > # zn=${zn%_trunk}; zn=${zn%_stable_branch}; > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > # remove one level of folder nesting - don't want an extra jbosstools-base-184e18cc3ac7c339ce406974b6a4917f73909cc4 folder under jbosstools-base_Alpha2-v20140221-1555-B437_184e18cc3ac7c339ce406974b6a4917f73909cc4 > unzip -qq -o -d ${tmpdir}/${zn}/ $z > mkdir -p ${STAGINGDIR}/all/sources/${zn}/ > mv ${tmpdir}/${zn}/jbosstools-*/* ${STAGINGDIR}/all/sources/${zn}/ > rm -fr ${tmpdir}/${zn}/ > done > # add component sources into sources zip > pushd ${STAGINGDIR}/all/sources > zip ${STAGINGDIR}/all/${SRCSNAME} -q -r * -x hudson_workspace\* -x documentation\* -x download.jboss.org\* -x requirements\* \ > -x workingset\* -x labs\* -x build\* -x \*test\* -x \*target\* -x \*.class -x \*classes\* -x \*bin\* -x \*.zip \ > -x \*docs\* -x \*reference\* -x \*releng\* -x \*.git\* -x \*/lib/\*.jar -x \*getRemoteFile\* > popd > rm -fr ${STAGINGDIR}/all/sources > z=${STAGINGDIR}/all/${SRCSNAME}; for m in $(md5sum ${z}); do if [[ $m != ${z} ]]; then echo $m > ${z}.MD5; fi; done > # JBIDE-7444 get aggregate metadata xml properties file > if [[ -f ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ]]; then > rsync -aq ${WORKSPACE}/sources/aggregate/site/zips/build.properties.all.xml ${STAGINGDIR}/logs/ > fi > fi > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19994) Import wizard: no applications are listed where I should be able to select the one to import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19994?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19994: ---------------------------------------- Assignee: Andre Dietisheim (was: Fred Bricon) Resolution: Done > Import wizard: no applications are listed where I should be able to select the one to import > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19994 > URL: https://issues.jboss.org/browse/JBIDE-19994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Blocker > Labels: import_wizard, respin-a > Fix For: 4.3.0.Beta1 > > Attachments: import_app_shell.png > > > When trying to import an existing application to the workspace via shell menu File - Import, there is opened OpenShift application wizard to import an existing application. After click on Browse button Select Existing Application shell is opened and there should be some applications/domains with applications, but the shell is empty. > !import_app_shell.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19994) Import wizard: no applications are listed where I should be able to select the one to import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19994?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19994: ------------------------------------------ merged and pushed to upstream/jbosstools-4.3.0.Beta1x > Import wizard: no applications are listed where I should be able to select the one to import > -------------------------------------------------------------------------------------------- > > Key: JBIDE-19994 > URL: https://issues.jboss.org/browse/JBIDE-19994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Blocker > Labels: import_wizard, respin-a > Fix For: 4.3.0.Beta1 > > Attachments: import_app_shell.png > > > When trying to import an existing application to the workspace via shell menu File - Import, there is opened OpenShift application wizard to import an existing application. After click on Browse button Select Existing Application shell is opened and there should be some applications/domains with applications, but the shell is empty. > !import_app_shell.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3123) JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3123?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3123: ------------------------------------------- it is an upstream problem. I haven't been able to reproduce on my OSX install so if someone has a linux install that can reproduce and report at eclipse bugzilla that would be the way forward. > JavaDoc popup does not respect monitor's physical border in dual side-by-side monitor configuration. > ---------------------------------------------------------------------------------------------------- > > Key: JBDS-3123 > URL: https://issues.jboss.org/browse/JBDS-3123 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.0.0.Beta3 > Environment: Fedora 20, RHEL6 > Reporter: Emil Cervenan > Fix For: 9.0.0.Beta2 > > > Code autocompletion popup JavaDoc window does not respect physical monitor borders. JavaDoc window is rendered across monitor borders and thus not readable. Problem occurs in side-by-side monitor configuration. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20009) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-20009: ---------------------------------------- Summary: Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import Key: JBIDE-20009 URL: https://issues.jboss.org/browse/JBIDE-20009 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 4.3.0.Beta1 Attachments: Import.png Description of problem: The context item of "Import Application..." display error. Version-Release number of selected component (if applicable): openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 How reproducible: Always. Steps to Reproduce: 1. EXEC: Connect to the openshift server in jbt 2. EXEC: Import existing OpenShift projects into Eclipse workspace: * EXEC: Select a connection or a project and right click * EXEC: Open context menu and look for "Import Application" in the context menu. Actual results: !Import.png! 2.2 The context menu item is "%openshift.command.application.import" Expected results: 2.2 The context menu should show "Import Application..." Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20009) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20009?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20009: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20009 > URL: https://issues.jboss.org/browse/JBIDE-20009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta2 > > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19968) Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19968?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19968: ------------------------------------- Fix Version/s: (was: 4.3.0.Beta2) > Explorer: Context menu item "Import Application..." is displayed as %openshift.command.application.import > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19968 > URL: https://issues.jboss.org/browse/JBIDE-19968 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Ma Deshuai > Assignee: Andre Dietisheim > Priority: Minor > Labels: respin-a > Fix For: 4.3.0.Beta1 > > Attachments: Import.png > > > Description of problem: > The context item of "Import Application..." display error. > Version-Release number of selected component (if applicable): > openshift-v3 plug: 3.0.0.Beta2-v20150606-0237-B829 > How reproducible: > Always. > Steps to Reproduce: > 1. EXEC: Connect to the openshift server in jbt > 2. EXEC: Import existing OpenShift projects into Eclipse workspace: > * EXEC: Select a connection or a project and right click > * EXEC: Open context menu and look for "Import Application" in the context menu. > Actual results: > !Import.png! > 2.2 The context menu item is "%openshift.command.application.import" > Expected results: > 2.2 The context menu should show "Import Application..." > Additional info: -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 June 2015