May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12066) Unable to create Maven archetype project from Nexus Indexer

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-12066: ---------------------------------------- Summary: Unable to create Maven archetype project from Nexus Indexer Key: JBIDE-12066 URL: https://issues.jboss.org/browse/JBIDE-12066 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Rastislav Wagner Assignee: Fred Bricon Priority: Blocker Fix For: 3.3.0.CR1 org.eclipse.core.runtime.CoreException: Could not resolve artifact jboss.maven-archetypes:jboss-archetype-simple:pom:1.0 at org.eclipse.m2e.core.internal.embedder.MavenImpl.resolve(MavenImpl.java:658) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.resolveArchetype(ProjectConfigurationManager.java:625) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:536) at org.eclipse.m2e.core.ui.internal.wizards.MavenProjectWizard$5.doCreateMavenProjects(MavenProjectWizard.java:241) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob$1.doCreateMavenProjects(AbstactCreateMavenProjectJob.java:45) at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73) at org.eclipse.m2e.core.ui.internal.wizards.AbstactCreateMavenProjectJob.runInWorkspace(AbstactCreateMavenProjectJob.java:49) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Contains: Missing jboss.maven-archetypes:jboss-archetype-simple:pom:1.0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
9
0 / 0

[JBoss JIRA] (JBDS-1878) Find a way to set up / install EAP6/WFK repos (automatically)

by Fred Bricon (Created) (JIRA)

Find a way to set up / install EAP6/WFK repos (automatically) ------------------------------------------------------------- Key: JBDS-1878 URL: https://issues.jboss.org/browse/JBDS-1878 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: installer, maven Affects Versions: 5.0.0.M2 Reporter: Fred Bricon Fix For: 5.0.0.CR1 We need to find a way to let users easily use the EAP6 / WFK maven repos. Basically, it boils down to 2 use cases : 1 - The user wants to use the repos from his enterprise repository manager 2 - The user wants to install the repos locally Installation / configuration of the repos can be done either via the JBDS installer (Burr's idea) or a JBDS plugin (Max's idea). 1 - If the user chooses to use a remote repo, then may be open a page detailing the required steps to install EAP6/WFK on nexus/artifactory/archiva. I'm not sure this would be necessary since Joe developper will probably won't have the rights to manage his enterprise repo management app. So we might as well bail and assume he has everything configured. 2 - The user chooses to install the repos locally. We can detect if the repos are already configured before continuing : Check if one remote repository already contains specific jars only available in EAP6/WFK repos or look for a specific snippet in the user / global settingsea. - if nothing is found, unzip and either ask the user to change his settings manually (showing him the right xml snippet) or do it automatically for him (by adding a new profile activated by default) Question is : where are the repos coming from? will they be publicly available, i.e. easily downloadable? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
7
0 / 0

[JBoss JIRA] (JBIDE-12053) JBoss Enterprise Application Platform 6 and JBoss AS 7

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-12053: ----------------------------------- Summary: JBoss Enterprise Application Platform 6 and JBoss AS 7 Key: JBIDE-12053 URL: https://issues.jboss.org/browse/JBIDE-12053 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Burr Sutter Use the phrase "JBoss Enterprise Application Platform 6 and JBoss AS 7" in the java ee 6 web archetype This is your project! It's a sample, deployable Maven 3 project to help you get your foot in the door developing with Java EE 6 on JBoss AS 7.1. This project is setup to allow you to create a compliant Java EE 6 application using JSF 2.0, CDI 1.0, EJB 3.1, JPA 2.0 and Bean Validation 1.0. It includes a persistence unit and some sample persistence and transaction code to help you get your feet wet with database access in enterprise Java. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-12032) JMX connection to remote AS7 not working even with -Dmanagement set up

by Martin Malina (JIRA)

Martin Malina created JBIDE-12032: ------------------------------------- Summary: JMX connection to remote AS7 not working even with -Dmanagement set up Key: JBIDE-12032 URL: https://issues.jboss.org/browse/JBIDE-12032 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar Reporter: Martin Malina Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.CR1 JMX connection to remote AS7 server is broken again :( It may have to do with JBIDE-11921 or JBIDE-12028. When you start a remote AS7 server with both "Listen on all interfaces" and "Expose your management port" checked and then try to expand the server in MBean Explorer, it displays "Loading" for a while and then errors with: {code} !ENTRY org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.013 !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property !STACK 1 org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:105) at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87) at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) Caused by: java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:154) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) ... 7 more !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-05-28 13:25:21.014 !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property !STACK 0 java.lang.RuntimeException: Operation failed with status WAITING at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:154) at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248) at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:105) at org.jboss.tools.jmx.core.tree.NodeUtils.createObjectNameTree(NodeUtils.java:51) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.loadRoot(JBossServerConnection.java:87) at org.jboss.tools.jmx.ui.internal.views.navigator.MBeanExplorerContentProvider$1.run(MBeanExplorerContentProvider.java:110) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} (Yes, two errors - perhaps for the two intended connections?) Also, the start poller was set to Web Poller, as the default JBoss 7 Manager Service currently doesn't work due to JBIDE-12028 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12028) Remote AS7 keeps starting forever

by Martin Malina (JIRA)

Martin Malina created JBIDE-12028: ------------------------------------- Summary: Remote AS7 keeps starting forever Key: JBIDE-12028 URL: https://issues.jboss.org/browse/JBIDE-12028 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.CR1 Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar Reporter: Martin Malina Assignee: Rob Stryker Fix For: 3.3.0.CR1 When you set up a remote AS7/EAP6 server and start it, it keeps starting forever. This problem occurs only when the management port is not set up. This may be a regression in JBIDE-11921 . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
7
0 / 0

[JBoss JIRA] (JBDS-2144) JBDS 5 Beta 3 - enterprise=true breaks Forge

by Burr Sutter (JIRA)

Burr Sutter created JBDS-2144: --------------------------------- Summary: JBDS 5 Beta 3 - enterprise=true breaks Forge Key: JBDS-2144 URL: https://issues.jboss.org/browse/JBDS-2144 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Environment: Version: 5.0.0.Beta3 Build id: v20120514-2058-H159-Beta3 Build date: 20120514-2058 Reporter: Burr Sutter Priority: Blocker steps to reproduce: 1) Click on Java EE Web Project in JBoss Central 2) Select EAP6 Beta2 as the Target Runtime - assumes you have updated the settings.xml with the correct EAP6.1 maven repo 3) Run As on Server works 4) Right-click on Project name and select Show In Forge Console 5) Type "entity" and hit return [jboss-javaee6-webapp-eap] jboss-javaee6-webapp-eap $ entity ***ERROR*** [entity] Plugin is not usable in current scope or project attached is the pom.xml for the project -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

8
25
0 / 0

[JBoss JIRA] (JBIDE-11850) OpenShift server: provide warning when changing deploy project

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11850: -------------------------------------- Summary: OpenShift server: provide warning when changing deploy project Key: JBIDE-11850 URL: https://issues.jboss.org/browse/JBIDE-11850 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers, openshift Affects Versions: 3.3.0.Beta3 Reporter: Stefan Bunciak Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.CR1 >From my point of view does not make sense to allow users to switch deploy project from JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app instead of JBoss a NPE was thrown: {code} java.lang.NullPointerException at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-12001) Cannot Start AS7.1.1 server with a space in path using JBoss Tools

by Darren Jones (JIRA)

Darren Jones created JBIDE-12001: ------------------------------------ Summary: Cannot Start AS7.1.1 server with a space in path using JBoss Tools Key: JBIDE-12001 URL: https://issues.jboss.org/browse/JBIDE-12001 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Environment: Windows 7 64-bit; Java 1.6.0u23; Eclipse 3.7.2 EE edition with JBoss Tools; Reporter: Darren Jones Assignee: Rob Stryker I have a 7.1.1 server installed in "F:\My Servers\jboss-as-7.1.1.Final" (note the space in the path). It starts just fine using the standalone.bat file within that folder. But if I try to start the server from within Eclipse using JBoss Tools (3.3.0 Beta 3), I get this error in the console: java.lang.NoClassDefFoundError: F:/My Caused by: java.lang.ClassNotFoundException: F:.My at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) Exception in thread "main" I've captured the command line used when I right-click on the server in Eclipse and Debug. Here it is (copied from Process Monitor's Process Tree): "C:\Program Files\Java\jdk1.6.0_23\bin\javaw.exe" -agentlib:jdwp=transport=dt_socket,suspend=y,address=localhost:63144 -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Dorg.jboss.boot.log.file= F:/My Servers/jboss-as-7.1.1.Final/standalone/log/boot.log Servers/jboss-as-7.1.1.Final/standalone/log/boot.log -Dlogging.configuration=file:/F:/My%20Servers/jboss-as-7.1.1.Final/standalone/configuration/logging.properties -Djboss.home.dir= F:/My Servers/jboss-as-7.1.1.Final Servers/jboss-as-7.1.1.Final -Dfile.encoding=Cp1252 -classpath "F:\My Servers\jboss-as-7.1.1.Final\jboss-modules.jar" org.jboss.modules.Main -mp "" F:/My Servers/jboss-as-7.1.1.Final/modules Servers/jboss-as-7.1.1.Final/modules -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -b localhost --server-config=standalone.xml -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

4
11
0 / 0

[JBoss JIRA] (JBIDE-11938) CLONE - CLONE - AS Component N&N

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11938: ------------------------------------------- Summary: CLONE - CLONE - AS Component N&N Key: JBIDE-11938 URL: https://issues.jboss.org/browse/JBIDE-11938 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: JBossAS/Servers Affects Versions: 3.3.0.M2 Reporter: Denis Golovin Assignee: Rob Stryker Fix For: 3.3.0.Beta3 project = "Tools (JBoss Tools)" AND affectedVersion = 12316349 AND fixVersion = "3.3.0.M3" AND component = "JBossAS/Servers" AND status = Resolved -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-11611) Cannot create Seam Project with Seam 2.3 Beta1

by Martin Malina (JIRA)

Martin Malina created JBIDE-11611: ------------------------------------- Summary: Cannot create Seam Project with Seam 2.3 Beta1 Key: JBIDE-11611 URL: https://issues.jboss.org/browse/JBIDE-11611 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta3 Environment: JBT nightly 2012-04-21 Mac OS X 10.7 Lion Reporter: Martin Malina Assignee: Alexey Kazakov Fix For: 3.3.0.Beta3 Attachments: seam-copy-failed.png When I try to create Seam project using EAP 6 ER5 and Seam 2.3.0.Beta1 from WFK 2.0 ER4, I get the following error: Failed while installing Seam 2.3. Copy failed - '/Users/rasp/jbossqa/runtimes/jboss-seam-2.3.0.Beta1-redhat-1/bootstrap' does not exist. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 10 months

5
16
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 May 2012