Regarding Bouncy Castle, IIRC they used to include the IDEA algorithm
in their distribution and provided a one-off for Geronimo to use to
bypass the patent issue. Not sure if that is an issue or not for
Tuscany but just a heads up.
On Feb 20, 2007, at 12:52 AM, Jeremy Boynes wrote:
On Fe
All of the instructions can be found at [1]. Just step through that and
it shouldn't take too long.
As far as I understand, each project is responsible for it's own
notifications.
- James
[1] http://www.apache.org/dev/crypto.html
Jeremy Boynes wrote:
> On Feb 17, 2007, at 5:27 PM, James M Snell
On Feb 17, 2007, at 5:27 PM, James M Snell wrote:
I've gone ahead and filed the export notification and updated the ASF
exports page [1]. I also added an appropriate notification to the
distributions README.
[1] http://www.apache.org/licenses/exports/
In Tuscany our next release will have a
Garrett Rooney wrote:
> Noel J. Bergma wrote:
> > Garrett Rooney wrote:
> > > We need to file a export notification for use of crypto code (not our
> > > code, third party, bouncy castle, I believe) in one of the abdera
> > > modules.
> > That's fine. I suspected that it might be something like t
On Feb 19, 2007, at 8:19 AM, Garrett Rooney wrote:
On 2/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Garrett Rooney wrote:
> Noel J. Bergman wrote:
> > Your quarterly report mentions possibly legal issues related
to crypto.
> > What are the issues?
> We need to file a export notifica
On 2/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Garrett Rooney wrote:
> Noel J. Bergman wrote:
> > Your quarterly report mentions possibly legal issues related to crypto.
> > What are the issues?
> We need to file a export notification for use of crypto code (not our
> code, third party,
Garrett Rooney wrote:
> Noel J. Bergman wrote:
> > Your quarterly report mentions possibly legal issues related to crypto.
> > What are the issues?
> We need to file a export notification for use of crypto code (not our
> code, third party, bouncy castle, I believe) in one of the abdera
> modules
I've gone ahead and filed the export notification and updated the ASF
exports page [1]. I also added an appropriate notification to the
distributions README.
[1] http://www.apache.org/licenses/exports/
Garrett Rooney wrote:
> On 2/17/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>> Your quarter
On 2/17/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Your quarterly report mentions possibly legal issues related to crypto.
What are the issues?
We need to file a export notification for use of crypto code (not our
code, third party, bouncy castle, I believe) in one of the abdera
modules.
-
Your quarterly report mentions possibly legal issues related to crypto. What
are the issues?
--- Noel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 2/9/07, James M Snell <[EMAIL PROTECTED]> wrote:
The Abdera team is ready to release version v0.2.2. This is a bug fix
release that addresses a number of critical issues. There are no new
features. We would appreciate if folks could take a look and weigh in.
// JDK 1.5
http://people.apache
+1
On 2/12/07, Garrett Rooney <[EMAIL PROTECTED]> wrote:
On 2/8/07, James M Snell <[EMAIL PROTECTED]> wrote:
> The Abdera team is ready to release version v0.2.2. This is a bug fix
> release that addresses a number of critical issues. There are no new
> features. We would appreciate if folks
On 2/8/07, James M Snell <[EMAIL PROTECTED]> wrote:
The Abdera team is ready to release version v0.2.2. This is a bug fix
release that addresses a number of critical issues. There are no new
features. We would appreciate if folks could take a look and weigh in.
// JDK 1.5
http://people.apache
I've added a short change list to the README included in the
distribution. Nothing detailed but enough to hit the high points.
- James
Luciano Resende wrote:
> This kind of information would be good to be documented, maybe in a form of
> a RELEASE_NOTES and included on the distribution. I didn't
Ok, not a problem. I'll add that in.
- James
Luciano Resende wrote:
> This kind of information would be good to be documented, maybe in a form of
> a RELEASE_NOTES and included on the distribution. I didn't see any
> reference
> for what's changed on the zip distribution for JDK 1.5.
>
This kind of information would be good to be documented, maybe in a form of
a RELEASE_NOTES and included on the distribution. I didn't see any reference
for what's changed on the zip distribution for JDK 1.5.
--
Luciano Resende
http://people.apache.org/~lresende
On 2/8/07, James M Snell <[EMAIL
The main issues resolved include a critical bug in handling XML and
XHTML content in Atom entries and resolving some StAX API conformance
issues by upgrading to Axiom 1.2.1. We've also eliminated our
dependence on the Stax Reference Implementation. Beyond that, the
remaining changes were relative
On 2/8/07, James M Snell <[EMAIL PROTECTED]> wrote:
The Abdera team is ready to release version v0.2.2. This is a bug fix
release that addresses a number of critical issues. There are no new
features. We would appreciate if folks could take a look and weigh in.
Do you have a list of changes
The Abdera team is ready to release version v0.2.2. This is a bug fix
release that addresses a number of critical issues. There are no new
features. We would appreciate if folks could take a look and weigh in.
// JDK 1.5
http://people.apache.org/~jmsnell/abdera.0.2.2-incubating.zip
http://peopl
19 matches
Mail list logo
