flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kessler CTR Mark J" <mark.kessler....@usmc.mil>
Subject RE: TLF Issue (was Re: SVN to Git migration in progress)
Date Thu, 14 Mar 2013 09:53:22 GMT
Would this be why I got a failed build on the text layout portion of the git develop branch?

    [compc] Loading configuration file D:\Development\Flex\Flex-SDK\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] D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\compile-
config.xml(58): Error: unable to open 'D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout/3.0.33/manifest.xml'
    [compc]     </include-file>

D:\Development\Flex\Flex-SDK\build.xml:361: The following error occurred while executing this
D:\Development\Flex\Flex-SDK\frameworks\build.xml:91: The following error occurred while executing
this line:
D:\Development\Flex\Flex-SDK\frameworks\build.xml:387: The following error occur red while
executing this line:
D:\Development\Flex\Flex-SDK\frameworks\projects\textLayout\build.xml:179: compc task failed.

Total time: 1 minute 3 seconds


-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com] 
Sent: Tuesday, March 12, 2013 1:00 PM
To: dev@flex.apache.org
Subject: TLF Issue (was Re: SVN to Git migration in progress)

Well, I'm still learning about Git, but it looks like we have to resolve the
TLF svn:externals issue and it isn't clear that links in the file system are
going to work on Windows and are the "correct" solution.

Does anybody actually know the answer?  Or do we just have to figure it out
on our own.

One thing I saw on the internet says that you can just pull from the other
project if there aren't any conflicts with file names.  Would that work?

Were submodules and/or subtrees ruled out?  It appeared from the Git manual
that an update of the main project doesn't automatically update the
submodules, so that will leave us open to making mistakes staying in sync.

IMO, we should re-think why we had TLF as an svn:external.  I think we just
did it so the build scripts wouldn't have to change that much from the Adobe
days, so we could find the source where we were used to seeing it.

But looking not to far into the future, our releases may become a
composition of stuff from the various Apache Flex "sub-projects".  For
example, the FlexJS stuff is compositing things from the old Flex SDK, the
Falcon project and the ASJS project.

So, given that we might have sync issues in Git even with submodules, maybe
the answer is to rework the release scripts to composite from multiple


On 3/12/13 3:59 AM, "Frédéric THOMAS" <webdoublefx@hotmail.com> wrote:

> Still that :)
> I guess on windows I should find a way to to a hard link, right ?
> -Fred
> -----Message d'origine-----
> From: Justin Mclean
> Sent: Tuesday, March 12, 2013 11:26 AM
> To: dev@flex.apache.org
> Subject: Re: SVN to Git migration in progress
> Hi,
> Well the good news is other than the flex-sdk git repo compiles a usable SDK
> if you work around the TLF issue.
> Justin 

Alex Harui
Flex SDK Team
Adobe Systems, Inc.

View raw message