Hi,
I'm still getting to know some of this stuff, so I'd like someone more
experienced to try and explain :)
In the meantime, I think this has something to do with namespaces and
manifests. I'd say you need to add something like
<namespace uri="*library://ns.adobe.com/flex/spark*"
manifest="${basedir}/manifest_spark.**xml"/>
You can then copy the contents for manifest_spark.xml from manifest.xml
inside the airspark folder, for example (you should even be able to remove
most of the declarations there and still get it to compile).
As I said, this is just something for you to try, but better see if someone
else can chime in.
Let us know!
Cheers,
Chema
2012/12/15 Frédéric THOMAS <[email protected]>
> Hi,
>
> I'm about to check in the sources, before, I tried to compile via Ant,
> creating the build targets, as I don't know Ant/compc/mxmlc (generaly, I
> compile via maven), I'm facing an issue, <s:SolidColorStroke> can't be
> resolved as a component implementation, this is my ant target :
>
>
> <target name="compile" description="Compiles experimental.swc">
> <echo message="Compiling frameworks/libs/experimental.**swc"/>
>
> <!-- Load the <compc> task. We can't do this at the <project> level
> -->
> <!-- because targets that run before flexTasks.jar gets built would
> fail. -->
> <taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/lib/**
> flexTasks.jar"/>
> <compc fork="true"
> include-classes="**ExperimentalClasses"
> output="${FLEX_HOME}/**frameworks/libs/experimental.**swc"
> resource-bundle-list="${**basedir}/bundles.properties">
> <jvmarg line="${compc.jvm.args}"/>
> <namespace
> uri="http://flex.apache.org/**experimental/ns<http://flex.apache.org/experimental/ns>"
> manifest="${basedir}/manifest.**xml"/>
>
> <include-namespaces>http://**flex.apache.org/experimental/**ns<http://flex.apache.org/experimental/ns>
> </include-namespaces>
> <source-path path-element="${basedir}/src"/**>
> <library-path />
> <external-library-path dir="${env.PLAYERGLOBAL_HOME}"**>
> <include name="${playerglobal.version}/**
> playerglobal.swc"/>
> </external-library-path>
> <external-library-path dir="${FLEX_HOME}/frameworks/**libs">
> <include name="framework.swc"/>
> <include name="spark.swc"/>
> </external-library-path>
> <include-file name="experimental.css"
> path="${basedir}/defaults.css"**/>
> <locale/>
> <keep-as3-metadata name="SkinPart"/>
> <accessible>true</accessible>
> <show-deprecation-warnings>**false</show-deprecation-**
> warnings>
> <warn-no-constructor>false</**warn-no-constructor>
> </compc>
> </target>
>
>
> Because SolidColorStroke is defined in mx.graphics, I thought may be
> include mx/mx.swc as external library path but it didn't work, a help would
> be very appreciated.
>
>
> - Fred
>
> -----Message d'origine----- From: Alex Harui
> Sent: Wednesday, December 12, 2012 5:29 PM
>
> To: [email protected]
> Subject: Re: New Spark components
>
> We've been putting them in SVN because we did so at Adobe. I know folks
> don't like it, but when the project setup isn't trivial (you need dependent
> projects) I think it is helpful. The pain point is you have to hand edit
> the file before submitting to make sure it doesn't have absolute paths in
> it.
>
>
> On 12/12/12 4:55 AM, "Frédéric THOMAS" <[email protected]> wrote:
>
> Thank's Nick
>>
>> - Fred
>>
>> -----Message d'origine-----
>> From: Nicholas Kwiatkowski
>> Sent: Wednesday, December 12, 2012 1:51 PM
>> To: [email protected]
>> Subject: Re: New Spark components
>>
>> I was pretty sure we were trying to avoid them when possible...
>>
>> -Nick
>>
>> On Wed, Dec 12, 2012 at 6:25 AM, Frédéric THOMAS
>> <[email protected]>**wrote:
>>
>> Hi,
>>>
>>> As it is not in my habit to commiting files dependent on specific tools
>>> like Eclipse but because I saw some of them in the develop branch and
>>> there
>>> are provided in the Bogdan's zip, I was wondering if I should still
>>> include
>>> them or not, what the policy ?
>>>
>>> - Fred
>>>
>>> -----Message d'origine----- From: Frédéric THOMAS
>>> Sent: Wednesday, December 12, 2012 11:42 AM
>>>
>>> To: [email protected]
>>> Subject: Re: New Spark components
>>>
>>> Oups, I missed this message.
>>>
>>> Yes, sure, I do that.
>>>
>>> - Fred
>>> -----Message d'origine----- From: Alex Harui
>>> Sent: Friday, December 07, 2012 8:25 AM
>>> To: [email protected]
>>> Subject: Re: New Spark components
>>>
>>> Frédéric,
>>>
>>> Do you have time to work on Bogdan's contribution?
>>>
>>> -Alex
>>>
>>>
>>> On 12/5/12 10:50 PM, "Bogdan DINU" <[email protected]> wrote:
>>>
>>> Hi everyone,
>>>
>>>>
>>>> the answer from the secretary was "This message acknowledges receipt of
>>>> your ICLA, which has been filed in the Apache Software Foundation
>>>> records. If you have been invited as a committer, please advise the
>>>> project
>>>> PMC that your ICLA has been filed."
>>>>
>>>> Just letting you know that ICLA was recorded :)
>>>>
>>>> Best regards,
>>>> Bogdan DINU
>>>>
>>>> On Mon, Dec 3, 2012 at 6:40 PM, Alex Harui <[email protected]> wrote:
>>>>
>>>> Hi Bogdan,
>>>>
>>>>>
>>>>> Thanks. We have to wait for the ICLA to be recorded before we take
>>>>> further
>>>>> action on this side.
>>>>>
>>>>> -Alex
>>>>>
>>>>>
>>>>> On 12/2/12 11:20 PM, "Bogdan DINU" <[email protected]> wrote:
>>>>>
>>>>> Hello everyone,
>>>>>
>>>>>>
>>>>>> as instructed, I have sent the ICLA to secretary and created JIRA
>>>>>> issue
>>>>>> (improvement) - Flex - 33284<
>>>>>>
>>>>>>
>>>>>> https://issues.apache.org/****jira/browse/FLEX-33284<https://issues.apache.org/**jira/browse/FLEX-33284>
>>>>> <https:/**/issues.apache.or <https://issues.apache.or>
>>>>> g/jira/browse/FLEX-33284>
>>>>>
>>>>>>
>>>>>>
>>>>> .
>>>>>>
>>>>>> Best regards,
>>>>>> Bogdan
>>>>>>
>>>>>> On Tue, Nov 27, 2012 at 3:58 PM, Frédéric THOMAS
>>>>>> <[email protected]>****wrote:
>>>>>>
>>>>>> Hi Bogdan,
>>>>>>
>>>>>>>
>>>>>>> I sent you a personnal email with the entire process too, I'll be
>>>>>>> away
>>>>>>>
>>>>>>> for
>>>>>>
>>>>>
>>>>> 2-3 days, I suppose Erik or someone will take care of your donation.
>>>>>>
>>>>>>>
>>>>>>> Thank you for your contribution.
>>>>>>>
>>>>>>> - Fred.
>>>>>>>
>>>>>>> -----Message d'origine----- From: Bogdan DINU
>>>>>>> Sent: Tuesday, November 27, 2012 11:46 AM
>>>>>>>
>>>>>>> To: [email protected]
>>>>>>> Subject: Re: New Spark components
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I own the components - even if I have used them in a commercial
>>>>>>> project,
>>>>>>> the owners of it know that they are open source (aside with a
>>>>>>> Robotlegs
>>>>>>> alike framework which they wanted to support being opened).
>>>>>>>
>>>>>>> I have no idea what the acronyms like IIRC or ICLA means, but I'm
>>>>>>> definitely interested in donating those components - since I've
>>>>>>> brought
>>>>>>> them to the community attention in the first place.
>>>>>>>
>>>>>>> Looking forward to know about the necessary steps.
>>>>>>>
>>>>>>> Best regards,
>>>>>>> Bogdan
>>>>>>>
>>>>>>>
>>>>>>> On Tue, Nov 27, 2012 at 2:17 AM, Frédéric THOMAS <
>>>>>>>
>>>>>>> [email protected]>
>>>>>>
>>>>>
>>>>> **wrote:
>>>>>>
>>>>>>>
>>>>>>> Ok, I just sent him an email with the all process, waitting now for
>>>>>>> its
>>>>>>>
>>>>>>> feedback.
>>>>>>>>
>>>>>>>> Thank's guys.
>>>>>>>>
>>>>>>>>
>>>>>>>> -----Message d'origine----- From: Alex Harui
>>>>>>>> Sent: Tuesday, November 27, 2012 1:13 AM
>>>>>>>>
>>>>>>>> To: [email protected]
>>>>>>>> Subject: Re: New Spark components
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On 11/26/12 4:00 PM, "Frédéric THOMAS" <[email protected]>
>>>>>>>>
>>>>>>>> wrote:
>>>>>>>
>>>>>>
>>>>>
>>>>>> Hi,
>>>>>>>>
>>>>>>>>
>>>>>>>> Either way, we do have to verify the ownership of all of this work
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> How does it happen ?
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> There used to be a checkbox on each JIRA issue where the patch
>>>>>>>>>
>>>>>>>>> submitter
>>>>>>>>
>>>>>>>
>>>>> had
>>>>>>
>>>>>>> to indicate that they owned their contribution. I think that went
>>>>>>>>
>>>>>>>> away,
>>>>>>>
>>>>>>
>>>>> so
>>>>>>
>>>>>>> if it isn't there anymore, then I guess we just have to ask them.
>>>>>>>>
>>>>>>>> You should also review the code before committing to the code base
>>>>>>>> and
>>>>>>>> handle any copyright notices according to Apache Legal. And, of
>>>>>>>>
>>>>>>>> course,
>>>>>>>
>>>>>>
>>>>> in
>>>>>>
>>>>>>> your review, if you notice any obvious IP violation, you should stop
>>>>>>>>
>>>>>>>> and
>>>>>>>
>>>>>>
>>>>> address it before committing it.
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> - Fred.
>>>>>>>>
>>>>>>>>
>>>>>>>>> -----Message d'origine-----
>>>>>>>>> From: Alex Harui
>>>>>>>>> Sent: Tuesday, November 27, 2012 12:53 AM
>>>>>>>>> To: [email protected]
>>>>>>>>> Subject: Re: New Spark components
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 11/26/12 3:01 PM, "Justin Mclean" <[email protected]>
>>>>>>>>>
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>
>>>>>
>>>>>> Hi,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 8 months ago, Bogdan presented missing spark components[1] he did
>>>>>>>>>>
>>>>>>>>>> but
>>>>>>>>>
>>>>>>>>
>>>>> at
>>>>>>
>>>>>>>
>>>>>>>>>> this
>>>>>>>>>>
>>>>>>>>>>> time there was so much excitement on the ML, it has not been so
>>>>>>>>>>> noticed,
>>>>>>>>>>> I
>>>>>>>>>>> wanted to bring to your attention he wanted to contribute them,
>>>>>>>>>>>
>>>>>>>>>>> what¹s
>>>>>>>>>>
>>>>>>>>>
>>>>> the
>>>>>>
>>>>>>> process to integrate them into the SDK ?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> Has he signed a ICLA? [1] Do we know that it's his own work or
>>>>>>>>>>>
>>>>>>>>>> was it
>>>>>>>>>> work
>>>>>>>>>> done for someone else/a company?
>>>>>>>>>>
>>>>>>>>>> IIRC, an ICLA is not mandatory for patches, but is a good idea
>>>>>>>>>> for
>>>>>>>>>>
>>>>>>>>>> significant contributions. Either way, we do have to verify the
>>>>>>>>> ownership
>>>>>>>>> of all of this work.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> From a quick glance at the code I wouldn't see an issue with these
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> been
>>>>>>>>>
>>>>>>>>
>>>>> added
>>>>>>
>>>>>>> to the experimental namespace and then moved into one of the other
>>>>>>>>>> namespaces
>>>>>>>>>> once they be in use for a while / have full tests.
>>>>>>>>>>
>>>>>>>>>> Thanks,
>>>>>>>>>> Justin
>>>>>>>>>>
>>>>>>>>>> 1.
>>>>>>>>>> http://www.apache.org/********licenses/icla.txt<http://www.apache.org/******licenses/icla.txt>
>>>>>>>>>> <http://www.**apache.org/** <http://www.apache.org/**>
>>>>>>>>>> **licenses/icla.txt>
>>>>>>>>>> <
>>>>>>>>>>
>>>>>>>>>> http://www.apache.org/**licens
>>>>>>>>>
>>>>>>>>
>>>>> es/icla.txt>
>>>>>>
>>>>>>> <http://www.**apache.org/****licenses/icla.txt<http://apache.org/**licenses/icla.txt>
>>>>>>>>>> <http://**apache.org/license <http://apache.org/license>
>>>>>>>>>> s/icla.txt>
>>>>>>>>>> <
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> http://www.apache.org/****licenses/<http://www.apache.org/**licenses/><
>>>>>>>>> http://www.apache.org/**licenses/<http://www.apache.org/licenses/>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>> icla.txt>
>>>>>>
>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Alex Harui
>>>>>>>> Flex SDK Team
>>>>>>>> Adobe Systems, Inc.
>>>>>>>> http://blogs.adobe.com/aharui
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>> http://www.badu.ro
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>> Alex Harui
>>>>> Flex SDK Team
>>>>> Adobe Systems, Inc.
>>>>> http://blogs.adobe.com/aharui
>>>>>
>>>>>
>>>>>
>>>>>
>>>> --
>>> Alex Harui
>>> Flex SDK Team
>>> Adobe Systems, Inc.
>>> http://blogs.adobe.com/aharui
>>>
>>>
>>>
>>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
>
