Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster » Changes to director in buckminster?
Changes to director in buckminster? [message #528607] Wed, 21 April 2010 04:55 Go to next message
Carsten Reckord is currently offline Carsten Reckord
Messages: 139
Registered: July 2009
Senior Member
Hi,

have there been any recent changes to the director app included with buckminster affecting how it should be called? My product build action
(pretty much the same as in the mail example) now only creates a p2 folder with the profile metadata in it. No executable, no plugins or
features, no errors or noteworthy log entries.

The call looks like this:

<equinox.launch app="org.eclipse.equinox.p2.director">
<args>
<arg value="-artifactRepository"/>
<arg value="@{repositories}"/>
<arg value="-metadataRepository"/>
<arg value="@{repositories}"/>
<arg value="-destination"/>
<arg value="@{destination}"/>
<arg value="-bundlepool"/>
<arg value="@{destination}"/>
<arg value="-profile"/>
<arg value="@{profile}"/>
<arg value="-profileProperties" />
<arg value="org.eclipse.update.install.features=true" />
<arg value="-installIU"/>
<arg value="@{iu}"/>
<arg value="-p2.os" />
<arg value="${target.os}" />
<arg value="-p2.ws" />
<arg value="${target.ws}" />
<arg value="-p2.arch" />
<arg value="${target.arch}" />
<arg value="-roaming"/>
<jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
<jvmarg value="-Declipse.p2.profile=@{profile}"/>
<jvmarg value="-Declipse.p2.MD5Check=false" />
<director.args/>
</args>
</equinox.launch>

Regards,
Carsten
Re: Changes to director in buckminster? [message #528661 is a reply to message #528607] Wed, 21 April 2010 08:13 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Carsten,
What version are you using?

In any case, I think you should remove these settings:

<jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
<jvmarg value="-Declipse.p2.profile=@{profile}"/>

To my knowledge, they don't do anything good. Theyseem to be relics from
how the old deprecated director app was used and may confuse things at best.

- thomas

On 04/21/2010 10:55 AM, Carsten Reckord wrote:
> Hi,
>
> have there been any recent changes to the director app included with
> buckminster affecting how it should be called? My product build action
> (pretty much the same as in the mail example) now only creates a p2
> folder with the profile metadata in it. No executable, no plugins or
> features, no errors or noteworthy log entries.
>
> The call looks like this:
>
> <equinox.launch app="org.eclipse.equinox.p2.director">
> <args>
> <arg value="-artifactRepository"/>
> <arg value="@{repositories}"/>
> <arg value="-metadataRepository"/>
> <arg value="@{repositories}"/>
> <arg value="-destination"/>
> <arg value="@{destination}"/>
> <arg value="-bundlepool"/>
> <arg value="@{destination}"/>
> <arg value="-profile"/>
> <arg value="@{profile}"/>
> <arg value="-profileProperties" />
> <arg value="org.eclipse.update.install.features=true" />
> <arg value="-installIU"/>
> <arg value="@{iu}"/>
> <arg value="-p2.os" />
> <arg value="${target.os}" />
> <arg value="-p2.ws" />
> <arg value="${target.ws}" />
> <arg value="-p2.arch" />
> <arg value="${target.arch}" />
> <arg value="-roaming"/>
> <jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
> <jvmarg value="-Declipse.p2.profile=@{profile}"/>
> <jvmarg value="-Declipse.p2.MD5Check=false" />
> <director.args/>
> </args>
> </equinox.launch>
>
> Regards,
> Carsten
Re: Changes to director in buckminster? [message #528691 is a reply to message #528661] Wed, 21 April 2010 09:48 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten Reckord
Messages: 139
Registered: July 2009
Senior Member
Hi Thomas,

Thanks for the tip. Without those settings it worked indeed (the eclipse.p2.profile seems to have been the culprit). You might want to
change the mailapp example, too. I had those lines from there.

I just noticed something else though: Occasionally, after the action that runs the director has finished, I get the following error in the
log - it doesn't seem to have any adverse effect on the build, though. My buckminster version is 1.2.0.r11375.

!ENTRY org.eclipse.buckminster.core 0 293 2010-04-21 15:22:19.214
!MESSAGE Doing full workspace refresh
Doing full workspace refresh

!ENTRY org.eclipse.buckminster.core 0 293 2010-04-21 15:22:19.315
!MESSAGE Waiting for jobs to end
Waiting for jobs to end

!ENTRY org.eclipse.pde.core 4 0 2010-04-21 15:22:19.593
!MESSAGE
!STACK 0
org.osgi.framework.BundleException: Exception in org.eclipse.pde.internal.core.PDECore.stop() of bundle org.eclipse.pde.core.
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:863)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:501)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:550)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1098)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:601)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:215)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
at org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:415)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:198)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
Caused by: java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry .findSelf(SimpleProfileRegistry.java:84)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:74)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:66)
at org.eclipse.equinox.internal.p2.engine.ProfileRegistryCompon ent.createService(ProfileRegistryComponent.java:26)
at org.eclipse.equinox.internal.p2.core.ProvisioningAgent.getSe rvice(ProvisioningAgent.java:69)
at org.eclipse.pde.internal.core.target.AbstractTargetHandle.ge tProfileRegistry(AbstractTargetHandle.java:161)
at org.eclipse.pde.internal.core.target.TargetPlatformService.c leanOrphanedTargetDefinitionProfiles(TargetPlatformService.j ava:610)
at org.eclipse.pde.internal.core.PDECore.stop(PDECore.java:276)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:843)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:836)
... 19 more
Root exception:
java.lang.NullPointerException
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry .findSelf(SimpleProfileRegistry.java:84)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:74)
at org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:66)
at org.eclipse.equinox.internal.p2.engine.ProfileRegistryCompon ent.createService(ProfileRegistryComponent.java:26)
at org.eclipse.equinox.internal.p2.core.ProvisioningAgent.getSe rvice(ProvisioningAgent.java:69)
at org.eclipse.pde.internal.core.target.AbstractTargetHandle.ge tProfileRegistry(AbstractTargetHandle.java:161)
at org.eclipse.pde.internal.core.target.TargetPlatformService.c leanOrphanedTargetDefinitionProfiles(TargetPlatformService.j ava:610)
at org.eclipse.pde.internal.core.PDECore.stop(PDECore.java:276)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:843)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:836)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:501)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:550)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1098)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:601)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:215)
at org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
at org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:415)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:198)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)


On 21.04.2010 14:13, Thomas Hallgren wrote:
> Hi Carsten,
> What version are you using?
>
> In any case, I think you should remove these settings:
>
> <jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
> <jvmarg value="-Declipse.p2.profile=@{profile}"/>
>
> To my knowledge, they don't do anything good. Theyseem to be relics from
> how the old deprecated director app was used and may confuse things at best.
>
> - thomas
>
> On 04/21/2010 10:55 AM, Carsten Reckord wrote:
>> Hi,
>>
>> have there been any recent changes to the director app included with
>> buckminster affecting how it should be called? My product build action
>> (pretty much the same as in the mail example) now only creates a p2
>> folder with the profile metadata in it. No executable, no plugins or
>> features, no errors or noteworthy log entries.
>>
>> The call looks like this:
>>
>> <equinox.launch app="org.eclipse.equinox.p2.director">
>> <args>
>> <arg value="-artifactRepository"/>
>> <arg value="@{repositories}"/>
>> <arg value="-metadataRepository"/>
>> <arg value="@{repositories}"/>
>> <arg value="-destination"/>
>> <arg value="@{destination}"/>
>> <arg value="-bundlepool"/>
>> <arg value="@{destination}"/>
>> <arg value="-profile"/>
>> <arg value="@{profile}"/>
>> <arg value="-profileProperties" />
>> <arg value="org.eclipse.update.install.features=true" />
>> <arg value="-installIU"/>
>> <arg value="@{iu}"/>
>> <arg value="-p2.os" />
>> <arg value="${target.os}" />
>> <arg value="-p2.ws" />
>> <arg value="${target.ws}" />
>> <arg value="-p2.arch" />
>> <arg value="${target.arch}" />
>> <arg value="-roaming"/>
>> <jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
>> <jvmarg value="-Declipse.p2.profile=@{profile}"/>
>> <jvmarg value="-Declipse.p2.MD5Check=false" />
>> <director.args/>
>> </args>
>> </equinox.launch>
>>
>> Regards,
>> Carsten
>
Re: Changes to director in buckminster? [message #528715 is a reply to message #528691] Wed, 21 April 2010 10:52 Go to previous message
Thomas Hallgren is currently offline Thomas Hallgren
Messages: 3214
Registered: July 2009
Senior Member
Hi Carsten,
Glad you got things working. The exception that you sometimes encounter
has been reported and a fix for that will be available in M7.

I'll review the mailapp example.

Regards,
Thomas Hallgren

On 04/21/2010 03:48 PM, Carsten Reckord wrote:
> Hi Thomas,
>
> Thanks for the tip. Without those settings it worked indeed (the
> eclipse.p2.profile seems to have been the culprit). You might want to
> change the mailapp example, too. I had those lines from there.
>
> I just noticed something else though: Occasionally, after the action
> that runs the director has finished, I get the following error in the
> log - it doesn't seem to have any adverse effect on the build, though.
> My buckminster version is 1.2.0.r11375.
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-04-21 15:22:19.214
> !MESSAGE Doing full workspace refresh
> Doing full workspace refresh
>
> !ENTRY org.eclipse.buckminster.core 0 293 2010-04-21 15:22:19.315
> !MESSAGE Waiting for jobs to end
> Waiting for jobs to end
>
> !ENTRY org.eclipse.pde.core 4 0 2010-04-21 15:22:19.593
> !MESSAGE
> !STACK 0
> org.osgi.framework.BundleException: Exception in
> org.eclipse.pde.internal.core.PDECore.stop() of bundle
> org.eclipse.pde.core.
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:863)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:501)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:550)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1098)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:601)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:215)
>
> at
> org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:415)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:198)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
> Caused by: java.lang.NullPointerException
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry .findSelf(SimpleProfileRegistry.java:84)
>
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:74)
>
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:66)
>
> at
> org.eclipse.equinox.internal.p2.engine.ProfileRegistryCompon ent.createService(ProfileRegistryComponent.java:26)
>
> at
> org.eclipse.equinox.internal.p2.core.ProvisioningAgent.getSe rvice(ProvisioningAgent.java:69)
>
> at
> org.eclipse.pde.internal.core.target.AbstractTargetHandle.ge tProfileRegistry(AbstractTargetHandle.java:161)
>
> at
> org.eclipse.pde.internal.core.target.TargetPlatformService.c leanOrphanedTargetDefinitionProfiles(TargetPlatformService.j ava:610)
>
> at org.eclipse.pde.internal.core.PDECore.stop(PDECore.java:276)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:843)
>
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:836)
>
> ... 19 more
> Root exception:
> java.lang.NullPointerException
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry .findSelf(SimpleProfileRegistry.java:84)
>
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:74)
>
> at
> org.eclipse.equinox.internal.p2.engine.SimpleProfileRegistry . <init>(SimpleProfileRegistry.java:66)
>
> at
> org.eclipse.equinox.internal.p2.engine.ProfileRegistryCompon ent.createService(ProfileRegistryComponent.java:26)
>
> at
> org.eclipse.equinox.internal.p2.core.ProvisioningAgent.getSe rvice(ProvisioningAgent.java:69)
>
> at
> org.eclipse.pde.internal.core.target.AbstractTargetHandle.ge tProfileRegistry(AbstractTargetHandle.java:161)
>
> at
> org.eclipse.pde.internal.core.target.TargetPlatformService.c leanOrphanedTargetDefinitionProfiles(TargetPlatformService.j ava:610)
>
> at org.eclipse.pde.internal.core.PDECore.stop(PDECore.java:276)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl$2 .run(BundleContextImpl.java:843)
>
> at java.security.AccessController.doPrivileged(Native Method)
> at
> org.eclipse.osgi.framework.internal.core.BundleContextImpl.s top(BundleContextImpl.java:836)
>
> at
> org.eclipse.osgi.framework.internal.core.BundleHost.stopWork er(BundleHost.java:501)
>
> at
> org.eclipse.osgi.framework.internal.core.AbstractBundle.susp end(AbstractBundle.java:550)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.suspendBu ndle(Framework.java:1098)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d ecFWSL(StartLevelManager.java:601)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:261)
>
> at
> org.eclipse.osgi.framework.internal.core.StartLevelManager.s hutdown(StartLevelManager.java:215)
>
> at
> org.eclipse.osgi.framework.internal.core.InternalSystemBundl e.suspend(InternalSystemBundle.java:266)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.shutdown( Framework.java:685)
>
> at
> org.eclipse.osgi.framework.internal.core.Framework.close(Fra mework.java:583)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Ecl ipseStarter.java:415)
>
> at
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseS tarter.java:198)
>
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39)
>
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:25)
>
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java: 619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
>
>
> On 21.04.2010 14:13, Thomas Hallgren wrote:
>> Hi Carsten,
>> What version are you using?
>>
>> In any case, I think you should remove these settings:
>>
>> <jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
>> <jvmarg value="-Declipse.p2.profile=@{profile}"/>
>>
>> To my knowledge, they don't do anything good. Theyseem to be relics
>> from how the old deprecated director app was used and may confuse
>> things at best.
>>
>> - thomas
>>
>> On 04/21/2010 10:55 AM, Carsten Reckord wrote:
>>> Hi,
>>>
>>> have there been any recent changes to the director app included with
>>> buckminster affecting how it should be called? My product build action
>>> (pretty much the same as in the mail example) now only creates a p2
>>> folder with the profile metadata in it. No executable, no plugins or
>>> features, no errors or noteworthy log entries.
>>>
>>> The call looks like this:
>>>
>>> <equinox.launch app="org.eclipse.equinox.p2.director">
>>> <args>
>>> <arg value="-artifactRepository"/>
>>> <arg value="@{repositories}"/>
>>> <arg value="-metadataRepository"/>
>>> <arg value="@{repositories}"/>
>>> <arg value="-destination"/>
>>> <arg value="@{destination}"/>
>>> <arg value="-bundlepool"/>
>>> <arg value="@{destination}"/>
>>> <arg value="-profile"/>
>>> <arg value="@{profile}"/>
>>> <arg value="-profileProperties" />
>>> <arg value="org.eclipse.update.install.features=true" />
>>> <arg value="-installIU"/>
>>> <arg value="@{iu}"/>
>>> <arg value="-p2.os" />
>>> <arg value="${target.os}" />
>>> <arg value="-p2.ws" />
>>> <arg value="${target.ws}" />
>>> <arg value="-p2.arch" />
>>> <arg value="${target.arch}" />
>>> <arg value="-roaming"/>
>>> <jvmarg value="-Declipse.p2.data.area=@{destination}/p2"/>
>>> <jvmarg value="-Declipse.p2.profile=@{profile}"/>
>>> <jvmarg value="-Declipse.p2.MD5Check=false" />
>>> <director.args/>
>>> </args>
>>> </equinox.launch>
>>>
>>> Regards,
>>> Carsten
>>
Previous Topic:headless update from 3.5.0 to 3.5.2
Next Topic:Packages not found during build
Goto Forum:
  


Current Time: Thu Jul 24 04:45:14 EDT 2014

Powered by FUDForum. Page generated in 0.04991 seconds