You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Wim Deblauwe <wi...@gmail.com> on 2005/11/09 17:49:21 UTC
[m2] building non-jar projects
Hi,
we are currently using Maven 1 to build c(++) projects and InstallShield
projects. I have written custom goals in my maven.xml to accomplish this.
Nobody would ever call jar:deploy on such a project but the custom defined
goals.
How would I do this in Maven 2. I want to avoid that the java compiler runs
and the jarring happens, but something of my own (a little piece of ant)
runs. For instance, a bit of ant that calls the c compiler or InstallShield
compiler and then a bit of ant that zips the result and puts it on the local
or remote repository.
How would I do this?
regards,
Wim
Re: [m2] building non-jar projects
Posted by Wim Deblauwe <wi...@gmail.com>.
Ah, yes, now I see it under "Specifying a New Packaging". It was a bit
confusing that the example also uses plexus. I was thinking that it was
something related to plexus and did not pay attention to it.
regards,
Wim
2005/11/10, Brett Porter <br...@gmail.com>:
>
> The required parts of the documentation are:
> - creating a lifecycle mapping for that packaging in components.xml of
> your plugin
> - specifying your plugin with <extensions>true</extensions>
>
> On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > Hi,
> >
> > ok, I found much info here:
> http://maven.apache.org/maven2/lifecycle.html
> >
> > but what I still miss, is how I define that when I run mvn install, it
> > should "see" that it is not a jar module, but for instance a msm
> > (InstallShield Merge Module). I know in the pom I should specify:
> >
> > <packaging>msm</packaging>
> >
> > But how would I tell Maven to use my plugin for such modules. If you
> could
> > add that information to the above documentation page, I would be very
> happy.
> >
> > regards,
> >
> > Wim
> >
> > 2005/11/10, Brett Porter <br...@gmail.com>:
> > >
> > > You would write a plugin that provides an alternative packaging (this
> > > allows you to redefine all of the phases). See the guide to the build
> > > lifecycle for details.
> > >
> > > Note that there is collaborative work under way to better support
> > > native compilation from Maven - see the recent threads on this list.
> > >
> > > - Brett
> > >
> > > On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > > > Hi,
> > > >
> > > > we are currently using Maven 1 to build c(++) projects and
> InstallShield
> > > > projects. I have written custom goals in my maven.xml to accomplish
> > > this.
> > > > Nobody would ever call jar:deploy on such a project but the custom
> > > defined
> > > > goals.
> > > >
> > > > How would I do this in Maven 2. I want to avoid that the java
> compiler
> > > runs
> > > > and the jarring happens, but something of my own (a little piece of
> ant)
> > > > runs. For instance, a bit of ant that calls the c compiler or
> > > InstallShield
> > > > compiler and then a bit of ant that zips the result and puts it on
> the
> > > local
> > > > or remote repository.
> > > >
> > > > How would I do this?
> > > >
> > > > regards,
> > > >
> > > > Wim
> > > >
> > > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] building non-jar projects
Posted by Brett Porter <br...@gmail.com>.
The required parts of the documentation are:
- creating a lifecycle mapping for that packaging in components.xml of
your plugin
- specifying your plugin with <extensions>true</extensions>
On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> Hi,
>
> ok, I found much info here: http://maven.apache.org/maven2/lifecycle.html
>
> but what I still miss, is how I define that when I run mvn install, it
> should "see" that it is not a jar module, but for instance a msm
> (InstallShield Merge Module). I know in the pom I should specify:
>
> <packaging>msm</packaging>
>
> But how would I tell Maven to use my plugin for such modules. If you could
> add that information to the above documentation page, I would be very happy.
>
> regards,
>
> Wim
>
> 2005/11/10, Brett Porter <br...@gmail.com>:
> >
> > You would write a plugin that provides an alternative packaging (this
> > allows you to redefine all of the phases). See the guide to the build
> > lifecycle for details.
> >
> > Note that there is collaborative work under way to better support
> > native compilation from Maven - see the recent threads on this list.
> >
> > - Brett
> >
> > On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > > Hi,
> > >
> > > we are currently using Maven 1 to build c(++) projects and InstallShield
> > > projects. I have written custom goals in my maven.xml to accomplish
> > this.
> > > Nobody would ever call jar:deploy on such a project but the custom
> > defined
> > > goals.
> > >
> > > How would I do this in Maven 2. I want to avoid that the java compiler
> > runs
> > > and the jarring happens, but something of my own (a little piece of ant)
> > > runs. For instance, a bit of ant that calls the c compiler or
> > InstallShield
> > > compiler and then a bit of ant that zips the result and puts it on the
> > local
> > > or remote repository.
> > >
> > > How would I do this?
> > >
> > > regards,
> > >
> > > Wim
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] building non-jar projects
Posted by Wim Deblauwe <wi...@gmail.com>.
Hi,
ok, I found much info here: http://maven.apache.org/maven2/lifecycle.html
but what I still miss, is how I define that when I run mvn install, it
should "see" that it is not a jar module, but for instance a msm
(InstallShield Merge Module). I know in the pom I should specify:
<packaging>msm</packaging>
But how would I tell Maven to use my plugin for such modules. If you could
add that information to the above documentation page, I would be very happy.
regards,
Wim
2005/11/10, Brett Porter <br...@gmail.com>:
>
> You would write a plugin that provides an alternative packaging (this
> allows you to redefine all of the phases). See the guide to the build
> lifecycle for details.
>
> Note that there is collaborative work under way to better support
> native compilation from Maven - see the recent threads on this list.
>
> - Brett
>
> On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> > Hi,
> >
> > we are currently using Maven 1 to build c(++) projects and InstallShield
> > projects. I have written custom goals in my maven.xml to accomplish
> this.
> > Nobody would ever call jar:deploy on such a project but the custom
> defined
> > goals.
> >
> > How would I do this in Maven 2. I want to avoid that the java compiler
> runs
> > and the jarring happens, but something of my own (a little piece of ant)
> > runs. For instance, a bit of ant that calls the c compiler or
> InstallShield
> > compiler and then a bit of ant that zips the result and puts it on the
> local
> > or remote repository.
> >
> > How would I do this?
> >
> > regards,
> >
> > Wim
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] building non-jar projects
Posted by Brett Porter <br...@gmail.com>.
You would write a plugin that provides an alternative packaging (this
allows you to redefine all of the phases). See the guide to the build
lifecycle for details.
Note that there is collaborative work under way to better support
native compilation from Maven - see the recent threads on this list.
- Brett
On 11/10/05, Wim Deblauwe <wi...@gmail.com> wrote:
> Hi,
>
> we are currently using Maven 1 to build c(++) projects and InstallShield
> projects. I have written custom goals in my maven.xml to accomplish this.
> Nobody would ever call jar:deploy on such a project but the custom defined
> goals.
>
> How would I do this in Maven 2. I want to avoid that the java compiler runs
> and the jarring happens, but something of my own (a little piece of ant)
> runs. For instance, a bit of ant that calls the c compiler or InstallShield
> compiler and then a bit of ant that zips the result and puts it on the local
> or remote repository.
>
> How would I do this?
>
> regards,
>
> Wim
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org