Resolving java package dependencies?

Two thoughts: Address sounds like a common component that can be used in different deliverables and so should be available in some common or core library It may make sense for your components to talk to an Address interface, and the implementation can be provided separately (e.g. Provide an Address interface and an AddressImpl implementation). This will reduce the amount of binding between the core library and the library your developers will develop.

Thanks Brian, for the interface advice as well – DJC Aug 30 '10 at 21:34 Please call it DefaultAddress rather than AddressImpl. *Impl implies it is the one (and only) implementation, which makes the use of an interface, well... senseless. Default* states what it is, the default implementation.

– whiskeysierra Aug 30 '10 at 21:40.

In this case Address is a part of a library which deserves its own jar. If you create a class named Address in my. Contacts, my.

Appointments, and my. Location and you want to use all theses jar in a same application, you'll have a conflict for your Address class.

Thanks Colin, appreciate it – DJC Aug 30 '10 at 21:35.

I suggest you don't "Deliver" these jars separately. Java has very subtle versioning issues that you don't want to run into. Build everything together and package it into one or two jars and always deliver both jars, or build them together and deliver a subset of jars (but never combine new and old jars--don't just try to send a single jar as an update).

If you must build them separately be very aware that final constants are compiled in and not referenced--so if you change one and deliver a new jar, any references from an older jar will not be updated. Also method signatures that change will have strange, unpredictable results. It sounds like you want a developer interface as well--that may be a set of interfaces and classes that reside in a separate jar.

If you make that one jar well enough that you never have to rev it (and, of course, with no references to external constants) you can probably get away with not updating it which will keep your customer's extensions from getting crusty.

Thanks Bill for saving me some misery :) – DJC Aug 30 '10 at 22:55.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.