> If we go a step further and also emit Flex class name in another property
> (perhaps in the 'class' property of DOM elements) we could make RIATest
> automatically recognize which Flex component does each DOM element
> represent and even aim to have a universal syntax for test scripts that
can
>
Hi,
> I can look into this more when I try to fix the release target, but I think
> we want an air-config with the substitution tokens in it, and the one in an
> official AIR SDK doesn't have them.
May need to be careful. Are the structure/entries of air-config and
airmobile-config the same AIR
HI,
> If the release target is not building it, then that is a problem with the
> release target, which I will fix.
I've fixed so that the release target creates the xml file - not 100% sure what
to do with the air config files however.
Thanks,
Justin
I can look into this more when I try to fix the release target, but I think
we want an air-config with the substitution tokens in it, and the one in an
official AIR SDK doesn't have them.
-Alex
On 4/14/13 10:03 PM, "Gordon Smith" wrote:
> In that case it sounds like air-config.xml doesn't belo
In that case it sounds like air-config.xml doesn't belong in the repo.
- Gordon
Sent from my iPad
On Apr 14, 2013, at 7:56 PM, "Justin Mclean" wrote:
> Hi,
>
>> Does anybody know why flex-config.xml is produced from
>> flex-config-template.xml by replacing the tokens @playerversion@,
>> @sw
On 4/14/13 6:52 AM, "Michael A. Labriola"
wrote:
>> My understanding is that, from a donation standpoint, it is ok to have
>> binaries in the donation as long as you legally have the right to donate
>> them. Then, at some point, the binaries "must" be removed because >Apache is
>> all about s
Given that the flex-config.xml file is build output produced from
flex-config-template.xml, it makes no sense to have it under source control. If
the release target is not building it, then that is a problem with the release
target, which I will fix.
- Gordon
Sent from my iPad
On Apr 14, 2013
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,
> Getting FalconJX up to parity with FalconJS has taken longer than expected.
> I'm almost done, then I will take on the release build.
Looks like a change Gordon made (removing the flex-config.xml file has also
broken the release build - either it need to be placed back in SVN or we need
t
Still on my list. I should be on it this week. FalconJX is take a bit
longer than expected.
On 4/14/13 5:26 PM, "Justin Mclean" wrote:
> Hi,
>
> Forgot to mention the JIRA issue:
>
> https://issues.apache.org/jira/browse/FLEX-33451
>
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, In
Getting FalconJX up to parity with FalconJS has taken longer than expected.
I'm almost done, then I will take on the release build.
On 4/14/13 7:20 PM, "Justin Mclean" wrote:
> Hi,
>
>> Do the relevant builds work in a non-jenkins environment?
> Currently all except the release build should wo
[
https://issues.apache.org/jira/browse/FLEX-33438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631478#comment-13631478
]
Alex Harui commented on FLEX-33438:
---
I would like to start thinking of TLF as an "upstre
Hi,
> Does anybody know why flex-config.xml is produced from
> flex-config-template.xml by replacing the tokens @playerversion@,
> @swfversion@, and @locale@, but air-config is not similarly produced?
As a guess it probably because the air (and air mobile) config files can be
obtained form the
Hi,
The frameworks/flex-config.xml file is required for ant release so this change
further breaks the already broken release build. Could you please revert part
of this checkin and add flex-config.xml back in.
Thanks,
Justin
Hi,
> Do the relevant builds work in a non-jenkins environment?
Currently all except the release build should work - but any checking in the
last few weeks may of broken things (TLF changes for instance) hard to know.
> If yes, it should not be too hard to get it working on jebkins
It should
[
https://issues.apache.org/jira/browse/FLEX-33438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631456#comment-13631456
]
Justin Mclean commented on FLEX-33438:
--
The three jobs in question are:
https://build
On Apr 14, 2013 6:52 PM, "Justin Mclean" wrote:
>
> Hi,
>
> Can someone with Jenkins and Git experience please try and fix this.
> https://issues.apache.org/jira/browse/FLEX-33438
>
> Currently we have no idea if any checkins will break the build.
>
> It also needs to build from the develop branch
Hi,
Can someone with Jenkins and Git experience please try and fix this.
https://issues.apache.org/jira/browse/FLEX-33438
Currently we have no idea if any checkins will break the build.
It also needs to build from the develop branch (not master/trunk) and also do a
release build - which is curr
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,
Forgot to mention the JIRA issue:
https://issues.apache.org/jira/browse/FLEX-33451
Justin
Hi,
Ant release (while in a better state than it was) is still broken - anyone have
some spare cycles to look. I took a look the other week but was unable to fix
the asdocs issue.
Thanks,
Justin
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
Hi,
I asked this before but got no answer - anyone have an idea of how to deal with
build.properties. In order to build the SDK you need to make changes to it (eg
TLF path), however we don't want to always check in those changes but the file
does needs to be in version control as you can't buil
Hi
Just pushed a fix to develop branch which fixes a ClassCastException
for following scenario.
package vo {
public interface ITestInterface { }
}
package vo {
public class TestObject implements ITestInterface {
public function TestObject() { }
}
}
Erik you may have a review look at it
> Hi Tigran,
>
> Thank you for your offer of a special license of RIATest for Apache
> Flex.
> I'm not familiar with RIATest at all. It appears to be more like what
> I would call an application testing framework like QTP. Is that
> correct?
Correct. RIATest does functional testing of GUI ju
Cyrill Zadra created FLEX-33494:
---
Summary: Migrate open jira issues from adobe
Key: FLEX-33494
URL: https://issues.apache.org/jira/browse/FLEX-33494
Project: Apache Flex
Issue Type: Sub-task
Cyrill Zadra created FLEX-33493:
---
Summary: Migrate FlexUnit build scripts
Key: FLEX-33493
URL: https://issues.apache.org/jira/browse/FLEX-33493
Project: Apache Flex
Issue Type: Sub-task
>Are those in adobe's jira? Tried to find them but without succes.
Side note, we also have a build setup and all scripts to donate:
http://flexunit.digitalprimates.net:8080/
Mike
>Is that branch (with removed harmcrest dependencies) also in github.. because
>as far as I can see there is only one branch (master) in github.
Correct. We only leave master under the main github repo and contributors work
in their own forks. That was out model
> There were only a few open issues. We will need to recreate as they were
> apparently lost when Adobe's jira moved.
>>Are those in adobe's jira? Tried to find them but without succes.
Correct, that's what I said. They were lost when Adobe moved
>My understanding is that, from a donation standpoint, it is ok to have
>binaries in the donation as long as you legally have the right to donate them.
> Then, at some point, the binaries "must" be removed because >Apache is all
>about source.
Right, that's my point. We don't have permission t
Ok I've gotten it up on a github. It is showing the changes now, the link
for it [1] starts at the level where the changes start.
[1]
https://github.com/KesslerConsulting/example/tree/master/frameworks/projects/spark/src/spark/components
-Mark
On Sun, Apr 14, 2013 at 8:31 AM, Mark Kessler
wr
I ended up creating a GITHub account... however, I will probably redo the
repo on it since I uploaded a clone of the Flex-SDK with my changes already
in it. This means the work I've done already doesn't stand out. so give
me about 20 mins and I'll have
> Logistically speaking that would be least
Aha! See, I'm perfectly capable of messing up a commit message ;-)
My bad, you're right, it should've read [ASJS]. Sorry for the confusion.
EdB
On Sun, Apr 14, 2013 at 8:11 AM, Alex Harui wrote:
>
>
>
> On 4/13/13 1:18 AM, "Erik de Bruin" wrote:
>
>>> It isn't obvious to me that a compiler t
> There were only a few open issues. We will need to recreate as they were
> apparently lost when Adobe's jira moved.
Are those in adobe's jira? Tried to find them but without succes.
Cyrill
[
https://issues.apache.org/jira/browse/FLEX-33492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-33492:
Description: https://github.com/flexunit/flexunit/pulls
> Migrate FlexUnit open pull request
>
[
https://issues.apache.org/jira/browse/FLEX-33492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cyrill Zadra updated FLEX-33492:
Summary: Migrate FlexUnit open pull request (was: Migrate Open Pull
Request)
> Migrate FlexUn
Cyrill Zadra created FLEX-33492:
---
Summary: Migrate Open Pull Request
Key: FLEX-33492
URL: https://issues.apache.org/jira/browse/FLEX-33492
Project: Apache Flex
Issue Type: Sub-task
Infra task to import git repo is created.
https://issues.apache.org/jira/browse/INFRA-6152
Sent from my iPhone
On 14.04.2013, at 11:20, "Michael A. Labriola"
wrote:
>> Just to double check: The sources on
>> https://github.com/flexunit/flexunit are the most up-to-date?
>
> Yes, those are th
On Apr 13, 2013 11:44 PM, "Alex Harui" wrote:
>
> Is the Git whiteboard read-write? Are there any issues with opening it if
> we do end up going to Github? If not, can you request that it be opened?
> I'm not sure how you were going about that for the other repos.
>
> Thanks,
> -Alex
Mark, mayb
45 matches
Mail list logo
