Java

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Shared modules and versioning

    0 answers - 706 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    So we have a module that is shared across multiple deployable units.
    It's imperative that each deployable unit uses the SAME version of this
    dependency.
    If these deployable units are in their WN project structure, how do you
    uniformly enforce they use the same version without letting each
    deployable unit have it's very own dependency listing. We've tried
    making the version a property in our current parent project, but this
    doesn't feel like it's the correct place to put them (we're slowly
    becoming more and more modular - and realizing there's no true parent to
    all projects).
    How have people solved this in scenario?

Re: Shared modules and versioning


max 4000 letters.
Your nickname that display:
In order to stop the spam: 4 + 3 =
QUESTION ON "Java"

EMSDN.COM