June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19991) Add possibility "Show in Properties" to batch diagram validation message dialog

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19991?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-19991: ----------------------------------------------- Content for this dialog is set internally in ValidationMarkerPresentation and there is no opening for custom extensions. > Add possibility "Show in Properties" to batch diagram validation message dialog > ------------------------------------------------------------------------------- > > Key: JBIDE-19991 > URL: https://issues.jboss.org/browse/JBIDE-19991 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: batch > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Viacheslav Kabanovich > Fix For: 4.3.0.Beta2 > > Attachments: validation.png > > > There is possibility "Show in source" but since you can edit some properties in Properties view, it makes sense to add also "Show in Properties view". > !validation.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20173) Clean up UI errors in case RSE is not installed

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20173: ----------------------------------- Summary: Clean up UI errors in case RSE is not installed Key: JBIDE-20173 URL: https://issues.jboss.org/browse/JBIDE-20173 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.3.0.Beta1 Reporter: Rob Stryker In an environment where RSE is not available, the UI fails in multiple fashions. It allows you to create RSE servers, even though it shouldn't. If there's a previously-existing RSE server, the server editor will fail to load with NPE. There is also no warning in the editor anywhere indicating that the server is incompatible with current profile. Also, start / debug / etc should fail indicating profile is unavailable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20016) Explorer: As a user I want to be able to create projects for OpenShift v3 connections

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20016?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-20016: ---------------------------------- Summary: Explorer: As a user I want to be able to create projects for OpenShift v3 connections (was: Explorer: As a user I want to be able to create and delete projects for OpenShift v3 connections) > Explorer: As a user I want to be able to create projects for OpenShift v3 connections > ------------------------------------------------------------------------------------- > > Key: JBIDE-20016 > URL: https://issues.jboss.org/browse/JBIDE-20016 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Labels: explorer, openshift_v3 > Fix For: 4.3.0.Beta2 > > > Currently there is no other way to create a new project for OpenShift v3 then via openshift CLI. It would be nice to have New - Project context menu for v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20172) Explorer: As a user I want to be able to delete projects for OpenShift v3 connections

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-20172: ------------------------------------- Summary: Explorer: As a user I want to be able to delete projects for OpenShift v3 connections Key: JBIDE-20172 URL: https://issues.jboss.org/browse/JBIDE-20172 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Assignee: Jeff Cantrill Priority: Critical Fix For: 4.3.0.Beta2 Currently there is no other way to create a new project for OpenShift v3 then via openshift CLI. It would be nice to have New - Project context menu for v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20128) Explorer: freshly created application (via wizard) is not showing up in explorer unless I refresh it

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20128?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20128: ------------------------------------- Labels: explorer (was: ) > Explorer: freshly created application (via wizard) is not showing up in explorer unless I refresh it > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20128 > URL: https://issues.jboss.org/browse/JBIDE-20128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: explorer > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20165) Text for WildFly 9.x in New Server wizard points to WildFly 8.x

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20165?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-20165. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.3.0.Beta2 Resolution: Done Fixed. One liner. no PR > Text for WildFly 9.x in New Server wizard points to WildFly 8.x > --------------------------------------------------------------- > > Key: JBIDE-20165 > URL: https://issues.jboss.org/browse/JBIDE-20165 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: new_server_wildfly9x.png > > > Text in details area for a new server showing type of server is incorrect for server WildFly 9.x (Experimental). It is pointing to WildFly 8.x. !new_server_wildfly9x.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20148 at 6/30/15 4:15 PM: ------------------------------------------------------------- Using overWrite=true and private maven repo... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Doesn't work. https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... shows the --del flag is still being ignored by the mojo :( was (Author: nickboldt): Using overWrite=true and private maven repo... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > releng scripts is an outdated version; jobs are not seeing latest from Nexus > ---------------------------------------------------------------------------- > > Key: JBIDE-20148 > URL: https://issues.jboss.org/browse/JBIDE-20148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: needinfo, nexus > Fix For: 4.3.0.Beta2 > > > I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log. > [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x > And the latest commits ARE built and available in Nexus [1], [2]: > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script. > Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... : > {code} > + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master > ... > [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core --- > ... > rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want: > {code} > + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del > ... > [DEBUG] RSYNCFLAGS = --del > ... > [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ? > [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20168) create buildinfo.json files for old project builds which predate buildinfo.json generator

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20168?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20168: ------------------------------------ On the plus side, the JBT agg site's buildinfo.json now contains an entry for Portlet from the 4.2.x branch: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... So we're batting .500 here. :D > create buildinfo.json files for old project builds which predate buildinfo.json generator > ----------------------------------------------------------------------------------------- > > Key: JBIDE-20168 > URL: https://issues.jboss.org/browse/JBIDE-20168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta2 > > > Max asked: > {quote} > i'm asking what shah's was used in the build for these components. > No sure if you are trolling me by us keeping having these conversations everytime we need to tag :) > Checking jbosstools-portlet the latest 4.3.0 tags are same as master but the link above you are pointing to Luna so that can't be right. > and jbosstools-xulrunner seem to have very little tags at all - so again; which tag/sha1 of these was put into our release so we can actually know what source is actually included ? > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20148) releng scripts is an outdated version; jobs are not seeing latest from Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20148?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20148: ------------------------------------ Using overWrite=true and private maven repo... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > releng scripts is an outdated version; jobs are not seeing latest from Nexus > ---------------------------------------------------------------------------- > > Key: JBIDE-20148 > URL: https://issues.jboss.org/browse/JBIDE-20148 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: needinfo, nexus > Fix For: 4.3.0.Beta2 > > > I've made some commits in the 4.3.x branch [0] of the build-ci repo, which should echo more details into the log. > [0] https://github.com/jbosstools/jbosstools-build-ci/commits/jbosstools-4.3.x > And the latest commits ARE built and available in Nexus [1], [2]: > [1] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... [2] https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo... > Yet, no such output appears when the job is run, which makes me think that the -d and --del flags are NOT being passed to the script. > Here's a snippet from https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... : > {code} > + /qa/tools/opt/apache-maven-3.2.5//bin/mvn deploy -Pdeploy-to-jboss.org -Dmaven.repo.local=/mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/.repository -B -U -fae -e -P hudson,unified.target,pack200,fetch-source-zips -Djbosstools_site_stream=master > ... > [INFO] --- exec-maven-plugin:1.3.2:exec (deploy-snapshot-updatesite) @ org.jboss.tools.site.core --- > ... > rsync -arzq --protocol=28 /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/repository/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > Yet when I run THE SAME SCRIPT from the workspace via shell, I get what I want: > {code} > + . /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/publish/rsync.sh -s /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo -t mars/snapshots/updates/core/master --del > ... > [DEBUG] RSYNCFLAGS = --del > ... > [INFO] rsync -arzq --protocol=28 --del /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_master/sources/aggregate/site/target/fullSite/all/repo/* tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > ++ rsync -arzq --protocol=28 --del ... tools@filemgmt.jboss.org:/downloads_htdocs/tools/mars/snapshots/updates/core/master/ > {code} > So... what am I doing wrong? Why isn't the mojo using the latest version of the rsync script, but it's IN the workspace [3] ? > [3] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20164) webtools server adapter installation shows "null"

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20164?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20164: ------------------------------------- Keeping this issue of the feature name separate, the previous feature name that showed in this UI was featureName=JBossAS Tools Would you suggest "JBoss / WildFly / EAP Server Tools" as a valid feature name? This feature name will be the same in the jbt update site as well as the server UI... so the name needs to work for both. > webtools server adapter installation shows "null" > ------------------------------------------------- > > Key: JBIDE-20164 > URL: https://issues.jboss.org/browse/JBIDE-20164 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.3.0.Beta2 > > Attachments: Install_New_Extension_and_New_Server.png > > > When using the "download additional adapters" for JBoss Tools it has a few issues. > a) shows "null" for vendor > b) does not actually say it is for WildFly nor EAP servers > c) (idea) should we add OpenShift to this ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 9 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