November 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2708) JBDS 7 download / subscription / info page needs an overhaul / reskin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2708?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2708: -------------------------------------- Fix Version/s: 7.1.x 8.0.x > JBDS 7 download / subscription / info page needs an overhaul / reskin > --------------------------------------------------------------------- > > Key: JBDS-2708 > URL: https://issues.jboss.org/browse/JBDS-2708 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Fix For: 7.1.x, 8.0.x > > > This page is ugly and in need of a do-over. > https://devstudio.jboss.com/download/7.x.html > This is also the default landing page when people hit http://devstudio.jboss.com for the first time. > Ideally, we would make this page more graphical, more punchy, and with more ease of use. It's way too text-heavy. > [~james.cobb] do you have time to mock up a better treatment for this page? [~mmurray], [~burrsutter], [~maxandersen], [~mmusaji] WDYT? > Should this page also link to these pages? > * Early Access: https://devstudio.jboss.com/earlyaccess/ > * Updates: https://devstudio.jboss.com/updates/ > Should those pages be reskinned too? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ] Peter Palaga commented on JBIDE-15848: -------------------------------------- The schema namespace for JSF 2.2 changed - see http://stackoverflow.com/a/16131589 > JSF Portal Project XML Problem > ------------------------------ > > Key: JBIDE-15848 > URL: https://issues.jboss.org/browse/JBIDE-15848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, portal-gatein > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 > Reporter: Radoslav Rábara > Priority: Blocker > Fix For: 4.1.1.Beta1 > > Attachments: jsf - Error.jpg, jsf - show details.jpg > > > Creating JSF Portal Project ends with error: > Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). > Type: XML Error, Resource: faces-config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15339: --------------------------------------------- Isn't this mixing different concerns ? Analyze if feature/plugin needs to be upversioned is unrelated to which commits went into an updatesite, jenkins builds etc. > Create version/change auditor/reporting tool > -------------------------------------------- > > Key: JBIDE-15339 > URL: https://issues.jboss.org/browse/JBIDE-15339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > > Plugin/Feature Version Auditor > Goal: be able to more easily see if a feature or plugin needs to be upversioned > Goal: be able to more easily see if a commit in github has been built into the jars in an update site > Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) > Output: generate a report of: > plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs > Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.) > May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15339) Create version/change auditor/reporting tool

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15339?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15339: ---------------------------------------- Fix Version/s: 4.2.x > Create version/change auditor/reporting tool > -------------------------------------------- > > Key: JBIDE-15339 > URL: https://issues.jboss.org/browse/JBIDE-15339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.x > > > Plugin/Feature Version Auditor > Goal: be able to more easily see if a feature or plugin needs to be upversioned > Goal: be able to more easily see if a commit in github has been built into the jars in an update site > Goal: be able to more easily see what has changed between two builds (with links to relevant Jenkins, JIRA, Github, upstream URLs, TP URLs) > Output: generate a report of: > plugins, features in JBT or JBDS by version, md5 #, JIRA #s related to latest commits, jenkins build IDs > Include URL links to content/metadata: Github, Jenkins, JIRA, dl.jb.org (upstream sites which feed the aggregates, target platforms, composites, etc.) > May also include some parallel work to provide improvements to QA's versionwatch tool (https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch ) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15383: --------------------------------------------- [~datallah] there does seem to be a bug in "restore defaults" here but before looking into that can you explain the usecase you got which requires you to add classpath entries to the server ? AS7 does not really support nor need that anymore unless you are trying to change the jboss-modules.jar ? > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15071) Remove the "Update Modules States" message from the status bar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15071?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15071: --------------------------------------------- Personally I don't see messages in the progress bar as a message to me saying "Don't touch the keyboard", I see it as "I can do stuff now, because otherwise the UI would be blocked" - but unfortunately I seem to be in the minority. I've started to hear very often that "eclipse is slow" and when I ask into it the answer is "it is always doing stuff in the progress bar" ...and sure ,eclipse is slow inplaces, but it started to look like users makes the connection that "stuff in progress bar = wait!" even though it is supposed to be the exact opposite. FIY: You can actually go to progress view and enable "Show sleeping and system operations" so it is not completely hidden if we were to hide it. Thus iif this is truly a background job and not something that is hooked into the progress bar for start/stopping I think putting "is modules still deployed" as a system job sounds reasonable. > Remove the "Update Modules States" message from the status bar > -------------------------------------------------------------- > > Key: JBIDE-15071 > URL: https://issues.jboss.org/browse/JBIDE-15071 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.1.0.CR1 > Reporter: Xavier Coulon > Assignee: Rob Stryker > > Sometimes, the server adapter calls the server to check if all modules are deployed. This operation can take a few seconds and the status bar displays a message. As a user, I believe that I should wait until this operation is done, which is a bit annoying -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-15848: ------------------------------------ Attachment: jsf - Error.jpg jsf - show details.jpg > JSF Portal Project XML Problem > ------------------------------ > > Key: JBIDE-15848 > URL: https://issues.jboss.org/browse/JBIDE-15848 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsf, portal-gatein > Affects Versions: 4.1.1.Beta1 > Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 > Reporter: Radoslav Rábara > Priority: Blocker > Fix For: 4.1.1.Beta1 > > Attachments: jsf - Error.jpg, jsf - show details.jpg > > > Creating JSF Portal Project ends with error: > Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). > Type: XML Error, Resource: faces-config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-15848: --------------------------------------- Summary: JSF Portal Project XML Problem Key: JBIDE-15848 URL: https://issues.jboss.org/browse/JBIDE-15848 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsf, portal-gatein Affects Versions: 4.1.1.Beta1 Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1 Reporter: Radoslav Rábara Priority: Blocker Fix For: 4.1.1.Beta1 Creating JSF Portal Project ends with error: Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd). Type: XML Error, Resource: faces-config.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15370) when port-offset is "0" and modifications are done to servers the xml is persisted incorrectly and the port-offset is not writen

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15370?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15370: --------------------------------------------- Just realized that we are offering users to edit these xml files but AS7+ will rewrite them on shutdown. Thus it does not really make sense to allow editing of them when the server is running - or at least we should warn about this when editing files on a running server. > when port-offset is "0" and modifications are done to servers the xml is persisted incorrectly and the port-offset is not writen > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15370 > URL: https://issues.jboss.org/browse/JBIDE-15370 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: thiago andrade > Assignee: Rob Stryker > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15671) WildFly / EAP domain mode management UI

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15671: --------------------------------------------- Also, we are not trying to be a admin tool - the server tooling is meant for developers thus not everything admin likes/uses are applicable. But there is of course some overlap but I think it is important to keep that in mind when working on this. > WildFly / EAP domain mode management UI > --------------------------------------- > > Key: JBIDE-15671 > URL: https://issues.jboss.org/browse/JBIDE-15671 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Ondrej Zizka > Attachments: domainmodeinitialmockup.bmml, domainmodeinitialmockup.png > > > Max brought the topic of Domain mode management UI. > The domain mode needs a special treatment. > Logically it's a matrix, and calls for a matrix-like UI instead of a tree. > The structure would be similar to the pictures of domain mode in tutorials (TBD: link). > An inspiration may be taken from AS web console. > As a preliminary solution, a tree may be used, in which case it may omit host controllers which do not play much role in domain mode management, from the admin PoV. > The nodes would represent server groups, and their leaves would represent particular servers (JVMs). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 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 November 2013