• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Best Pratices to maintain Source code in VAJ

 
Ranch Hand
Posts: 65
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,
We are running Visual Age 3.5 on a WIn2K environment. We also have the EMSRV
installed for team development. Our source base is huge so I am trying to come up with the good way to organize it.
We have a system which has 32 Menu options and each menu item in turn might have up to 5-10 sub menu items under it. SO we end up with approx 300
programs/classes to work with. Now as of now I have all the code in 1 Project and1 package. I have finished developing only 50% of the 32 menu
items and our workspace is already huge.
So here are my questions,
1. Would it be logical to break my code in to separate packages as follows-
Menu 1-10 --> Package A
Menu 11-20 --> Package B
Menu 21-32 --> Package C
and so any cross referencing of menu items between packages will have to be
qualified by the package name. But again this way I think having all my packages loaded in to the workspace will make it very huge anyway so that
might not help.
2. Would it be better to leave all the code in the same package but have
multiple workspace files such as
Menu 1-10 --> ide.icx.A
Menu 11-20 --> ide.icx.B
Menu 21-32 --> ide.icx.C
So, depending on which piece of code I work on , I use that workspace file to view those classes. This way I will not have problems referencing the
various packages and the workspace file will not be too huge. ANy downsides to this anyone can think of???
3. Is there any way tobuild an executable for all the files in the repository not just those which showup int he workspace? If I use any one of
the above two forms, I'll end up with 3 jar files instead of 1.?
Any other advice or solution will be greatly appreciated.
Thanks & Regards,
Veni.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic