incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject RE: [MENTOR] Source code layout for committers
Date Tue, 07 Aug 2012 19:44:48 GMT

> -----Original Message-----
> From: Greg Reddin [mailto:gredbug@gmail.com]
> Sent: Tuesday, August 07, 2012 12:30 PM
> To: flex-dev@incubator.apache.org
> Subject: Re: [MENTOR] Source code layout for committers
> 
> On Tue, Aug 7, 2012 at 1:22 PM, Alex Harui <aharui@adobe.com> wrote:
> > While that's fine for the vast majority of users that are just
> consumers of the SDK, my question is about the committers and other
> folks who want to make changes to the SDK.  Is there any Apache policy
> that requires committers to have "clean" source code layouts such that
> no non-compatible licensed files are mixed into the source tree?  Or do
> folks just have to be careful that they don't accidentally modify or
> check in something they shouldn't?
> 
> Apache can't control what committers do with the code once they check
> it out to their machines. If they want to fold non-compatible code
> into the tree they checked out they can -- so long as they don't
> commit any of it back to the repo.
> 
> I think we need a better story for this though. It seems dangerous to
> me to have a working copy of a source code tree with stuff folded into
> it that you don't want to commit. How hard would it be to set up some
> svn:ignore properties for the files that get folded in? Is that enough
> to ensure they don't get committed (at least that would ensure they
> don't get committed by mistake without some kind of warning)? That's
> basically what we do with Maven projects to keep from checking in the
> target directory, for example.
> 
> Greg

I think there is probably a better story.  I hadn't thought of svn:ignore,
we can certainly explore that, but also, in theory it should be possible
to use Flash Builder to work on Apache Flex, but it just wouldn't
recognize the results as an Apache Flex SDK.  Which would hopefully be
fine when you're in the mode of changing the SDK.  Then when you want to 
build apps on top of the SDK, you can run the build and maybe some
other script that copies your new libraries out to some folder tree that
does look like an SDK to Flash Builder.  I will explore these options
now that I know at someone else thinks something like this is worth
looking into.


Alex Harui
Flex SDK Developer
Adobe Systems Inc.
Blog: http://blogs.adobe.com/aharui


Mime
View raw message