[JBoss JIRA] Created: (JBIDE-3439) Refactoring calls Project not found exception when any console configuration reffers to non-existing project
by Dmitry Geraskov (JIRA)
Refactoring calls Project not found exception when any console configuration reffers to non-existing project
------------------------------------------------------------------------------------------------------------
Key: JBIDE-3439
URL: https://jira.jboss.org/jira/browse/JBIDE-3439
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.0.0.cr1
Reporter: Dmitry Geraskov
Assignee: Dmitry Geraskov
Fix For: 3.0.0.CR2
org.eclipse.core.runtime.CoreException: Launch configuration Ddl gen (1) references non-existing project B.
at org.eclipse.jdt.launching.JavaRuntime.abort(JavaRuntime.java:1327)
at org.eclipse.jdt.launching.JavaRuntime.getJavaProject(JavaRuntime.java:1207)
at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.isClassPathAffected(HibernateRefactoringUtil.java:109)
at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.isConfigurationAffected(HibernateRefactoringUtil.java:80)
at org.hibernate.eclipse.launch.core.refactoring.HibernateRefactoringUtil.getAffectedLaunchConfigurations(HibernateRefactoringUtil.java:334)
at org.hibernate.eclipse.launch.core.refactoring.RenameResourceParticipant.createChange(RenameResourceParticipant.java:48)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.createChange(ProcessorBasedRefactoring.java:309)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
at org.eclipse.ltk.core.refactoring.PerformChangeOperation.run(PerformChangeOperation.java:211)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBDS-530) Runtimes still not configured correctly
by Max Rydahl Andersen (JIRA)
Runtimes still not configured correctly
---------------------------------------
Key: JBDS-530
URL: https://jira.jboss.org/jira/browse/JBDS-530
Project: Developer Studio
Issue Type: Bug
Components: integration
Affects Versions: 2.0.0.cr1
Environment: 1812 build
Reporter: Max Rydahl Andersen
Assignee: Denis Golovin
Priority: Blocker
Fix For: 2.0.0.cr1
Using the EAP installer and adding the SOA-P server I get a file with this content:
#Thu Dec 18 12:23:02 CET 2008
server1=jboss-soa-p.4.3.0,SOA-P,4.3,C\:\\work\\products\\jboss-soa-p.4.3.0
The file name is properly escaped now (good), but the error log now says:
Can't create new JBoss Server
java.io.IOException: The filename, directory name, or volume label syntax is incorrect
at java.io.WinNTFileSystem.canonicalize0(Native Method)
at java.io.Win32FileSystem.canonicalize(Unknown Source)
at java.io.File.getCanonicalPath(Unknown Source)
at java.io.File.getCanonicalFile(Unknown Source)
at org.jboss.tools.runtime.JBossRuntimeStartup.earlyStartup(JBossRuntimeStartup.java:172)
at org.eclipse.ui.internal.EarlyStartupRunnable.runEarlyStartup(EarlyStartupRunnable.java:87)
at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:66)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
at org.eclipse.ui.internal.Workbench$54.run(Workbench.java:2169)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
But for some reason the two servers (the builtin and the soap seem to be configured correctly ?)
But there is NO Seam nor jbpm runtimes setup for neither of these.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBIDE-1928) JBoss server runtime points to wrong folder.
by Aliaksey Nis (JIRA)
JBoss server runtime points to wrong folder.
--------------------------------------------
Key: JBIDE-1928
URL: http://jira.jboss.com/jira/browse/JBIDE-1928
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 2.1
Environment: WindowsXP SP2
jbdevstudio-win32-1.0.0.GA.jar
JBoss Developer Studio
Version: 2.1
Build: jbdevstudio-win32-1.0.0.GA.jar
JDK 1.5_08
Reporter: Aliaksey Nis
EXECUTE: Install 2/1 JBDS
EXECUTE: Window > Preferences > Server > Installed Runtimes
EXECUTE: Select Server runtime, press Edit.
FAILURE: Default folder settings - points to D:\EclipseJBDS2.1\jboss-eap\jboss-as , warning with "Invalid directory " shown.
EXECUTE: Change path to D:\EclipseJBDS2.1\jboss-eap\jboss-as\jboss-eap-4.3\jboss-as
ASSERT: All ok now.
Something wrong with folder structure in \jboss-eap\ .
Related to JBIDE-1925 .
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBDS-646) Still weird exception errors in log for windows JBDS
by Max Rydahl Andersen (JIRA)
Still weird exception errors in log for windows JBDS
----------------------------------------------------
Key: JBDS-646
URL: https://jira.jboss.org/jira/browse/JBDS-646
Project: Developer Studio
Issue Type: Bug
Components: Build
Affects Versions: 2.0.0.GA
Reporter: Max Rydahl Andersen
Assignee: Snjezana Peco
Priority: Critical
Fix For: 2.0.0.GA
We are still getting these weird exceptions on fstartup of jbds on windows.
Apparently linux users does not see them
Snjezana, I remember you talking about them at some point - did you know what causes them ?
!SESSION 2009-03-03 19:48:42.880 -----------------------------------------------
eclipse.buildId=M20090211-1700
java.version=1.6.0_10
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK
Command-line arguments: -os win32 -ws win32 -arch x86
!ENTRY org.eclipse.equinox.p2.reconciler.dropins 4 0 2009-03-03 19:49:17.268
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: State change in progress for bundle "reference:file:plugins/org.eclipse.equinox.p2.reconciler.dropins_1.0.4.v20081027-2115.jar" by thread "Start Level Event Dispatcher".
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:529)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:281)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:416)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:224)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:162)
at java.lang.Thread.run(Unknown Source)
Caused by: org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
... 8 more
Root exception:
org.eclipse.osgi.framework.internal.core.AbstractBundle$BundleStatusException
at org.eclipse.osgi.framework.internal.core.AbstractBundle.beginStateChange(AbstractBundle.java:1144)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(AbstractBundle.java:529)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Framework.java:1104)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.suspendBundle(PackageAdminImpl.java:281)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.processDelta(PackageAdminImpl.java:416)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl.doResolveBundles(PackageAdminImpl.java:224)
at org.eclipse.osgi.framework.internal.core.PackageAdminImpl$1.run(PackageAdminImpl.java:162)
at java.lang.Thread.run(Unknown Source)
!ENTRY org.eclipse.equinox.p2.metadata.repository 4 0 2009-03-03 19:49:20.412
!MESSAGE ProvisioningEventBus could not be obtained. Metadata caches may not be cleaned up properly.
!ENTRY org.eclipse.equinox.p2.garbagecollector 4 0 2009-03-03 19:49:20.453
!MESSAGE ProvisioningEventBus service could not be obtained, CoreGarbageCollector will not function properly.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years