[aerogear-dev] Details on the build process and dependencies

[Matthias Wessendorf]

IMO it does not hurt to list dependencies in a README.md file

of course, for java weenies, pom is the source of truth.

JS and iOS are different...

On Monday, November 5, 2012, Marko Strukelj wrote:

> I personally don't trust text files that claim to list library
> dependencies, as there's always a chance they are out-of-sync with build
> scripts. I just go straight to pom.xml or deploy instructions.
>
> just my 2c
>
> - marko
>
> On Mon, Nov 5, 2012 at 1:09 PM, Jay Balunas <jbalunas at redhat.com<javascript:_e({}, 'cvml', 'jbalunas at redhat.com');>
> > wrote:
>
>> Hi All,
>>
>> One thing we need to be sure to document is the details of our build
>> process and dependencies for each of libraries and repos.
>>
>> The question is whether to centralize these or keep them with each of the
>> respective repos?  Thoughts?
>>
>> If we the repos we should adopt of specific convention for the files and
>> the names.  i.e. BUILD.md, and/or DEPENDENCIES.md.
>>
>> Wdyt?
>>
>> Thanks,
>> Jay
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org <javascript:_e({}, 'cvml',
>> 'aerogear-dev at lists.jboss.org');>
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>

-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20121105/de084343/attachment.html