Home » Archived » Visual Editor (VE) » Classpath of visual editor virtual machine
| Classpath of visual editor virtual machine [message #47549] |
Tue, 06 July 2004 08:52  |
Eclipse User |
|
|
|
Is there any way of overriding the class path of the VM for the visual
editor in such a way that it ignores project dependencies and uses only the
path that you specify?
If not, how is its classpath calculated in terms of project dependencies
and the bean info path etc.?
|
|
| |
| Re: Classpath of visual editor virtual machine [message #47864 is a reply to message #47804] |
Tue, 06 July 2004 12:05  |
| Eclipse User |
|
|
|
What you say is not really true. For example, if you have a project that
refers to classes via reflection (possibly specified via system properties
or other command line arguments), then it need not have the project
containing such classes on its compile path, but will need them to run
properly with those arguments. This can be very useful. An example I can
think of for such a situation is one where you have a pluggable orb
implementation, and specify the implementation class as a system property.
You would not however want to tie your generic project within Eclipse to a
particular implementation, and the options in the run configurations enable
you to specify one or the other (via command line argument and overriding a
projects default classpath) to run with.
Anyhow my problem boils down to the following questions
1) If you add a project to the visual editor's BeanInfo path will it put
it before all of the dependencies of the project or after them in the visual
editor's classpath?
2) If the answer to 1) is that it puts it after them (as I suspect),
then is there any way of making it put them before?
By the way, the project properties editor no longer opens up if you add more
than one project to the bean info path (Eclipse 3.0).
Is this a known issue? It seems though that you can just edit the
beanInfoConfig file, so I can work around it.
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccee2u$rup$1@eclipse.org...
> Why do you need to? If you need those dependencies to compile, don't you
> also need them to run?
>
> The calculation is done via, first Eclipse JDT calculates the classpath
> of the project like it does for any normal project, then we add in the
> beaninfo jar files that are needed.
>
>
> --
> Thanks, Rich Kulp
>
>
|
|
| |
| Re: Classpath of visual editor virtual machine [message #48639 is a reply to message #48274] |
Wed, 07 July 2004 04:58 |
| Eclipse User |
|
|
|
OK, I have entered the bug into Bugzilla (no. 69444).
On the other issue
1) If you add a project to the visual editor's BeanInfo path will it put
> > it before all of the dependencies of the project or after them in the
visual
> > editor's classpath?
> No, they go after. And there is no way to put them before any from the
> classpath itself.
I would like to request more control over the visual editors classpath.
I think you should be able to override the bean info path for a
project,
just as you can override the classpath of a run configuration that is based
on a
particular project. Although situations that require you to do so are
probably rare,
I think it is better to have more control than people generally need, than
to not
have enough.
As an argument for this, I will describe in more detail the situation I
have that requires
such control.
We have a java project A containing various classes. There are then two
further projects B and C,
which both duplicate some of the classes in A, and one or the other is used
at run-time instead of A.
The other projects only refer to A in their dependencies (in order to
compile), even though in practice
you need to run with B or C, which contain real implementations of some of
the classes in A.
It is no use to me to simply add B or C to the bean info classpath as A will
still be picked up first.
The structure of the Java projects cannot be changed and part of the reason
is due to third party products anyhow, so I am not interested in any
argument about our
project structure being odd or incorrect.
If I request this feature, do you think there is any chance of it being
implemented?
Darren Hurt
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccf2sh$i4e$1@eclipse.org...
>
> >
> > Anyhow my problem boils down to the following questions
> >
> > 1) If you add a project to the visual editor's BeanInfo path will it
put
> > it before all of the dependencies of the project or after them in the
visual
> > editor's classpath?
> No, they go after. And there is no way to put them before any from the
> classpath itself.
>
> > By the way, the project properties editor no longer opens up if you add
more
> > than one project to the bean info path (Eclipse 3.0).
> > Is this a known issue? It seems though that you can just edit the
> > beanInfoConfig file, so I can work around it.
>
> Please, I would appreciate if you would open a Bugzilla defect about
> this. That should not occur and is a bug. We need to get it fixed. We
> didn't know about it. :-(
>
> Also, there is a way to have a customized remote VM launched by the VE
> where you can remove projects from the list. But you got to be careful
> to not remove one that is needed.
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
| Re: Classpath of visual editor virtual machine [message #594466 is a reply to message #47549] |
Tue, 06 July 2004 10:48 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
Why do you need to? If you need those dependencies to compile, don't you
also need them to run?
The calculation is done via, first Eclipse JDT calculates the classpath
of the project like it does for any normal project, then we add in the
beaninfo jar files that are needed.
--
Thanks, Rich Kulp
|
|
|
| Re: Classpath of visual editor virtual machine [message #594479 is a reply to message #47804] |
Tue, 06 July 2004 12:05 |
| Eclipse User |
|
|
|
What you say is not really true. For example, if you have a project that
refers to classes via reflection (possibly specified via system properties
or other command line arguments), then it need not have the project
containing such classes on its compile path, but will need them to run
properly with those arguments. This can be very useful. An example I can
think of for such a situation is one where you have a pluggable orb
implementation, and specify the implementation class as a system property.
You would not however want to tie your generic project within Eclipse to a
particular implementation, and the options in the run configurations enable
you to specify one or the other (via command line argument and overriding a
projects default classpath) to run with.
Anyhow my problem boils down to the following questions
1) If you add a project to the visual editor's BeanInfo path will it put
it before all of the dependencies of the project or after them in the visual
editor's classpath?
2) If the answer to 1) is that it puts it after them (as I suspect),
then is there any way of making it put them before?
By the way, the project properties editor no longer opens up if you add more
than one project to the bean info path (Eclipse 3.0).
Is this a known issue? It seems though that you can just edit the
beanInfoConfig file, so I can work around it.
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccee2u$rup$1@eclipse.org...
> Why do you need to? If you need those dependencies to compile, don't you
> also need them to run?
>
> The calculation is done via, first Eclipse JDT calculates the classpath
> of the project like it does for any normal project, then we add in the
> beaninfo jar files that are needed.
>
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
| Re: Classpath of visual editor virtual machine [message #594598 is a reply to message #47864] |
Tue, 06 July 2004 16:43 |
| Eclipse User |
|
|
|
Originally posted by: richkulp.NO.SPAM.us.ibm.com
>
> Anyhow my problem boils down to the following questions
>
> 1) If you add a project to the visual editor's BeanInfo path will it put
> it before all of the dependencies of the project or after them in the visual
> editor's classpath?
No, they go after. And there is no way to put them before any from the
classpath itself.
> By the way, the project properties editor no longer opens up if you add more
> than one project to the bean info path (Eclipse 3.0).
> Is this a known issue? It seems though that you can just edit the
> beanInfoConfig file, so I can work around it.
Please, I would appreciate if you would open a Bugzilla defect about
this. That should not occur and is a bug. We need to get it fixed. We
didn't know about it. :-(
Also, there is a way to have a customized remote VM launched by the VE
where you can remove projects from the list. But you got to be careful
to not remove one that is needed.
--
Thanks, Rich Kulp
|
|
|
| Re: Classpath of visual editor virtual machine [message #594703 is a reply to message #48274] |
Wed, 07 July 2004 04:58 |
| Eclipse User |
|
|
|
OK, I have entered the bug into Bugzilla (no. 69444).
On the other issue
1) If you add a project to the visual editor's BeanInfo path will it put
> > it before all of the dependencies of the project or after them in the
visual
> > editor's classpath?
> No, they go after. And there is no way to put them before any from the
> classpath itself.
I would like to request more control over the visual editors classpath.
I think you should be able to override the bean info path for a
project,
just as you can override the classpath of a run configuration that is based
on a
particular project. Although situations that require you to do so are
probably rare,
I think it is better to have more control than people generally need, than
to not
have enough.
As an argument for this, I will describe in more detail the situation I
have that requires
such control.
We have a java project A containing various classes. There are then two
further projects B and C,
which both duplicate some of the classes in A, and one or the other is used
at run-time instead of A.
The other projects only refer to A in their dependencies (in order to
compile), even though in practice
you need to run with B or C, which contain real implementations of some of
the classes in A.
It is no use to me to simply add B or C to the bean info classpath as A will
still be picked up first.
The structure of the Java projects cannot be changed and part of the reason
is due to third party products anyhow, so I am not interested in any
argument about our
project structure being odd or incorrect.
If I request this feature, do you think there is any chance of it being
implemented?
Darren Hurt
"Rich Kulp" <richkulp@NO.SPAM.us.ibm.com> wrote in message
news:ccf2sh$i4e$1@eclipse.org...
>
> >
> > Anyhow my problem boils down to the following questions
> >
> > 1) If you add a project to the visual editor's BeanInfo path will it
put
> > it before all of the dependencies of the project or after them in the
visual
> > editor's classpath?
> No, they go after. And there is no way to put them before any from the
> classpath itself.
>
> > By the way, the project properties editor no longer opens up if you add
more
> > than one project to the bean info path (Eclipse 3.0).
> > Is this a known issue? It seems though that you can just edit the
> > beanInfoConfig file, so I can work around it.
>
> Please, I would appreciate if you would open a Bugzilla defect about
> this. That should not occur and is a bug. We need to get it fixed. We
> didn't know about it. :-(
>
> Also, there is a way to have a customized remote VM launched by the VE
> where you can remove projects from the list. But you got to be careful
> to not remove one that is needed.
>
> --
> Thanks, Rich Kulp
>
>
|
|
|
Goto Forum:
Current Time: Wed May 07 11:29:36 EDT 2025
Powered by FUDForum. Page generated in 0.03998 seconds |
Home