December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15313) Investigate how to handle Wildfly port multiplexing

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15313?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15313: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Investigate how to handle Wildfly port multiplexing > ---------------------------------------------------- > > Key: JBIDE-15313 > URL: https://issues.jboss.org/browse/JBIDE-15313 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > While JBIDE-14979 and JBIDE-14402 assist in getting wildfly to work out-of-the-box, it does not assist in the possibility of turning multi-plexing on and off. This jira may include additions to UI and API, though it may NOT require both. It remains to be seen. > This jira will investigate what's necessary and what may need to change. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15921) Conversion of Deploy-only server after all subsystems are created

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15921?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15921: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Conversion of Deploy-only server after all subsystems are created > ----------------------------------------------------------------- > > Key: JBIDE-15921 > URL: https://issues.jboss.org/browse/JBIDE-15921 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > Once all subsystems are created, Deploy-only server should be the first to consume it and switch its primary behavior class over to using the new API. -- 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, 4 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15383: -------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > 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 > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16171) Separation of module filters and traversing a publish tree for copy / rm / mkdir / etc

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16171?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-16171: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Separation of module filters and traversing a publish tree for copy / rm / mkdir / etc > -------------------------------------------------------------------------------------- > > Key: JBIDE-16171 > URL: https://issues.jboss.org/browse/JBIDE-16171 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > The current code in charge of traversing a module tree or its delta for publish suffers from many problems: > 1) The class name is vague and not informative (PublishCopyUtil) > 2) It suffers from an inconsistant api (was designed stateless, became stateful, but not fully converted) > 3) It suffers from overlapping concerns (filtering and determining if module requires restart are intertwined in this logic) > > These systems need to be broken apart. The scope of this jira is to create new runners (for incremental or full publish) without reference to IModulePathFilter, and to enhance the interface for IModulePathFilter to be able to provide clean deltas. > Test cases for all should be provided. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15618) Add server mode for management; all tasks performed over management api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15618?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-15618: -------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Add server mode for management; all tasks performed over management api > ----------------------------------------------------------------------- > > Key: JBIDE-15618 > URL: https://issues.jboss.org/browse/JBIDE-15618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha2 > > > A mode for management-specific behavior. This mode would be a third mode, similar to 'local' or 'rse'. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15618) Add server mode for management; all tasks performed over management api

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15618?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15618: ----------------------------------- Assignee: Rob Stryker > Add server mode for management; all tasks performed over management api > ----------------------------------------------------------------------- > > Key: JBIDE-15618 > URL: https://issues.jboss.org/browse/JBIDE-15618 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > A mode for management-specific behavior. This mode would be a third mode, similar to 'local' or 'rse'. -- 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, 4 months

1
0
0 / 0

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

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15671?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15671: ----------------------------------- Assignee: Rob Stryker > 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 > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16239) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16239?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick closed JBIDE-16239. ------------------------------------- Resolution: Done Updated version to 1.7.0-SNAPSHOT Verified POM parent version is 4.2.0.Alpha1-SNAPSHOT Built locally Branched Done. > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices] > ---------------------------------------------------------- > > Key: JBIDE-16239 > URL: https://issues.jboss.org/browse/JBIDE-16239 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Xavier Coulon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1 [Webservices]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16226) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16226?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-16226: ------------------------------- Assignee: Mickael Istria > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch > -------------------------------------------- > > Key: JBIDE-16226 > URL: https://issues.jboss.org/browse/JBIDE-16226 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2855 -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16226) For JBIDE 4.2.0.Alpha1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16226?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16226: ------------------------------------ Jobs are enabled and ready to run tonight. Committed changes via https://github.com/jbdevstudio/jbdevstudio-ci/pull/87 Just waiting on last 3 projects to branch: Server, JavaEE, WS, and we can close this JIRA too. > For JBIDE 4.2.0.Alpha1: Code Freeze + Branch > -------------------------------------------- > > Key: JBIDE-16226 > URL: https://issues.jboss.org/browse/JBIDE-16226 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Alpha1 > > > For JBIDE 4.2.0.Alpha1: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Alpha1 > [Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Alpha1-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha1; > {code} > mvn clean verify -Dtpc.version=4.40.0.Alpha1 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha1x branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Alpha1x > git push origin jbosstools-4.2.0.Alpha1x > {code} > 5. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-2855 -- 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, 4 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 December 2013