On Sep 17, 2010, at 2:25 PM, Josh Thompson wrote:
>
> Kevan and Matt - thanks for the info. I added instructions to
>
> https://cwiki.apache.org/confluence/display/VCL/VCL+Release+Procedures
>
> on downloading and including Dojo Toolkit in the section that explains how to
> create the RC.
>
On Friday September 17, 2010, Kevan Miller wrote:
> On Sep 17, 2010, at 10:52 AM, Josh Thompson wrote:
> > So, it just needs to be somewhere in the repo to ensure it is always
> > available, but it doesn't actually have to be part of the release tag
> > such that an export of the release tag includ
On Sep 17, 2010, at 10:52 AM, Josh Thompson wrote:
> So, it just needs to be somewhere in the repo to ensure it is always
> available, but it doesn't actually have to be part of the release tag such
> that an export of the release tag includes it? My plan was to actually
> include it in the r
So, it just needs to be somewhere in the repo to ensure it is always
available, but it doesn't actually have to be part of the release tag such
that an export of the release tag includes it? My plan was to actually
include it in the release already untarred and in place to remove a few steps
o
Geronimo had similar issues where they needed to include jars from other
projects so that they could have a repeatable build process. Take for
instance, a customer that is trying to build the project 10 years from now
(unlikely but that is the thought).
They included the tar balls for Dojo i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mentors:
I have a question about bundling 3rd party software in the release artifact.
I'm planning to include the Dojo Toolkit in the artifact. It is released
under the Academic Free License. I've done what is needed with the LICENSE
and NOTICE
