> -----Original Message----- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: dimanche 2 octobre 2005 11:04 > To: 'Maven Developers List' > Subject: RE: [jira] Closed: (MPPLUGIN-3) Resolve project.xml inheritance > when installing plugin > > Hi Vincent, > > It's right, it's why I changed it some hours after : > > === > using the artifact plugin code, the generated pom doesn't have hardcoded > paths. > but this plugin will now need maven 1.1 (needed by the artifact plugin). > the last thing to do is to use override properties when they are > defined... > === > > Now, the POM is really rewritten as it's done when we deploy a pom on a > repository. > What I did, worked also because I asked to the pom object to give me (at > runtime) its content in XML. The problem was that ALL > variables were resolved and we don't need to have a hardcoded path for the > basedir for example. > The only problem to fix is to manage maven.override properties...
Ok thanks Arnaud and sorry for not noticing the subsequent JIRA post, I somehow missed it. Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
