I thought the build process was going to
download 3rd party libraries from the web site of the organization that
created them. I have a hard time picturing someone downloading 20 jar files to
get started with Corona.
We should have a target to tell people that they should review licenses of the listed
3rd party libraries so that they signal their acceptance of these
other libraries’ licenses.
Glenn Everitt
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn,
Dennis
Sent: Monday, October 23, 2006
11:40 AM
To: Corona
development
Subject: RE: [corona-dev]
Preparation for 1.0.0M5
We should not be including any 3rd
party libraries that have not been approved by the EMO. Therefore, our
build output should not include these libraries in any Corona distribution.
Instructions on “how to” use
any Corona distribution
need to be posted on our wiki. These instructions must include the manual
steps needed to install the 3rd party libraries that are required by
Corona.
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek,
Pawel
Sent: Monday, October 23, 2006
11:06 AM
To: Corona
development
Subject: RE: [corona-dev]
Preparation for 1.0.0M5
What about 3rd party libraries that
have no IP approval in binary distribution? They cannot be available with
sources. I assume that they cannot be available with binary distribution also.
Is it correct? So far, all libraries were added to build.properties. Should
they be removed?
In this case, the downloadable
distribution can not be "installed" in Eclipse and run. We need to
supply a list of libraries (about 20 jars) with their locations that ought to
be downloaded by the end user.
From: corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of O'Flynn,
Dennis
Sent: Sunday, October 22, 2006 7:11
PM
To: Corona
development
Subject: [corona-dev] Preparation
for 1.0.0M5
We are begining the final preparation for
1.0.0M5. For this milestone to be met, we (the committers) need to focus
on the following:
- Update all Bugzilla items ensure that their
status and historical comments are acurate.
- Build process: must be able to consistently
build the release and create all deliverables
- Demo: update the demo to reflect any
changes. ensure all sample context container definitions work
properly.
- Documentaiton: JavaDoc, online Help, HowTo
articles, and any tutorials must be completed.
- Virtual server: setup our virtual server so that
it can used to host Corona's
server-side deployment. This will be used for Corona's development team to begin using
our own software as well as an environment for the Demo.
We
will discuss these items at our weekly development confernce call on Tuesday.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the named
addressee or an authorized designee, you may not copy or use it, or disclose it
to anyone else. If you received it in error please notify us immediately and
then destroy it.
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.