Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Plugin Development Environment (PDE) » How to add an external jar (in the network) to the classpath of a plugin project
How to add an external jar (in the network) to the classpath of a plugin project [message #24683] Mon, 29 September 2008 13:01 Go to next message
Kobi Perl is currently offline Kobi Perl
Messages: 7
Registered: July 2009
Junior Member
I can't add an address in the network (\\blah\blah.jar) to the the
Bundle-path.

It's important for me to use that adress for the specific jar, and not
just copy the jar to a lib folder in the project, because another team is
responsible for that jar, and is changing it from time to time, so I need
that changes that the other team does, will affect my jar.

Is it too much to ask? Can I do that?
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #24762 is a reply to message #24683] Mon, 29 September 2008 17:03 Go to previous messageGo to next message
Eclipse User
Originally posted by: eclipse-news.rizzoweb.com

On 9/29/2008 9:01 AM, Kobi Perl wrote:
> I can't add an address in the network (\\blah\blah.jar) to the the
> Bundle-path.
>
> It's important for me to use that adress for the specific jar, and not
> just copy the jar to a lib folder in the project, because another team
> is responsible for that jar, and is changing it from time to time, so I
> need that changes that the other team does, will affect my jar.
>
> Is it too much to ask? Can I do that?
>

Even if you could, how would you handle building and deploying your
plugin? At some point it is going to have to have a copy of the JAR to
run against.
Is that other team using CVS or some other configuration
management/source control tool that you could tap into?

Eric
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #24866 is a reply to message #24762] Thu, 02 October 2008 05:09 Go to previous messageGo to next message
Kobi Perl is currently offline Kobi Perl
Messages: 7
Registered: July 2009
Junior Member
It's quite simple - all of my customers are in the same network as me, so
the deployment is not a problem. After the deployment it will still use
the network address.
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #24916 is a reply to message #24866] Thu, 02 October 2008 17:32 Go to previous messageGo to next message
Eclipse User
Originally posted by: eclipse-news.rizzoweb.com

On 10/2/2008 1:09 AM, Kobi Perl wrote:
> It's quite simple - all of my customers are in the same network as me,
> so the deployment is not a problem. After the deployment it will still
> use the network address.
>

This is a really bad idea from a configuration management perspective.
If the JAR can change at any time, your use of it (your plugin(s)) could
break at any time. Also, what if the location of the JAR is offline or
the user's network access experiences a hiccup - your plugin(s) will
have serious problems.

I don't think Eclipse supports this kind of deployment, and I don't
think it should.

Eric
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #25040 is a reply to message #24916] Thu, 02 October 2008 20:49 Go to previous messageGo to next message
Kobi Perl is currently offline Kobi Perl
Messages: 7
Registered: July 2009
Junior Member
Thinking about it, I quite agree with your opinion.
After all, all the resources that my plugin uses - icons, help files etc.
must be in the plugin, so why should the classpath be any different.

Yet, it bothers me that java (simple jars) allows something that the
eclipse pde doesn't approve.

The big statement you made about the "changing jar" - well, me and the
other team agreed about a common API before the developement took place,
so it wouldn't have been a problem. I just wanted that backstage changes
in the jar will affect immediately, without having to release an update.
(A classic case for web services, but the developement would me precious
time)
Also, I've configuration files in the network, and also a TNS file that is
needed for connection to my db - so I am already dependent of the network.

But desoute of my last paragrath, I'll adapt your hook on the csv advice
(subversion in my case), because it is: a. Far more easy b. as you said,
it is safer c. Eclipse aren't going to change it.

So thank for all of your great help :)
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #25205 is a reply to message #25040] Mon, 06 October 2008 15:56 Go to previous message
Andrew Niefer is currently offline Andrew Niefer
Messages: 990
Registered: July 2009
Senior Member
For headless build, you can set "jars.extra.classpath" in your
build.properties to add items to the build time classpath.

http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/reference/pde_feature_generating_build.htm

I believe the same can be done for the workspace by setting project
properties for the build path.

In both these cases, I'm not sure about whether UNC network paths would
work, or if you need to mount a drive.

-Andrew

Kobi Perl wrote:
> Thinking about it, I quite agree with your opinion.
> After all, all the resources that my plugin uses - icons, help files
> etc. must be in the plugin, so why should the classpath be any different.
>
> Yet, it bothers me that java (simple jars) allows something that the
> eclipse pde doesn't approve.
>
> The big statement you made about the "changing jar" - well, me and the
> other team agreed about a common API before the developement took place,
> so it wouldn't have been a problem. I just wanted that backstage changes
> in the jar will affect immediately, without having to release an update.
> (A classic case for web services, but the developement would me precious
> time)
> Also, I've configuration files in the network, and also a TNS file that
> is needed for connection to my db - so I am already dependent of the
> network.
>
> But desoute of my last paragrath, I'll adapt your hook on the csv advice
> (subversion in my case), because it is: a. Far more easy b. as you said,
> it is safer c. Eclipse aren't going to change it.
> So thank for all of your great help :)
>
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #581933 is a reply to message #24683] Mon, 29 September 2008 17:03 Go to previous message
Eric Rizzo is currently offline Eric Rizzo
Messages: 2313
Registered: July 2009
Senior Member
On 9/29/2008 9:01 AM, Kobi Perl wrote:
> I can't add an address in the network (\\blah\blah.jar) to the the
> Bundle-path.
>
> It's important for me to use that adress for the specific jar, and not
> just copy the jar to a lib folder in the project, because another team
> is responsible for that jar, and is changing it from time to time, so I
> need that changes that the other team does, will affect my jar.
>
> Is it too much to ask? Can I do that?
>

Even if you could, how would you handle building and deploying your
plugin? At some point it is going to have to have a copy of the JAR to
run against.
Is that other team using CVS or some other configuration
management/source control tool that you could tap into?

Eric
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #582033 is a reply to message #24762] Thu, 02 October 2008 05:09 Go to previous message
Kobi Perl is currently offline Kobi Perl
Messages: 7
Registered: July 2009
Junior Member
It's quite simple - all of my customers are in the same network as me, so
the deployment is not a problem. After the deployment it will still use
the network address.
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #582087 is a reply to message #24866] Thu, 02 October 2008 17:32 Go to previous message
Eric Rizzo is currently offline Eric Rizzo
Messages: 2313
Registered: July 2009
Senior Member
On 10/2/2008 1:09 AM, Kobi Perl wrote:
> It's quite simple - all of my customers are in the same network as me,
> so the deployment is not a problem. After the deployment it will still
> use the network address.
>

This is a really bad idea from a configuration management perspective.
If the JAR can change at any time, your use of it (your plugin(s)) could
break at any time. Also, what if the location of the JAR is offline or
the user's network access experiences a hiccup - your plugin(s) will
have serious problems.

I don't think Eclipse supports this kind of deployment, and I don't
think it should.

Eric
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #582127 is a reply to message #24916] Thu, 02 October 2008 20:49 Go to previous message
Kobi Perl is currently offline Kobi Perl
Messages: 7
Registered: July 2009
Junior Member
Thinking about it, I quite agree with your opinion.
After all, all the resources that my plugin uses - icons, help files etc.
must be in the plugin, so why should the classpath be any different.

Yet, it bothers me that java (simple jars) allows something that the
eclipse pde doesn't approve.

The big statement you made about the "changing jar" - well, me and the
other team agreed about a common API before the developement took place,
so it wouldn't have been a problem. I just wanted that backstage changes
in the jar will affect immediately, without having to release an update.
(A classic case for web services, but the developement would me precious
time)
Also, I've configuration files in the network, and also a TNS file that is
needed for connection to my db - so I am already dependent of the network.

But desoute of my last paragrath, I'll adapt your hook on the csv advice
(subversion in my case), because it is: a. Far more easy b. as you said,
it is safer c. Eclipse aren't going to change it.

So thank for all of your great help :)
Re: How to add an external jar (in the network) to the classpath of a plugin project [message #582215 is a reply to message #25040] Mon, 06 October 2008 15:56 Go to previous message
Andrew Niefer is currently offline Andrew Niefer
Messages: 990
Registered: July 2009
Senior Member
For headless build, you can set "jars.extra.classpath" in your
build.properties to add items to the build time classpath.

http://help.eclipse.org/ganymede/index.jsp?topic=/org.eclips e.pde.doc.user/reference/pde_feature_generating_build.htm

I believe the same can be done for the workspace by setting project
properties for the build path.

In both these cases, I'm not sure about whether UNC network paths would
work, or if you need to mount a drive.

-Andrew

Kobi Perl wrote:
> Thinking about it, I quite agree with your opinion.
> After all, all the resources that my plugin uses - icons, help files
> etc. must be in the plugin, so why should the classpath be any different.
>
> Yet, it bothers me that java (simple jars) allows something that the
> eclipse pde doesn't approve.
>
> The big statement you made about the "changing jar" - well, me and the
> other team agreed about a common API before the developement took place,
> so it wouldn't have been a problem. I just wanted that backstage changes
> in the jar will affect immediately, without having to release an update.
> (A classic case for web services, but the developement would me precious
> time)
> Also, I've configuration files in the network, and also a TNS file that
> is needed for connection to my db - so I am already dependent of the
> network.
>
> But desoute of my last paragrath, I'll adapt your hook on the csv advice
> (subversion in my case), because it is: a. Far more easy b. as you said,
> it is safer c. Eclipse aren't going to change it.
> So thank for all of your great help :)
>
Previous Topic:Getting list of classes defined in a plugin
Next Topic:Why is "permissions.properties" not supported anymore in Eclipse 3.4 Ganymede?
Goto Forum:
  


Current Time: Sat Oct 25 16:17:32 GMT 2014

Powered by FUDForum. Page generated in 0.09489 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software