[ANNOUNCE] ApacheDS 2.0.0-M19 released

2014-11-25 Thread Emmanuel Lecharny
The Apache Directory team is pleased to announce the release of
ApacheDS 2.0.0-M19, the 19th milestone towards a 2.0 version.

Note that this milestone is a security fix above 2.0.0-M18, which has
not been announced.

ApacheDS is an extensible and embeddable directory server entirely
written in Java, which has been certified LDAPv3 compatible by the
Open Group. Besides LDAP it supports Kerberos 5 and the Change
Password Protocol. It has been designed to introduce triggers, stored
procedures, queues and views to the world of LDAP which has lacked
these rich constructs.

This release fixes many critical bugs.


Here is the release note for Apache Directory ApacheDS 2.0.0-M19:

Bugs

[DIRSERVER-2020]
https://issues.apache.org/jira/browse/DIRSERVER-2020 Poodle
remediation for ApacheDS 2.X
[DIRSERVER-2016] Race condition in PasswordPolicy Bind handling
[DIRSERVER-2016] Another Java 8 only error (with Kerberos)
[DIRSERVER-2016] Java 7 vs Java 8 : failure in Java 8
[DIRSERVER-2014] Synchronization is stopped if remote server was
not restored during refresh interval
[DIRSERVER-2012] Replication ignores startTLS when
ads-replStrictCertValidation is true
[DIRSERVER-2010] LdifFileLoader cannot load LDIFS from the
classpath unless they are very specific location
[DIRSERVER-2006] Licencing for apacheds-all
[DIRSERVER-2003] Remove ONE and SUB level index configuration from
default configuration file
[DIRSERVER-2002] OutOfMemory error while loading more than 70K
entries at once
[DIRSERVER-2001] Replication using TLS does not work when
confidentiality is enforced
[DIRSERVER-1992] LRUMap used as Entry DN cache in
AbstractBTreePartition is going into an inconsistent state
[DIRSERVER-1986] Delegated authentication fails when password
policy is enabled
[DIRSERVER-1978] Unable to import ldif when operational attribute
pwdChangedTime is present


Improvements

[DIRSERVER-1965] An Index should speed up searches starting with '*'

Note that this is a milestone, and some parts of the API or
configuration can change before the 2.0 GA. We don't have any defined
time frame for the 2.0-G1 release, we do expect to release a few more
milestones before reaching the 2.0-GA.


Website : http://directory.apache.org/apacheds

Download : http://directory.apache.org/apacheds/downloads.html

User's Guide : http://directory.apache.org/apacheds/basic-users-guide.html


The Apache Directory Team

-- 
Regards,
Cordialement,
Emmanuel Lécharnywww.iktek.com


[ANN] Apache Tomcat 6.0.43 released

2014-11-25 Thread Mark Thomas
The Apache Tomcat team announces the immediate availability of Apache
Tomcat 6.0.43.

Apache Tomcat is an open source software implementation of the Java
Servlet, JavaServer Pages and Java Expression Language technologies.

This release contains a number of bug fixes and improvements compared to
version 6.0.41. The notable changes since 6.0.41 include:
- Update to Tomcat Native Library version 1.1.32 to pick up the Windows
   binaries that are based on OpenSSL 1.0.1j and APR 1.5.1.
- Add support for TLSv1.1 and TLSv1.2 for APR connector. Based upon
   a patch by Marcel Šebek. This feature requires Tomcat Native library
   1.1.32 or later.
- Disable SSLv3 by default for all HTTPS connectors.


Please refer to the change log for the complete list of changes:
http://tomcat.apache.org/tomcat-6.0-doc/changelog.html
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Note: This version has 4 zip binaries: a generic one and
  three bundled with Tomcat native binaries for Windows operating
  systems running on different CPU architectures.

Downloads:
http://tomcat.apache.org/download-60.cgi
http://tomcat.apache.org/download-70.cgi

Migration guides from Apache Tomcat 5.5.x:
http://tomcat.apache.org/migration.html

- The Apache Tomcat team


[ANNOUNCEMENT] Apache Commons CSV 1.1 Released

2014-11-25 Thread Gary Gregory
The Apache Commons CSV team is pleased to announce the 1.1 release!

The Apache Commons CSV library provides a simple interface for reading and
writing
CSV files of various types.

This is our second release.

Changes in this version include:

New features:
o [CSV-129] Add CSVFormat#with 0-arg methods matching boolean arg methods.
o [CSV-131] Save positions of records to enable random access. Thanks to
Holger Stratmann.
o [CSV-139] CSVPrinter.printRecord(ResultSet) with metadata.

Fixed Bugs:
o [CSV-140] QuoteMode.NON_NUMERIC doesn't work with
CSVPrinter.printRecords(ResultSet). Thanks to Damjan Jovanovic.
o [CSV-130] CSVFormat#withHeader doesn't work well with #printComment, add
withHeaderComments(String...). Thanks to Sergei Lebedev.
o [CSV-128] CSVFormat.EXCEL should ignore empty header names.
o [CSV-132] Incorrect Javadoc referencing org.apache.commons.csv.CSVFormat
withQuote(). Thanks to Sascha Szott.

Changes:
o [CSV-124] Improve toString() implementation of CSVRecord. Thanks to
Kalyan.
o [CSV-134] Unified parameter validation. Thanks to wu wen.

For complete information on Commons CSV, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the Apache
Commons CSV website:

Site: http://commons.apache.org/proper/commons-csv/

Download: http://commons.apache.org/csv/download_codec.cgi

Happy Coding!
Happy Thanksgiving!
Gary Gregory on behalf of the Apache Commons CSV team

-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition
http://www.manning.com/bauer3/
JUnit in Action, Second Edition http://www.manning.com/tahchiev/
Spring Batch in Action http://www.manning.com/templier/
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory


[ANNOUNCE] Apache Directory LDAP API 1.0.0-M26 released

2014-11-25 Thread Emmanuel Lecharny
The Apache Directory Team is proud to announce the availability of the
1.0.0-M26 version of the Apache Directory LDAP API.

The Apache Directory LDAP client API is an ongoing effort to provide
an enhanced LDAP API, as a replacement for JNDI and the existing LDAP
API (jLdap and Mozilla LDAP API).

This is a schema aware API, with some convenient ways to access a LDAP
server. This API is not only targeting the Apache Directory Server,
but should work pristine with any LDAP server.

It's also an extensible API : new Controls, schema elements and
network layer could be added or used in the near future. It's also
OSGi capable.


This release is just a security fix over the 1.0.0-M25 release : it
forbid the use of SSLV3 when using a secured LDAP connection (either
LDAPS or StartTLS).


Feel free to experiment, we highly appreciate your feedback !


Website : http://directory.apache.org/api
Download : http://directory.apache.org/api/downloads.html
User's Guide : http://directory.apache.org/api/user-guide.html

The Apache Directory Team



-- 
Regards,
Cordialement,
Emmanuel Lécharn
ywww.iktek.com


[ANNOUNCE] Apache Storm 0.9.3 Released

2014-11-25 Thread P. Taylor Goetz
The Apache Storm team is pleased to announce the release of Apache Storm 
version 0.9.3.

Storm is a distributed, fault-tolerant, and high-performance realtime 
computation system that provides strong guarantees on the processing of data. 
You can read more about Storm on the project website:

http://storm.apache.org

Downloads of source and binary distributions are listed in our download
section:

http://storm.incubator.apache.org/downloads.html

You can read more about this release in the following blog post:

http://storm.apache.org/2014/11/25/storm093-released.html

Distribution artifacts are available in Maven Central at the following 
coordinates:

groupId: org.apache.storm
artifactId: storm-core
version: 0.9.3

The full list of changes is available here[1]. Please let us know [2] if you 
encounter any problems.

Regards,

The Apache Storm Team

[1]: https://github.com/apache/incubator-storm/blob/v0.9.3/CHANGELOG.md
[2]: https://issues.apache.org/jira/browse/STORM


signature.asc
Description: Message signed with OpenPGP using GPGMail


ApacheCon North America returns to Austin

2014-11-25 Thread Sally Khudairi
 this announcement is online at http://s.apache.org/60N 


by Rich Bowen, ASF Executive Vice President 

We just got done with ApacheCon Europe in Budapest last week - 
http://apachecon.eu/ - and it's time to start thinking about ApacheCon North 
America. 

We'll be holding ApacheCon North America, April 13-17th, 2015, in Austin, 
Texas. The call for papers is already open, at http://apachecon.com/, and we 
are hoping that this event will represent the breadth of the Apache Software 
Foundation projects. 

Organize your community 
The most important thing at this stage in the process is getting the Apache 
community involved in this event. ApacheCon exists to unite our community, get 
various projects to interact with one another, and bring new members into our 
community. The best way to accomplish these goals is to ensure that your 
project has representation at ApacheCon. Here are four specific areas where we 
need the help of Apache project communities: 

Track layout 
We've found that the very best way to have a project well represented in the 
content tracks is for someone deeply familiar with the project to craft an 
ideal track schedule, and then solicit speakers for those sessions. This has 
two immediate benefits. 

First, it goes a long way to ensuring that the topic is covered with the 
breadth that it deserves, rather than having a few random talks that cover 
random esoteric parts of the technology, and ignore segments of the audience 
that you most want to attract. 

Second, it is very encouraging to first-time speakers. It's very difficult, and 
very intimidating, to try to come up with a topic to speak about the first few 
times. Seeing a list of proposed topics is the perfect way to say to a new 
speaker that what they know about is worth them proposing to a conference. 
Hey, I could speak about that, and nobody would think it's a stupid idea. 

Speakers 
Some talks require certain speakers. You know this a lot better than we do, 
because it's your project. We need your help to go to those specific speakers 
and encourage them to submit the specific talk(s) that you know they'll shine 
at. 

Reviewing and Scheduling 
Once the talks have been submitted, we're going to need your help reviewing 
them and building the schedule. To help with the review process, you'll need to 
create an account in the CFP system (if you haven't already done so) at 
https://identity.linuxfoundation.org/user and then email me - rbo...@apache.org 
- with your username, so that I can get you added to the review system. From 
there, you'll see a list of talks to consider, and you can rate them according 
to how well you think they'll fit the conference. 

Of course, if you specifically solicited those talks, then you'll quickly mark 
them as Strongly Accept with a comment of I solicited this specific talk, 
and move on. (The CFP review interface is at 
http://events.linuxfoundation.org/cfp/cfp-list if you already have an account.) 
You can review talks from other topics/tracks, too, if you feel that you have 
some domain knowledge. 

Once the review process is complete, we'll select the talks that rate the 
highest, and at that point we'll be back in touch with you to help us order 
them correctly. Here, again, if you've already approached us with a layout of 
your ideal content track, there's really nothing else to do. But if there are 
other talks that made it in through the review process, we'll need help. 

Hackathons 
A key benefit of ApacheCon is getting your developers together in one place to 
work on things. We've got a a general hackathon area where you can gather to 
work on bugs, features, documentation, or discuss thorny community issues. 
(Don't forget to summarize your conversations back to the mailing list for the 
people who can't make it!) 

If you want to have a sponsored hackathon specifically for your project, we can 
find room to make that happen. Just get in touch with me, and we'll work out 
the details. 

Talking before the event about what you'll be working on has a number of 
benefits. 

First, it gives people time to think about how they can contribute, and plan 
accordingly. 

Second, it encourages people to come in from the edges of the project to 
participate more fully in the life of the community, because they can select 
something that they're particularly interested in, and work on it in company 
with the rest of the project members. 

Using the ApacheCon wiki - http://wiki.apache.org/apachecon/ - as a place to 
work on your hackathon topics gives conference attendees an easy way to find 
topics that they might be interested in, and connecting with the community. If 
you don't have write permissions to the wiki, send me your wiki username, and 
I'll get you added to the access list. 

Sponsor 
Your company uses Apache software every day. Perhaps you even contribute to a 
project as part of your day job. ApacheCon is the best place in the world for 
your company to show off their