Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of cframpto@adobe.com designates
 64.18.1.183 as permitted sender)
From: Carol Frampton <cframpto@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Wed, 30 May 2012 14:53:09 -0700
Subject: [MENTOR]  source package questions 
Thread-Topic: [MENTOR]  source package questions 
Thread-Index: Ac0+rptzdIDzTRcmSCS8UvsJkNwk+w==
Message-ID: <CBEC0F05.15B52%cframpto@adobe.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.14.0.111121
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_CBEC0F0515B52cframptoadobecom_"
MIME-Version: 1.0

--_000_CBEC0F0515B52cframptoadobecom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Mentors,

As we attempt to lock down and actually arrive at a realistic release candi=
date we keep bumping into the "what is source" since we all know that the o=
fficial Apache release for a product consists of only source code.

From: http://www.apache.org/dev/release.html

The Apache Software Foundation produces open source software. All releases =
are in the form of the source materials needed to make changes to the softw=
are being released. In some cases, binary/bytecode packages are also produc=
ed as a convenience to users that might not have the appropriate tools to b=
uild a compiled version of the source. In all such cases, the binary/byteco=
de package must have the same version number as the source release and may =
only add binary/bytecode files that are the result of compiling that versio=
n of the source code release.

-------

1. Per Bertrand's suggestion, I just forked velocity and batik since we've =
made numerous changes to them.  (As an aside I think the devs that long ago=
 did the work did consider donating the changes back to Apache but it was d=
ecided not to do that.)  I merged our changes into the source distributions=
 for velocity and batik and changed the packages to org.apache.flex.forks.v=
elocity/batik.  Each of these source distributions include numerous jars, d=
iscounting the ones in the test directories.

~/dev/trunk/modules/thirdparty/velocity$ find . -name "*.jar" -print
./build/lib/antlr-runtime.jar
./build/lib/bcel-5.0rc1.jar
./build/lib/commons-collections.jar
./build/lib/fop-bin-0_17_0.jar
./build/lib/jdom-b9.jar
./build/lib/junit-3.7.jar
./build/lib/log4j-1.1.3.jar
./build/lib/log4j-core-1.1.3.jar
./build/lib/logkit-1.0.1.jar
./build/lib/oro.jar
./build/lib/servlet.jar
./build/lib/w3c.jar
./build/lib/werken.xpath.jar

~/dev/trunk/modules/thirdparty/batik$ find . -name "*.jar" -print
./lib/build/ant_1_4_1.jar
./lib/build/crimson-ant.jar
./lib/build/jaxp.jar
./lib/build/stylebook-1.0-b3_xalan-2.jar
./lib/build/xalan-2.0.1.jar
./lib/js.jar
./lib/pdf-transcoder.jar
./lib/xerces_2_5_0.jar
./lib/xml-apis.jar

While I suspect they are all Apache jars I don't believe the source code fo=
r all the jars is in the package.  I thought source packages were suppose t=
o be just source although in http://incubator.apache.org/guides/releasemana=
gement.html#best-practice-jars there is an incomplete statement about depen=
dent jars in the "Distributing Libraries" section.

Does this mean that we can include the apache jars that we use in our sourc=
e package?  How about in our binary package?

2.  We've run RAT.  We currently have a few hundred files flagged as binari=
es.  Many of them are asset files.  Is there some sort of exception process=
 for these?

3.  If you have a .fla file which is a source file for Adobe Flash Professi=
onal does that mean we have to require Adobe Flash Professional as a prereq=
uisite build tool?  We have other similar situations which involve differen=
t apps/tools to produce different assets.

Carol

--_000_CBEC0F0515B52cframptoadobecom_--