| Problems with Classpath Container in Eclipse 3.0 M7 [message #142880] |
Wed, 18 February 2004 06:17  |
Eclipse User |
|
|
|
Hi,
I'm using a custom classpath container which will - depending on a
properties-file in the project - resolve to some other projects (if they
are available in the workspace), or to jar-files containing these
projects (if the developer is only using them, but not actively working
on them).
This works fine - for normal development, i.e. resolving dependencies
for the projects I'm working on - in both I20040128 and M7.
The problem is, that when I try to "run" something the resolved
classpath is very different in 3.0 M7.
In I20040128 Eclipse took the classpath of the project containing the
main-class (or probably simply the project specified in the run-dialog).
The result is a command-line with a length of ~800 bytes.
In 3.0 M7 Eclipse seems to resolve this classpath recursively, which
means that I end up with a commandline of ~40000 bytes (and an
IOException while Eclipse tries to create the process whose message is
unfortunately truncated to 1024 bytes, so that I don't get the
error-code from Windows).
Is this change expected (and should I try to find my own solution), or
is this maybe a "bug"? (In some parts I understand the "new" behaviour -
the projects my "start-project" is depending on are exporting there own
"bin"-dir, so it seems correct that this is added to the classpath. But
what I don't understand is that for example junit.jar is for example
added to the classpath 201 times - and I don't think that I have marked
JUnit as exported in *any* project)
Thanks for your input in advance.
Nico
|
|
|
| Re: Problems with Classpath Container in Eclipse 3.0 M7 [message #142893 is a reply to message #142880] |
Wed, 18 February 2004 08:48  |
| Eclipse User |
|
|
|
This looks similar to bug
https://bugs.eclipse.org/bugs/show_bug.cgi?id=51533
but this one was related to using the PDE container only.
I think your point is valid, and you should jump into the fight to gain a
more flexible solution.
The problem is that the command line has a physical size limit.
"Nico Seessle" <nico@seessle.de> wrote in message
news:c0vhe9$b6t$1@eclipse.org...
> Hi,
>
> I'm using a custom classpath container which will - depending on a
> properties-file in the project - resolve to some other projects (if they
> are available in the workspace), or to jar-files containing these
> projects (if the developer is only using them, but not actively working
> on them).
>
> This works fine - for normal development, i.e. resolving dependencies
> for the projects I'm working on - in both I20040128 and M7.
>
> The problem is, that when I try to "run" something the resolved
> classpath is very different in 3.0 M7.
>
> In I20040128 Eclipse took the classpath of the project containing the
> main-class (or probably simply the project specified in the run-dialog).
> The result is a command-line with a length of ~800 bytes.
>
> In 3.0 M7 Eclipse seems to resolve this classpath recursively, which
> means that I end up with a commandline of ~40000 bytes (and an
> IOException while Eclipse tries to create the process whose message is
> unfortunately truncated to 1024 bytes, so that I don't get the
> error-code from Windows).
>
> Is this change expected (and should I try to find my own solution), or
> is this maybe a "bug"? (In some parts I understand the "new" behaviour -
> the projects my "start-project" is depending on are exporting there own
> "bin"-dir, so it seems correct that this is added to the classpath. But
> what I don't understand is that for example junit.jar is for example
> added to the classpath 201 times - and I don't think that I have marked
> JUnit as exported in *any* project)
>
> Thanks for your input in advance.
>
> Nico
|
|
|
| Re: Problems with Classpath Container in Eclipse 3.0 M7 [message #142921 is a reply to message #142893] |
Wed, 18 February 2004 09:05 |
| Eclipse User |
|
|
|
We had a bug in container resolution for runtime classpaths. Projects
resolved from a container, were not properly expanded on the runtime
classpath. There may still be some issues here. I filed an assoicated bug.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=52357
Darin
"Philippe Mulet" <philippe_mulet@fr.ibm.com> wrote in message
news:c0vq9q$mqb$1@eclipse.org...
> This looks similar to bug
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51533
> but this one was related to using the PDE container only.
> I think your point is valid, and you should jump into the fight to gain a
> more flexible solution.
> The problem is that the command line has a physical size limit.
>
> "Nico Seessle" <nico@seessle.de> wrote in message
> news:c0vhe9$b6t$1@eclipse.org...
> > Hi,
> >
> > I'm using a custom classpath container which will - depending on a
> > properties-file in the project - resolve to some other projects (if they
> > are available in the workspace), or to jar-files containing these
> > projects (if the developer is only using them, but not actively working
> > on them).
> >
> > This works fine - for normal development, i.e. resolving dependencies
> > for the projects I'm working on - in both I20040128 and M7.
> >
> > The problem is, that when I try to "run" something the resolved
> > classpath is very different in 3.0 M7.
> >
> > In I20040128 Eclipse took the classpath of the project containing the
> > main-class (or probably simply the project specified in the run-dialog).
> > The result is a command-line with a length of ~800 bytes.
> >
> > In 3.0 M7 Eclipse seems to resolve this classpath recursively, which
> > means that I end up with a commandline of ~40000 bytes (and an
> > IOException while Eclipse tries to create the process whose message is
> > unfortunately truncated to 1024 bytes, so that I don't get the
> > error-code from Windows).
> >
> > Is this change expected (and should I try to find my own solution), or
> > is this maybe a "bug"? (In some parts I understand the "new" behaviour -
> > the projects my "start-project" is depending on are exporting there own
> > "bin"-dir, so it seems correct that this is added to the classpath. But
> > what I don't understand is that for example junit.jar is for example
> > added to the classpath 201 times - and I don't think that I have marked
> > JUnit as exported in *any* project)
> >
> > Thanks for your input in advance.
> >
> > Nico
>
>
|
|
|
Powered by
FUDForum. Page generated in 0.29071 seconds
Home