Jason van Zyl wrote: > > I'll see if I can make it work, but the idea is that the build will be > transparent so hopefully people won't need to look in the binary > installation directory. Once you have accepted a directory structure, the next step is to recognize that directories may have internal structure, and what you need is a descriptor telling you where you can find what you need. Furthermore, that directory structure really should match the layout of the individual projects released distributions. If you stop for a moment and think about it, you will figure out where I am going with this. I already have such project descriptors... ;-) Of course, some people might want to mix and match between released versions of things and stuff they build for themselves, so these descriptors need to be organized into profiles and referenced by a workspace... - Sam Ruby
- Version numbers on release JARs Jason van Zyl
- Re: Version numbers on release JARs Vincent Massol
- Re: Version numbers on release JARs Vincent Massol
- Re: Version numbers on release JARs Sam Ruby
- Re: Version numbers on release JARs Jason van Zyl
- Re: Version numbers on release JARs Geir Magnusson Jr.
- Re: Version numbers on release JARs Craig R. McClanahan
- Re: Version numbers on release JARs Sam Ruby
- Re: Version numbers on release JARs Jason van Zyl
- Re: Version numbers on release JARs Jason van Zyl
- Re: Version numbers on release JARs Sam Ruby
- RE: Version numbers on release JARs Morrison, John
- Re: Version numbers on release JARs Geir Magnusson Jr.
- RE: Version numbers on release JARs Morrison, John
- Re: Version numbers on release JARs Geir Magnusson Jr.
- RE: Version numbers on release JARs Morrison, John
- Re: Version numbers on release JARs Geir Magnusson Jr.
- RE: Version numbers on release JARs Morrison, John
