ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitriy Setrakyan <dsetrak...@apache.org>
Subject Re: maven builds
Date Fri, 13 Mar 2015 01:46:50 GMT
On Thu, Mar 12, 2015 at 6:01 PM, Konstantin Boudnik <cos@apache.org> wrote:

> Ah, I see. Yes, I think a better way to go from a pure Maven perspective
> is to
> bind this sort of generation to assembly step perhaps. Cause 'package' is
> expected to produce jar files. What you do with them afterwards - isn't a
> 'package' business, IMO.
>
>
Agree.


>
> On Thu, Mar 12, 2015 at 05:36PM, Dmitriy Setrakyan wrote:
> > It is OK for "mvn package" to generate JAR files. However, in case of
> > Ignite, it also generates the release binary ZIP archive which actually
> > requires that you are in the root of a valid Ignite GIT tree. I would
> > rather have the release ZIP file generated with an additional option
> added
> > to the "mvn" command.
> >
> > D.
> >
> > On Thu, Mar 12, 2015 at 5:23 PM, Konstantin Boudnik <cos@apache.org>
> wrote:
> >
> > > I think package is by default bound to the binary generation, so it
> > > would'be
> > > pretty messy if you'll try to break this dependency.
> > >
> > > Cos
> > >
> > > On Thu, Mar 12, 2015 at 04:38PM, Dmitriy Setrakyan wrote:
> > > > Igniters,
> > > >
> > > > Based on the latest feedback from the mentors, I think we need to
> make
> > > sure
> > > > that standard "mvn clean package -DskipTests" command can run
> > > successfully
> > > > by default. This means that that this command should not generate a
> > > binary
> > > > build by default.
> > > >
> > > > It is OK to add extra parameters when doing the binary build though.
> > > >
> > > > How hard would it be to implement this change?
> > > >
> > > > D.
> > >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message