[Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

Hey

We had to issue a release because of a "bug" in Android, I'm wanting to
delete the entire build script directory unless someone wants to take on
the task of making sure that works.  Since ant jar works, I don't see the
reason for having this directory, and it seems to cause more problems than
it's actually worth.

Any thoughts?

Joe

Re: [Android] Getting rid of the bin directory

[Shazron <sh...@gmail.com>]

Fil,
You can assign iOS to me and/or create a task (with sub-tasks?) in jira

On Fri, Apr 13, 2012 at 8:05 AM, Joe Bowser <bo...@gmail.com> wrote:
> Awesome. I'm fine with that.
> On Apr 13, 2012 7:57 AM, "Filip Maj" <fi...@adobe.com> wrote:
>
>> You can assign them to me
>>
>> On 4/13/12 7:48 AM, "Joe Bowser" <bo...@gmail.com> wrote:
>>
>> >Except it did break. It broke in 1.6.0 due to neglect, and was most likely
>> >broken in 1.5 as well.
>> >
>> >I personally despise the build tools, since there seems to be no good
>> >happy
>> >medium for them.  They either totally get neglected or they attract so
>> >much
>> >attention when they're written in the flavor of the week that people
>> >bikeshed the hell out of them.
>> >
>> >But it sounds like the majority want to keep it.  Who do I assign build
>> >tool ticket to in this case? If people really care about them, who wants
>> >to
>> >do the work?
>> >On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:
>> >
>> >> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
>> >>
>> >> > We're trying to figure out what the command line tooling is gonna look
>> >> > like ...
>> >> >
>> >> > Until that decision is made I don't think we should touch the scripts.
>> >> >
>> >>
>> >> +1 Ain't broke, don't fix it.
>> >>
>> >> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
>> >> make a "decision" on command line tooling.  I'm figuring that we'll be
>> >> doing one or two CLI's to "throw away" [1] before figuring out what
>> >>works.
>> >> (and so, the sooner we start building the throw aways, the better).
>> >>
>> >> And especially: I don't want to remove it in 1.7 only to have to add it
>> >> back in 1.8.
>> >>
>> >> [1]
>> >>
>> >>
>> http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
>> >>
>> >> --
>> >> Patrick Mueller
>> >> http://muellerware.org
>> >>
>>
>>

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

Awesome. I'm fine with that.
On Apr 13, 2012 7:57 AM, "Filip Maj" <fi...@adobe.com> wrote:

> You can assign them to me
>
> On 4/13/12 7:48 AM, "Joe Bowser" <bo...@gmail.com> wrote:
>
> >Except it did break. It broke in 1.6.0 due to neglect, and was most likely
> >broken in 1.5 as well.
> >
> >I personally despise the build tools, since there seems to be no good
> >happy
> >medium for them.  They either totally get neglected or they attract so
> >much
> >attention when they're written in the flavor of the week that people
> >bikeshed the hell out of them.
> >
> >But it sounds like the majority want to keep it.  Who do I assign build
> >tool ticket to in this case? If people really care about them, who wants
> >to
> >do the work?
> >On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:
> >
> >> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
> >>
> >> > We're trying to figure out what the command line tooling is gonna look
> >> > like ...
> >> >
> >> > Until that decision is made I don't think we should touch the scripts.
> >> >
> >>
> >> +1 Ain't broke, don't fix it.
> >>
> >> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
> >> make a "decision" on command line tooling.  I'm figuring that we'll be
> >> doing one or two CLI's to "throw away" [1] before figuring out what
> >>works.
> >> (and so, the sooner we start building the throw aways, the better).
> >>
> >> And especially: I don't want to remove it in 1.7 only to have to add it
> >> back in 1.8.
> >>
> >> [1]
> >>
> >>
> http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
> >>
> >> --
> >> Patrick Mueller
> >> http://muellerware.org
> >>
>
>

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

We should run bin/create which does run ant/jar.  I think we should have a
QA step to make sure this script works and not leave everything to
automation.

On Fri, Apr 13, 2012 at 1:43 PM, Simon MacDonald
<si...@gmail.com>wrote:

> I just updated the build.xml so the version in that file is updated
> automatically. For anyone who cares this is how you prepare to tag
> cordova-android.
>
> 1) edit the VERSION file with the new version number.
> 2) Run "ant jar"
> 3) Create a new commit adding the files:
>
> VERSION
> bin/templates/project/cordova/templates/project/assets/www/index.html
> framework/assets/www/index.html
> framework/src/org/apache/cordova/Device.java
>
> 4) tag the new version
>
> git tag -a {version} -m '{version}'
>
> 5) Push the commit and tag
>
> git push cordova master
> git push --tags cordova master
>
> Hmmm...I should probably write a script for this but instead I'm off
> to take my family to supper.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
>
> On Fri, Apr 13, 2012 at 4:19 PM, Joe Bowser <bo...@gmail.com> wrote:
> > OK, saw that change.  I updated index.html, since we weren't adding the
> .js
> > at the end for some unknown reason.  I also updated the checklist on the
> > wiki so we run the bin/create script instead of ant.  If we're following
> > that, we should catch stupid mistakes such as this.
> >
> > Also, who is not in a bad mood?
> >
> > On Fri, Apr 13, 2012 at 12:42 PM, Simon MacDonald <
> simon.macdonald@gmail.com
> >> wrote:
> >
> >> I'm about to push up a change to the android "bin/create" script. That
> >> script calls "bin/templates/project/cordova/create" which in turn
> >> expects the files:
> >>
> >>    bin/templates/project/cordova/templates/project/res/xml/cordova.xml
> >>    bin/templates/project/cordova/templates/project/res/xml/plugins.xml
> >>
> >> to be hanging around. This is what caused the bug in 1.6.0 as they
> >> were not up to date. Since I'm a firm believer that source code
> >> control should only have one copy of any given file I've modified the
> >> scripts so they go get cordova.xml and plugins.xml from their
> >> canonical locations in "framework/res/xml".
> >>
> >> I think the benefits are obvious.
> >>
> >> Simon Mac Donald
> >> http://hi.im/simonmacdonald
> >>
> >> P.S. Yes, I am in a bad mood.
> >>
> >> On Fri, Apr 13, 2012 at 3:26 PM, Joe Bowser <bo...@gmail.com> wrote:
> >> > OK, It's clear we're not deleting the directory, and we have people
> who
> >> > care about this.  I'm going to be bumping up priority on the build
> >> scripts,
> >> > since they've proven to be higher.  That's pretty much what I wanted
> out
> >> of
> >> > this thread.
> >> >
> >> > On Fri, Apr 13, 2012 at 10:19 AM, Brian LeRoux <b...@brian.io> wrote:
> >> >
> >> >> > Now, an XML file in these scripts have caused 1.6.1 to exist, which
> >> has
> >> >> now
> >> >> > been extended to Monday,
> >> >>
> >> >> Thats ok. Bugs manifest. A point release, while a pain in the ass,
> >> >> isn't the end of the world and a part of doing things right by our
> >> >> users.
> >> >>
> >> >>
> >> >> > and have thrown the release schedule out of whack
> >> >>
> >> >> I do not think it has to.
> >> >>
> >> >>
> >> >> > such that it looks like I'll have to delay CordovaWebView to 1.8
> >> because
> >> >> it
> >> >> > probably won't be ready by the end of the month.
> >> >>
> >> >> Thats ok too. Lets work towards it and get it done when its ready to
> >> >> ship. Let go of the attachment to a particular date and focus that
> >> >> quiet rage on the code you want rather than a particular date.
> >> >>
> >> >>
> >> >> > I don't think moving this into ant is a good idea,
> >> >>
> >> >> Me either. But wanted to know how you'd approach it. Also: I take
> >> >> exception to your assertion that Bash is, or ever has been, a flavor
> >> >> of the month. ;) (And ya I remember the Ruby, then jRuby, then
> Python,
> >> >> and then Node attempts.)
> >> >>
> >> >>
> >> >> > and these helper scripts belong in some tooling repository separate
> >> from
> >> >> the Cordova project.
> >> >>
> >> >> I disagree but only b/c ppl still use Cordova projects stand alone
> >> >> instead of simultaneously for all platforms. View this a stepping
> >> >> stone to a future where that master script finally comes to fruition.
> >> >>
> >>
>

Re: [Android] Getting rid of the bin directory

[Simon MacDonald <si...@gmail.com>]

I just updated the build.xml so the version in that file is updated
automatically. For anyone who cares this is how you prepare to tag
cordova-android.

1) edit the VERSION file with the new version number.
2) Run "ant jar"
3) Create a new commit adding the files:

VERSION
bin/templates/project/cordova/templates/project/assets/www/index.html
framework/assets/www/index.html
framework/src/org/apache/cordova/Device.java

4) tag the new version

git tag -a {version} -m '{version}'

5) Push the commit and tag

git push cordova master
git push --tags cordova master

Hmmm...I should probably write a script for this but instead I'm off
to take my family to supper.

Simon Mac Donald
http://hi.im/simonmacdonald



On Fri, Apr 13, 2012 at 4:19 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, saw that change.  I updated index.html, since we weren't adding the .js
> at the end for some unknown reason.  I also updated the checklist on the
> wiki so we run the bin/create script instead of ant.  If we're following
> that, we should catch stupid mistakes such as this.
>
> Also, who is not in a bad mood?
>
> On Fri, Apr 13, 2012 at 12:42 PM, Simon MacDonald <simon.macdonald@gmail.com
>> wrote:
>
>> I'm about to push up a change to the android "bin/create" script. That
>> script calls "bin/templates/project/cordova/create" which in turn
>> expects the files:
>>
>>    bin/templates/project/cordova/templates/project/res/xml/cordova.xml
>>    bin/templates/project/cordova/templates/project/res/xml/plugins.xml
>>
>> to be hanging around. This is what caused the bug in 1.6.0 as they
>> were not up to date. Since I'm a firm believer that source code
>> control should only have one copy of any given file I've modified the
>> scripts so they go get cordova.xml and plugins.xml from their
>> canonical locations in "framework/res/xml".
>>
>> I think the benefits are obvious.
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>> P.S. Yes, I am in a bad mood.
>>
>> On Fri, Apr 13, 2012 at 3:26 PM, Joe Bowser <bo...@gmail.com> wrote:
>> > OK, It's clear we're not deleting the directory, and we have people who
>> > care about this.  I'm going to be bumping up priority on the build
>> scripts,
>> > since they've proven to be higher.  That's pretty much what I wanted out
>> of
>> > this thread.
>> >
>> > On Fri, Apr 13, 2012 at 10:19 AM, Brian LeRoux <b...@brian.io> wrote:
>> >
>> >> > Now, an XML file in these scripts have caused 1.6.1 to exist, which
>> has
>> >> now
>> >> > been extended to Monday,
>> >>
>> >> Thats ok. Bugs manifest. A point release, while a pain in the ass,
>> >> isn't the end of the world and a part of doing things right by our
>> >> users.
>> >>
>> >>
>> >> > and have thrown the release schedule out of whack
>> >>
>> >> I do not think it has to.
>> >>
>> >>
>> >> > such that it looks like I'll have to delay CordovaWebView to 1.8
>> because
>> >> it
>> >> > probably won't be ready by the end of the month.
>> >>
>> >> Thats ok too. Lets work towards it and get it done when its ready to
>> >> ship. Let go of the attachment to a particular date and focus that
>> >> quiet rage on the code you want rather than a particular date.
>> >>
>> >>
>> >> > I don't think moving this into ant is a good idea,
>> >>
>> >> Me either. But wanted to know how you'd approach it. Also: I take
>> >> exception to your assertion that Bash is, or ever has been, a flavor
>> >> of the month. ;) (And ya I remember the Ruby, then jRuby, then Python,
>> >> and then Node attempts.)
>> >>
>> >>
>> >> > and these helper scripts belong in some tooling repository separate
>> from
>> >> the Cordova project.
>> >>
>> >> I disagree but only b/c ppl still use Cordova projects stand alone
>> >> instead of simultaneously for all platforms. View this a stepping
>> >> stone to a future where that master script finally comes to fruition.
>> >>
>>

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

OK, saw that change.  I updated index.html, since we weren't adding the .js
at the end for some unknown reason.  I also updated the checklist on the
wiki so we run the bin/create script instead of ant.  If we're following
that, we should catch stupid mistakes such as this.

Also, who is not in a bad mood?

On Fri, Apr 13, 2012 at 12:42 PM, Simon MacDonald <simon.macdonald@gmail.com
> wrote:

> I'm about to push up a change to the android "bin/create" script. That
> script calls "bin/templates/project/cordova/create" which in turn
> expects the files:
>
>    bin/templates/project/cordova/templates/project/res/xml/cordova.xml
>    bin/templates/project/cordova/templates/project/res/xml/plugins.xml
>
> to be hanging around. This is what caused the bug in 1.6.0 as they
> were not up to date. Since I'm a firm believer that source code
> control should only have one copy of any given file I've modified the
> scripts so they go get cordova.xml and plugins.xml from their
> canonical locations in "framework/res/xml".
>
> I think the benefits are obvious.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
> P.S. Yes, I am in a bad mood.
>
> On Fri, Apr 13, 2012 at 3:26 PM, Joe Bowser <bo...@gmail.com> wrote:
> > OK, It's clear we're not deleting the directory, and we have people who
> > care about this.  I'm going to be bumping up priority on the build
> scripts,
> > since they've proven to be higher.  That's pretty much what I wanted out
> of
> > this thread.
> >
> > On Fri, Apr 13, 2012 at 10:19 AM, Brian LeRoux <b...@brian.io> wrote:
> >
> >> > Now, an XML file in these scripts have caused 1.6.1 to exist, which
> has
> >> now
> >> > been extended to Monday,
> >>
> >> Thats ok. Bugs manifest. A point release, while a pain in the ass,
> >> isn't the end of the world and a part of doing things right by our
> >> users.
> >>
> >>
> >> > and have thrown the release schedule out of whack
> >>
> >> I do not think it has to.
> >>
> >>
> >> > such that it looks like I'll have to delay CordovaWebView to 1.8
> because
> >> it
> >> > probably won't be ready by the end of the month.
> >>
> >> Thats ok too. Lets work towards it and get it done when its ready to
> >> ship. Let go of the attachment to a particular date and focus that
> >> quiet rage on the code you want rather than a particular date.
> >>
> >>
> >> > I don't think moving this into ant is a good idea,
> >>
> >> Me either. But wanted to know how you'd approach it. Also: I take
> >> exception to your assertion that Bash is, or ever has been, a flavor
> >> of the month. ;) (And ya I remember the Ruby, then jRuby, then Python,
> >> and then Node attempts.)
> >>
> >>
> >> > and these helper scripts belong in some tooling repository separate
> from
> >> the Cordova project.
> >>
> >> I disagree but only b/c ppl still use Cordova projects stand alone
> >> instead of simultaneously for all platforms. View this a stepping
> >> stone to a future where that master script finally comes to fruition.
> >>
>

Re: [Android] Getting rid of the bin directory

[Simon MacDonald <si...@gmail.com>]

I'm about to push up a change to the android "bin/create" script. That
script calls "bin/templates/project/cordova/create" which in turn
expects the files:

    bin/templates/project/cordova/templates/project/res/xml/cordova.xml
    bin/templates/project/cordova/templates/project/res/xml/plugins.xml

to be hanging around. This is what caused the bug in 1.6.0 as they
were not up to date. Since I'm a firm believer that source code
control should only have one copy of any given file I've modified the
scripts so they go get cordova.xml and plugins.xml from their
canonical locations in "framework/res/xml".

I think the benefits are obvious.

Simon Mac Donald
http://hi.im/simonmacdonald

P.S. Yes, I am in a bad mood.

On Fri, Apr 13, 2012 at 3:26 PM, Joe Bowser <bo...@gmail.com> wrote:
> OK, It's clear we're not deleting the directory, and we have people who
> care about this.  I'm going to be bumping up priority on the build scripts,
> since they've proven to be higher.  That's pretty much what I wanted out of
> this thread.
>
> On Fri, Apr 13, 2012 at 10:19 AM, Brian LeRoux <b...@brian.io> wrote:
>
>> > Now, an XML file in these scripts have caused 1.6.1 to exist, which has
>> now
>> > been extended to Monday,
>>
>> Thats ok. Bugs manifest. A point release, while a pain in the ass,
>> isn't the end of the world and a part of doing things right by our
>> users.
>>
>>
>> > and have thrown the release schedule out of whack
>>
>> I do not think it has to.
>>
>>
>> > such that it looks like I'll have to delay CordovaWebView to 1.8 because
>> it
>> > probably won't be ready by the end of the month.
>>
>> Thats ok too. Lets work towards it and get it done when its ready to
>> ship. Let go of the attachment to a particular date and focus that
>> quiet rage on the code you want rather than a particular date.
>>
>>
>> > I don't think moving this into ant is a good idea,
>>
>> Me either. But wanted to know how you'd approach it. Also: I take
>> exception to your assertion that Bash is, or ever has been, a flavor
>> of the month. ;) (And ya I remember the Ruby, then jRuby, then Python,
>> and then Node attempts.)
>>
>>
>> > and these helper scripts belong in some tooling repository separate from
>> the Cordova project.
>>
>> I disagree but only b/c ppl still use Cordova projects stand alone
>> instead of simultaneously for all platforms. View this a stepping
>> stone to a future where that master script finally comes to fruition.
>>

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

OK, It's clear we're not deleting the directory, and we have people who
care about this.  I'm going to be bumping up priority on the build scripts,
since they've proven to be higher.  That's pretty much what I wanted out of
this thread.

On Fri, Apr 13, 2012 at 10:19 AM, Brian LeRoux <b...@brian.io> wrote:

> > Now, an XML file in these scripts have caused 1.6.1 to exist, which has
> now
> > been extended to Monday,
>
> Thats ok. Bugs manifest. A point release, while a pain in the ass,
> isn't the end of the world and a part of doing things right by our
> users.
>
>
> > and have thrown the release schedule out of whack
>
> I do not think it has to.
>
>
> > such that it looks like I'll have to delay CordovaWebView to 1.8 because
> it
> > probably won't be ready by the end of the month.
>
> Thats ok too. Lets work towards it and get it done when its ready to
> ship. Let go of the attachment to a particular date and focus that
> quiet rage on the code you want rather than a particular date.
>
>
> > I don't think moving this into ant is a good idea,
>
> Me either. But wanted to know how you'd approach it. Also: I take
> exception to your assertion that Bash is, or ever has been, a flavor
> of the month. ;) (And ya I remember the Ruby, then jRuby, then Python,
> and then Node attempts.)
>
>
> > and these helper scripts belong in some tooling repository separate from
> the Cordova project.
>
> I disagree but only b/c ppl still use Cordova projects stand alone
> instead of simultaneously for all platforms. View this a stepping
> stone to a future where that master script finally comes to fruition.
>

Re: [Android] Getting rid of the bin directory

[Brian LeRoux <b...@brian.io>]

> Now, an XML file in these scripts have caused 1.6.1 to exist, which has now
> been extended to Monday,

Thats ok. Bugs manifest. A point release, while a pain in the ass,
isn't the end of the world and a part of doing things right by our
users.


> and have thrown the release schedule out of whack

I do not think it has to.


> such that it looks like I'll have to delay CordovaWebView to 1.8 because it
> probably won't be ready by the end of the month.

Thats ok too. Lets work towards it and get it done when its ready to
ship. Let go of the attachment to a particular date and focus that
quiet rage on the code you want rather than a particular date.


> I don't think moving this into ant is a good idea,

Me either. But wanted to know how you'd approach it. Also: I take
exception to your assertion that Bash is, or ever has been, a flavor
of the month. ;) (And ya I remember the Ruby, then jRuby, then Python,
and then Node attempts.)


> and these helper scripts belong in some tooling repository separate from the Cordova project.

I disagree but only b/c ppl still use Cordova projects stand alone
instead of simultaneously for all platforms. View this a stepping
stone to a future where that master script finally comes to fruition.

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

OK, first of all, they aren't build scripts.  They don't build Cordova, the
ant scripts in framework build Cordova.  These are helper scripts that
generate Cordova projects, which now really only automate six things:

1. Running the Android Command Line Tool
2. Running ant jar
3. Copying ant jar into the libs directory of the generated project
4. Copying Android Manifest
5. Copying the res/xml directory
6. Copying the latest version of cordova js into assets/www

Now, an XML file in these scripts have caused 1.6.1 to exist, which has now
been extended to Monday, and have thrown the release schedule out of whack
such that it looks like I'll have to delay CordovaWebView to 1.8 because it
probably won't be ready by the end of the month.

I don't think moving this into ant is a good idea, and these helper scripts
belong in some tooling repository separate from the Cordova project.
 However, since it's been decided that they have to live in the Android
repository, that's where they're staying, which means that similar bugs
will probably happen again when we're trying to get another release out
unless someone keeps an eye on it. I'd rather have it be someone who is
invested in having these scripts work than someone who is not.

On Fri, Apr 13, 2012 at 8:45 AM, Brian LeRoux <b...@brian.io> wrote:

> Hey Joe, I understand you don't like the build tooling but Android is
> in part your responsibility and saying you despise it really isn't
> helping. I am certain you know the value of automation so, how would
> you refactor to achieve the same end? Should we roll it into ant
> scripts and java?
>
>
> On Fri, Apr 13, 2012 at 7:48 AM, Joe Bowser <bo...@gmail.com> wrote:
> > Except it did break. It broke in 1.6.0 due to neglect, and was most
> likely
> > broken in 1.5 as well.
> >
> > I personally despise the build tools, since there seems to be no good
> happy
> > medium for them.  They either totally get neglected or they attract so
> much
> > attention when they're written in the flavor of the week that people
> > bikeshed the hell out of them.
> >
> > But it sounds like the majority want to keep it.  Who do I assign build
> > tool ticket to in this case? If people really care about them, who wants
> to
> > do the work?
> > On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:
> >
> >> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
> >>
> >> > We're trying to figure out what the command line tooling is gonna look
> >> > like ...
> >> >
> >> > Until that decision is made I don't think we should touch the scripts.
> >> >
> >>
> >> +1 Ain't broke, don't fix it.
> >>
> >> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
> >> make a "decision" on command line tooling.  I'm figuring that we'll be
> >> doing one or two CLI's to "throw away" [1] before figuring out what
> works.
> >> (and so, the sooner we start building the throw aways, the better).
> >>
> >> And especially: I don't want to remove it in 1.7 only to have to add it
> >> back in 1.8.
> >>
> >> [1]
> >>
> http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
> >>
> >> --
> >> Patrick Mueller
> >> http://muellerware.org
> >>
>

Re: [Android] Getting rid of the bin directory

[Brian LeRoux <b...@brian.io>]

Hey Joe, I understand you don't like the build tooling but Android is
in part your responsibility and saying you despise it really isn't
helping. I am certain you know the value of automation so, how would
you refactor to achieve the same end? Should we roll it into ant
scripts and java?


On Fri, Apr 13, 2012 at 7:48 AM, Joe Bowser <bo...@gmail.com> wrote:
> Except it did break. It broke in 1.6.0 due to neglect, and was most likely
> broken in 1.5 as well.
>
> I personally despise the build tools, since there seems to be no good happy
> medium for them.  They either totally get neglected or they attract so much
> attention when they're written in the flavor of the week that people
> bikeshed the hell out of them.
>
> But it sounds like the majority want to keep it.  Who do I assign build
> tool ticket to in this case? If people really care about them, who wants to
> do the work?
> On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:
>
>> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
>>
>> > We're trying to figure out what the command line tooling is gonna look
>> > like ...
>> >
>> > Until that decision is made I don't think we should touch the scripts.
>> >
>>
>> +1 Ain't broke, don't fix it.
>>
>> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
>> make a "decision" on command line tooling.  I'm figuring that we'll be
>> doing one or two CLI's to "throw away" [1] before figuring out what works.
>> (and so, the sooner we start building the throw aways, the better).
>>
>> And especially: I don't want to remove it in 1.7 only to have to add it
>> back in 1.8.
>>
>> [1]
>> http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
>>
>> --
>> Patrick Mueller
>> http://muellerware.org
>>

Re: [Android] Getting rid of the bin directory

[Filip Maj <fi...@adobe.com>]

You can assign them to me

On 4/13/12 7:48 AM, "Joe Bowser" <bo...@gmail.com> wrote:

>Except it did break. It broke in 1.6.0 due to neglect, and was most likely
>broken in 1.5 as well.
>
>I personally despise the build tools, since there seems to be no good
>happy
>medium for them.  They either totally get neglected or they attract so
>much
>attention when they're written in the flavor of the week that people
>bikeshed the hell out of them.
>
>But it sounds like the majority want to keep it.  Who do I assign build
>tool ticket to in this case? If people really care about them, who wants
>to
>do the work?
>On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:
>
>> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
>>
>> > We're trying to figure out what the command line tooling is gonna look
>> > like ...
>> >
>> > Until that decision is made I don't think we should touch the scripts.
>> >
>>
>> +1 Ain't broke, don't fix it.
>>
>> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
>> make a "decision" on command line tooling.  I'm figuring that we'll be
>> doing one or two CLI's to "throw away" [1] before figuring out what
>>works.
>> (and so, the sooner we start building the throw aways, the better).
>>
>> And especially: I don't want to remove it in 1.7 only to have to add it
>> back in 1.8.
>>
>> [1]
>> 
>>http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
>>
>> --
>> Patrick Mueller
>> http://muellerware.org
>>

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

Except it did break. It broke in 1.6.0 due to neglect, and was most likely
broken in 1.5 as well.

I personally despise the build tools, since there seems to be no good happy
medium for them.  They either totally get neglected or they attract so much
attention when they're written in the flavor of the week that people
bikeshed the hell out of them.

But it sounds like the majority want to keep it.  Who do I assign build
tool ticket to in this case? If people really care about them, who wants to
do the work?
On Apr 13, 2012 5:43 AM, "Patrick Mueller" <pm...@gmail.com> wrote:

> On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:
>
> > We're trying to figure out what the command line tooling is gonna look
> > like ...
> >
> > Until that decision is made I don't think we should touch the scripts.
> >
>
> +1 Ain't broke, don't fix it.
>
> But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
> make a "decision" on command line tooling.  I'm figuring that we'll be
> doing one or two CLI's to "throw away" [1] before figuring out what works.
> (and so, the sooner we start building the throw aways, the better).
>
> And especially: I don't want to remove it in 1.7 only to have to add it
> back in 1.8.
>
> [1]
> http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away
>
> --
> Patrick Mueller
> http://muellerware.org
>

Re: [Android] Getting rid of the bin directory

[Patrick Mueller <pm...@gmail.com>]

On Thu, Apr 12, 2012 at 18:53, Filip Maj <fi...@adobe.com> wrote:

> We're trying to figure out what the command line tooling is gonna look
> like ...
>
> Until that decision is made I don't think we should touch the scripts.
>

+1 Ain't broke, don't fix it.

But even more: UNTIL WE HAVE NEW COMMAND LINE TOOLING, not just when we
make a "decision" on command line tooling.  I'm figuring that we'll be
doing one or two CLI's to "throw away" [1] before figuring out what works.
(and so, the sooner we start building the throw aways, the better).

And especially: I don't want to remove it in 1.7 only to have to add it
back in 1.8.

[1]
http://www.tbray.org/ongoing/When/200x/2008/08/22/Build-One-to-Throw-Away

-- 
Patrick Mueller
http://muellerware.org

Re: [Android] Getting rid of the bin directory

[Brian LeRoux <b...@brian.io>]

Let's not throw the baby out with the bath water! I totally use them. The
next couple of sprints are dedicated to fixing this stuff up. And yes,
these scripts do belong to the project they act on. Agree they need
maintenance but given none are >30 loc I am confident we can handle it. ;p

On Thursday, April 12, 2012, Joe Bowser wrote:

> Here's the thing. The tooling was added before we had this project donated
> to Apache, and the tooling hasn't been updated as well as it needs to be.
>  I don't want to have another point release just because of something that
> can be fixed by copying an XML file to happen again, because it runs into
> issues where we have to revert people's work in places like cordova-js,
> which sucks.  So, I propose that it goes somewhere else and leaves the
> Android repository.
>
> While the README on the repository indicates how to get started, this
> README isn't consistent with the Getting Started Docs which discuss how to
> get started with Eclipse.  The fact is that someone should own the tooling
> for all the platforms, and this shouldn't be in the Android or iOS
> repositories because they will get ignored.  That's why I want to delete
> it/move it/find another home for it.
>
>
> On Thu, Apr 12, 2012 at 2:52 PM, Steven Gill <stevengill97@gmail.com<javascript:;>>
> wrote:
>
> > With all the talk about improving CLI tooling, I don't know if removing
> > what we have is a step forward
> >
> > On Thu, Apr 12, 2012 at 2:45 PM, Shazron <shazron@gmail.com<javascript:;>>
> wrote:
> >
> > > Which reminds me, the iOS bin directory hasn't been updated for 7
> > > months and so far no one has complained (I don't use it myself) - it
> > > is definitely outdated
> > >
> > > On Thu, Apr 12, 2012 at 2:45 PM, Filip Maj <fil@adobe.com<javascript:;>>
> wrote:
> > > > I use it :(
> > > >
> > > > When I want to create a standalone folder for a single android
> phonegap
> > > > app
> > > >
> > > > On 4/12/12 2:39 PM, "Joe Bowser" <bowserj@gmail.com <javascript:;>>
> wrote:
> > > >
> > > >>Hey
> > > >>
> > > >>We had to issue a release because of a "bug" in Android, I'm wanting
> to
> > > >>delete the entire build script directory unless someone wants to take
> > on
> > > >>the task of making sure that works.  Since ant jar works, I don't see
> > the
> > > >>reason for having this directory, and it seems to cause more problems
> > > than
> > > >>it's actually worth.
> > > >>
> > > >>Any thoughts?
> > > >>
> > > >>Joe
> > > >
> > >
> >
>

Re: [Android] Getting rid of the bin directory

[Filip Maj <fi...@adobe.com>]

We're trying to figure out what the command line tooling is gonna look
like [1], it is not yet clear if we will be managing the various
build/platform tasks on a per-platform basis, or if we're going to unify
it all under a different project.

Until that decision is made I don't think we should touch the scripts.

>The fact is that someone should own the tooling
>for all the platforms, and this shouldn't be in the Android or iOS
>repositories because they will get ignored.  That's why I want to delete
>it/move it/find another home for it.

I don't buy the notion that build scripts for each platform will be
ignored by platform maintainers. Almost any library has a build script
that automates common tasks. Almost any project I work on has some manner
of automation that is necessary, and should not be ignored.

My 2 cents.

[1] http://wiki.apache.org/cordova/CommandLineToolingDesign

Re: [Android] Getting rid of the bin directory

[Joe Bowser <bo...@gmail.com>]

Here's the thing. The tooling was added before we had this project donated
to Apache, and the tooling hasn't been updated as well as it needs to be.
 I don't want to have another point release just because of something that
can be fixed by copying an XML file to happen again, because it runs into
issues where we have to revert people's work in places like cordova-js,
which sucks.  So, I propose that it goes somewhere else and leaves the
Android repository.

While the README on the repository indicates how to get started, this
README isn't consistent with the Getting Started Docs which discuss how to
get started with Eclipse.  The fact is that someone should own the tooling
for all the platforms, and this shouldn't be in the Android or iOS
repositories because they will get ignored.  That's why I want to delete
it/move it/find another home for it.


On Thu, Apr 12, 2012 at 2:52 PM, Steven Gill <st...@gmail.com> wrote:

> With all the talk about improving CLI tooling, I don't know if removing
> what we have is a step forward
>
> On Thu, Apr 12, 2012 at 2:45 PM, Shazron <sh...@gmail.com> wrote:
>
> > Which reminds me, the iOS bin directory hasn't been updated for 7
> > months and so far no one has complained (I don't use it myself) - it
> > is definitely outdated
> >
> > On Thu, Apr 12, 2012 at 2:45 PM, Filip Maj <fi...@adobe.com> wrote:
> > > I use it :(
> > >
> > > When I want to create a standalone folder for a single android phonegap
> > > app
> > >
> > > On 4/12/12 2:39 PM, "Joe Bowser" <bo...@gmail.com> wrote:
> > >
> > >>Hey
> > >>
> > >>We had to issue a release because of a "bug" in Android, I'm wanting to
> > >>delete the entire build script directory unless someone wants to take
> on
> > >>the task of making sure that works.  Since ant jar works, I don't see
> the
> > >>reason for having this directory, and it seems to cause more problems
> > than
> > >>it's actually worth.
> > >>
> > >>Any thoughts?
> > >>
> > >>Joe
> > >
> >
>

Re: [Android] Getting rid of the bin directory

[Steven Gill <st...@gmail.com>]

With all the talk about improving CLI tooling, I don't know if removing
what we have is a step forward

On Thu, Apr 12, 2012 at 2:45 PM, Shazron <sh...@gmail.com> wrote:

> Which reminds me, the iOS bin directory hasn't been updated for 7
> months and so far no one has complained (I don't use it myself) - it
> is definitely outdated
>
> On Thu, Apr 12, 2012 at 2:45 PM, Filip Maj <fi...@adobe.com> wrote:
> > I use it :(
> >
> > When I want to create a standalone folder for a single android phonegap
> > app
> >
> > On 4/12/12 2:39 PM, "Joe Bowser" <bo...@gmail.com> wrote:
> >
> >>Hey
> >>
> >>We had to issue a release because of a "bug" in Android, I'm wanting to
> >>delete the entire build script directory unless someone wants to take on
> >>the task of making sure that works.  Since ant jar works, I don't see the
> >>reason for having this directory, and it seems to cause more problems
> than
> >>it's actually worth.
> >>
> >>Any thoughts?
> >>
> >>Joe
> >
>

Re: [Android] Getting rid of the bin directory

[Shazron <sh...@gmail.com>]

Which reminds me, the iOS bin directory hasn't been updated for 7
months and so far no one has complained (I don't use it myself) - it
is definitely outdated

On Thu, Apr 12, 2012 at 2:45 PM, Filip Maj <fi...@adobe.com> wrote:
> I use it :(
>
> When I want to create a standalone folder for a single android phonegap
> app
>
> On 4/12/12 2:39 PM, "Joe Bowser" <bo...@gmail.com> wrote:
>
>>Hey
>>
>>We had to issue a release because of a "bug" in Android, I'm wanting to
>>delete the entire build script directory unless someone wants to take on
>>the task of making sure that works.  Since ant jar works, I don't see the
>>reason for having this directory, and it seems to cause more problems than
>>it's actually worth.
>>
>>Any thoughts?
>>
>>Joe
>

Re: [Android] Getting rid of the bin directory

[Filip Maj <fi...@adobe.com>]

I use it :(

When I want to create a standalone folder for a single android phonegap
app 

On 4/12/12 2:39 PM, "Joe Bowser" <bo...@gmail.com> wrote:

>Hey
>
>We had to issue a release because of a "bug" in Android, I'm wanting to
>delete the entire build script directory unless someone wants to take on
>the task of making sure that works.  Since ant jar works, I don't see the
>reason for having this directory, and it seems to cause more problems than
>it's actually worth.
>
>Any thoughts?
>
>Joe