Home » Language IDEs » Java Development Tools (JDT) » Huh? "A class file was not written. The project may be inconsistent, if so try refreshing this
| Huh? "A class file was not written. The project may be inconsistent, if so try refreshing this [message #125556] |
Tue, 09 December 2003 16:30  |
Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
I added an inner class to a source, and now get this error Task.
A complete rebuild does not help.
I should note that the coding was done while in the midst a debugger session, I
had forgotten that the debugger was active.
After saving I also received some error about the debugger, terminated the debug
session, rebuilt All, but am still left with this.
Any advice will be appreciated.
-nat
|
|
| | |
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #125685 is a reply to message #125556] |
Tue, 09 December 2003 19:49  |
| Eclipse User |
|
|
|
Originally posted by: eclipse-user.jibeinc.com
natG wrote:
> I added an inner class to a source, and now get this error Task.
> A complete rebuild does not help.
> I should note that the coding was done while in the midst a debugger session, I
> had forgotten that the debugger was active.
> After saving I also received some error about the debugger, terminated the debug
> session, rebuilt All, but am still left with this.
>
> Any advice will be appreciated.
Can you narrow it down to a simple, stand-alone example and post?
I also suggest checking Bugzilla to see if it is an open/known issue.
HTH,
Eric
--
Eric Rizzo
Software Architect
Jibe, Inc.
http://www.jibeinc.com
|
|
| |
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #125723 is a reply to message #125685] |
Wed, 10 December 2003 00:47 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
> Can you narrow it down to a simple, stand-alone example and post?
> I also suggest checking Bugzilla to see if it is an open/known issue.
>
> HTH,
> Eric
> --
> Eric Rizzo
> Software Architect
> Jibe, Inc.
> http://www.jibeinc.com
Its kinda hard to narrow down, although the inner class is rather simple, but
implements Comparator.
Due to time constraints on this, I factored it out into a regular class, and
everything is fine. (But of course does not solve the problem.)
As far as Bugzilla goes, I tried before posting here, and what a PITA to use that
interface! Are they for real?
I have to set who-knows how many parameters (including version numbers of
modules!!) to get a query?
I still feel I must have overlooked the obvious query sheet. Can't one just input
Eclipse/JDT/inner class and SEARCH?
Anyhow....
thanks
-nat
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #125899 is a reply to message #125723] |
Wed, 10 December 2003 14:43 |
| Eclipse User |
|
|
|
Originally posted by: wegener.cboenospam.com
Check out but 23373
https://bugs.eclipse.org/bugs/show_bug.cgi?id=23373
It talks about a file name path length issue on Windows.
Text searches of open bugs can be performed quite simply off of the Bugs
page on the Eclipse site. If you want to search all bug reports, you can
click the Edit Query and add the Resolved, Verified, and Closed entries to
the Status.
natG wrote:
> > Can you narrow it down to a simple, stand-alone example and post?
> > I also suggest checking Bugzilla to see if it is an open/known issue.
> >
> > HTH,
> > Eric
> > --
> > Eric Rizzo
> > Software Architect
> > Jibe, Inc.
> > http://www.jibeinc.com
> Its kinda hard to narrow down, although the inner class is rather simple, but
> implements Comparator.
> Due to time constraints on this, I factored it out into a regular class, and
> everything is fine. (But of course does not solve the problem.)
> As far as Bugzilla goes, I tried before posting here, and what a PITA to use
that
> interface! Are they for real?
> I have to set who-knows how many parameters (including version numbers of
> modules!!) to get a query?
> I still feel I must have overlooked the obvious query sheet. Can't one just
input
> Eclipse/JDT/inner class and SEARCH?
> Anyhow....
> thanks
> -nat
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #125964 is a reply to message #125899] |
Wed, 10 December 2003 19:29 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
Thanks for the pointer on the bug. If the bug status wouldn't have been "resolved
WONTFIX", I would tell them that it happens with very short path names as well,
and the path length is NOT the cause [in my case]. It is nested classes, even one
level deep.
Ta
-nat
"Dave Wegener" <wegener@cboenospam.com> wrote in message
news:br7bfd$71t$1@eclipse.org...
> Check out but 23373
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=23373
> It talks about a file name path length issue on Windows.
>
>
> Text searches of open bugs can be performed quite simply off of the Bugs
> page on the Eclipse site. If you want to search all bug reports, you can
> click the Edit Query and add the Resolved, Verified, and Closed entries to
> the Status.
>
>
> natG wrote:
>
> > > Can you narrow it down to a simple, stand-alone example and post?
> > > I also suggest checking Bugzilla to see if it is an open/known issue.
> > >
> > > HTH,
> > > Eric
> > > --
> > > Eric Rizzo
> > > Software Architect
> > > Jibe, Inc.
> > > http://www.jibeinc.com
>
> > Its kinda hard to narrow down, although the inner class is rather simple, but
> > implements Comparator.
>
> > Due to time constraints on this, I factored it out into a regular class, and
> > everything is fine. (But of course does not solve the problem.)
>
> > As far as Bugzilla goes, I tried before posting here, and what a PITA to use
> that
> > interface! Are they for real?
> > I have to set who-knows how many parameters (including version numbers of
> > modules!!) to get a query?
> > I still feel I must have overlooked the obvious query sheet. Can't one just
> input
> > Eclipse/JDT/inner class and SEARCH?
>
> > Anyhow....
> > thanks
> > -nat
>
>
|
|
| |
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #126385 is a reply to message #125988] |
Thu, 11 December 2003 18:27 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
Oh; I have inner classes in other sources without this problem.
I would have to play "what if" with this source to try to pinpoint it.
Sorry, but I can't post the thing, the containing class is too complex.
-nat
"Eric Rizzo" <eclipse-user@jibeinc.com> wrote in message
news:br7t51$upn$2@eclipse.org...
> natG wrote:
> >
> > Its kinda hard to narrow down, although the inner class is rather simple, but
> > implements Comparator.
>
> Can't you just create a simple class with an inner class similar to the
> one in your "real" code and reproduce the problem?
> Or how about posting the code that fails and see what everyone thinks...
>
> --
> Eric Rizzo
> Software Architect
> Jibe, Inc.
> http://www.jibeinc.com
>
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #126875 is a reply to message #125964] |
Fri, 12 December 2003 18:09 |
 Genady Beryozkin
Messages: 410
Registered: July 2009 |
Senior Member |
|
|
What is is the path to your file ?
Do you use any plugins? Do you have anything special in the log file?
Genady
natG wrote:
> Thanks for the pointer on the bug. If the bug status wouldn't have been "resolved
> WONTFIX", I would tell them that it happens with very short path names as well,
> and the path length is NOT the cause [in my case]. It is nested classes, even one
> level deep.
>
> Ta
> -nat
>
> "Dave Wegener" <wegener@cboenospam.com> wrote in message
> news:br7bfd$71t$1@eclipse.org...
>
>>Check out but 23373
>>https://bugs.eclipse.org/bugs/show_bug.cgi?id=23373
>>It talks about a file name path length issue on Windows.
>>
>>
>>Text searches of open bugs can be performed quite simply off of the Bugs
>>page on the Eclipse site. If you want to search all bug reports, you can
>>click the Edit Query and add the Resolved, Verified, and Closed entries to
>>the Status.
>>
>>
>>natG wrote:
>>
>>
>>>>Can you narrow it down to a simple, stand-alone example and post?
>>>>I also suggest checking Bugzilla to see if it is an open/known issue.
>>>>
>>>>HTH,
>>>>Eric
>>>>--
>>>>Eric Rizzo
>>>>Software Architect
>>>>Jibe, Inc.
>>>>http://www.jibeinc.com
>>
>>>Its kinda hard to narrow down, although the inner class is rather simple, but
>>>implements Comparator.
>>
>>>Due to time constraints on this, I factored it out into a regular class, and
>>>everything is fine. (But of course does not solve the problem.)
>>
>>>As far as Bugzilla goes, I tried before posting here, and what a PITA to use
>>
>>that
>>
>>>interface! Are they for real?
>>>I have to set who-knows how many parameters (including version numbers of
>>>modules!!) to get a query?
>>>I still feel I must have overlooked the obvious query sheet. Can't one just
>>
>>input
>>
>>>Eclipse/JDT/inner class and SEARCH?
>>
>>>Anyhow....
>>>thanks
>>>-nat
>>
>>
>
>
--
Genady Beryozkin
http://www.genady.net/
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #127696 is a reply to message #126875] |
Mon, 15 December 2003 19:35 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
The name of the file is EzModelBase.java and it resides in:
F:\Data\MyJavaProj\1.4.2\libs\ez\swing\tables
The workspace location is: F:Data\MyJavProj\Eclipse\Main.
When I created the project, I simply pointed the wizard to
F:\data\MyJavaProj1.4.2\libs and it eloquently read and rebuilt all the packages
whose outermost level is "ez".
I must admit that I didn't realize that the source was 7 levels deep, since my
Eclipse Title Bar (I set the startup parameters to display) says:
F:Data\MyJavaProj\Eclipse\Main which is only 4 levels deep.
So. maybe it is related after all to the aforementioned bug.
Plugins? I tried two, but deleted both. (Still hesitant on installing a new
database plugin.)
Logfile: I recall reading a quick way of getting the log but it is eluding me now.
Thank you much.
-nat
"Genady" <eclipse@genady.org> wrote in message news:brd04a$4d2$1@eclipse.org...
> What is is the path to your file ?
> Do you use any plugins? Do you have anything special in the log file?
>
> Genady
>
> natG wrote:
>
> > Thanks for the pointer on the bug. If the bug status wouldn't have been
"resolved
> > WONTFIX", I would tell them that it happens with very short path names as
well,
> > and the path length is NOT the cause [in my case]. It is nested classes, even
one
> > level deep.
> >
> > Ta
> > -nat
> >
> > "Dave Wegener" <wegener@cboenospam.com> wrote in message
> > news:br7bfd$71t$1@eclipse.org...
> >
> >>Check out but 23373
> >>https://bugs.eclipse.org/bugs/show_bug.cgi?id=23373
> >>It talks about a file name path length issue on Windows.
> >>
> >>
> >>Text searches of open bugs can be performed quite simply off of the Bugs
> >>page on the Eclipse site. If you want to search all bug reports, you can
> >>click the Edit Query and add the Resolved, Verified, and Closed entries to
> >>the Status.
> >>
> >>
> >>natG wrote:
> >>
> >>
> >>>>Can you narrow it down to a simple, stand-alone example and post?
> >>>>I also suggest checking Bugzilla to see if it is an open/known issue.
> >>>>
> >>>>HTH,
> >>>>Eric
> >>>>--
> >>>>Eric Rizzo
> >>>>Software Architect
> >>>>Jibe, Inc.
> >>>>http://www.jibeinc.com
> >>
> >>>Its kinda hard to narrow down, although the inner class is rather simple, but
> >>>implements Comparator.
> >>
> >>>Due to time constraints on this, I factored it out into a regular class, and
> >>>everything is fine. (But of course does not solve the problem.)
> >>
> >>>As far as Bugzilla goes, I tried before posting here, and what a PITA to use
> >>
> >>that
> >>
> >>>interface! Are they for real?
> >>>I have to set who-knows how many parameters (including version numbers of
> >>>modules!!) to get a query?
> >>>I still feel I must have overlooked the obvious query sheet. Can't one just
> >>
> >>input
> >>
> >>>Eclipse/JDT/inner class and SEARCH?
> >>
> >>>Anyhow....
> >>>thanks
> >>>-nat
> >>
> >>
> >
> >
>
>
> --
> Genady Beryozkin
> http://www.genady.net/
>
|
|
| |
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #127761 is a reply to message #127696] |
Tue, 16 December 2003 02:57 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
Genady, Darin, and others.
We got him!<g>. The logfile reports the REASON for that message: "Resource exists
with different case". And I understand it, and possibly stumbled on a different
Eclipse bug.
I remember that when I coded that inner class, I mistakenly named it with a name
beginning with a lowercase letter. Later, I simply uppercased it. And the fun
started. Evidently Eclipse did not delete the old class file (Outer$inner.class).
So, it complained when it had to create a class with the same name but different
case (since the os does not differentiate them). A refresh/rebuild should
definetly catch that.
To be honest, although I now found that old lowercase useless .class file, and
deleted it, I have not re-tested. I am confident that this is the reason.
thanks, (oops...Thanks gg)
-nat
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #127926 is a reply to message #127761] |
Tue, 16 December 2003 20:45 |
Genady Beryozkin
Messages: 410
Registered: July 2009 |
Senior Member |
|
|
Tell us whether it's the problem.
I believe opening a bug would be appropriate to request such situation.
Genady
natG wrote:
> Genady, Darin, and others.
>
> We got him!<g>. The logfile reports the REASON for that message: "Resource exists
> with different case". And I understand it, and possibly stumbled on a different
> Eclipse bug.
> I remember that when I coded that inner class, I mistakenly named it with a name
> beginning with a lowercase letter. Later, I simply uppercased it. And the fun
> started. Evidently Eclipse did not delete the old class file (Outer$inner.class).
> So, it complained when it had to create a class with the same name but different
> case (since the os does not differentiate them). A refresh/rebuild should
> definetly catch that.
>
> To be honest, although I now found that old lowercase useless .class file, and
> deleted it, I have not re-tested. I am confident that this is the reason.
>
> thanks, (oops...Thanks gg)
> -nat
>
>
--
Genady Beryozkin
http://www.genady.net/
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #128002 is a reply to message #127926] |
Wed, 17 December 2003 00:51 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
Yes! Reproducible (simply) and happens ALWAYS.
Anyone can try it.
1. Create a class.
2. Inside the class create another (inner) class with a mixed-case name.
3. Save/Compile.
4. Change the CASE of the inner class name. And SAVE.
* voila, you get the error AND the inner class is indeed NOT compiled. *
5. From the os, externally, locate the inner class .class file (which should have
been deleted via refresh), and DELETE it.
6. You can now save, and the previous error/Todo will be cleaned up. And the new
inner class file will be written.
-nat
"Genady" <eclipse@genady.org> wrote in message news:brnqtg$eq5$1@eclipse.org...
> Tell us whether it's the problem.
> I believe opening a bug would be appropriate to request such situation.
>
> Genady
>
> natG wrote:
> > Genady, Darin, and others.
> >
> > We got him!<g>. The logfile reports the REASON for that message: "Resource
exists
> > with different case". And I understand it, and possibly stumbled on a
different
> > Eclipse bug.
> > I remember that when I coded that inner class, I mistakenly named it with a
name
> > beginning with a lowercase letter. Later, I simply uppercased it. And the fun
> > started. Evidently Eclipse did not delete the old class file
(Outer$inner.class).
> > So, it complained when it had to create a class with the same name but
different
> > case (since the os does not differentiate them). A refresh/rebuild should
> > definetly catch that.
> >
> > To be honest, although I now found that old lowercase useless .class file, and
> > deleted it, I have not re-tested. I am confident that this is the reason.
> >
> > thanks, (oops...Thanks gg)
> > -nat
> >
> >
>
>
> --
> Genady Beryozkin
> http://www.genady.net/
>
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #128041 is a reply to message #128002] |
Wed, 17 December 2003 10:19 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
Which build are you using? Which platform? In I200312162000 and on Windows
2000 I tried your steps and I could not reprodice the problem.
Jerome
"natG" <natgross.rentalsystems@verizon.net> wrote in message
news:bro99a$tg5$1@eclipse.org...
> Yes! Reproducible (simply) and happens ALWAYS.
>
> Anyone can try it.
> 1. Create a class.
> 2. Inside the class create another (inner) class with a mixed-case name.
> 3. Save/Compile.
> 4. Change the CASE of the inner class name. And SAVE.
> * voila, you get the error AND the inner class is indeed NOT compiled. *
> 5. From the os, externally, locate the inner class .class file (which
should have
> been deleted via refresh), and DELETE it.
> 6. You can now save, and the previous error/Todo will be cleaned up. And
the new
> inner class file will be written.
>
> -nat
>
> "Genady" <eclipse@genady.org> wrote in message
news:brnqtg$eq5$1@eclipse.org...
> > Tell us whether it's the problem.
> > I believe opening a bug would be appropriate to request such situation.
> >
> > Genady
> >
> > natG wrote:
> > > Genady, Darin, and others.
> > >
> > > We got him!<g>. The logfile reports the REASON for that message:
"Resource
> exists
> > > with different case". And I understand it, and possibly stumbled on a
> different
> > > Eclipse bug.
> > > I remember that when I coded that inner class, I mistakenly named it
with a
> name
> > > beginning with a lowercase letter. Later, I simply uppercased it. And
the fun
> > > started. Evidently Eclipse did not delete the old class file
> (Outer$inner.class).
> > > So, it complained when it had to create a class with the same name but
> different
> > > case (since the os does not differentiate them). A refresh/rebuild
should
> > > definetly catch that.
> > >
> > > To be honest, although I now found that old lowercase useless .class
file, and
> > > deleted it, I have not re-tested. I am confident that this is the
reason.
> > >
> > > thanks, (oops...Thanks gg)
> > > -nat
> > >
> > >
> >
> >
> > --
> > Genady Beryozkin
> > http://www.genady.net/
> >
>
>
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #128181 is a reply to message #128041] |
Wed, 17 December 2003 15:43 |
| Eclipse User |
|
|
|
Originally posted by: natgross.rentalsystems.verizon.net
Version: 2.1.2
Build id: 2003110308002
Windows xpPro
-nat
"Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
news:brpajf$su3$1@eclipse.org...
> Which build are you using? Which platform? In I200312162000 and on Windows
> 2000 I tried your steps and I could not reprodice the problem.
>
> Jerome
>
> "natG" <natgross.rentalsystems@verizon.net> wrote in message
> news:bro99a$tg5$1@eclipse.org...
> > Yes! Reproducible (simply) and happens ALWAYS.
> >
> > Anyone can try it.
> > 1. Create a class.
> > 2. Inside the class create another (inner) class with a mixed-case name.
> > 3. Save/Compile.
> > 4. Change the CASE of the inner class name. And SAVE.
> > * voila, you get the error AND the inner class is indeed NOT compiled. *
> > 5. From the os, externally, locate the inner class .class file (which
> should have
> > been deleted via refresh), and DELETE it.
> > 6. You can now save, and the previous error/Todo will be cleaned up. And
> the new
> > inner class file will be written.
> >
> > -nat
> >
> > "Genady" <eclipse@genady.org> wrote in message
> news:brnqtg$eq5$1@eclipse.org...
> > > Tell us whether it's the problem.
> > > I believe opening a bug would be appropriate to request such situation.
> > >
> > > Genady
> > >
> > > natG wrote:
> > > > Genady, Darin, and others.
> > > >
> > > > We got him!<g>. The logfile reports the REASON for that message:
> "Resource
> > exists
> > > > with different case". And I understand it, and possibly stumbled on a
> > different
> > > > Eclipse bug.
> > > > I remember that when I coded that inner class, I mistakenly named it
> with a
> > name
> > > > beginning with a lowercase letter. Later, I simply uppercased it. And
> the fun
> > > > started. Evidently Eclipse did not delete the old class file
> > (Outer$inner.class).
> > > > So, it complained when it had to create a class with the same name but
> > different
> > > > case (since the os does not differentiate them). A refresh/rebuild
> should
> > > > definetly catch that.
> > > >
> > > > To be honest, although I now found that old lowercase useless .class
> file, and
> > > > deleted it, I have not re-tested. I am confident that this is the
> reason.
> > > >
> > > > thanks, (oops...Thanks gg)
> > > > -nat
> > > >
> > > >
> > >
> > >
> > > --
> > > Genady Beryozkin
> > > http://www.genady.net/
> > >
> >
> >
>
>
|
|
|
| Re: Huh? "A class file was not written. The project may be inconsistent, if so try refreshing t [message #128246 is a reply to message #128181] |
Wed, 17 December 2003 17:28 |
Jerome Lanneluc
Messages: 572
Registered: July 2009 |
Senior Member |
|
|
So I guess this is fixed in the 3.0 stream...
Jerome
"natG" <natgross.rentalsystems@verizon.net> wrote in message
news:brptht$kt6$1@eclipse.org...
> Version: 2.1.2
> Build id: 2003110308002
> Windows xpPro
>
> -nat
>
> "Jerome Lanneluc" <jerome_lanneluc@fr.ibm.com> wrote in message
> news:brpajf$su3$1@eclipse.org...
> > Which build are you using? Which platform? In I200312162000 and on
Windows
> > 2000 I tried your steps and I could not reprodice the problem.
> >
> > Jerome
> >
> > "natG" <natgross.rentalsystems@verizon.net> wrote in message
> > news:bro99a$tg5$1@eclipse.org...
> > > Yes! Reproducible (simply) and happens ALWAYS.
> > >
> > > Anyone can try it.
> > > 1. Create a class.
> > > 2. Inside the class create another (inner) class with a mixed-case
name.
> > > 3. Save/Compile.
> > > 4. Change the CASE of the inner class name. And SAVE.
> > > * voila, you get the error AND the inner class is indeed NOT compiled.
*
> > > 5. From the os, externally, locate the inner class .class file (which
> > should have
> > > been deleted via refresh), and DELETE it.
> > > 6. You can now save, and the previous error/Todo will be cleaned up.
And
> > the new
> > > inner class file will be written.
> > >
> > > -nat
> > >
> > > "Genady" <eclipse@genady.org> wrote in message
> > news:brnqtg$eq5$1@eclipse.org...
> > > > Tell us whether it's the problem.
> > > > I believe opening a bug would be appropriate to request such
situation.
> > > >
> > > > Genady
> > > >
> > > > natG wrote:
> > > > > Genady, Darin, and others.
> > > > >
> > > > > We got him!<g>. The logfile reports the REASON for that message:
> > "Resource
> > > exists
> > > > > with different case". And I understand it, and possibly stumbled
on a
> > > different
> > > > > Eclipse bug.
> > > > > I remember that when I coded that inner class, I mistakenly named
it
> > with a
> > > name
> > > > > beginning with a lowercase letter. Later, I simply uppercased it.
And
> > the fun
> > > > > started. Evidently Eclipse did not delete the old class file
> > > (Outer$inner.class).
> > > > > So, it complained when it had to create a class with the same name
but
> > > different
> > > > > case (since the os does not differentiate them). A refresh/rebuild
> > should
> > > > > definetly catch that.
> > > > >
> > > > > To be honest, although I now found that old lowercase useless
..class
> > file, and
> > > > > deleted it, I have not re-tested. I am confident that this is the
> > reason.
> > > > >
> > > > > thanks, (oops...Thanks gg)
> > > > > -nat
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Genady Beryozkin
> > > > http://www.genady.net/
> > > >
> > >
> > >
> >
> >
>
>
|
|
| |
Goto Forum:
Current Time: Fri Apr 26 00:23:06 GMT 2024
Powered by FUDForum. Page generated in 0.04639 seconds |
] 
Search
Help
Register
Login
Home
