October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18461) org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18461?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18461: ------------------------------------- I've closed the clone, because as far as I can tell, there won't be a 4.1.3. Sorry. > org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > -------------------------------------------------------------------------------- > > Key: JBIDE-18461 > URL: https://issues.jboss.org/browse/JBIDE-18461 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Brian Fitzpatrick > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.CR2 > > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18523) [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18523?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18523. --------------------------------- Fix Version/s: (was: 4.1.2.Final) Resolution: Rejected 4.1.2 was like 9 months ago. There is no 4.1.3 planned. Sorry. > [JBDS 7.1.1] org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants doesn't include EAP_61 > --------------------------------------------------------------------------------------------- > > Key: JBIDE-18523 > URL: https://issues.jboss.org/browse/JBIDE-18523 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Priority: Critical > > When working through JBIDE-16066 for the web services wizard, I discovered that EAP_61 is not included in the array provided by the ALL_JBOSS_RUNTIMES list in org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants. I can work around this on the WS side, but I would imagine that this has a broader impact to other tooling projects using the runtime framework -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15189) Check compatible JRE/JDK when adding server via runtime detection

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15189?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15189: ----------------------------------- Assignee: Rob Stryker > Check compatible JRE/JDK when adding server via runtime detection > ----------------------------------------------------------------- > > Key: JBIDE-15189 > URL: https://issues.jboss.org/browse/JBIDE-15189 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.1.0.CR1 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.1.x, 4.2.x > > > Now, people are not allowed to create runtime when no compatible java is configured in eclipse (JBIDE-14858). > But when adding server and runtime via runtime detection, server and runtime are added even though no compatible java is configured. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18554) JPP 6.1 is in "started" state before it is completely started.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18554?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-18554. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.2.0.Final Resolution: Rejected I've tested the following workarounds: 1) Open server editor, change pollers to mgmt poller or 2) Open server editor, click on behavior profile, switch to local and "prefers mgmt operations" Both of these work as expected. If you want a server that uses mgmt operations in all places, you should modify the behavior profile as done in step 2). This would include performing deployments over management. If on the other hand you just want to use the management poller, you should perform as step 1) indicates, and only modify the server state detectors / pollers to use management. As far as I'm concerned, the server is behaving appropriately. We should not be using management pollers if the user created it in the local + filesystem operation profile. The web port poller has its limitations but is functioning as expected here. The management poller works as expected here as well. > JPP 6.1 is in "started" state before it is completely started. > -------------------------------------------------------------- > > Key: JBIDE-18554 > URL: https://issues.jboss.org/browse/JBIDE-18554 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.2.0.Final > > > When starting JPP 6.1 (I haven't tried it with other versions yet), the server is in "Started" state in servers view before it is completely started. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error

by Cássio Mazzochi Molin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ] Cássio Mazzochi Molin commented on JBIDE-18697: ----------------------------------------------- [~rob.stryker], the error no longer occurred after changing the permissions. So, I think it's a good idea changing the error message. PS.: The latest JBoss Tools version is amazing! And I am really impressed with the quick responses I have on JBoss Developer. > Error deploying exploded war on windows; fs / copy error > -------------------------------------------------------- > > Key: JBIDE-18697 > URL: https://issues.jboss.org/browse/JBIDE-18697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Rob Stryker > Fix For: 4.2.1.Final > > > https://developer.jboss.org/message/907562 > A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-18700: -------------------------------- Fix Version/s: 4.3.0.Alpha1 > EAP 6.x Configuration doesn't select Java 7 by default > ------------------------------------------------------ > > Key: JBIDE-18700 > URL: https://issues.jboss.org/browse/JBIDE-18700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha1 > > > - Create a new EAP 6.3 server > - Create a new Dynamic Web Project > - Select the EAP runtime > => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer." > !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png! > The EAP 6 Default Configuration should have the Java 1.7 Facet set by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18700) EAP 6.x Configuration doesn't select Java 7 by default

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18700?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-18700: ------------------------------------- We have a few options here, but not really ;) We're basically stuck and have to wait for new API =P Our current API only has a minimum execution environment. If we move this up to java7 for eap6.x, then unfortunately java6 will no longer appear as an option to users for any eap6.x server. This obviously isn't acceptable. We should ideally have a minimim execenv, a maximum, and a default, for each server/runtime type. The second problem is that AbstractJREComposite unfortunately fills its data during its constructor, rather than fit in with the workflow of the other widgets like RuntimeHomeComposite which are created first, and filled after the runtime working copy has been created. That should be an easy fix, though, and may open the possibility that we could ensure different default / min / max execenv depending on the inner details of a given server home. But, since we're lacking that api, and currently only have minimums, I think we're pretty stuck here until API addition has occurred. > EAP 6.x Configuration doesn't select Java 7 by default > ------------------------------------------------------ > > Key: JBIDE-18700 > URL: https://issues.jboss.org/browse/JBIDE-18700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Fred Bricon > Assignee: Rob Stryker > > - Create a new EAP 6.3 server > - Create a new Dynamic Web Project > - Select the EAP runtime > => An error is shown : "Dynamic Web Module 3.1 requires Java 1.7 or newer." > !http://content.screencast.com/users/fbricon/folders/Jing/media/ee20c272-5761-40ab-8fe8-1004533501c7/00000025.png! > The EAP 6 Default Configuration should have the Java 1.7 Facet set by default. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18708) Provide content assist on hibernate properties values in persistence.xml

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18708: ------------------------------------- Summary: Provide content assist on hibernate properties values in persistence.xml Key: JBIDE-18708 URL: https://issues.jboss.org/browse/JBIDE-18708 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: hibernate Affects Versions: 4.2.0.Final Reporter: Xavier Coulon in persistence.xml, it would be convenient to have content assist on values for Hibernate properties such as those below: {code} <property name="hibernate.hbm2ddl.auto" value="create-drop" /> <property name="hibernate.show_sql" value="false" /> {code} especially the alternative values to {{create-drop}} ;-) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Chunyun Chen commented on JBIDE-18696: -------------------------------------- refreshing connection does not take effect. > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-18696: ------------------------------------------ ok, thanks that clarifies it. The weird part is that you cannot replicate it in OpenShift online and so can't I. Does refreshing your connection in OpenShift Explorer (in OpenShift Explorer: pick "Refresh" in the context menu of the connection) help? > Application wizard: Can not show quickstarts list > ------------------------------------------------- > > Key: JBIDE-18696 > URL: https://issues.jboss.org/browse/JBIDE-18696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Final > Environment: Windows 8 + Eclipse Luna (4.4) > Reporter: Chunyun Chen > Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log > > > The quickstarts are unable to be shown, so any quickstarts can not be chosen to create. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014