H
Harpstein
Here's the deal...
I have a jar file that I'm using to develop integration into various Java
IDE's. Specifically JBuilder and Eclipse.
I'm pretty new to Java, so I'm not really sure how to handle building the
jar for each of these.
Should I maintain two seperate jar files or should I combine them all into
one jar, seperated by namespaces?
Using one jar would simplify the maintenance and I'm already using
namespaces so I could just tack on an extra name for eclipse (like
com.harpstein.eclipse) and one for JBuilder. However, is it lame to have
code in a jar that can't be used by an app loading it (ie. OpenTools code
when the Eclipse IDE is being used), or is this going to cause problems when
Eclipse loads my jar? I'm leaning toward going with one jar, seperated with
namespaces, but was hoping people here could shed light on the various
pros/cons of going this route compared with the seperate jars route.
Any feedback you can give would be greatly appreciated.
Thanks,
harpstein
I have a jar file that I'm using to develop integration into various Java
IDE's. Specifically JBuilder and Eclipse.
I'm pretty new to Java, so I'm not really sure how to handle building the
jar for each of these.
Should I maintain two seperate jar files or should I combine them all into
one jar, seperated by namespaces?
Using one jar would simplify the maintenance and I'm already using
namespaces so I could just tack on an extra name for eclipse (like
com.harpstein.eclipse) and one for JBuilder. However, is it lame to have
code in a jar that can't be used by an app loading it (ie. OpenTools code
when the Eclipse IDE is being used), or is this going to cause problems when
Eclipse loads my jar? I'm leaning toward going with one jar, seperated with
namespaces, but was hoping people here could shed light on the various
pros/cons of going this route compared with the seperate jars route.
Any feedback you can give would be greatly appreciated.
Thanks,
harpstein