While reviewing summers' PR I've found myself doing that tedious work of fixing license headers again - what do y'all think part of our default tools (like maven-license-plugin) on an aerogear parent pom (which inherits from jboss parent pom, of course) Thoughts? -- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

While reviewing summers' PR I've found myself doing that tedious work of fixing license headers again - what do y'all think part of our default tools (like maven-license-plugin) on an aerogear parent pom (which inherits from jboss parent pom, of course) Thoughts?

On May 20, 2013, at 2:18 PM, Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: 100101001 Bruno - Any significance to saying +297 ? :P _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

To finish this task I'd like to create two repositories on our GitHub organization: - aerogear-parent[1] (contains the parent pom) - aerogear-misc[2] (contains license header templates + code formatting rules) Here follows a proper example[3] of the optimizations we can have by using this parent pom. Any objections?

Thanks! [1]:https://github.com/qmx/aerogear-parent [2]:https://github.com/qmx/aerogear-misc [3]:https://github.com/aerogear/aerogear-android/pull/76 -- qmx _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

+1 - abstractj On Jun 29, 2013, 8:15 AM, Matthias Wessendorf wrote: > Ha! > > On Sat, Jun 29, 2013 at 7:39 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >> To finish this task I'd like to create two repositories on our GitHub >> >>> organization: >> >> >>> - aerogear-parent[1] (contains the parent pom) >> >>> - aerogear-misc[2] (contains license header templates + code formatting >> >>> rules) >> >> >>> Here follows a proper example[3] of the optimizations we can have by >> >>> using this parent pom. >> >> >>> Any objections? > > Not at all. I like it. Gave some feedback/PRs on your repos > > >> >> >>> Thanks! >> >> >>> [1]:https://github.com/qmx/aerogear-parent >> >>> [2]:https://github.com/qmx/aerogear-misc >> >>> [3]:https://github.com/aerogear/aerogear-android/pull/76 >> >> >>> -- >> >>> qmx >> _______________________________________________ >> >>> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > > -- > Matthias Wessendorf > > blog: http://matthiaswessendorf.wordpress.com/ > >> sessions: http://www.slideshare.net/mwessendorf > twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

+1 On Jun 29, 2013, at 9:24 AM, Kris Borchers <kborcher(a)redhat.com&gt; wrote: +1 On Jun 29, 2013, at 7:11, Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: +1 - abstractj On Jun 29, 2013, 8:15 AM, Matthias Wessendorf wrote: Ha! On Sat, Jun 29, 2013 at 7:39 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: > To finish this task I'd like to create two repositories on our GitHub > organization: > > - aerogear-parent[1] (contains the parent pom) > - aerogear-misc[2] (contains license header templates + code formatting > rules) > > Here follows a proper example[3] of the optimizations we can have by > using this parent pom. > > Any objections? > Not at all. I like it. Gave some feedback/PRs on your repos > > Thanks! > > [1]:https://github.com/qmx/aerogear-parent > [2]:https://github.com/qmx/aerogear-misc > [3]:https://github.com/aerogear/aerogear-android/pull/76 > > -- > qmx > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

+1 On Jul 1, 2013, at 3:18 PM, Daniel Bevenius <daniel.bevenius(a)gmail.com&gt; wrote: > +1 > > > On 1 July 2013 14:13, Lucas Holmquist <lholmqui(a)redhat.com&gt; wrote: > +1 > > On Jun 29, 2013, at 9:24 AM, Kris Borchers <kborcher(a)redhat.com&gt; wrote: > >> +1 >> >> On Jun 29, 2013, at 7:11, Bruno Oliveira <bruno(a)abstractj.org&gt; wrote: >> >>> +1 >>> >>> - >>> abstractj >>> >>> On Jun 29, 2013, 8:15 AM, Matthias Wessendorf wrote: >>> >>>> Ha! >>>> >>>> On Sat, Jun 29, 2013 at 7:39 AM, Douglas Campos <qmx(a)qmx.me&gt; wrote: >>>> To finish this task I'd like to create two repositories on our GitHub >>>> organization: >>>> >>>> - aerogear-parent[1] (contains the parent pom) >>>> - aerogear-misc[2] (contains license header templates + code formatting >>>> rules) >>>> >>>> Here follows a proper example[3] of the optimizations we can have by >>>> using this parent pom. >>>> >>>> Any objections? >>>> >>>> Not at all. I like it. Gave some feedback/PRs on your repos >>>> >>>> >>>> >>>> Thanks! >>>> >>>> [1]:https://github.com/qmx/aerogear-parent >>>> [2]:https://github.com/qmx/aerogear-misc >>>> [3]:https://github.com/aerogear/aerogear-android/pull/76 >>>> >>>> -- >>>> qmx >>>> _______________________________________________ >>>> aerogear-dev mailing list >>>> aerogear-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >>>> >>>> >>>> >>>> -- >>>> Matthias Wessendorf >>>> >>>> blog: http://matthiaswessendorf.wordpress.com/ >>>> sessions: http://www.slideshare.net/mwessendorf >>>> twitter: http://twitter.com/mwessendorf >>> _______________________________________________ >>> aerogear-dev mailing list >>> aerogear-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/aerogear-dev >> _______________________________________________ >> aerogear-dev mailing list >> aerogear-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/aerogear-dev > > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev > > _______________________________________________ > aerogear-dev mailing list > aerogear-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/aerogear-dev _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev