organizing larger application code / modules

[zenner]

I've gotten proficient with the Java language.. (solo work; coming from a C C++ background)

now I want to understand how a team of programmers would work on a large application.. how is an app divided into modules that can be joined... like DDL libraries in C ...

but so that each programmers section will be built (compiled successfully).. to allow that section to be tested and then joined..

I've tried to search for this.. but since I don't know the Java terms that would be used, I can't find a discussion or tutorial
.. what are the submodules called ?? libraries ?? class libraries??

[Eranga]

Are you talking about source code handling applications, may be like a subversion?

[zenner]

no, I'm sorry if I'm not clear... I'm not talking about source code control, nor version control..


in a large C or C++ project, one person works on the GUI display, another on the filesystem/database , another person may write a set of CLASSES that are to be shared by the other two..

these are compiled (in C) into a library (such as a DLL)

that both can include in their compilations to gain the reuseabilty of those libraries..


how do you do this in Java ??

thanks

[Eranga]

Ah, I got the point. In that case what we can do is, create jar files and use them in other application as a library.

Say, one person develop GUI, and other person develop all other functionality related to the application. What we do is, first code the GUI classes and create a jar file. Then it's given to the second person. He added that jar file as a library in his application and import required class and do the rest.

I hope it's clear to you now.

[zenner]

thanks so much...

i'm off researching jars ... will hae one soon..

thanks
s

[Eranga]

Do to the suns' official web site. You find lots of details there about jars.

By the way, regarding the SubVersions, I think you don't know much about them. SubVersions are like VSS, which can be used to handle source codes, in large products, in different levels(different developers). CollabNetSubversion is the one I used. It's a grate tool. No need to use jar files and so on, as I said. Simply you can merge others projects with your one and working on it. Not only that, there are lots of functionality you can have.

Search on the Google, you may find lots of such SubVersions.