Well I was simply assuming that IF Adobe would say: "Nah ... We don't want to
work ourselves into deploying stuff at Maven Central, but if you want you guys
at Apache could do that for us, if you want." Then it would be really stupid
for Apache to say: "It's not the Apache way to deploy third party stuff",
because the benefits for Apache flex would be great. I have to admit that I
don't know how do actually deploy stuff there, but I think it's manageable.
Velo (Flexmojos Head) seems to have managed to deploy the playerglobals there
for quite some time (Even if I would vote for a different groupId:
"com.adobe.flash:playerglobal:{player-version} instead of
"com.adobe.flex.framework:playerglobal:{flex-sdk-version}-{player-version}).
Chris
-----Ursprüngliche Nachricht-----
Von: Dave Fisher [mailto:dave2w...@comcast.net]
Gesendet: Mittwoch, 27. Juni 2012 23:37
An: flex-dev@incubator.apache.org
Betreff: Re: AW: AW: AW: Distinguishing Adobe from Apache SDKs?
On Jun 27, 2012, at 10:21 AM, Alex Harui wrote:
>
>
>
> On 6/27/12 10:00 AM, "christofer.d...@c-ware.de"
> <christofer.d...@c-ware.de>
> wrote:
>
>> Hi,
>>
>> I think you got me wrong on the company repo thing.
>> The repo is not public. It's just for usage inside the company. So I
>> don't think this should be a problem.
>> It's just something everybody will have to do over and over again.
> I will check, but I think that even internal company re-deployment
> requires an agreement from Adobe.
>
> What I'm more curious to hear from others on the list is whether this
> is going to be a hurdle for adoption. If having Adobe publish
> Maven-friendly stuff is going to make it tons easier, then I will push to
> make it happen.
>>
>> And I was suggesting to volunteer to publish the artifacts for Apache
>> ... so if they have something new Apache could offer their services
>> to do it for them, if they want this to happen.
> Did you mean "Apache" in the first sentence? I was expecting that
> part of Apache Flex's release process would eventually include
> deploying Maven-friendly stuff.
Lots of Apache projects deploy releases to Maven. One example is Apache POI.
Those scripts are in svn and the build, but are purposefully undocumented on
the site.
I don't think that Apache will publish third party artifacts into Maven for
others. Others will need to do that and then the project can consume those. POI
does handle dependencies with maven downloads within its build.xml.
<!-- the repository to download jars from -->
<property name="repository.m2" value="http://repo1.maven.org"/>
...
<property name="ooxml.xmlbeans.jar"
location="${ooxml.lib}/xmlbeans-2.3.0.jar"/>
<property name="ooxml.xmlbeans.url"
value="${repository.m2}/maven2/org/apache/xmlbeans/xmlbeans/2.3.0/xmlbeans-2.3.0.jar"/>
<property name="ooxml.jsr173.jar"
location="${ooxml.lib}/stax-api-1.0.1.jar"/>
<property name="ooxml.jsr173.url"
value="${repository.m2}/maven2/stax/stax-api/1.0.1/stax-api-1.0.1.jar"/>
...
<antcall target="downloadfile">
<param name="sourcefile" value="${ooxml.xmlbeans.url}"/>
<param name="destfile" value="${ooxml.xmlbeans.jar}"/>
</antcall>
<antcall target="downloadfile">
<param name="sourcefile" value="${ooxml.jsr173.url}"/>
<param name="destfile" value="${ooxml.jsr173.jar}"/>
</antcall>
This is an FYI - I'm not sure if this fits the current build and wouldn't want
to delay any release if it doesn't. But if someone is playing with Maven...
Regards,
Dave
>>
>
> --
> Alex Harui
> Flex SDK Team
> Adobe Systems, Inc.
> http://blogs.adobe.com/aharui
>
