Yes, that is correct. I understand that the redistribution limitation may be somewhat inconvenient since the tasks are a separate deliverable from the SDK, but as the long-term goal is for them to be included in the SDK it causes us precedence problems if these are redistributable now (don't ask me to figure out how to not make our lawyers twitchy).
If this is causing undue hardship in your model contact me off-list and I can see what we can come up with. Matt ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Anatole Tartakovsky Sent: Sunday, January 28, 2007 11:44 AM To: [email protected] Subject: RE: [flexcomponents] Export Components via Ant Matt, Thank you for explanation. Here is the case I am trying to understand. We have plugins that are distributed to our clients and are also prepared for commercial distribution. One of them - flex2ant - converts development settings into ant/maven build file among other things. We would like to give an option of Ant tasks for compiler stage. If I read your explanation correctly : 1.we may not distribute jar file 2. we may build somewhat extended jar file ourselves and distribute that within our plugins. We will not distribute SDK or shell compiler. Thank you, Anatole ----- Original Message ----- From: Matt Chotin <mailto:[EMAIL PROTECTED]> To: [email protected] <mailto:[email protected]> Sent: Friday, January 26, 2007 5:29 PM Subject: [SPAM] RE: [flexcomponents] Export Components via Ant Also, if you make modifications you would be allowed to distribute those modifications provided all the licensing restrictions (e.g., copyright) are followed. ________________________________ From: Matt Chotin Sent: Friday, January 26, 2007 2:28 PM To: '[email protected]' <mailto:'[email protected]'> Subject: RE: [flexcomponents] Export Components via Ant Hi, #1 matches with our SDK license, and these tools are meant to be used with the SDK. Since the SDK cannot be redistributed, there isn't much value in redistributing the tasks on their own. #2 is actually incorrect. You are allowed to modify the source as long as you retain copyright notices, the phrasing is in the main section of 2, in the (ii) section. 2.1 states that modification/reverse engineering that doesn't fall under 2 (ii) is not allowed. HTH, Matt ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Anatole Tartakovsky Sent: Thursday, January 25, 2007 7:32 PM To: [email protected] Subject: Re: [flexcomponents] Export Components via Ant Very interesting. Few questions on the license that is unusual for Labs section: 1. no redistribution rights which makes it difficult to be used within consulting projects or products - very strange for such a generic task that will most benefit SDK/command line users 2. No reverse engineering clause on the product that comes with complete source Is there a chance that the wrong license file was included? Thanks, Anatole ----- Original Message ----- From: dorkie dork from dorktown <mailto:[EMAIL PROTECTED]> To: [email protected] <mailto:[email protected]> Sent: Thursday, January 25, 2007 8:51 PM Subject: Re: [flexcomponents] Export Components via Ant This was just posted on one of the adobe blogs. http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks <http://labs.adobe.com/wiki/index.php/Flex_Ant_Tasks> On 1/24/07, dorkie dork from dorktown <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: cool. thank you On 1/24/07, Darron J. Schall < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Have a look at one of the build scripts I wrote for the ActionScript 3.0 Libraries on Google Code: http://as3syndicationlib.googlecode.com/svn/trunk/build/ <http://as3syndicationlib.googlecode.com/svn/trunk/build/> The "lib" target is what you're looking for. If you need additional options, just run "compc -help" from the command line and follow the instructions for detailed help. -d dorkie dork from dorktown wrote: > > Is there an Ant build script that will export a component to an swc? I > have written what seems to be a very basic one that exports a mxml > component using a script file but it doesn't work with the flex-config > file. > > build.xml - > > <?xml version="1.0" ?> > <project default="main"> > <target name="main" depends="compile" description="Main target"> > <echo> > Building the component for you > </echo> > </target> > > <target name="compile" description="Compilation target"> > <exec command="compc -load-config Countdown-config.xml"/> > </target> > > </project> > > Countdown-config.xml - > > <?xml version="1.0"?> > <flex-config xmlns=" http://www.adobe.com/2006/flex-config <http://www.adobe.com/2006/flex-config> > <http://www.adobe.com/2006/flex-config <http://www.adobe.com/2006/flex-config> >"> > <compiler> > <source-path> > <path-element>.</path-element> > <path-element>C:\Documents and Settings\Judah\My > Documents\Flex Builder 2\Countdown</path-element> > </source-path> > <output>C:\Documents and Settings\Judah\My Documents\Flex > Builder 2\ComponentTester\swc\Countdown.swc</output> > </compiler> > > <include-classes> > <class>Countdown</class> > </include-classes> > </flex-config> > > >
