Home » Newcomers » Newcomers » Problem referencing files in other projects
| Problem referencing files in other projects [message #235042] |
Thu, 27 September 2007 12:39  |
Eclipse User |
|
|
|
Originally posted by: sreed.spamcop.net
I have two projects, ProjectA & ProjectB, ProjectA is dependent on
ProjectB. ProjectB contains files that are loaded at runtime which works
fine when I run a test application from ProjectB. When I run the real
application from ProjectA, it cannot find the files. I get errors
messages like:
ERROR: '<full path to ProjectA>/<path of file in ProjectB> (The
system cannot find the file specified)'
Here is a snippet of code that attempts to open the files is:
fop_xslt = factory.newTransformer(new StreamSource(new
File("fop/fop.xsl")));
where we are attempting to open the file, ProjectB/fop/fop.xsl.
It appears we need to have ProjectB in the classpath, but simply
referencing it in ProjectA doesn't seem to do that.
I would appreciate any help in how to get this to work.
Thanks,
Scott
|
|
|
| Re: Problem referencing files in other projects [message #235049 is a reply to message #235042] |
Thu, 27 September 2007 12:46  |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------030509020703000800060103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Scott,
Well, your file name is relative so resolving it will depend on the
current working directory. When you run an application from a project,
the working directory is set to be the project. How exactly are you
expecting these files to be found when you really deploy your final
application? Often it makes sense to include such files in the library
itself and to access it using MyClass.class.getResourceAsString() where
the file is in the same folder (package) as MyClass.
This will turn up some older threads talking about such things:
http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail
< http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail>
S Reed wrote:
> I have two projects, ProjectA & ProjectB, ProjectA is dependent on
> ProjectB. ProjectB contains files that are loaded at runtime which
> works fine when I run a test application from ProjectB. When I run the
> real application from ProjectA, it cannot find the files. I get errors
> messages like:
>
> ERROR: '<full path to ProjectA>/<path of file in ProjectB> (The
> system cannot find the file specified)'
>
> Here is a snippet of code that attempts to open the files is:
>
> fop_xslt = factory.newTransformer(new StreamSource(new
> File("fop/fop.xsl")));
>
> where we are attempting to open the file, ProjectB/fop/fop.xsl.
>
> It appears we need to have ProjectB in the classpath, but simply
> referencing it in ProjectA doesn't seem to do that.
>
> I would appreciate any help in how to get this to work.
>
> Thanks,
> Scott
>
--------------030509020703000800060103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Scott,<br>
<br>
Well, your file name is relative so resolving it will depend on the
current working directory. When you run an application from a project,
the working directory is set to be the project. How exactly are you
expecting these files to be found when you really deploy your final
application? Often it makes sense to include such files in the
library itself and to access it using
MyClass.class.getResourceAsString() where the file is in the same
folder (package) as MyClass.<br>
<br>
This will turn up some older threads talking about such things:<br>
<blockquote><a
href=" http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am& ;cmd=Search%21&form=extended&wf=574a74&a mp;ps=10&m=all&t=5&ul=%2Fnewslists%2 Fnews.eclipse.newcomer&wm=wrd&t=News& ;t=Mail "> http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am& ;cmd=Search%21&form=extended&wf=574a74&a mp;ps=10&m=all&t=5&ul=%2Fnewslists%2 Fnews.eclipse.newcomer&wm=wrd&t=News& ;t=Mail </a><br>
</blockquote>
<br>
S Reed wrote:
<blockquote cite="mid:fdgmcl$k6t$1@build.eclipse.org" type="cite">I
have two projects, ProjectA & ProjectB, ProjectA is dependent on
ProjectB. ProjectB contains files that are loaded at runtime which
works fine when I run a test application from ProjectB. When I run the
real application from ProjectA, it cannot find the files. I get errors
messages like:
<br>
<br>
ERROR: '<full path to ProjectA>/<path of file in
ProjectB> (The
<br>
system cannot find the file specified)'
<br>
<br>
Here is a snippet of code that attempts to open the files is:
<br>
<br>
fop_xslt = factory.newTransformer(new StreamSource(new
<br>
File("fop/fop.xsl")));
<br>
<br>
where we are attempting to open the file, ProjectB/fop/fop.xsl.
<br>
<br>
It appears we need to have ProjectB in the classpath, but simply
referencing it in ProjectA doesn't seem to do that.
<br>
<br>
I would appreciate any help in how to get this to work.
<br>
<br>
Thanks,
<br>
Scott
<br>
</blockquote>
<br>
</body>
</html>
--------------030509020703000800060103--
|
|
|
| Re: Problem referencing files in other projects [message #235185 is a reply to message #235049] |
Fri, 28 September 2007 11:56 |
| Eclipse User |
|
|
|
Originally posted by: sreed.spamcop.net
Ed Merks's message received 9/27/2007 12:46 PM:
> Scott,
>
> Well, your file name is relative so resolving it will depend on the
> current working directory. When you run an application from a
> project, the working directory is set to be the project. How exactly
> are you expecting these files to be found when you really deploy your
> final application?
For deployment these files will be jarred up with directories relative
to the jar root, but I'd rather not have to build a jar file each time I
make a change in one of these files while I am developing in Eclipse.
> Often it makes sense to include such files in the library itself and
> to access it using MyClass.class.getResourceAsString() where the file
> is in the same folder (package) as MyClass.
I am not sure what you mean by including the files "in the library". I
tried adding the folders to the library and that works for
non-hierarchical directories but if the files are one or more levels
down, the loader doesn't seem to be able to find them. I got the same
results when I added the folders as source directories.
If I add the folder "a" to the library or the source folders,
A stream obtained from that top level, e.g.
MyClass.class.getResourceAsString("/a/fop.xsl"), works fine.
But a stream obtained from one or more levels down, e.g.
MyClass.class.getResourceAsString("/a/b/fop.xsl"), throws an exception
in the XSL Transformer.
>
> This will turn up some older threads talking about such things:
>
> http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail
> < http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail>
>
>
> S Reed wrote:
>> I have two projects, ProjectA & ProjectB, ProjectA is dependent on
>> ProjectB. ProjectB contains files that are loaded at runtime which
>> works fine when I run a test application from ProjectB. When I run
>> the real application from ProjectA, it cannot find the files. I get
>> errors messages like:
>>
>> ERROR: '<full path to ProjectA>/<path of file in ProjectB> (The
>> system cannot find the file specified)'
>>
>> Here is a snippet of code that attempts to open the files is:
>>
>> fop_xslt = factory.newTransformer(new StreamSource(new
>> File("fop/fop.xsl")));
>>
>> where we are attempting to open the file, ProjectB/fop/fop.xsl.
>>
>> It appears we need to have ProjectB in the classpath, but simply
>> referencing it in ProjectA doesn't seem to do that.
>>
>> I would appreciate any help in how to get this to work.
>>
>> Thanks,
>> Scott
>>
>
|
|
|
| Re: Problem referencing files in other projects [message #235193 is a reply to message #235185] |
Fri, 28 September 2007 12:16 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Scott,
Comments below.
S Reed wrote:
> Ed Merks's message received 9/27/2007 12:46 PM:
>> Scott,
>>
>> Well, your file name is relative so resolving it will depend on the
>> current working directory. When you run an application from a
>> project, the working directory is set to be the project. How
>> exactly are you expecting these files to be found when you really
>> deploy your final application?
> For deployment these files will be jarred up with directories relative
> to the jar root, but I'd rather not have to build a jar file each time
> I make a change in one of these files while I am developing in Eclipse.
That's why one typically puts such "resources" in the src folder and
then Eclipse automatically copies it to the bin folder and it will be
visible during development time the same was as at deploy time.
>> Often it makes sense to include such files in the library itself and
>> to access it using MyClass.class.getResourceAsString() where the
>> file is in the same folder (package) as MyClass.
> I am not sure what you mean by including the files "in the library".
I.e., move the file to be in your source folders in the same folder as
where the .java file that will load it is (or relative to which you will
load it) is. So if it's x.z.y.MyClass.java put it in the z folder and
use MyClass.class.getResourceAsStream("fop.xsl").
> I tried adding the folders to the library and that works for
> non-hierarchical directories but if the files are one or more levels
> down, the loader doesn't seem to be able to find them. I got the same
> results when I added the folders as source directories.
>
> If I add the folder "a" to the library or the source folders,
>
> A stream obtained from that top level, e.g.
> MyClass.class.getResourceAsString("/a/fop.xsl"), works fine.
>
> But a stream obtained from one or more levels down, e.g.
> MyClass.class.getResourceAsString("/a/b/fop.xsl"), throws an
> exception in the XSL Transformer.
As long as that stuff is visible on the classpath (i.e., is in the jar
in in the bin folder at development time, it should be found okay).
>
>>
>> This will turn up some older threads talking about such things:
>>
>>
>> http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail
>>
>>
>> < http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail>
>>
>>
Did you look at those other threads? Your problem is pretty much a
standard problem that many folks have asked about...
>>
>> S Reed wrote:
>>> I have two projects, ProjectA & ProjectB, ProjectA is dependent on
>>> ProjectB. ProjectB contains files that are loaded at runtime which
>>> works fine when I run a test application from ProjectB. When I run
>>> the real application from ProjectA, it cannot find the files. I get
>>> errors messages like:
>>>
>>> ERROR: '<full path to ProjectA>/<path of file in ProjectB> (The
>>> system cannot find the file specified)'
>>>
>>> Here is a snippet of code that attempts to open the files is:
>>>
>>> fop_xslt = factory.newTransformer(new StreamSource(new
>>> File("fop/fop.xsl")));
>>>
>>> where we are attempting to open the file, ProjectB/fop/fop.xsl.
>>>
>>> It appears we need to have ProjectB in the classpath, but simply
>>> referencing it in ProjectA doesn't seem to do that.
>>>
>>> I would appreciate any help in how to get this to work.
>>>
>>> Thanks,
>>> Scott
>>>
>>
|
|
|
| Re: Problem referencing files in other projects [message #235197 is a reply to message #235193] |
Fri, 28 September 2007 12:37 |
| Eclipse User |
|
|
|
Originally posted by: sreed.spamcop.net
Thanks for the quick response, Ed! My reply is at the end.
Ed Merks's message received 9/28/2007 12:16 PM:
> Scott,
>
> Comments below.
>
>
> S Reed wrote:
>> Ed Merks's message received 9/27/2007 12:46 PM:
>>> Scott,
>>>
>>> Well, your file name is relative so resolving it will depend on the
>>> current working directory. When you run an application from a
>>> project, the working directory is set to be the project. How
>>> exactly are you expecting these files to be found when you really
>>> deploy your final application?
>> For deployment these files will be jarred up with directories
>> relative to the jar root, but I'd rather not have to build a jar file
>> each time I make a change in one of these files while I am developing
>> in Eclipse.
> That's why one typically puts such "resources" in the src folder and
> then Eclipse automatically copies it to the bin folder and it will be
> visible during development time the same was as at deploy time.
>>> Often it makes sense to include such files in the library itself and
>>> to access it using MyClass.class.getResourceAsString() where the
>>> file is in the same folder (package) as MyClass.
>> I am not sure what you mean by including the files "in the library".
> I.e., move the file to be in your source folders in the same folder as
> where the .java file that will load it is (or relative to which you
> will load it) is. So if it's x.z.y.MyClass.java put it in the z
> folder and use MyClass.class.getResourceAsStream("fop.xsl").
>> I tried adding the folders to the library and that works for
>> non-hierarchical directories but if the files are one or more levels
>> down, the loader doesn't seem to be able to find them. I got the same
>> results when I added the folders as source directories.
>>
>> If I add the folder "a" to the library or the source folders,
>>
>> A stream obtained from that top level, e.g.
>> MyClass.class.getResourceAsString("/a/fop.xsl"), works fine.
>>
>> But a stream obtained from one or more levels down, e.g.
>> MyClass.class.getResourceAsString("/a/b/fop.xsl"), throws an
>> exception in the XSL Transformer.
> As long as that stuff is visible on the classpath (i.e., is in the jar
> in in the bin folder at development time, it should be found okay).
>>
>>>
>>> This will turn up some older threads talking about such things:
>>>
>>>
>>> http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail
>>>
>>>
>>> < http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail>
>>>
>>>
> Did you look at those other threads? Your problem is pretty much a
> standard problem that many folks have asked about...
Yes, I read those over. The idea that the files must be located in java
source folders is unsatisfactory. For one, it will disorganize our file
structure, mixing java source with properties, xml, and xsl files and
creating an unmanageable file count for the java folders.
I am beginning to grok how Eclipse constructs the classpath and I fear
disappointment is over the horizon.
We want these ancillary files to be located from the top level of the
project, in a logically organized, hierarchical file structure. If
Eclipse cannot support such a structure without putting the files in
jars, that is a major drawback.
|
|
|
| Re: Problem referencing files in other projects [message #235211 is a reply to message #235197] |
Fri, 28 September 2007 13:06 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
Scott,
I haven't tried, but likely you can add "." to your classpath to beat
Eclipse into submission. Or you could put some other subfolder like
"data" on your classpath and ensure that the contents of that folder
will be jarred up via the build.properties. Then you could use the
"/..." approach you are trying...
S Reed wrote:
> Thanks for the quick response, Ed! My reply is at the end.
>
> Ed Merks's message received 9/28/2007 12:16 PM:
>> Scott,
>>
>> Comments below.
>>
>>
>> S Reed wrote:
>>> Ed Merks's message received 9/27/2007 12:46 PM:
>>>> Scott,
>>>>
>>>> Well, your file name is relative so resolving it will depend on the
>>>> current working directory. When you run an application from a
>>>> project, the working directory is set to be the project. How
>>>> exactly are you expecting these files to be found when you really
>>>> deploy your final application?
>>> For deployment these files will be jarred up with directories
>>> relative to the jar root, but I'd rather not have to build a jar
>>> file each time I make a change in one of these files while I am
>>> developing in Eclipse.
>> That's why one typically puts such "resources" in the src folder and
>> then Eclipse automatically copies it to the bin folder and it will be
>> visible during development time the same was as at deploy time.
>>>> Often it makes sense to include such files in the library itself
>>>> and to access it using MyClass.class.getResourceAsString() where
>>>> the file is in the same folder (package) as MyClass.
>>> I am not sure what you mean by including the files "in the library".
>> I.e., move the file to be in your source folders in the same folder
>> as where the .java file that will load it is (or relative to which
>> you will load it) is. So if it's x.z.y.MyClass.java put it in the z
>> folder and use MyClass.class.getResourceAsStream("fop.xsl").
>>> I tried adding the folders to the library and that works for
>>> non-hierarchical directories but if the files are one or more levels
>>> down, the loader doesn't seem to be able to find them. I got the
>>> same results when I added the folders as source directories.
>>>
>>> If I add the folder "a" to the library or the source folders,
>>>
>>> A stream obtained from that top level, e.g.
>>> MyClass.class.getResourceAsString("/a/fop.xsl"), works fine.
>>>
>>> But a stream obtained from one or more levels down, e.g.
>>> MyClass.class.getResourceAsString("/a/b/fop.xsl"), throws an
>>> exception in the XSL Transformer.
>> As long as that stuff is visible on the classpath (i.e., is in the
>> jar in in the bin folder at development time, it should be found okay).
>>>
>>>>
>>>> This will turn up some older threads talking about such things:
>>>>
>>>>
>>>> http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail
>>>>
>>>>
>>>> < http://www.eclipse.org/search/search.cgi?q=getResourceAsStre am&cmd=Search%21&form=extended&wf=574a74&ps= 10&m=all&t=5&ul=%2Fnewslists%2Fnews.eclipse.newc omer&wm=wrd&t=News&t=Mail>
>>>>
>>>>
>> Did you look at those other threads? Your problem is pretty much a
>> standard problem that many folks have asked about...
> Yes, I read those over. The idea that the files must be located in
> java source folders is unsatisfactory. For one, it will disorganize
> our file structure, mixing java source with properties, xml, and xsl
> files and creating an unmanageable file count for the java folders.
>
> I am beginning to grok how Eclipse constructs the classpath and I fear
> disappointment is over the horizon.
>
> We want these ancillary files to be located from the top level of the
> project, in a logically organized, hierarchical file structure. If
> Eclipse cannot support such a structure without putting the files in
> jars, that is a major drawback.
|
|
| | | |
| Re: Problem referencing files in other projects [message #235242 is a reply to message #235236] |
Fri, 28 September 2007 14:45 |
| Eclipse User |
|
|
|
Originally posted by: merks.ca.ibm.com
This is a multi-part message in MIME format.
--------------040700010405000305040100
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Dave,
Yes, that's a good suggestion too. That way just the bin folder being
on the classpath is sufficient...
Dave Wegener wrote:
> You can define a separate source folder to hold the extra resource files
> that you need. That way the resource files will be kept separate from the
> .java files. The non .java files in source folders are copied to the output
> location so they will be available on the classpath. If you are using
> getResourceAsStream, make sure you are following the rules regarding when to
> include a leading '/' character.
>
> "S Reed" <sreed@spamcop.net> wrote in message
> news:fdjeq8$lmk$1@build.eclipse.org...
>
>> Ed Merks's message received 9/28/2007 1:06 PM:
>>
>>> Scott,
>>>
>>> I haven't tried, but likely you can add "." to your classpath to beat
>>> Eclipse into submission.
>>>
>> I'm not sure how to add "." to the classpath in Eclipse. Please explain.
>>
>>> Or you could put some other subfolder like "data" on your classpath
>>> and ensure that the contents of that folder will be jarred up via the
>>> build.properties.
>>>
>> If this works it may be an acceptable option. Thanks!
>>
>>> Then you could use the "/..." approach you are trying...
>>>
>
>
>
--------------040700010405000305040100
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Dave,<br>
<br>
Yes, that's a good suggestion too. That way just the bin folder being
on the classpath is sufficient...<br>
<br>
<br>
Dave Wegener wrote:
<blockquote cite="mid:fdjhfb$i81$1@build.eclipse.org" type="cite">
<pre wrap="">You can define a separate source folder to hold the extra resource files
that you need. That way the resource files will be kept separate from the
..java files. The non .java files in source folders are copied to the output
location so they will be available on the classpath. If you are using
getResourceAsStream, make sure you are following the rules regarding when to
include a leading '/' character.
"S Reed" <a class="moz-txt-link-rfc2396E" href="mailto:sreed@spamcop.net"><sreed@spamcop.net></a> wrote in message
<a class="moz-txt-link-freetext" href="news:fdjeq8$lmk$1@build.eclipse.org">news:fdjeq8$lmk$1@build.eclipse.org</a>...
</pre>
<blockquote type="cite">
<pre wrap="">Ed Merks's message received 9/28/2007 1:06 PM:
</pre>
<blockquote type="cite">
<pre wrap="">Scott,
I haven't tried, but likely you can add "." to your classpath to beat
Eclipse into submission.
</pre>
</blockquote>
<pre wrap="">I'm not sure how to add "." to the classpath in Eclipse. Please explain.
</pre>
<blockquote type="cite">
<pre wrap="">Or you could put some other subfolder like "data" on your classpath
and ensure that the contents of that folder will be jarred up via the
build.properties.
</pre>
</blockquote>
<pre wrap="">If this works it may be an acceptable option. Thanks!
</pre>
<blockquote type="cite">
<pre wrap="">Then you could use the "/..." approach you are trying...
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>
--------------040700010405000305040100--
|
|
| |
| Re: Problem referencing files in other projects [message #235256 is a reply to message #235249] |
Fri, 28 September 2007 15:12 |
| Eclipse User |
|
|
|
Originally posted by: sreed.spamcop.net
S Reed's message received 9/28/2007 3:07 PM:
> Dave Wegener's message received 9/28/2007 2:34 PM:
>> You can define a separate source folder to hold the extra resource files
>> that you need. That way the resource files will be kept separate
>> from the
>> .java files. The non .java files in source folders are copied to the
>> output
>> location so they will be available on the classpath. If you are using
>> getResourceAsStream, make sure you are following the rules regarding
>> when to
>> include a leading '/' character.
> Are any of the following true:
>
> a) The separate source folder has the same file hierarchy as the java
> file with the resources in the same location in the hierarchy as the
> class where they are loaded, i.e.
> a.b.c.MyClass.class.getResourceAsStream("a/b/c/f.xml").
>
> b) If the files reside in a separate source folder hierarchy below the
> package hierarchy (e.g. a/b/c/d/e/f.xml) I can call
> a.b.c.MyClass.class.getResourceAsStream("a/b/c/d/e/f.xml").
>
> b) The separate source folder can have an arbitrary folder hierarchy
> as long as the file path starts with '/' and lists the folders from
> the project root down, i.e. new FileInputStream("/x/y/z/f.xml").
>
> While this thread has led me to believe these might all be true, none
> of them are working in my app. Am I missing the boat entirely? I will
> put together a little test case to demonstrate.
I just figured out that the errors I am getting are coming from the XSL
transformer which is handling references to other xsl files from xsl
files that ARE properly loaded using the techniques described here.
Please forgive my obtusity. Thanks for the help. I hope this will be the
end of these travails.
|
|
|
Goto Forum:
Current Time: Sat Jul 19 19:25:48 EDT 2025
Powered by FUDForum. Page generated in 0.11931 seconds |
Home