The problem is that there is already a parent pom defined for say, app 1 listed below. App 2 lives off in its own structure with no parent defined (and can't use app 1's parent pom as it would break config/deploy related items).
Is there a way I can just have a "config" project (sort of like "<packaging>config<packaing>") that would place properties into the local repository for use in other, non-related projects? -----Original Message----- From: Allen, Daniel [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 5:48 PM To: Maven Users List Subject: RE: sharing properties between modules If you're talking about just properties and not any code or classes, then perhaps you could just use variables and filtering in the configuration files, and then have a profile that's used in both builds? I would suggest perhaps a sort of token parent project whose POM doesn't really contain anything except for a <profile> element that defines these shared values, and then they will be available for <resource> elements in your projects' POMs. Of course, I'm still new at this, so I'd say get a second opinion on that. ~Dan Allen -----Original Message----- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Friday, March 07, 2008 5:47 PM To: Maven Users List Subject: RE: sharing properties between modules So we have app1 and it has a property like, db.username. App2 needs to connect to the same database, but doesn't share a parent. For example, app1 loads data into a db, app2 displays said data via a website. There is no common/shared code other than the data access layer. How would you do a "grand parent" type dependency? -- This message may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived by any transmission to an unintended recipient. If you are not an intended recipient, please notify the sender and delete this message immediately. Any views expressed in this message are those of the sender, not those of any entity within the KBC Financial Products group of companies (together referred to as "KBC FP"). This message does not create any obligation, contractual or otherwise, on the part of KBC FP. It is not an offer (or solicitation of an offer) of, or a recommendation to buy or sell, any financial product. Any prices or other values included in this message are indicative only, and do not necessarily represent current market prices, prices at which KBC FP would enter into a transaction, or prices at which similar transactions may be carried on KBC FP's own books. The information contained in this message is provided "as is", without representations or warranties, express or implied, of any kind. Past performance is not indicative of future returns. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
