You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by Frédéric THOMAS <we...@hotmail.com> on 2013/03/26 11:21:49 UTC
asdoc - Release build broken (was: Release build broken)
Hi,
Ok, it seems I solved the TLF release build issues, now I've got asdoc
issues [1] with the experimental lib, did it exist before ?
I don't know anything in as doc generation but from far, I would say, that's
a NS problem between http://flex.apache.org/experimental/ns and the Spark
one, someone better than me can help ?
Thanks,
-Fred
[1]
translation:
Chargement du fichier de configuration -> loading config file
Erreur: Impossible de rÚsoudre -> error: Can not resolve
en une implÚmentation de composant. > in a component implementation
doc:
[asdoc] Chargement du fichier de configuration
U:\sources\asf\flex\sdk\frameworks\flex-config.xml
[zip] Updating zip:
U:\sources\asf\flex\sdk\frameworks\locale\en_US\apache_rb.swc
[copy] Copying 1 file to
U:\sources\asf\flex\sdk\frameworks\projects\apache\bundles\en_US
clean-temp-docs:
[delete] Deleting directory U:\sources\asf\flex\sdk\tempDoc
doc:
[asdoc] Chargement du fichier de configuration
U:\sources\asf\flex\sdk\frameworks\flex-config.xml
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\MenuSkin.mxml(46):
Erreur: Impossib
le de rÚsoudre <s:SolidColorStroke> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke" weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\MenuSkin.mxml(55):
Erreur: Impossib
le de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\AlertSkin.mxml(161):
Erreur: Imposs
ible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColorStroke
id="borderStroke" weight="1" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\AlertSkin.mxml(171):
Erreur: Imposs
ible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="backgroundFill"
color="#FFFFFF"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ArrowDownToggleButtonSkin.mxml(257)
: Erreur: Impossible de rÚsoudre <s:GradientEntry> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:GradientEntry id="arrowFill1"
color="0" alpha="0.6" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ArrowDownToggleButtonSkin.mxml(261)
: Erreur: Impossible de rÚsoudre <s:GradientEntry> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:GradientEntry id="arrowFill2"
color="0" alpha="0.8" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\DataNavigatorSkin.mxml(111):
Erreur
: Impossible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke"
weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\DataNavigatorSkin.mxml(120):
Erreur
: Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF"
/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\AccordionSkin.mxml(110):
Erreur: Im
possible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF"
/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\AccordionSkin.mxml(119):
Erreur: Im
possible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke"
weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\NavigatorSkin.mxml(103):
Erreur: Im
possible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke"
weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\NavigatorSkin.mxml(112):
Erreur: Im
possible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF"
/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\TabNavigatorSkin.mxml(113):
Erreur:
Impossible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke
id="borderStroke" weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\TabNavigatorSkin.mxml(122):
Erreur:
Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill"
color="0xFFFFFF" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\MenuBarSkin.mxml(46):
Erreur: Impos
sible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke" weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\MenuBarSkin.mxml(55):
Erreur: Impos
sible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ArrowRightToggleButtonSkin.mxml(258
): Erreur: Impossible de rÚsoudre <s:GradientEntry> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:GradientEntry id="arrowFill1"
color="0" alpha="0.6" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ArrowRightToggleButtonSkin.mxml(262
): Erreur: Impossible de rÚsoudre <s:GradientEntry> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:GradientEntry id="arrowFill2"
color="0" alpha="0.8" />
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\DataAccordionSkin.mxml(111):
Erreur
: Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0xFFFFFF"
/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\DataAccordionSkin.mxml(120):
Erreur
: Impossible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke"
weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ColorPickerSkin.mxml(154):
Erreur:
Impossible de rÚsoudre <s:SolidColorStroke> en une implÚmentation de
composant.
[asdoc]
[asdoc] <s:SolidColorStroke id="borderStroke"
weight="1"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ColorPickerSkin.mxml(160):
Erreur:
Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="bgFill" color="0x1F1F1F"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ColorPickerSkin.mxml(167):
Erreur:
Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="previewColor"/>
[asdoc]
[asdoc]
U:\sources\asf\flex\sdk\frameworks\projects\experimental\src\spark\skins\ColorPickerSkin.mxml(198):
Erreur:
Impossible de rÚsoudre <s:SolidColor> en une implÚmentation de composant.
[asdoc]
[asdoc] <s:SolidColor id="solidColor"/>
[asdoc]
BUILD FAILED
U:\sources\asf\flex\sdk\build.xml:1253: The following error occurred while
executing this line:
U:\sources\asf\flex\sdk\frameworks\build.xml:216: The following error
occurred while executing this line:
U:\sources\asf\flex\sdk\frameworks\projects\experimental\build.xml:209:
asdoc task failed.
Total time: 29 minutes 59 seconds
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Note: If the resolution of some of the sub-issues would have required more
than one commit, opening a sub-branch would have been a good practice
because the set of commits done in the sub-branch would has been merged into
the mother branch first.
-Fred
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 5:42 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
You right, I had to do that but didn't do it, feel free to open other
tickets.
There're no needs to open a new branch, the mother one exists already, just
prepend the commit messages with the real issue ids, I'll modify the commit
messages of the others before merging to reflect the new issue ids.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:37 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.
There still a minor workflow issue here in that unless we make each of those
sub tasks real JIRA subtasks how do I know who's working on each one (or if
anyone is). I can't assign the entire bug to myself as I wouldn't want to
indicate that I'm working on all of it and only one person can be assigned
the bug so that could stop other people from working on it. We could make
each task be a real JIRA sub task but then do each of those need their own
git branches as well?
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
You right, I had to do that but didn't do it, feel free to open other
tickets.
There're no needs to open a new branch, the mother one exists already, just
prepend the commit messages with the real issue ids, I'll modify the commit
messages of the others before merging to reflect the new issue ids.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:37 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.
There still a minor workflow issue here in that unless we make each of those
sub tasks real JIRA subtasks how do I know who's working on each one (or if
anyone is). I can't assign the entire bug to myself as I wouldn't want to
indicate that I'm working on all of it and only one person can be assigned
the bug so that could stop other people from working on it. We could make
each task be a real JIRA sub task but then do each of those need their own
git branches as well?
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
and delete the 3.0.33 link if you have it too.
-Fred
-----Message d'origine-----
From: Frédéric THOMAS
Sent: Thursday, March 28, 2013 6:31 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
It has been fixed in the build.xml, how did you call your flex-tlf repo ?
It should be ${FLEX_HOME}/../flex-tlf or ${FLEX_HOME}/../tlf
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 6:23 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi
Also doesn't look like the TLF issue is fixed in that branch:
git branch
* FLEX-33451
develop
master
ompile:
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml(58):
Error: configuration variable 'include-file' value contains unknown token
'tlf.branch'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/build.xml:361: The
following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:91:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:393:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:193:
compc task failed.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
It has been fixed in the build.xml, how did you call your flex-tlf repo ?
It should be ${FLEX_HOME}/../flex-tlf or ${FLEX_HOME}/../tlf
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 6:23 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi
Also doesn't look like the TLF issue is fixed in that branch:
git branch
* FLEX-33451
develop
master
ompile:
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml(58):
Error: configuration variable 'include-file' value contains unknown token
'tlf.branch'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/build.xml:361: The
following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:91:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:393:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:193:
compc task failed.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi
Also doesn't look like the TLF issue is fixed in that branch:
git branch
* FLEX-33451
develop
master
ompile:
[compc] Loading configuration file /Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc] /Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml(58): Error: configuration variable 'include-file' value contains unknown token 'tlf.branch'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/build.xml:361: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:91: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:393: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:193: compc task failed.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> You right, I just filled the jira accordingly.
Thanks that's a lot clearer.
There still a minor workflow issue here in that unless we make each of those sub tasks real JIRA subtasks how do I know who's working on each one (or if anyone is). I can't assign the entire bug to myself as I wouldn't want to indicate that I'm working on all of it and only one person can be assigned the bug so that could stop other people from working on it. We could make each task be a real JIRA sub task but then do each of those need their own git branches as well?
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
You right, I just filled the jira accordingly.
> Does that remove the history of each fix? I'd rather see how each
> issue/sub task was fixed not just a generic single comment and one set of
> changes
No but I'll re-organize the commits to make it clean, example, at the
moment, there's still the asdoc generation problem for the experimental lib,
so, to make the build pass until the end, I commented the 'doc' target, and
included it in a temporary commit, one fixed in an other commit, I'll remove
the temporary one before to merge.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 5:20 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> It's not a silly question, the answer is because, I opened a jira ticket
> [1] in which there are few sub-issues/tasks.
I guess that one way of doing it - but IMO would be better if they were
either merged into develop as each sub task was fixed. As that JIRA issue is
unassigned I'd assume no one has stated work on it and if anything had been
fixed I would of assumed there would be a comment in there saying so. The
JIRA issue should mention the (remote) Git branch as well that the work is
being done in if it not develop. (especially as "git branch" doesn't show
remotes you don't know about). Every little bit of info helps. :-)
> merge it to the develop branch as a set of commit to fix the release
> build.
Does that remove the history of each fix? I'd rather see how each issue/sub
task was fixed not just a generic single comment and one set of changes.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> It's not a silly question, the answer is because, I opened a jira ticket [1] in which there are few sub-issues/tasks.
I guess that one way of doing it - but IMO would be better if they were either merged into develop as each sub task was fixed. As that JIRA issue is unassigned I'd assume no one has stated work on it and if anything had been fixed I would of assumed there would be a comment in there saying so. The JIRA issue should mention the (remote) Git branch as well that the work is being done in if it not develop. (especially as "git branch" doesn't show remotes you don't know about). Every little bit of info helps. :-)
> merge it to the develop branch as a set of commit to fix the release build.
Does that remove the history of each fix? I'd rather see how each issue/sub task was fixed not just a generic single comment and one set of changes.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
It's not a silly question, the answer is because, I opened a jira ticket [1]
in which there are few sub-issues/tasks :
The release build due to the Git migration is broken:
- TLF external build
- Build Number
- ASDoc for the experimental lib
- Building process (.gitignore, empty.properties)
So, I created a branch where I/we will solve all of them, for each
particular sub-issues/tasks resolution, it will be one commit with a message
prepend with the jira issue id, once all done, I'll clean up the branch and
merge it to the develop branch as a set of commit to fix the release build.
In jira, because I prepended each commit with the jira issue id, I'll find
on the jira issue source tab, the links to all the sources fixed (as soon as
fisheye will be operational, probably in the week).
-Fred
[1] https://issues.apache.org/jira/browse/FLEX-33451
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 4:48 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn't it
been merged into develop? Especially if it fixes an issue. Other people may
have this issue but they wouldn't know that your branch fixes it.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> You can see the fix in the branch I did
Perhaps a silly question but if you have a fix in a branch why hasn't it been merged into develop? Especially if it fixes an issue. Other people may have this issue but they wouldn't know that your branch fixes it.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
You can see the fix in the branch I did
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Thursday, March 28, 2013 2:33 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
Ok files the compiler issue but still getting an error to do with TLF.
Assume this is to do with the recent TLF changes.
Can you remind me how the SDK build files now knows where TLF is? There
nothing in the README that I can see.
compile:
[compc] Loading configuration file
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc]
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml(58):
Error: configuration variable 'include-file' value contains unknown token
'tlf.branch'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/build.xml:361: The
following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:91:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:393:
The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:193:
compc task failed.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
Ok files the compiler issue but still getting an error to do with TLF. Assume this is to do with the recent TLF changes.
Can you remind me how the SDK build files now knows where TLF is? There nothing in the README that I can see.
compile:
[compc] Loading configuration file /Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml
[compc] Apache Flex compc (Component Compiler)
[compc] Version 4.10.0 build 0
[compc] Copyright 2012 The Apache Software Foundation.
[compc]
[compc] /Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/compile-config.xml(58): Error: configuration variable 'include-file' value contains unknown token 'tlf.branch'
[compc]
[compc] </include-file>
[compc]
BUILD FAILED
/Users/justinmclean/Documents/ApacheFlexDevelopGit/build.xml:361: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:91: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/build.xml:393: The following error occurred while executing this line:
/Users/justinmclean/Documents/ApacheFlexDevelopGit/frameworks/projects/textLayout/build.xml:193: compc task failed.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Alex Harui <ah...@adobe.com>.
On 3/27/13 12:43 AM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> Hi,
>
>> For me, it is using the one in lib, not in ant/lib.
>
> Mine was using the one in ant/lib and issue was fixed my moving the lib one to
> this location. However I'd still like to know why it was using the one in
> ant/lib and not lib - anyone know where this is specified?
In the build.xml for arcade, it tries for ant/lib first. The SDK repo
should not have a flextasks.jar in ant/lib. Falcon builds used to or still
put a Falcon version there. Maybe clean should clean it.
>
> As far as I know I only build the SDK (ant main), tried to make a release (ant
> release) and run the checkin tests (ant checkin-tests) and a few of the
> mustella tests (./mustella/mini_run.sh). Does mustella need/use the other
> compiler.jar?
no
>
> The only ant related environment var I can find is:
> ANT_HOME=/usr/share/ant
>
> And there's nothing in the various build.properties or env.properties files.
>
> Thanks,
> Justin
>
>
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> For me, it is using the one in lib, not in ant/lib.
Mine was using the one in ant/lib and issue was fixed my moving the lib one to this location. However I'd still like to know why it was using the one in ant/lib and not lib - anyone know where this is specified?
As far as I know I only build the SDK (ant main), tried to make a release (ant release) and run the checkin tests (ant checkin-tests) and a few of the mustella tests (./mustella/mini_run.sh). Does mustella need/use the other compiler.jar?
The only ant related environment var I can find is:
ANT_HOME=/usr/share/ant
And there's nothing in the various build.properties or env.properties files.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Ok, so I'm curious to know where the issue you have comes from as we don't
have it, keep us in touch.
Thanks,
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:44 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> Couldn't you simply clone again the sdk, build on the develop branch,
> checkout the 'FLEX-33451' and build release on it ?
Tried that it failed as well.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> Couldn't you simply clone again the sdk, build on the develop branch, checkout the 'FLEX-33451' and build release on it ?
Tried that it failed as well.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
humm... weird, I'ld like to see the others result then.
Thanks Erik,
-Fred
-----Message d'origine-----
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:51 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I ran 'ant doc' and got a successful build.
However, one of the 'sections' (?) did show a "Fatal Error":
doc:
[asdoc] Loading configuration file
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
[asdoc] [Fatal Error] :54:6: The element type "p" must be
terminated by the matching end-tag "</p>".
[asdoc] Encountered not well-formed text. Please see
/Users/erik/Documents/ApacheFlex/git/flex-sdk/tempDoc/validation_errors.log
for details.
[zip] Updating zip:
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/locale/en_US/spark_rb.swc
[copy] Copying 1 file to
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark/bundles/en_US
HTH,
EdB
On Wed, Mar 27, 2013 at 10:40 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Well, sorry, I meant 'ant doc' from the experimental lib.
>
>
> Thanks,
> -Fred
>
> -----Message d'origine----- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:29 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> Running 'ant asdoc' gives me:
>
> Buildfile: build.xml
>
> asdoc:
>
> clean:
>
> doc:
> [asdoc] Loading configuration file
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
> Error: Can not resolve a multiname reference unambiguously.
> spark.components:Alert (from
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/experimental/src/spark/components/Alert.as)
> and mx.controls:Alert (from
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/mx/src/mx/controls/Alert.as)
> are available.
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(100):
> col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] return _interactiveChildrenCount;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(894):
> col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] ++ _interactiveChildrenCount ;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(898):
> col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] -- _interactiveChildrenCount ;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(903):
> col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] return _interactiveChildrenCount != 0 ;
> [asdoc] ^
> [asdoc]
>
> BUILD FAILED
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/build.xml:477: The
> following error occurred while executing this line:
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/asdoc/build.xml:58:
> asdoc task failed.
>
> HTH,
>
> EdB
>
>
>
> On Wed, Mar 27, 2013 at 10:15 AM, Frédéric THOMAS
> <we...@hotmail.com> wrote:
>>
>> Did you tried the asdoc target for the experimental project ?
>>
>> I deactivated it in the release to be able to continue to build and see
>> if
>> there wasn't any other errors, to try it you should run the asdoc target
>> directly from the experimental lib itself.
>>
>> Thanks,
>> -Fred
>>
>> -----Message d'origine----- From: Erik de Bruin
>> Sent: Wednesday, March 27, 2013 10:06 AM
>>
>> To: dev@flex.apache.org
>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>
>> I just did this (OS X) and the build was successful both times (on
>> develop with 'main', on FLEX-33451 with 'release').
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
>> <we...@hotmail.com> wrote:
>>>
>>>
>>> Hi Justin,
>>>
>>> Couldn't you simply clone again the sdk, build on the develop branch,
>>> checkout the 'FLEX-33451' and build release on it ?
>>>
>>> -Fred
>>>
>>> -----Message d'origine----- From: Justin Mclean
>>> Sent: Wednesday, March 27, 2013 8:11 AM
>>> To: dev@flex.apache.org
>>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>>
>>>
>>> Hi,
>>>
>>>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>>>> have a Falcon flexTasks.jar in ant/lib?
>>>
>>>
>>>
>>> Is there an easy way to tell which one it's using? I have flexTasks.jar
>>> in
>>> both places.
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I ran 'ant doc' and got a successful build.
However, one of the 'sections' (?) did show a "Fatal Error":
doc:
[asdoc] Loading configuration file
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
[asdoc] [Fatal Error] :54:6: The element type "p" must be
terminated by the matching end-tag "</p>".
[asdoc] Encountered not well-formed text. Please see
/Users/erik/Documents/ApacheFlex/git/flex-sdk/tempDoc/validation_errors.log
for details.
[zip] Updating zip:
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/locale/en_US/spark_rb.swc
[copy] Copying 1 file to
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/spark/bundles/en_US
HTH,
EdB
On Wed, Mar 27, 2013 at 10:40 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Well, sorry, I meant 'ant doc' from the experimental lib.
>
>
> Thanks,
> -Fred
>
> -----Message d'origine----- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:29 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> Running 'ant asdoc' gives me:
>
> Buildfile: build.xml
>
> asdoc:
>
> clean:
>
> doc:
> [asdoc] Loading configuration file
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
> Error: Can not resolve a multiname reference unambiguously.
> spark.components:Alert (from
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/experimental/src/spark/components/Alert.as)
> and mx.controls:Alert (from
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/mx/src/mx/controls/Alert.as)
> are available.
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(100):
> col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] return _interactiveChildrenCount;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(894):
> col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] ++ _interactiveChildrenCount ;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(898):
> col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] -- _interactiveChildrenCount ;
> [asdoc] ^
> [asdoc]
> [asdoc]
> /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(903):
> col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
> [asdoc]
> [asdoc] return _interactiveChildrenCount != 0 ;
> [asdoc] ^
> [asdoc]
>
> BUILD FAILED
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/build.xml:477: The
> following error occurred while executing this line:
> /Users/erik/Documents/ApacheFlex/git/flex-sdk/asdoc/build.xml:58:
> asdoc task failed.
>
> HTH,
>
> EdB
>
>
>
> On Wed, Mar 27, 2013 at 10:15 AM, Frédéric THOMAS
> <we...@hotmail.com> wrote:
>>
>> Did you tried the asdoc target for the experimental project ?
>>
>> I deactivated it in the release to be able to continue to build and see if
>> there wasn't any other errors, to try it you should run the asdoc target
>> directly from the experimental lib itself.
>>
>> Thanks,
>> -Fred
>>
>> -----Message d'origine----- From: Erik de Bruin
>> Sent: Wednesday, March 27, 2013 10:06 AM
>>
>> To: dev@flex.apache.org
>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>
>> I just did this (OS X) and the build was successful both times (on
>> develop with 'main', on FLEX-33451 with 'release').
>>
>> EdB
>>
>>
>>
>> On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
>> <we...@hotmail.com> wrote:
>>>
>>>
>>> Hi Justin,
>>>
>>> Couldn't you simply clone again the sdk, build on the develop branch,
>>> checkout the 'FLEX-33451' and build release on it ?
>>>
>>> -Fred
>>>
>>> -----Message d'origine----- From: Justin Mclean
>>> Sent: Wednesday, March 27, 2013 8:11 AM
>>> To: dev@flex.apache.org
>>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>>
>>>
>>> Hi,
>>>
>>>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>>>> have a Falcon flexTasks.jar in ant/lib?
>>>
>>>
>>>
>>> Is there an easy way to tell which one it's using? I have flexTasks.jar
>>> in
>>> both places.
>>>
>>> Thanks,
>>> Justin
>>
>>
>>
>>
>>
>> --
>> Ix Multimedia Software
>>
>> Jan Luykenstraat 27
>> 3521 VB Utrecht
>>
>> T. 06-51952295
>> I. www.ixsoftware.nl
>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Well, sorry, I meant 'ant doc' from the experimental lib.
Thanks,
-Fred
-----Message d'origine-----
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:29 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Running 'ant asdoc' gives me:
Buildfile: build.xml
asdoc:
clean:
doc:
[asdoc] Loading configuration file
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
Error: Can not resolve a multiname reference unambiguously.
spark.components:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/experimental/src/spark/components/Alert.as)
and mx.controls:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/mx/src/mx/controls/Alert.as)
are available.
[asdoc]
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(100):
col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] return _interactiveChildrenCount;
[asdoc] ^
[asdoc]
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(894):
col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] ++ _interactiveChildrenCount ;
[asdoc] ^
[asdoc]
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(898):
col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] -- _interactiveChildrenCount ;
[asdoc] ^
[asdoc]
[asdoc]
/Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(903):
col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] return _interactiveChildrenCount != 0 ;
[asdoc] ^
[asdoc]
BUILD FAILED
/Users/erik/Documents/ApacheFlex/git/flex-sdk/build.xml:477: The
following error occurred while executing this line:
/Users/erik/Documents/ApacheFlex/git/flex-sdk/asdoc/build.xml:58:
asdoc task failed.
HTH,
EdB
On Wed, Mar 27, 2013 at 10:15 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Did you tried the asdoc target for the experimental project ?
>
> I deactivated it in the release to be able to continue to build and see if
> there wasn't any other errors, to try it you should run the asdoc target
> directly from the experimental lib itself.
>
> Thanks,
> -Fred
>
> -----Message d'origine----- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:06 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> I just did this (OS X) and the build was successful both times (on
> develop with 'main', on FLEX-33451 with 'release').
>
> EdB
>
>
>
> On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
> <we...@hotmail.com> wrote:
>>
>> Hi Justin,
>>
>> Couldn't you simply clone again the sdk, build on the develop branch,
>> checkout the 'FLEX-33451' and build release on it ?
>>
>> -Fred
>>
>> -----Message d'origine----- From: Justin Mclean
>> Sent: Wednesday, March 27, 2013 8:11 AM
>> To: dev@flex.apache.org
>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>
>>
>> Hi,
>>
>>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>>> have a Falcon flexTasks.jar in ant/lib?
>>
>>
>> Is there an easy way to tell which one it's using? I have flexTasks.jar
>> in
>> both places.
>>
>> Thanks,
>> Justin
>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Erik de Bruin <er...@ixsoftware.nl>.
Running 'ant asdoc' gives me:
Buildfile: build.xml
asdoc:
clean:
doc:
[asdoc] Loading configuration file
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/flex-config.xml
[asdoc] /Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/airspark/src/spark/components/WindowedApplication.as:
Error: Can not resolve a multiname reference unambiguously.
spark.components:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/experimental/src/spark/components/Alert.as)
and mx.controls:Alert (from
/Users/erik/Documents/ApacheFlex/git/flex-sdk/frameworks/projects/mx/src/mx/controls/Alert.as)
are available.
[asdoc]
[asdoc] /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(100):
col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] return _interactiveChildrenCount;
[asdoc] ^
[asdoc]
[asdoc] /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(894):
col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] ++ _interactiveChildrenCount ;
[asdoc] ^
[asdoc]
[asdoc] /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(898):
col: 7 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] -- _interactiveChildrenCount ;
[asdoc] ^
[asdoc]
[asdoc] /Users/erik/Documents/ApacheFlex/git/flex-tlf/textLayout/src/flashx/textLayout/elements/ParagraphElement.as(903):
col: 11 Error: Ambiguous reference to _interactiveChildrenCount.
[asdoc]
[asdoc] return _interactiveChildrenCount != 0 ;
[asdoc] ^
[asdoc]
BUILD FAILED
/Users/erik/Documents/ApacheFlex/git/flex-sdk/build.xml:477: The
following error occurred while executing this line:
/Users/erik/Documents/ApacheFlex/git/flex-sdk/asdoc/build.xml:58:
asdoc task failed.
HTH,
EdB
On Wed, Mar 27, 2013 at 10:15 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Did you tried the asdoc target for the experimental project ?
>
> I deactivated it in the release to be able to continue to build and see if
> there wasn't any other errors, to try it you should run the asdoc target
> directly from the experimental lib itself.
>
> Thanks,
> -Fred
>
> -----Message d'origine----- From: Erik de Bruin
> Sent: Wednesday, March 27, 2013 10:06 AM
>
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
> I just did this (OS X) and the build was successful both times (on
> develop with 'main', on FLEX-33451 with 'release').
>
> EdB
>
>
>
> On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
> <we...@hotmail.com> wrote:
>>
>> Hi Justin,
>>
>> Couldn't you simply clone again the sdk, build on the develop branch,
>> checkout the 'FLEX-33451' and build release on it ?
>>
>> -Fred
>>
>> -----Message d'origine----- From: Justin Mclean
>> Sent: Wednesday, March 27, 2013 8:11 AM
>> To: dev@flex.apache.org
>> Subject: Re: asdoc - Release build broken (was: Release build broken)
>>
>>
>> Hi,
>>
>>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>>> have a Falcon flexTasks.jar in ant/lib?
>>
>>
>> Is there an easy way to tell which one it's using? I have flexTasks.jar in
>> both places.
>>
>> Thanks,
>> Justin
>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Did you tried the asdoc target for the experimental project ?
I deactivated it in the release to be able to continue to build and see if
there wasn't any other errors, to try it you should run the asdoc target
directly from the experimental lib itself.
Thanks,
-Fred
-----Message d'origine-----
From: Erik de Bruin
Sent: Wednesday, March 27, 2013 10:06 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
I just did this (OS X) and the build was successful both times (on
develop with 'main', on FLEX-33451 with 'release').
EdB
On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Hi Justin,
>
> Couldn't you simply clone again the sdk, build on the develop branch,
> checkout the 'FLEX-33451' and build release on it ?
>
> -Fred
>
> -----Message d'origine----- From: Justin Mclean
> Sent: Wednesday, March 27, 2013 8:11 AM
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
>
> Hi,
>
>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>> have a Falcon flexTasks.jar in ant/lib?
>
> Is there an easy way to tell which one it's using? I have flexTasks.jar in
> both places.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Erik de Bruin <er...@ixsoftware.nl>.
I just did this (OS X) and the build was successful both times (on
develop with 'main', on FLEX-33451 with 'release').
EdB
On Wed, Mar 27, 2013 at 8:42 AM, Frédéric THOMAS
<we...@hotmail.com> wrote:
> Hi Justin,
>
> Couldn't you simply clone again the sdk, build on the develop branch,
> checkout the 'FLEX-33451' and build release on it ?
>
> -Fred
>
> -----Message d'origine----- From: Justin Mclean
> Sent: Wednesday, March 27, 2013 8:11 AM
> To: dev@flex.apache.org
> Subject: Re: asdoc - Release build broken (was: Release build broken)
>
>
> Hi,
>
>> For me, it is using the one in lib, not in ant/lib. Is it possible you
>> have a Falcon flexTasks.jar in ant/lib?
>
> Is there an easy way to tell which one it's using? I have flexTasks.jar in
> both places.
>
> Thanks,
> Justin
--
Ix Multimedia Software
Jan Luykenstraat 27
3521 VB Utrecht
T. 06-51952295
I. www.ixsoftware.nl
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi Justin,
Couldn't you simply clone again the sdk, build on the develop branch,
checkout the 'FLEX-33451' and build release on it ?
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Wednesday, March 27, 2013 8:11 AM
To: dev@flex.apache.org
Subject: Re: asdoc - Release build broken (was: Release build broken)
Hi,
> For me, it is using the one in lib, not in ant/lib. Is it possible you
> have a Falcon flexTasks.jar in ant/lib?
Is there an easy way to tell which one it's using? I have flexTasks.jar in
both places.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> For me, it is using the one in lib, not in ant/lib. Is it possible you have a Falcon flexTasks.jar in ant/lib?
Is there an easy way to tell which one it's using? I have flexTasks.jar in both places.
Thanks,
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Alex Harui <ah...@adobe.com>.
I don't think so. I don't have a compiler.jar in my sdk tree and themes
build.
The build is failing on flexTasks.tasks loading classes from one of the two
flexTasks.jar you see in the build.xml. For me, it is using the one in lib,
not in ant/lib. Is it possible you have a Falcon flexTasks.jar in ant/lib?
On 3/26/13 11:04 PM, "Justin Mclean" <ju...@classsoftware.com> wrote:
> Hi,
>
>> If Justin doesn't help you with asdoc, I will try to find time tomorrow.
>
> My build is still broken (unable to build the themes) so unable to help. Are
> you sure a falcon dependancy hasn't accidentally got into the SDK release
> build - that's the only reference to compiler.jar I could find.
>
> Justin
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: asdoc - Release build broken (was: Release build broken)
Posted by Justin Mclean <ju...@classsoftware.com>.
Hi,
> If Justin doesn't help you with asdoc, I will try to find time tomorrow.
My build is still broken (unable to build the themes) so unable to help. Are you sure a falcon dependancy hasn't accidentally got into the SDK release build - that's the only reference to compiler.jar I could find.
Justin
Re: asdoc - Release build broken (was: Release build broken)
Posted by Alex Harui <ah...@adobe.com>.
I had to pull before I could see your branch. Once I checked it out, the
build script ran fine on my Mac. If Justin doesn't help you with asdoc, I
will try to find time tomorrow.
On 3/26/13 10:50 AM, "Frédéric THOMAS" <we...@hotmail.com> wrote:
> Ok, I double checked, all good for the release except the build number and
> the asdoc, so, TLF, empty.properties and .gitignore are ok.
>
> If someone wants to give a hand for the asdoc, run the asdoc target of the
> experimental build after you built the sdk.
> Once fixed, uncomment <ant dir="${basedir}/projects/experimental"
> target="doc" /> in framework.build.xml, commit prepending the message with
> the jira issue id and push it, I'll merge later, after we'll find the best
> way for the build number.
>
> If you want to work on, I created a remote branch 'FLEX-33451' for
> https://issues.apache.org/jira/browse/FLEX-33451
>
> I assume you're on flex-sdk, whatever the branch you're currently on.
>
> Before to check it out:
> git stash -u "my current work"
>
> To check it out:
> git checkout -b origin/FLEX-33451
>
> To see what I did (I assume, you set your .gitconfig as described on the
> wiki)
> git hist
>
> To see what there's inside a particular commit:
> git show <HASH> (can be obtain form the previous command)
>
> If you need to update from origin/develop to FLEX-33451:
> git pull --rebase origin develop
>
> To add a file to the staged area:
> git add <My_FILE>
>
> To add all the current files to the staged area:
> git add .
>
> To commit:
> git pull --rebase (if I just pushed the same files than the ones you're
> trying to commit, resolve the conflicts)
> git commit -m "FLEX-33451:<MESSAGE>"
>
> To push:
> git push
>
> To go back on the branch you was before and the same working tree / index:
> git stash -u "release" (if you've got uncommitted files/untracked files
> which you can check with git status)
> git checkout <BRANCH>
> git stash apply "my current work"
>
> Thanks,
> -Fred
>
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
Re: asdoc - Release build broken (was: Release build broken)
Posted by Frédéric THOMAS <we...@hotmail.com>.
Ok, I double checked, all good for the release except the build number and
the asdoc, so, TLF, empty.properties and .gitignore are ok.
If someone wants to give a hand for the asdoc, run the asdoc target of the
experimental build after you built the sdk.
Once fixed, uncomment <ant dir="${basedir}/projects/experimental"
target="doc" /> in framework.build.xml, commit prepending the message with
the jira issue id and push it, I'll merge later, after we'll find the best
way for the build number.
If you want to work on, I created a remote branch 'FLEX-33451' for
https://issues.apache.org/jira/browse/FLEX-33451
I assume you're on flex-sdk, whatever the branch you're currently on.
Before to check it out:
git stash -u "my current work"
To check it out:
git checkout -b origin/FLEX-33451
To see what I did (I assume, you set your .gitconfig as described on the
wiki)
git hist
To see what there's inside a particular commit:
git show <HASH> (can be obtain form the previous command)
If you need to update from origin/develop to FLEX-33451:
git pull --rebase origin develop
To add a file to the staged area:
git add <My_FILE>
To add all the current files to the staged area:
git add .
To commit:
git pull --rebase (if I just pushed the same files than the ones you're
trying to commit, resolve the conflicts)
git commit -m "FLEX-33451:<MESSAGE>"
To push:
git push
To go back on the branch you was before and the same working tree / index:
git stash -u "release" (if you've got uncommitted files/untracked files
which you can check with git status)
git checkout <BRANCH>
git stash apply "my current work"
Thanks,
-Fred