October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18655) Project location should be set to "workspace" in Forge Project New wizard by default

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18655?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-18655: ----------------------------------- [~psrna] I think that it makes perfect sense to make nested projects. The JBossTools and Forge projects themselves are examples of heavily nested projects and there are plenty of other examples. Moreover, creating projects in the currently selected resource exactly reflects the Forge command line behavior. > Project location should be set to "workspace" in Forge Project New wizard by default > ------------------------------------------------------------------------------------ > > Key: JBIDE-18655 > URL: https://issues.jboss.org/browse/JBIDE-18655 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.CR2 > Reporter: Pavol Srna > > Current implementation is that "Project Location" is set to forge current selection. Which is set for the first project to "workspace", but for any other subsequent project to "forge current_selection" > But it doesn't make much sense unless we want nested projects. *Is there a use case for nested projects?* I don't thinks so. Thus I would set "Project Location" to "workspace" by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3185) For JBDS 8.0.0.GA: Prepare for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3185?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3185. ---------------------------- Assignee: Nick Boldt Resolution: Done > For JBDS 8.0.0.GA: Prepare for Final/GA release > ----------------------------------------------- > > Key: JBDS-3185 > URL: https://issues.jboss.org/browse/JBDS-3185 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 8.0.0.GA > > > For JBDS 8.0.0.GA: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. 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...] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18630) For JBIDE 4.2.0.Final: Prepare for Final/GA release

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18630?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18630. ------------------------------ Assignee: Nick Boldt Resolution: Done Children are done so this is done. Closing. > For JBIDE 4.2.0.Final: Prepare for Final/GA release > --------------------------------------------------- > > Key: JBIDE-18630 > URL: https://issues.jboss.org/browse/JBIDE-18630 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Final > > > For JBIDE 4.2.0.Final: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 8.0.0.CR2, 4.2.0.Final or 8.0.0.GA. > [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...] > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Final-SNAPSHOT</version> > </parent> > {code} > 2. Ensure you've built & run your plugin tests using the latest target platform versions > {code} > mvn clean verify -Dtpc.version=4.40.0.Final-SNAPSHOT > mvn clean verify -Dtpc.version=4.41.0.Final-SNAPSHOT > {code} > 4. 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-3185 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18366) Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18366?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18366 at 10/16/14 11:47 PM: --------------------------------------------------------------- have to push it. sorry. Slip to 4.2.1 & 4.3.0. was (Author: rob.stryker): have to push it. sorry. > Sometimes, EAP6/WildFly8/AS7 fails to start - Failed initializing module org.jboss.as.logging > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18366 > URL: https://issues.jboss.org/browse/JBIDE-18366 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > Sometimes, right after start of the IDE, a server fails to start. When this happens, it produces something like this in the server log: > {code} > INFO: JBoss MSC version 1.1.5.Final-redhat-1 > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ApplicationServerService start > INFO: JBAS015899: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) starting > Sep 17, 2014 11:27:40 AM org.jboss.as.controller.AbstractOperationContext executeStep > ERROR: JBAS014612: Operation ("parallel-extension-add") failed - address: ([]) > java.lang.RuntimeException: JBAS014670: Failed initializing module org.jboss.as.logging > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:111) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:611) > at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:489) > at org.jboss.as.controller.AbstractOperationContext.completeStepInternal(AbstractOperationContext.java:290) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:285) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1132) > at org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:299) > at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:292) > at org.jboss.as.server.ServerService.boot(ServerService.java:346) > at org.jboss.as.server.ServerService.boot(ServerService.java:321) > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:254) > at java.lang.Thread.run(Thread.java:695) > Caused by: java.util.concurrent.ExecutionException: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) > at java.util.concurrent.FutureTask.get(FutureTask.java:83) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$1.execute(ParallelExtensionAddHandler.java:103) > ... 11 more > Caused by: java.lang.IllegalStateException: JBAS011592: The logging subsystem requires the log manager to be org.jboss.logmanager.LogManager. The subsystem has not be initialized and cannot be used. To use JBoss Log Manager you must add the system property "java.util.logging.manager" and set it to "org.jboss.logmanager.LogManager" > at org.jboss.as.logging.LoggingExtension.initialize(LoggingExtension.java:106) > at org.jboss.as.controller.extension.ExtensionAddHandler.initializeExtension(ExtensionAddHandler.java:97) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:139) > at org.jboss.as.controller.extension.ParallelExtensionAddHandler$ExtensionInitializeTask.call(ParallelExtensionAddHandler.java:125) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) > at java.util.concurrent.FutureTask.run(FutureTask.java:138) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) > at java.lang.Thread.run(Thread.java:695) > at org.jboss.threads.JBossThread.run(JBossThread.java:122) > Sep 17, 2014 11:27:40 AM org.jboss.as.server.ServerService boot > FATAL: JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details. > {code} > Unfortunately I don't have a reliable way to reproduce this. It happened to me like 3 times over the last few days. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18620) server New and Noteworthy for 4.2.0.CR2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18620?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-18620. --------------------------------------- Resolution: Rejected > server New and Noteworthy for 4.2.0.CR2 > --------------------------------------- > > Key: JBIDE-18620 > URL: https://issues.jboss.org/browse/JBIDE-18620 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.CR2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18620) server New and Noteworthy for 4.2.0.CR2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18620?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-18620. --------------------------------------- Resolution: Done nothing new. > server New and Noteworthy for 4.2.0.CR2 > --------------------------------------- > > Key: JBIDE-18620 > URL: https://issues.jboss.org/browse/JBIDE-18620 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.CR2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18548) Image dropped to VPE is not rendered on server

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18548?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18548: ---------------------------------------- Yes it does. This context root variable is not needed for JSF components like <h:graphicImage> but it's useful for plain html tags in JSF pages. > Image dropped to VPE is not rendered on server > ---------------------------------------------- > > Key: JBIDE-18548 > URL: https://issues.jboss.org/browse/JBIDE-18548 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.CR2 > Environment: JBT 4.2.0.CR2-v20141005-0541-B267 > Reporter: Vlado Pakan > Assignee: Alexey Kazakov > Fix For: 4.3.0.Alpha1 > > > 1. Import HTML 5 project from JBoss Central > 2. Open index.html page > 3. Drag&drop some image from img subdirectory to source part of VPE > ASSERT: Image is displayed in visual part of VPE > 4. Run project on server > ERROR: Dropped Image is not rendered in web browser > Once leading "/" is removed from img tag source attribute droped image is rendered on web page deployed to server -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18617) Project Examples New and Noteworthy for 4.2.0.CR2

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18617?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-18617. --------------------------------------- Resolution: Rejected nothing new. > Project Examples New and Noteworthy for 4.2.0.CR2 > ------------------------------------------------- > > Key: JBIDE-18617 > URL: https://issues.jboss.org/browse/JBIDE-18617 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: project-examples > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.0.CR2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Project Examples is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Project Examples by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18619) Forge New and Noteworthy for 4.2.0.CR2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18619?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-18619. ------------------------------- Resolution: Rejected > Forge New and Noteworthy for 4.2.0.CR2 > -------------------------------------- > > Key: JBIDE-18619 > URL: https://issues.jboss.org/browse/JBIDE-18619 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18619) Forge New and Noteworthy for 4.2.0.CR2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18619?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-18619. ----------------------------- > Forge New and Noteworthy for 4.2.0.CR2 > -------------------------------------- > > Key: JBIDE-18619 > URL: https://issues.jboss.org/browse/JBIDE-18619 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Forge is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Forge by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014