On Nov 11, 2014, at 11:16 PM, Ian Duffy wrote:
> I did not I will check them out. Does it matter for tooling?
No, using (say) GPL licensed or commercially licensed build tools is fine. The
only thing we don't want is really crazy tool licenses that place some kind of
claim on generated arti
not sure actually, i supposed there that a build time dependency is
something that might surprise a user and thus needs attention.
On Tue, Nov 11, 2014 at 11:16 PM, Ian Duffy wrote:
> Daan,
>
> I did not I will check them out. Does it matter for tooling?
>
> On 11 November 2014 20:39, Daan Ho
Daan,
I did not I will check them out. Does it matter for tooling?
On 11 November 2014 20:39, Daan Hoogland wrote:
> Ian, did you check the license categories for the dependencies? any Cat. X?
>
> On Tue, Nov 11, 2014 at 9:13 PM, Ian Duffy wrote:
> > It would be really interesting to see b
Ian, did you check the license categories for the dependencies? any Cat. X?
On Tue, Nov 11, 2014 at 9:13 PM, Ian Duffy wrote:
> It would be really interesting to see build tools like grunt[1] or gulp[2]
> being used around frontend work I've recently been working on a
> personal project[3] wi
It would be really interesting to see build tools like grunt[1] or gulp[2]
being used around frontend work I've recently been working on a
personal project[3] with gulp and integration with maven through
exec-maven-plugin and yeoman-maven-plugin[4]
It would allow us to pull external dependenci
> I encounter java script with lots of superfluent whitespace and irregular
indentation.
Intellij's code reformat feature is awesome for fixing this. You'll
probably annoy folk with such large whitespace changes(I know I did).
> Do we have coding standards for that?
As far as I'm aware we do not
H,
I encounter java script with lots of superfluent whitespace and
irregular indentation. Do we have coding standards for that? And tools
to enforce those?
--
Daan
