June 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13139) Improve libs import for EAP 6

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-13139?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-13139. --------------------------------- Closing, nothing to do. > Improve libs import for EAP 6 > ----------------------------- > > Key: JBIDE-13139 > URL: https://issues.redhat.com/browse/JBIDE-13139 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 3.3.0.Final > Environment: JBDS 4.x > EAP 6/AS 7 > Reporter: William Siqueira > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.1.x > > > In previous version of EAP, we could create a LIB and all our JARs files to the application build path, so we didn't have problem with imports. in EAP 6(AS 7), we have the modules new concept. > The problem is that when migrating from older EAP version to EAP 6, we have to create modules to represent our libs and when setting a server to your project, it is not bringing our custom modules which our application is dependent. > What is needed is a way to select which modules will be in the project classpath whn adding a server lib to the project or perhaps automatically import all modules based on the jboss-deployment-structure.xml descriptor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18564) Provide a default connection to in-memory database

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-18564?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-18564. --------------------------------- Closing, nothing to do. > Provide a default connection to in-memory database > -------------------------------------------------- > > Key: JBIDE-18564 > URL: https://issues.redhat.com/browse/JBIDE-18564 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Arun Gupta > Priority: Major > Fix For: 4.3.x > > > If WildFly is chosen as the application server to run the project, then show a default connection to the in-memory database. Otherwise user will have to figure it out by googling. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

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

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-15313?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-15313. --------------------------------- Closing, nothing to do. > Investigate how to handle Wildfly port multiplexing > ---------------------------------------------------- > > Key: JBIDE-15313 > URL: https://issues.redhat.com/browse/JBIDE-15313 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.1.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Major > Fix For: 4.2.0.Final > > > 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 was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10337) Found components with duplicated names!

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-10337?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-10337. --------------------------------- Closing, nothing to do. > Found components with duplicated names! > ---------------------------------------- > > Key: JBIDE-10337 > URL: https://issues.redhat.com/browse/JBIDE-10337 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 3.3.0.M5 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 3.3.0.M5 > > > See parent jira JBIDE-10336 for steps to reproduce. Full log is here: > https://issues.jboss.org/secure/attachment/12349551/eclipse.log.Sun_Dec4_... > !ENTRY org.jboss.ide.eclipse.as.management.as71 2 0 2011-12-04 10:29:51.541 > !MESSAGE [SCR] Found components with duplicated names! Details: > Component1 : Component[ > name = org.jboss.ide.eclipse.as.management.as7.service > activate = activate > deactivate = deactivate > modified = > configuration-policy = optional > factory = null > autoenable = true > immediate = true > implementation = org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService > state = Unsatisfied > properties = {as.version=710.beta1} > serviceFactory = false > serviceInterface = [org.jboss.ide.eclipse.as.core.server.v7.management.IJBoss7ManagerService] > references = null > located in bundle = org.jboss.ide.eclipse.as.management.as71_2.3.0.v20111202-0909-H875-M5 [786] > ] > Component2: Component[ > name = org.jboss.ide.eclipse.as.management.as7.service > activate = activate > deactivate = deactivate > modified = > configuration-policy = optional > factory = null > autoenable = true > immediate = true > implementation = org.jboss.ide.eclipse.as.internal.management.as7.JBoss7ManagerService > state = Unsatisfied > properties = {as.version=700} > serviceFactory = false > serviceInterface = [org.jboss.ide.eclipse.as.core.server.v7.management.IJBoss7ManagerService] > references = null > located in bundle = org.jboss.ide.eclipse.as.management.as7_2.3.0.v20111202-0909-H875-M5 [785] > ] -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17685) why does forge website trigger automatic restart when changing just a .class ?

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-17685?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-17685. --------------------------------- Closing, nothing to do. > why does forge website trigger automatic restart when changing just a .class ? > ------------------------------------------------------------------------------ > > Key: JBIDE-17685 > URL: https://issues.redhat.com/browse/JBIDE-17685 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Max Andersen > Priority: Major > > git clone git://github.com/forge/website.git > import the project > deploy to server see it deployed > change a java class - save. > it redeploys the app - as if the rewrite servlet jar changed. > why is that ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16123) server adapter does not detect running server

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-16123?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-16123. --------------------------------- Closing, nothing to do. > server adapter does not detect running server > --------------------------------------------- > > Key: JBIDE-16123 > URL: https://issues.redhat.com/browse/JBIDE-16123 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.CR1 > Reporter: André Dietisheim > Assignee: Rob Stryker > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14592) jboss EAP 6.1.0.alpha1 domain mode deployment on Eclipse Kepler Release

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-14592?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-14592. --------------------------------- Closing, nothing to do. > jboss EAP 6.1.0.alpha1 domain mode deployment on Eclipse Kepler Release > ----------------------------------------------------------------------- > > Key: JBIDE-14592 > URL: https://issues.redhat.com/browse/JBIDE-14592 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Jignesh Patel > Assignee: Rob Stryker > Priority: Major > > When we have tried to deploy Jboss EAP6.1.alpha in domain mode through eclipse Kepler, encounter following bug. > 14:42:31,064 INFO [org.jboss.as] (MSC service thread 1-6) JBAS015899: JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) starting > 14:42:31,346 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:141) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.server.ServerService.boot(ServerService.java:308) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:188) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_45] > Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[3,1] > Message: Unexpected element '{urn:jboss:domain:1.4}domain' > at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final] > at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:133) [jboss-as-controller-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > ... 3 more -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17256) "Next" button still disabled after completed download of a runtime

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-17256?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-17256. --------------------------------- Closing, nothing to do. > "Next" button still disabled after completed download of a runtime > ------------------------------------------------------------------ > > Key: JBIDE-17256 > URL: https://issues.redhat.com/browse/JBIDE-17256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Reporter: Lars Heinemann > Priority: Major > > After downloading a runtime the Home directory is pointing to the correct folder but the "Next" button is disabled still. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16742) wildfly server always crashes in eclipse 4.3.1 during deployment

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-16742?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-16742. --------------------------------- Closing, nothing to do. > wildfly server always crashes in eclipse 4.3.1 during deployment > ----------------------------------------------------------------- > > Key: JBIDE-16742 > URL: https://issues.redhat.com/browse/JBIDE-16742 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Final > Environment: windows 7, eclipse 4.3.1, wildfly 8.0.0.Final jboss tools 4.1.1 > Reporter: Richard Yang > Assignee: Rob Stryker > Priority: Major > Fix For: 4.1.2.Final > > Attachments: .log, server.log > > > When Wildfly tries to deploy war, after a while, eclipse pops out error saying eclipse.exe is not responding and then eclipse exits with javaw.exe not cleaned up. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17111) Publish to server always grayed out

by Josef Kopriva (Jira)

[ https://issues.redhat.com/browse/JBIDE-17111?page=com.atlassian.jira.plug... ] Josef Kopriva closed JBIDE-17111. --------------------------------- Closing, nothing to do. > Publish to server always grayed out > ----------------------------------- > > Key: JBIDE-17111 > URL: https://issues.redhat.com/browse/JBIDE-17111 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Eclipse 4.4M6 > Windows 7 > Reporter: George Lindholm > Assignee: Rob Stryker > Priority: Minor > Attachments: JBIDE-17111.png, clipboard.png, clipboard.png > > > The Publish icon in the Servers view is always grayed out > JBossAS Tools: 3.0.0.Beta1-v20140408-1231-B31 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 2020