You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Kevin Burton <bu...@spinn3r.com> on 2015/08/02 22:40:00 UTC

Running jdeb plugin by itself .. not attached to the package lifecycle.

The Maven jdeb plugin (for building debian packages) recommends you set it
up like:

<executions>
          <execution>
            <phase>package</phase>
            <goals>
              <goal>jdeb</goal>
            </goals>

… but this means that if I do an

mvn install

that packages are built and installed into the maven repo.

1. this doesn’t make a ton of sense.  No one is going to install our .debs
from a maven repo.

2. it significantly slows down the build.  I imagine our build could be
from 30-200% faster if I could remove this.  It’s slowing down our
continuous integration system.

What I’d like to do is run it like

mvn jdeb:jdeb

… but it doesn’t seem to have any goals associated.

Any thoughts?

-- 

Founder/CEO Spinn3r.com
Location: *San Francisco, CA*
blog: http://burtonator.wordpress.com
… or check out my Google+ profile
<https://plus.google.com/102718274791889610666/posts>

Re: Running jdeb plugin by itself .. not attached to the package lifecycle.

Posted by João Rodrigues <jl...@gmail.com>.
BTW, you're not installing your deb into your maven repo. When you do mvn
*install*, you're instructing maven to execute all phases up to install
phase. Probably jdeb default phase is *package*, if you run mvn
*package *-Pbuilddeb
it will create your deb file. More about lifecycles (check Lifecycle
Reference):
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html

On Thu, Aug 6, 2015 at 10:29 AM João Rodrigues <jl...@gmail.com>
wrote:

> I would recommend using maven profiles. Just add to your pom:
>
>     <profiles>
>         <profile>
>             <id>*builddeb*</id>
>             <build>
>                 <plugins>
>                     <!-- MOVE your jdeb plugin configuration -->
>                </plugins>
>             </build>
>         </profile>
>     </profiles>
>
> If you run mvn install, you'll notice your jdeb won't be executed. If you
> run mvn install -P*builddeb* it will add your jdeb execution to maven
> lifecycle.
> More about profiles:
> http://maven.apache.org/guides/introduction/introduction-to-profiles.html
>
>
>
> On Thu, Aug 6, 2015 at 7:46 AM Baptiste Mathus <ml...@batmat.net> wrote:
>
>> IMO disabling it for perf reason for snapshot might be acceptable, but in
>> your place I would really create and deploy the .deb at least for the
>> release so that you have a central place where all your released binaries
>> can be found.
>>
>> Cheers
>> Le 3 août 2015 2:09 AM, "Benson Margulies" <bi...@gmail.com> a
>> écrit :
>>
>> > <attach>false</attach>
>> >
>> > On Sun, Aug 2, 2015 at 4:40 PM, Kevin Burton <bu...@spinn3r.com>
>> wrote:
>> > > The Maven jdeb plugin (for building debian packages) recommends you
>> set
>> > it
>> > > up like:
>> > >
>> > > <executions>
>> > >           <execution>
>> > >             <phase>package</phase>
>> > >             <goals>
>> > >               <goal>jdeb</goal>
>> > >             </goals>
>> > >
>> > > … but this means that if I do an
>> > >
>> > > mvn install
>> > >
>> > > that packages are built and installed into the maven repo.
>> > >
>> > > 1. this doesn’t make a ton of sense.  No one is going to install our
>> > .debs
>> > > from a maven repo.
>> > >
>> > > 2. it significantly slows down the build.  I imagine our build could
>> be
>> > > from 30-200% faster if I could remove this.  It’s slowing down our
>> > > continuous integration system.
>> > >
>> > > What I’d like to do is run it like
>> > >
>> > > mvn jdeb:jdeb
>> > >
>> > > … but it doesn’t seem to have any goals associated.
>> > >
>> > > Any thoughts?
>> > >
>> > > --
>> > >
>> > > Founder/CEO Spinn3r.com
>> > > Location: *San Francisco, CA*
>> > > blog: http://burtonator.wordpress.com
>> > > … or check out my Google+ profile
>> > > <https://plus.google.com/102718274791889610666/posts>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
>

Re: Running jdeb plugin by itself .. not attached to the package lifecycle.

Posted by João Rodrigues <jl...@gmail.com>.
I would recommend using maven profiles. Just add to your pom:

    <profiles>
        <profile>
            <id>*builddeb*</id>
            <build>
                <plugins>
                    <!-- MOVE your jdeb plugin configuration -->
               </plugins>
            </build>
        </profile>
    </profiles>

If you run mvn install, you'll notice your jdeb won't be executed. If you
run mvn install -P*builddeb* it will add your jdeb execution to maven
lifecycle.
More about profiles:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html



On Thu, Aug 6, 2015 at 7:46 AM Baptiste Mathus <ml...@batmat.net> wrote:

> IMO disabling it for perf reason for snapshot might be acceptable, but in
> your place I would really create and deploy the .deb at least for the
> release so that you have a central place where all your released binaries
> can be found.
>
> Cheers
> Le 3 août 2015 2:09 AM, "Benson Margulies" <bi...@gmail.com> a
> écrit :
>
> > <attach>false</attach>
> >
> > On Sun, Aug 2, 2015 at 4:40 PM, Kevin Burton <bu...@spinn3r.com> wrote:
> > > The Maven jdeb plugin (for building debian packages) recommends you set
> > it
> > > up like:
> > >
> > > <executions>
> > >           <execution>
> > >             <phase>package</phase>
> > >             <goals>
> > >               <goal>jdeb</goal>
> > >             </goals>
> > >
> > > … but this means that if I do an
> > >
> > > mvn install
> > >
> > > that packages are built and installed into the maven repo.
> > >
> > > 1. this doesn’t make a ton of sense.  No one is going to install our
> > .debs
> > > from a maven repo.
> > >
> > > 2. it significantly slows down the build.  I imagine our build could be
> > > from 30-200% faster if I could remove this.  It’s slowing down our
> > > continuous integration system.
> > >
> > > What I’d like to do is run it like
> > >
> > > mvn jdeb:jdeb
> > >
> > > … but it doesn’t seem to have any goals associated.
> > >
> > > Any thoughts?
> > >
> > > --
> > >
> > > Founder/CEO Spinn3r.com
> > > Location: *San Francisco, CA*
> > > blog: http://burtonator.wordpress.com
> > > … or check out my Google+ profile
> > > <https://plus.google.com/102718274791889610666/posts>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>

Re: Running jdeb plugin by itself .. not attached to the package lifecycle.

Posted by Baptiste Mathus <ml...@batmat.net>.
IMO disabling it for perf reason for snapshot might be acceptable, but in
your place I would really create and deploy the .deb at least for the
release so that you have a central place where all your released binaries
can be found.

Cheers
Le 3 août 2015 2:09 AM, "Benson Margulies" <bi...@gmail.com> a écrit :

> <attach>false</attach>
>
> On Sun, Aug 2, 2015 at 4:40 PM, Kevin Burton <bu...@spinn3r.com> wrote:
> > The Maven jdeb plugin (for building debian packages) recommends you set
> it
> > up like:
> >
> > <executions>
> >           <execution>
> >             <phase>package</phase>
> >             <goals>
> >               <goal>jdeb</goal>
> >             </goals>
> >
> > … but this means that if I do an
> >
> > mvn install
> >
> > that packages are built and installed into the maven repo.
> >
> > 1. this doesn’t make a ton of sense.  No one is going to install our
> .debs
> > from a maven repo.
> >
> > 2. it significantly slows down the build.  I imagine our build could be
> > from 30-200% faster if I could remove this.  It’s slowing down our
> > continuous integration system.
> >
> > What I’d like to do is run it like
> >
> > mvn jdeb:jdeb
> >
> > … but it doesn’t seem to have any goals associated.
> >
> > Any thoughts?
> >
> > --
> >
> > Founder/CEO Spinn3r.com
> > Location: *San Francisco, CA*
> > blog: http://burtonator.wordpress.com
> > … or check out my Google+ profile
> > <https://plus.google.com/102718274791889610666/posts>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Re: Running jdeb plugin by itself .. not attached to the package lifecycle.

Posted by Benson Margulies <bi...@gmail.com>.
<attach>false</attach>

On Sun, Aug 2, 2015 at 4:40 PM, Kevin Burton <bu...@spinn3r.com> wrote:
> The Maven jdeb plugin (for building debian packages) recommends you set it
> up like:
>
> <executions>
>           <execution>
>             <phase>package</phase>
>             <goals>
>               <goal>jdeb</goal>
>             </goals>
>
> … but this means that if I do an
>
> mvn install
>
> that packages are built and installed into the maven repo.
>
> 1. this doesn’t make a ton of sense.  No one is going to install our .debs
> from a maven repo.
>
> 2. it significantly slows down the build.  I imagine our build could be
> from 30-200% faster if I could remove this.  It’s slowing down our
> continuous integration system.
>
> What I’d like to do is run it like
>
> mvn jdeb:jdeb
>
> … but it doesn’t seem to have any goals associated.
>
> Any thoughts?
>
> --
>
> Founder/CEO Spinn3r.com
> Location: *San Francisco, CA*
> blog: http://burtonator.wordpress.com
> … or check out my Google+ profile
> <https://plus.google.com/102718274791889610666/posts>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org