Jason van Zyl wrote: > > Maybe we could specify the default/main target in the project descriptor? > Or maybe we give the targets names and than hook onto a target by name: OK, now we have a concrete proposal. However, consider for a moment, jakarta-commons. One cvs module, with several independent projects. Not just targets, but separate build files, non-overlapping sets of source files, the works. How about the container being a "module", with one or more nested projects? If we go that way, should we go for consistency and require single project modules (which is actually the norm) to be enclosed in modules, or do we make that implicit? - Sam Ruby --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
- [gump] normalizing project descriptors Jason van Zyl
- Re: [gump] normalizing project descriptors Sam Ruby
- Re: [gump] normalizing project descriptors Jason van Zyl
- Re: [gump] normalizing project descriptors Sam Ruby
- Re: [gump] normalizing project descriptors Jason van Zyl
- Re: [gump] normalizing project descriptors Sam Ruby
- Re: [gump] normalizing project descriptors Jason van Zyl
- Re: [gump] normalizing project descriptors Geir Magnusson Jr.
- RE: [gump] normalizing project descriptors Morrison, John
- Re: [gump] normalizing project descriptors Jason van Zyl
- Re: [gump] normalizing project descriptors Geir Magnusson Jr.
- Re: [gump] normalizing project descriptors Geir Magnusson Jr.
- Re: [gump] normalizing project descriptors Sam Ruby
- RE: [gump] normalizing project descriptors Morrison, John
- RE: [gump] normalizing project descriptors Morrison, John
- Re: [gump] normalizing project descriptors Shane_Curcuru
