On Thu, Jan 28, 2010 at 3:20 PM, David Hoffer <[email protected]> wrote:
> Thanks for the detailed reply.
>
> I'd have to think through all the issues to come with optimal plan. But my
> first thoughts do something like this...
>
> Flexmojos overloaded the maven scope concept to mean something different,
> in the case of rsl scope it means get a different artifact type. I'm not
> sure I would have done that. I think I'd elevate rsl to a type (or possibly
> classifier) because you might want different scopes for rsls. For instance
> I might want to use an rsl with test scope, etc.
>
Doing on type would allow people to add a library as rsls and as internal at
same time, which is not good. Also it is complicated deal with a type that
doesn't match the artifact file extension.
Classifier also had the same issue of duplicated entries, and the artifact
should exist.... so not something easy to deal with.
Ideally I won't use scope also... I would prefer something like...
<dependency>
<groupId>com.adobe.flex.framework</groupId>
<artifactId>framework</artifactId>
<version>3.2.0.3958</version>
<type>swc</type>
<properties>
<flex.policy>caching</flex.policy>
</properties>
</dependency>
But since this is not possible, can't do =/
> Idea. Flexmojos could add support for rsl project type. Then if swc or
> swf type is specified it builds just that, but if rsl is specified then it
> builds swc & rsl. Then subsequent projects can specify a dependency type of
> swc or rsl. If swc it uses it as normal (merged/internal/etc) but if rsl is
> specified it adds an rsl dependency to the project/component with full maven
> support for transitive dependencies. (I think of the flex rsls as being
> about equivalent to java jars.)
>
> I don't think flexmojos has to do any/much 'majic'. It should fail the
> build if what is asked for does not exist, just like if I asked for a java
> jar with classifier...it will fail if it doesn't exist.
>
> I'd love to see a feature like this if you can make it work :)
>
I wouldn't spend time on doing this.... if maven 3 allow me properties I may
think on doing, otherwise no.
>
> -Dave
>
>
>
> On Thu, Jan 28, 2010 at 9:58 AM, Marvin Froeder <[email protected]> wrote:
>
>>
>>
>> On Thu, Jan 28, 2010 at 2:37 PM, David Hoffer <[email protected]> wrote:
>>
>>> We could declare all rsls at the application level but then this requires
>>> us to manually add all the transitive dependencies. This can get hard to
>>> manage. How do you know what all your transitive dependencies are? This is
>>> one of the big features of maven that does not exist for flex.
>>>
>>
>> Well, maven doesn't do this. You wanna, sometimes, magically the external
>> scope dependencies become to be rsl. Maven don't do this. That is for sure.
>>
>>
>>>
>>> In maven you are only supposed to have to declare your direct
>>> dependencies, as you know what these are, its easy/natural to do. However
>>> you often times do not know what your transitive dependencies are and that
>>> is the beauty of maven...it figures this out for you. If it doesn't work
>>> for flex, I'm questioning the virtue of the RSL approach.
>>>
>>> In the ideal case, maven would allow me to specify my swc dependencies as
>>> rsl then in the swf if I reference the swc with rsl scope it would find all
>>> its rsl dependencies. This feature would allow maven to fully support
>>> transitive dependencies just like maven does for java/jars.
>>>
>>
>> This can be a wrong approach, for instance your swc could be build with
>> something merged or included.... if flexmojos just decide to change the
>> transitive dependencies scopes it will cause problems. Best case scenario
>> something will be downloaded twice.
>>
>> Flex/maven does support transitive dependency as maven does. And exactly
>> that. It doesn't change the scopes because it may be better....
>>
>> Also, who can ensure the transitive dependency has the swf?! If it doesn't
>> have rsl what should flexmojos do? Fail the build? Create one? Rechange the
>> scope and use merged? Or internal? Or just ignore the library?
>>
>> It think it is possible to build something that does that.... but it is an
>> entire new dependency management thing.... built over maven ok, but still a
>> new deal.
>>
>> Giving this a second thought it is a really good idea, and all this
>> questions can come with a default reply and make it configurable so users
>> can change the default behavior.
>>
>> In the end, everything is possible, the only issue I see is who is gona do
>> that?
>>
>>
>> VELO
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "Flex Mojos" group.
>> To post to this group, send email to [email protected]
>> To unsubscribe from this group, send email to
>> [email protected]<flex-mojos%[email protected]>
>> For more options, visit this group at
>> http://groups.google.com/group/flex-mojos?hl=en?hl=en
>>
>> http://blog.flex-mojos.info/
>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Flex Mojos" group.
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]<flex-mojos%[email protected]>
> For more options, visit this group at
> http://groups.google.com/group/flex-mojos?hl=en?hl=en
>
> http://blog.flex-mojos.info/
>
--
You received this message because you are subscribed to the Google
Groups "Flex Mojos" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/flex-mojos?hl=en?hl=en
http://blog.flex-mojos.info/
