September 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-12463) git executable not found in Windows and JBoss Tools

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12463?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-12463: ----------------------------------------- Hi Koen / Nick, I haven't used Windows for awhile, so I guess this issue could be closed for now. I'll reopen in case this happens again. Thank you very much. > git executable not found in Windows and JBoss Tools > --------------------------------------------------- > > Key: JBIDE-12463 > URL: https://issues.jboss.org/browse/JBIDE-12463 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Fix For: 4.0.0.Beta1 > > > I have msysgit installed on my machine and placed on the PATH dir. When I run the "git" command, the following is displayed: > {code} > [bootdemo] bootdemo $ git > ***ERROR*** [git] Cannot run program "git" (in directory "D:\work\workspace\bootdemo"): CreateProcess error=2, The system cannot find the file specified > {code} -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12701) Server runtime libraries are not added into classpath of the project

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12701: ----------------------------------------- Summary: Server runtime libraries are not added into classpath of the project Key: JBIDE-12701 URL: https://issues.jboss.org/browse/JBIDE-12701 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Jaroslav Jankovič Assignee: Rob Stryker Priority: Blocker When I tried several project/components requiring server runtime libraries, all of them cannot be resolved. Then I found out, that there are no libraries located in Project Explorer under Libraries -> JBoss 7.1 Runtime. I tried EAP 6.0, AS 7.1.1, AS 7.1.0, AS 7.0.0, AS 6.0 with same result, so it doesn't seem to be runtime-specific issue. -- 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

13 years, 6 months

4
7
0 / 0

[JBoss JIRA] (JBIDE-12616) Project examples have disabled Finish button

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-12616: --------------------------------------- Summary: Project examples have disabled Finish button Key: JBIDE-12616 URL: https://issues.jboss.org/browse/JBIDE-12616 Project: Tools (JBoss Tools) Issue Type: Bug Environment: Nightly build from 13th Sept 2012 Reporter: Lucia Jelinkova Priority: Critical I installed the following plugins into Eclipse Juno: org.jboss.tools.community.project.examples.feature_1.4.0.Alpha2-v20120913-1254-B32 org.jboss.tools.project.examples.feature_1.4.0.Alpha2-v20120913-1254-B32 When I select any example the Finish button is always disabled. This used to work all right before. -- 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

13 years, 6 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12692) Cannot install org.jboss.tools.ws.jaxrs.feature.source.feature.group from JBT US

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-12692: ------------------------------------ Summary: Cannot install org.jboss.tools.ws.jaxrs.feature.source.feature.group from JBT US Key: JBIDE-12692 URL: https://issues.jboss.org/browse/JBIDE-12692 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.0.0.Alpha2 Reporter: Jiri Peterka Assignee: Nick Boldt Priority: Blocker Fix For: 4.0.0.Alpha2 Cannot complete the install because one or more required items could not be found. Software being installed: org.jboss.tools.ws.jaxrs.feature.source.feature.group 1.4.0.Alpha2-v20120922-0406-B33 Missing requirement: JBoss JAX-RS Tooling (Core) 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.core 1.4.0.Alpha2-v20120922-0406-B33) requires 'bundle org.eclipse.wst.sse.core 1.1.701' but it could not be found Cannot satisfy dependency: From: JBoss JAX-RS Tools 1.4.0.Alpha2-v20120922-0406-B33 (org.jboss.tools.ws.jaxrs.feature.feature.group 1.4.0.Alpha2-v20120922-0406-B33) To: org.jboss.tools.ws.jaxrs.core [1.4.0.Alpha2-v20120922-0406-B33] Cannot satisfy dependency: From: org.jboss.tools.ws.jaxrs.feature.source.feature.group 1.4.0.Alpha2-v20120922-0406-B33 To: org.jboss.tools.ws.jaxrs.feature.feature.group [1.4.0.Alpha2-v20120922-0406-B33] -- 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

13 years, 6 months

4
12
0 / 0

[JBoss JIRA] (JBIDE-12202) Publishing of exploded projects to remote servers is very slow

by Martin Malina (JIRA)

13 years, 6 months

2
4
0 / 0

[JBoss JIRA] Created: (JBIDE-8866) Move all plugins up to baseline

by Rob Stryker (JIRA)

Move all plugins up to baseline ------------------------------- Key: JBIDE-8866 URL: https://issues.jboss.org/browse/JBIDE-8866 Project: Tools (JBoss Tools) Issue Type: Task Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Rob Stryker Assignee: Nick Boldt Fix For: 3.3.0.M2 Not really sure who to assign this to, short of making three dozen separate jira issues ;) I have 33 patches, one for each module, which modify all manifest.mf version numbers (in plugins, not in tests) to be brought up to our current baseline. So assuming our baseline for some specific plugin is 3.6.200, these patches will turn a dependency on this.specific.runtime into this.specific.runtime;bundle-version="3.6.200". If a plugin currently reads this.specific.plugin;bundle-version="3.5.0", it will move it up to this.specific.runtime;bundle-version="3.6.200". Etc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7472) ZipException occurs if I remove any JAR from WEB-INF/lib when the target server is running.

by Alexey Kazakov (JIRA)

ZipException occurs if I remove any JAR from WEB-INF/lib when the target server is running. ------------------------------------------------------------------------------------------- Key: JBIDE-7472 URL: https://jira.jboss.org/browse/JBIDE-7472 Project: Tools (JBoss Tools) Issue Type: Bug Components: common Affects Versions: 3.2.0.Beta2 Reporter: Alexey Kazakov Assignee: Rob Stryker Fix For: 3.2.0.Beta2 1. Create JSF2 project (I guess it can be any dynamic web project) 2. Deploy it to AS6.M5 (haven't try on other servers) 3. Start the server 4. Remove any JAR from WEB-INF/lib folder 5. I get a lot of IOExceptions and the project is not built anymore 6. Stopping server/re-building project doesn't help. In debugger I see that all the threads which try to open any JAR in class path (at least from AS/common/lib folder) fail with ZipException 7. Only restarting Eclipse can help. Here are the exceptions (a lot of them): org.eclipse.core.runtime.CoreException: I/O exception at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2524) at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getJar(JarPackageFragmentRoot.java:152) at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.computeChildren(JarPackageFragmentRoot.java:78) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.initializePackageNames(JavaProjectElementInfo.java:252) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.getProjectCache(JavaProjectElementInfo.java:225) at org.eclipse.jdt.internal.core.JavaProjectElementInfo.newNameLookup(JavaProjectElementInfo.java:290) at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2282) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:57) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:64) at org.eclipse.jdt.internal.core.CancelableNameEnvironment.<init>(CancelableNameEnvironment.java:26) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:162) at org.eclipse.jdt.internal.core.CompilationUnitProblemFinder.process(CompilationUnitProblemFinder.java:255) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.makeConsistent(ReconcileWorkingCopyOperation.java:190) at org.eclipse.jdt.internal.core.ReconcileWorkingCopyOperation.executeOperation(ReconcileWorkingCopyOperation.java:89) at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:728) at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788) at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1244) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87) at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178) at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114) at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:133) at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105) at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:398) at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173) Caused by: java.util.zip.ZipException: error in opening zip file at java.util.zip.ZipFile.open(Native Method) at java.util.zip.ZipFile.<init>(ZipFile.java:114) at java.util.zip.ZipFile.<init>(ZipFile.java:131) at org.eclipse.jdt.internal.core.JavaModelManager.getZipFile(JavaModelManager.java:2518) ... 27 more -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
18
0 / 0

[JBoss JIRA] (JBDS-2245) every time I restart JBDS 5.0.1, I get prompted to add a new (identical) EAP 6 runtime

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2245: -------------------------------- Summary: every time I restart JBDS 5.0.1, I get prompted to add a new (identical) EAP 6 runtime Key: JBDS-2245 URL: https://issues.jboss.org/browse/JBDS-2245 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: runtime Affects Versions: 5.0.1.GA Reporter: Nick Boldt 0. Install JBDS 5.0.0 from jbdevstudio-product-eap-universal-5.0.0.v20120615-1714-H213-GA.jar 1. Start JBDS. Help > Check for Updates. Install all updates. Restart. 2. On restart, you'll be prompted to "Press OK to create the runtimes with a checkmark." Select the included runtime (the one that came in the installer) and hit OK. 3. Restart JBDS via File > Restart. 4. On restart, you'll be prompted to "Press OK to create the runtimes with a checkmark." Select the included runtime (the one that came in the installer) and hit OK. 5. Restart JBDS via File > Restart. 6. ... -- 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, 6 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-12445) Maven plugin for Hibernate Tools 4.x

by Marcel Stör (JIRA)

Marcel Stör created JBIDE-12445: ----------------------------------- Summary: Maven plugin for Hibernate Tools 4.x Key: JBIDE-12445 URL: https://issues.jboss.org/browse/JBIDE-12445 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Marcel Stör There's a Maven plugin for the older tools line and Hibernate 3.6.x: http://mojo.codehaus.org/maven-hibernate3/hibernate3-maven-plugin/. There's nothing similar for Hibernate 4.x which is a pity. Please either: - provide a new Maven plugin from under the JBoss/Hibernate umbrella or - take the hibernate3-maven-plugin guys under your wings and have them upgrade their plugin -- 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, 6 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-12444) Support auto type registration during hbm2ddl

by Marcel Stör (JIRA)

Marcel Stör created JBIDE-12444: ----------------------------------- Summary: Support auto type registration during hbm2ddl Key: JBIDE-12444 URL: https://issues.jboss.org/browse/JBIDE-12444 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Marcel Stör As discussed at https://community.jboss.org/message/753496. One can't make use of Hibernate 4 auto type registration if you also want to run hbm2ddl at some point in the build process. hbm2ddl needs a hook that triggers auto type registration similar to what happens at SessionFactory creation time. Of course the actual user types need to be in the classpath while hbm2ddl runs. -- 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, 6 months

3
3
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 September 2012