I would write a wrapper pom for installing your ear and use the build-helper
plugin to attach the ear as an artifact to that wrapper pom.xml

On Wed, Mar 5, 2008 at 2:11 AM, Wayne Fay <[EMAIL PROTECTED]> wrote:

> As far as I know, you can't.
>
> Most people would simply write a shell script to deal with repeatedly
> installing wars into a repo with different versions.
>
> Wayne
>
> On 3/4/08, gotama <[EMAIL PROTECTED]> wrote:
> >
> >
> > How can I do:
> >
> > > mvn install:install-file
> >
> > not from the command line, but configured in a POM?
> >
> > I'd like to automate this as the EAR I am installing to the repo will
> change
> > frequently, but is not built w/ Maven. Until the module is Mavenized, I
> > simply want a module POM to copy an EAR from a directory, say
> > c:\deploy\version_3.0.1\app.EAR, version it using the parameter
> specified in
> > the POM and install it in the local/company repository. Once the module
> has
> > been Mavenized, I can tear this out and the parent POM will not know
> that
> > the module is now building with Maven. I basically want to create a
> place
> > holder POM for various modules which simply copies EARs from a location
> and
> > trick the parent POM into thinking its a regular Maven module. I don't
> want
> > to manually exec this on the command line because there are 15 EARs like
> > this and 40 developers would have to do the same thing. I just want to
> > automate this w/ "mvn" and be done.
> >
> > Thanks.
> >
> >
> > --
> > View this message in context:
> http://www.nabble.com/install%3Ainstall-file-via-POM-file-tp15841398s177p15841398.html
> > Sent from the Maven - Users mailing list archive at Nabble.com.
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>

Reply via email to