On Mon, Nov 19, 2012 at 11:28 AM, Alex Harui <aha...@adobe.com> wrote:
> Do you have plans to handle the commit as well? I've always wanted a tool > that would coordinate the commit log and the related JIRA issues. I'm > always having to look up the revision number to put in the JIRA issues and > the JIRA issues to put in the commit log. > > We could do it, but it would be a bit tricky. In my set up, I sign in every time I want to commit something (so that I dont commit anything by mistake) Not sure how I would handle such a scenario. But I do see the value in this feature... Thanks, Om > > On 11/19/12 11:19 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > > > Well, believe it or not, developers are "users" too and an AIR app > > allows for a (better) UI, improving usability and allowing for a > > richer feature set with a shallower learning curve. > > > > EdB > > > > > > On Mon, Nov 19, 2012 at 8:13 PM, Carol Frampton <cfram...@adobe.com> > wrote: > >> > >> > >> On 11/19/12 2 :01PM, "Om" <bigosma...@gmail.com> wrote: > >> > >>> What Fredric says is correct. The plan is to have it entered only > once - > >>> like a settings menu. There is no need to enter those details every > time. > >>> > >>> After the first time, all the developer has to do is click the "Scan > and > >>> Test" button which will scan the svn changes, figure out which tests to > >>> run, call mini_run.sh and run just those tests to completion. > >> > >> Ok but why an air app? Why not just a new target in mustella/build.xml? > >> > >> Carol > >> > > > > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
