Yes, this is what I've done, but now I find I need another POM. Here's what I have
A pom project called PARENT1 it contains developer and distManagement stuff. A jar project called PMD that contains the PMD config file. It inherits from PARENT1 A pom project called PARENT2 that inherits from PARENT1 and uses PMD. Lots of jar projects that inherit from PARENT2. This seems too complex. If I could just roll the PMD config file (and others as needed) into PARENT1 than two projects could be eliminated. I'm also considering putting the configuration file in a well known location (http://mystuff/pmd.xml) the same way we do for JPEGs and getting on with life. Any thoughts? Thanks, Christopher Helck -----Original Message----- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Thursday, May 31, 2007 11:39 AM To: Maven Users List Subject: Re: Is it possible for a pom project to build a jar file? On 5/31/07, Chris Helck <[EMAIL PROTECTED]> wrote: > I have a parent pom which depends on a simple jar file containing > configuration files (PMD config). I'm wondering if it is possible to > combine these into one project? > > So I need <packaging>pom</packaging> and to somehow cause a jar file > to be build and deployed. How can I do this? Is it wise? I would put the PMD config in a separate module that builds a jar. You may have other build-related files like Checkstyle config that could all go in one myproject-build artifact. -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ********************************************************************** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the "Information") is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates ("ICAP") or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. ********************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
