apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pramod Immaneni <pra...@datatorrent.com>
Subject Re: malhar dependency in apex-app-archetype
Date Thu, 18 Feb 2016 01:27:34 GMT
Comments sounds good.

On Wed, Feb 17, 2016 at 5:12 PM, David Yan <david@datatorrent.com> wrote:

> I think it's a good idea.  We can add comments to the generated pom to
> explain to the user that he/she may want to add malhar-library and/or other
> libraries in malhar like contrib or kafka, depending on the use case,
> instead of adding malhar-library dependency by default for the user.
>
> David
>
> On Wed, Feb 17, 2016 at 4:59 PM, Pramod Immaneni <pramod@datatorrent.com>
> wrote:
>
> > Currently we include a dependency to malhar-library in apps generated
> using
> > apex-app-archetype. This results in a soft dependency from apex to
> malhar,
> > namely a previously released version of malhar, which is reverse of the
> > build dependency.
> >
> > Secondly we only include malhar-library and not malhar-contrib even
> though
> > it is a component of malhar possibly because the user would still need to
> > include the transitive dependencies based on the application. This again
> > makes the out-of-box experience a little less consistent.
> >
> > How about not including the malhar-library dependency in the generated
> > default pom.xml.
> >
> > Thanks
> >
>

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