| Recommendation for new developer [message #465087] |
Thu, 22 March 2007 18:06  |
Eclipse User |
|
|
|
Originally posted by: mmccaskill.healthdec.com
RCP is being considered for porting a current JFace/SWT application (which uses Spring,Hibernate,Derby). I want to know the more appropriate approach to package our various libraries/common code.
Our current structure in eclipse is broken into separate projects:
(Note I'm not using our real domain)
libs
- JARs in root, with substructure data,ws (webstart), web, swt{windows,osx,linux}, net.
domain
- has package com.comany.domain
commons
- has packages for com.company.
Would it be appropriate to make libs a plugin? (unzip jars?).
|
|
|
| Re: Recommendation for new developer [message #465089 is a reply to message #465087] |
Thu, 22 March 2007 18:26  |
 Charlie Kelly
Messages: 276
Registered: July 2009 |
Senior Member |
|
|
Hi Michael,
I also use Hibernate/Derby on the client (and Hibernate/Postgres on the
server side). I've found the following structure to work well:
I use three separate copies of Eclipse IDE:
1) Client (3.3M5 for plugin development)
2) Common (3.3M5 for java project development)
3) Server (JBoss IDE 2.0 Beta for EJB3 development)
The Common IDE has several java projects that are shared by Client and
Server. Each project has its own build.xml.
Within Common, I also use a "Master" build.xml in a separate project
that calls the individual build.xml files and then transports the
resulting jar file to folders on the server and client sides.
Within the Client IDE I have a project that contains jar files for
Hibernate, Derby, other external libraries, and the jar files generated
by the Common Master build. I use the "create new project from existing
jar files" Wizard to create a new plugin project from these jars. I use
"Eclipse-Buddy-Policy: registered" within the generated plugin.
Hope this helps.
Charlie
Michael McCaskill wrote:
> RCP is being considered for porting a current JFace/SWT application (which uses Spring,Hibernate,Derby). I want to know the more appropriate approach to package our various libraries/common code.
>
> Our current structure in eclipse is broken into separate projects:
> (Note I'm not using our real domain)
> libs
> - JARs in root, with substructure data,ws (webstart), web, swt{windows,osx,linux}, net.
> domain
> - has package com.comany.domain
> commons
> - has packages for com.company.
>
> Would it be appropriate to make libs a plugin? (unzip jars?).
|
|
|
|
|
| Re: Recommendation for new developer [message #465095 is a reply to message #465087] |
Thu, 22 March 2007 20:08 |
| Eclipse User |
|
|
|
Originally posted by: lamont_gilbert.rigidsoftware.com
On Thu, 22 Mar 2007 14:06:32 -0400, Michael McCaskill wrote:
> RCP is being considered for porting a current JFace/SWT application (which uses Spring,Hibernate,Derby). I want to know the more appropriate approach to package our various libraries/common code.
>
> Our current structure in eclipse is broken into separate projects:
> (Note I'm not using our real domain)
> libs
> - JARs in root, with substructure data,ws (webstart), web, swt{windows,osx,linux}, net.
> domain
> - has package com.comany.domain
> commons
> - has packages for com.company.
>
> Would it be appropriate to make libs a plugin? (unzip jars?).
That would be my strategy. Appearantly your company has already decided
how it wants to partition its code. libraries are changeable and
upgradeable units and you will get that with plugins. Dependencies will
take a bit of learning, but you can do it all.
|
|
|
| Re: Recommendation for new development [message #465097 is a reply to message #465093] |
Thu, 22 March 2007 20:10 |
| Eclipse User |
|
|
|
Originally posted by: lamont_gilbert.rigidsoftware.com
On Thu, 22 Mar 2007 15:49:06 -0400, Michael McCaskill wrote:
> Would it really be reasonable to create a plugin for all 100+ JARs in my libs project?
Thats a question for your company. If there is a valid reason for them to
be seperate jars now, then likely that same reason will hold as to why
they will be seperate plugins. But not necessarily.
I have some multi jar plugins. the seperate jars just help me maintain
proper dependency seperation in places, but i still will upgrade those
jars as a unit. I find seperate jars to be my preferred way over simply
seperate packages.
|
|
|
|
|
|
| Re: Recommendation for new development [message #465146 is a reply to message #465097] |
Fri, 23 March 2007 12:59 |
| Eclipse User |
|
|
|
Originally posted by: mmccaskill.healthdec.com
The only reason they are separated is because it makes sense. But ultimately, each project copies what JARs it requires into its build directory upon creating a WAR, etc.
Thanks for all the help.
|
|
|
Powered by
FUDForum. Page generated in 0.04966 seconds
] 
Search
Help
Register
Login
Home
