July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18951) jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18951?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18951: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > jboss-web_8_0.xsd in AS XML catalog reported as "containing errors" by Luna > --------------------------------------------------------------------------- > > Key: JBIDE-18951 > URL: https://issues.jboss.org/browse/JBIDE-18951 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Final > Environment: W7 Pro SP1 > eclipse.buildId=4.4.1.M20140925-0400 > org.jboss.tools.as.catalog (3.0.0.Final-v20141016-1911-B95) "JBoss AS XML Catalog Entries" > Reporter: Jordan Glassman > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: Capture4.PNG, xsd-details.png > > > In a jboss-web.xml file, a namespace declaration like: > {code} <jboss-web xmlns="http://www.jboss.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-web_8_0.xsd" version="8.0" > >{code} > Gives eclipse error: > {quote}Referenced file contains errors (jar:file:/C:/eclipse/plugins/org.jboss.tools.as.catalog_3.0.0.Final-v20141016-1911-B95.jar!/schema/xsd/jboss-web_8_0.xsd). > For more information, right click on the message in the Problems View and select "Show Details..."{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22269) Work with WildFly/EAP to generate unit tests on server installation layout

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22269?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22269: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Work with WildFly/EAP to generate unit tests on server installation layout > -------------------------------------------------------------------------- > > Key: JBIDE-22269 > URL: https://issues.jboss.org/browse/JBIDE-22269 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.1.AM2 > > Attachments: JBIDE-22269.mock.zip > > > A task to track work on making sure changes to EAP don't inadvertently break tools when changing directory structure or important keys we read. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22243) Properties: "Refresh" has no effect

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22243?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22243: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Properties: "Refresh" has no effect > ----------------------------------- > > Key: JBIDE-22243 > URL: https://issues.jboss.org/browse/JBIDE-22243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.4.1.AM2 > > Attachments: refreshing-wont-help.ogv > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22241: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.1.AM2 > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22239) Allow a user to choose to permanently update their desired replicas for their deployment

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22239?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22239: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Allow a user to choose to permanently update their desired replicas for their deployment > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22239 > URL: https://issues.jboss.org/browse/JBIDE-22239 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Jeff Cantrill > Assignee: Viacheslav Kabanovich > Labels: openshift_v3 > Fix For: 4.4.1.AM2 > > > When scaling, we should provide an option to a user who is scaling their deployment to update the deploymentconfig desired replias setting. Currently, if you scale the deployment in the explorer view or the replicationcontroller in the tabs view, image or config change triggers from a DC will set the replica count to whats defined their. Suggest: > * Adding a custom dialog in the "..to.." option > * Update to use a spinner > * Add a checkbox to 'make the change perminent' > * If checkbox=true, you should only need to update the dc if it has a configchange trigger. > * Optionally show checkbox if unable to determine the dc associated with the deployment. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22376: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22319: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22305: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.1.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22304) Server Editor: Pod deployment path is not shown

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22304?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22304: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Server Editor: Pod deployment path is not shown > ----------------------------------------------- > > Key: JBIDE-22304 > URL: https://issues.jboss.org/browse/JBIDE-22304 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v3, server_editor > Fix For: 4.4.1.AM2 > > > In Server Adapter wizard is not shown Pod deployment path. Widget supposed to display the path is empty. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22294) Build Configuration: Git Source section is cropped on OSX

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22294?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22294: ----------------------------------- Fix Version/s: 4.4.1.AM2 (was: 4.4.1.AM1) > Build Configuration: Git Source section is cropped on OSX > --------------------------------------------------------- > > Key: JBIDE-22294 > URL: https://issues.jboss.org/browse/JBIDE-22294 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.4.1.AM2 > > > After creating a new openshift application, selecting a builder image, then on the next page: > !http://content.screencast.com/users/fbricon/folders/Jing/media/5e21b5d7-9cb1-43cf-bfe9-05c1ef6e0dad/00000404.png|width=800! > Context directory field / label are cropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 July 2016