Re: [orion-dev] Problem with Run Configuration web-ide

[Anthony Hunter <anthonyh@xxxxxxxxxx>]

Yes, in this case "because I had old
data in that foo" Orion expects you to run the migration using the
documentation. The problem is that the migration moves files and deletes
what it thinks are orphans, so we do not do an automatic migration.

Cheers...
Anthony




From:      
 Adrian Aichner <adrian.aichner@xxxxxxxxx>
To:      
 Orion developer discussions
<orion-dev@xxxxxxxxxxx>
Date:      
 2014/05/27 10:48 AM
Subject:    
   Re: [orion-dev]
Problem with Run Configuration web-ide
Sent by:    
   orion-dev-bounces@xxxxxxxxxxx

---

On Tue, May 27, 2014 at 4:28 PM, Anthony Hunter <anthonyh@xxxxxxxxxx>
wrote:
Hi Adrian, 

You have hit [server]
startup failure needs to be improved when starting with legacy metadata
. 

Thanks Anthony, the bug above seems to be exactly what
I saw.
 

You need to do two migrations as documented in https://wiki.eclipse.org/Orion/Metadata_migration


But my local server workspace is not involved here at
all.

I am just trying to run configuration web-ide as it comes
straight out of git master and uses an unmodified web-ide.conf, which has
#orion.core.metastore=legacy

It uses its own
-data ${workspace_loc}/../foo 
and didn't seem to manage to run that configuration, perhaps
because I had old data in that foo, but that is a transition many other
developers should experience as well, right?

Adrian
 

Cheers...
Anthony




From:        Adrian
Aichner <adrian.aichner@xxxxxxxxx>
To:        Orion
developer discussions <orion-dev@xxxxxxxxxxx>
Date:        2014/05/25
11:02 AM 
Subject:        [orion-dev]
Problem with Run Configuration web-ide 
Sent by:        orion-dev-bounces@xxxxxxxxxxx

---

I update my eclipse Luna environment and workspace occasionally from the
orion git master source.

I do so by pulling from master in client and server projects inside eclipse
GIT perspective.

Then I 
Set Target Platform 
in Plugin Configuration perspective. 

And finally 
Run configuration web-ide.

I was not able to get that to work since yesterday.

Took me a while to spot the metastore exception in this:


!SESSION 2014-05-24 23:18:13.862 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.7.0_55
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=de_DE
Framework arguments:  -product org.eclipse.orion.product
Command-line arguments:  -dev file:/var/home/adrian/workspace-luna-M5-2/.metadata/.plugins/org.eclipse.pde.core/web-ide/dev.properties
-os linux -ws gtk -arch x86 -consoleLog -console -data /var/home/adrian/workspace-luna-M5-2/../foo
-clean -product org.eclipse.orion.product

!ENTRY org.eclipse.osgi 4 0 2014-05-24 23:18:16.912
!MESSAGE An error occurred while automatically activating bundle org.eclipse.orion.server.core
(94).
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.orion.internal.server.core.Activator.start()
of bundle org.eclipse.orion.server.core.
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:792)
35 LINES DELETED HERE...
    at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: java.lang.RuntimeException: Cannot initialize MetaStore - old
metadata must be upgraded!
    at org.eclipse.orion.internal.server.core.Activator.initializeMetaStore(Activator.java:159)
    at org.eclipse.orion.internal.server.core.Activator.start(Activator.java:173)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:771)
    at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
    at java.security.AccessController.doPrivileged(Native
Method)
    at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:764)
    ... 36 more
Root exception:
java.lang.RuntimeException: Cannot initialize MetaStore - old metadata
must be upgraded! 


Only after I made following change, I was able to run the configuration.

--- a/bundles/org.eclipse.orion.client.core/web-ide.conf
+++ b/bundles/org.eclipse.orion.client.core/web-ide.conf
@@ -50,6 +50,7 @@
 
 #uncomment this line to specify to use the legacy metastore rather
than the de
 #orion.core.metastore=legacy
+orion.core.metastore=simple2
 
 #uncomment the lines below and specify the keystore location and
passwords to 
 #jetty.https.enabled=true 

I have the suspicion this might be caused by old data in
-data ${workspace_loc}/../foo 
but I cannot reproduce the problem with an old copy of foo now.

So -- this mail is just a heads up to people with similar problems.

I am not sure at this point whether there is a build cleanup step that's
missing here for the transition to simple2.

Adrian 
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev


_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev

_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev