October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15645) Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15645?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15645: ------------------------------------- [~rafabene] : I submitted a PR for adding Labels to the Archetype model : https://github.com/jboss-jdf/jdf-stacks-client/pull/12 You'll need to perform a release ASAP so I can embed the new stacks client to JBoss Tools. Once I'm done with my changes in JBT/Central, I'll amend your own PR to update the stacks.yaml with the new archetype labels. As discussed by email, we'll add the following labels to the Archetype definitions : - type : javaee-web, javaee-ear, html5-mobile, richfaces, errai - isBlank : true if it's a blank archetype - environment : web-ee6 or full-ee6, depending on the required Java EE profile. We'll add web-ee7, full-ee7 for future wildfly archetypes - target : product or community > Revisit archetype switching based on runtime (community/product) and runtime level (ee6 vs ee7) > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15645 > URL: https://issues.jboss.org/browse/JBIDE-15645 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.1.0.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Beta1 > > > Enterprise/Community versions of archetypes will no longer be switchable through the -Denterprise switch. Different GAV coordinates will need to be used instead. > We need to come up with changes in both stacks.yaml format and JBDS to cope with this > Some discussion on etherpad : http://ether-man.rhcloud.com/p/funkyarchetype -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15672) bump maintenance parent pom

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15672?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15672: ------------------------------------- Approved by Andre. > bump maintenance parent pom > --------------------------- > > Key: JBIDE-15672 > URL: https://issues.jboss.org/browse/JBIDE-15672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.1.1.Beta1 > > -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15672) bump maintenance parent pom

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15672: ----------------------------------- Summary: bump maintenance parent pom Key: JBIDE-15672 URL: https://issues.jboss.org/browse/JBIDE-15672 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.1.1.Beta1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.1.1.Beta1 -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15614: --------------------------------------- The above comment really belongs to JBIDE-15651. I'm copying it there. > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15651) EAP 6.2 cannot be connected to in MBean Explorer

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15651?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15651: --------------------------------------- Rob said in JBIDE-15614: {quote} Martin: It works for me, but only assuming you have already done the following: 1) Added a user via the add-user.sh script 2) Update the username / password in the server editor to match those values Have you done both of these things? {quote} You're right, when I set up an admin user it then works. But I checked again and for EAP 6.1.0 no user is needed to access JMX on a local server. So something has changed in EAP 6.2. But I spoke to EAP QE and they say the <local> is still set for the SecurityRealm, so things should work the same. And indeed, jboss-cli.sh is still able to connect to a local running EAP 6.2 without any password. So can you please check what changed here? It may even be a bug in EAP. > EAP 6.2 cannot be connected to in MBean Explorer > ------------------------------------------------ > > Key: JBIDE-15651 > URL: https://issues.jboss.org/browse/JBIDE-15651 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx > Affects Versions: 4.1.1.Alpha2 > Environment: JBDS 7.1.0.Alpha2 B431 > Reporter: Martin Malina > Fix For: 4.1.1.Beta1 > > > When you start EAP 6.2.0.ER4 (or ER5) added manually and then try Show in -> MBean Explorer, it will show the server as [disconnected] and the server won't connect. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-15614 at 10/15/13 4:12 AM: ----------------------------------------------------------------- [~rawb], you're right, when I set up an admin user it then works. But I checked again and for EAP 6.1.0 no user is needed to access JMX on a local server. So something has changed in EAP 6.2. But I spoke to EAP QE and they say the <local> is still set for the SecurityRealm, so things should work the same. And indeed, jboss-cli.sh is still able to connect to a local running EAP 6.2 without any password. So can you please check what changed here? It may even be a bug in EAP. was (Author: mmalina): Rob, is this a new thing with EAP 6.2 that the local filesystem authetication is no longer on? Because I don't need to setup any users for EAP 6.1.0 and JMX connection just works (on a local server that is). It seems this is the case - even web admin console asks me for password now :-\ And yes, I just checked, and when I set up a user it works. > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15647) Compile errors when building arquillian with Luna target platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15647?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15647: --------------------------------------------- I grepped all of jbosstools code base and I can only find reference to BundleClassLoader in Arquillian and it is only referenced in an instanceof check. That should be trivial to do dynamic test instead of hardcoded version ? or even better - find a way to avoid having to rely on super internal class loading semantics :) > Compile errors when building arquillian with Luna target platform > ----------------------------------------------------------------- > > Key: JBIDE-15647 > URL: https://issues.jboss.org/browse/JBIDE-15647 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.x > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > > When building the arquillian component with Luna TP(tpc.version=4.40.0.Alpha1-SNAPSHOT) there are the following compile errors: > {code} > [ERROR] import org.eclipse.osgi.framework.adaptor.BundleClassLoader; > [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > [ERROR] The import org.eclipse.osgi.framework.adaptor cannot be resolved > [ERROR] > ... > [ERROR] || tmp instanceof BundleClassLoader) > [ERROR] ^^^^^^^^^^^^^^^^^ > [ERROR] BundleClassLoader cannot be resolved to a type > {code} > The errors are caused by the change of OSGi internals. > The org.eclipse.osgi.framework.adaptor package and the BundleClassloader class have been removed from Luna. > The changes aren't compatible with the previous Eclipse versions, so we need a separate branch for Luna. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15614: --------------------------------------- Rob, is this a new thing with EAP 6.2 that the local filesystem authetication is no longer on? Because I don't need to setup any users for EAP 6.1.0 and JMX connection just works (on a local server that is). It seems this is the case - even web admin console asks me for password now :-\ And yes, I just checked, and when I set up a user it works. > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15614: ------------------------------------- Martin: It works for me, but only assuming you have already done the following: 1) Added a user via the add-user.sh script 2) Update the username / password in the server editor to match those values Have you done both of these things? > Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate > ------------------------------------------------------------------------ > > Key: JBIDE-15614 > URL: https://issues.jboss.org/browse/JBIDE-15614 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection, server > Affects Versions: 4.1.0.Final > Environment: JBDS 7.0.0.GA > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Beta1 > > > 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0. > 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2 > Let me know if you want subtasks for these two. -- 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13208) Allow custom 'standalone' mode directory in AS7 server plugin

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13208?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-13208: ------------------------------------- > This issue was set to be fixed in 4.2.0.Alpha1 which was released a month ago - so that seems wrong. I am 99% sure that 4.2.0.Alpha1 is unreleased. I do not recall us branching master at all, as the focus has mostly been on maintenance. Also the team calendar indicates that 4.1.1.Final will be in December, and 4.2.0.Alpha1 has no date attached to it, so I assume that is for next year. > Allow custom 'standalone' mode directory in AS7 server plugin > ------------------------------------------------------------- > > Key: JBIDE-13208 > URL: https://issues.jboss.org/browse/JBIDE-13208 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Environment: Mac OS-X 10.8.2, Java 6, Java 7, JBoss AS 7.x, JBoss EAP 6, JBDS 5.0.1 > Reporter: Duncan Doyle > Assignee: Rob Stryker > Labels: f2f2012, new_and_noteworthy > Fix For: 4.2.0.Alpha1 > > > As with JBoss EAP5.x, I have the habit of working in a copy of a 'profile' directory. With JBoss AS7/EAP6 I therefore work in copies of 'standalone' and 'domain' (depending on the operational mode). When I start AS/EAP, I reference the correct server directory with the 'jboss.server.base.dir' or 'jboss.domain.base.dir' system property. This allows me, among other things, to run multiple AS/EAP instances from a single JBoss AS/EAP installation. > It seems that the JBDS AS7 plugin only allows me to reference the default 'standalone' directory. I'm not able to select a different directory in the 'JBoss Runtime' configuration screen. I would propose to add the possibility to start a JBoss AS7/EAP6 instance from a different directory than 'standalone'. -- 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, 8 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 2013