On 4/16/13 4:37 PM, "Justin Mclean" wrote:
> Hi,
>
>>> I'm as far as the docs build now. Is there something I need to change to
>>> see the issue in the experimental swc?
>
> An "ant doc' in framework/projects/experimental should show the first issue.
>
OK, I am seeing an error where it ca
Hi,
>> I'm as far as the docs build now. Is there something I need to change to
>> see the issue in the experimental swc?
An "ant doc' in framework/projects/experimental should show the first issue.
Justin
Hi,
> I'm as far as the docs build now. Is there something I need to change to
> see the issue in the experimental swc?
Not that I can recall.
Justin
On 4/16/13 3:34 PM, "Justin Mclean" wrote:
> HI,
>
>> The default location for TLF should be a flex-tlf directory that is a sibling
>> of the flex-sdk directory.
> The path as far as I know in build.properties needs to be a full path not a
> relative path, so thats going to be be different on
HI,
> The default location for TLF should be a flex-tlf directory that is a sibling
> of the flex-sdk directory.
The path as far as I know in build.properties needs to be a full path not a
relative path, so thats going to be be different on different machine. Perhaps
this can be fixed?
Justin
ctory.
- Gordon
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, April 16, 2013 11:03 AM
To: dev@flex.apache.org
Subject: Re: Git and build.properties
On 4/16/13 2:45 AM, "Kessler CTR Mark J" wrote:
> +1 to the TLF_HOME
I think I am going to go i
]
Sent: Tuesday, April 16, 2013 2:03 PM
To: dev@flex.apache.org
Subject: Re: Git and build.properties
On 4/16/13 2:45 AM, "Kessler CTR Mark J" wrote:
> +1 to the TLF_HOME
I think I am going to go in the direction of a versioned build.properties, a
local-template.properties and TLF_HOME.
; Sent: Tuesday, April 16, 2013 2:42 AM
> To: dev@flex.apache.org
> Subject: Re: Git and build.properties
>
>
>
>
> On 4/15/13 11:33 PM, "Justin Mclean" wrote:
>
>>> I liked the old way
>> So did I but it didn't work with git in a nice way.
use a standard setup.
People using a nonstandard setup should override with local.properties.
- Gordon
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Monday, April 15, 2013 11:04 PM
To: dev@flex.apache.org
Subject: Re: Git and build.properties
I just pulled and tr
+1 to the TLF_HOME
-Original Message-
From: Alex Harui [mailto:aha...@adobe.com]
Sent: Tuesday, April 16, 2013 2:42 AM
To: dev@flex.apache.org
Subject: Re: Git and build.properties
On 4/15/13 11:33 PM, "Justin Mclean" wrote:
>> I liked the old way
> So did I
Hi,
>> So did I but it didn't work with git in a nice way.
> TLF is the only reason? Or did you run into other things?
It's the major one. I think most of the other values (version number, locale
etc) a local.properties file works fine as they all have reasonable default
values.
> Why couldn't
On 4/15/13 11:33 PM, "Justin Mclean" wrote:
>> I liked the old way
> So did I but it didn't work with git in a nice way.
TLF is the only reason? Or did you run into other things?
>
>> we had it which was:
>> 1) a build.properties is in version control
>> 2) anything you need to override in
Hi,
> I just pulled and tried ant release and it immediately failed because there
> is no build.properties.
Yes as discussed on list we you need to copy the template file and edit. Once
in place there no need to change it again and it wont be overwritten.
> I liked the old way
So did I but it d
I just pulled and tried ant release and it immediately failed because there
is no build.properties. I liked the old way we had it which was:
1) a build.properties is in version control
2) anything you need to override in your system was changed in
local.properties for which there was a local.templ
All of our ant scripts should load a local.properties that override the
build.properties. Build.properties should have some sensible values and
should not be changed very often.
Local.properties should have a template and the template should be checked
in, and local.properties should be in .gitig
Hi,
>> The local changes can be made in this file. The template
>> remains unchanged.
>>
>> We can add a specific entry into gitignore for the build.properties file.
>
> I'll give it a try and see if I can get it to work.
Looks like I got it working, checked in - as always feedback welcome.
T
Hi,
> build.properties is need for paths to various bits required in building the
> SDK.
And java settings and the like.
Justin
Hi,
> Could we just have the build version in the command line or accessed like a
> system variable?
I've fixed the build version issue by changing it to be the date in MMDD
format, build.properties is need for paths to various bits required in building
the SDK.
Thanks,
Justin
Hi,
> I suggested this a while ago. We check in build.properties.template.
That would break the CI build I believe (if it was currently working).
> The developer (or the build script) copies the contents into build.properties
> while building.
I think build.properties is read before the script
Could we just have the build version in the command line or accessed like a
system variable?
On Sun, Apr 14, 2013 at 8:28 PM, OmPrakash Muppirala
wrote:
> I suggested this a while ago. We check in build.properties.template. The
> developer (or the build script) copies the contents into build.p
I suggested this a while ago. We check in build.properties.template. The
developer (or the build script) copies the contents into build.properties
while building. The local changes can be made in this file. The template
remains unchanged.
We can add a specific entry into gitignore for the buil
HI,
This also breaks the usefulness of "git stash" in that you have to reapply the
changes made to build.properties. Is there as easy way to tell git stash to
ignore a file or only stash a set of files?
Justin
22 matches
Mail list logo
