[ANN] Apache Archiva 1.1.1 released

[Brett Porter <br...@apache.org>]

The Apache Archiva team is pleased to announce the release of Archiva  
1.1.1.

Apache Archiva is an extensible repository management software that  
helps taking care of your own personal or enterprise-wide build  
artifact repository. It is the perfect companion for build tools such  
as Maven, Continuum, and ANT.

Archiva offers several capabilities, amongst which remote repository  
proxying, security access management, build artifact storage,  
delivery, browsing, indexing and usage reporting, extensible scanning  
functionality... and many more!

The latest release is now available here:
http://archiva.apache.org/download.html

If you have any questions, please consult:
- the web site: http://archiva.apache.org
- the archiva-user mailing list: http://archiva.apache.org/mail-lists.html

Change Log for Archiva 1.1.1
============================

Bug

	• [MRM-584] - Newly created user cannot login
	• [MRM-631] - network proxy is always used when defined
	• [MRM-814] - Invalid cron expressions are accepted in Database  
Scanning
	• [MRM-873] - repository groups - move up/down should not show when  
it's not possible
	• [MRM-883] - RSS syndication java.lang.ArrayIndexOutOfBoundsException
	• [MRM-884] - network proxy fails after upgrading to archiva 1.1
	• [MRM-888] - add notes on reindexing to the upgrade docs
	• [MRM-891] - Unable to use archiva as http source with maven-stage- 
plugin
	• [MRM-892] - Search for java classes and package names is broken
	• [MRM-895] - Archiva version doesn't appear on the footer when it is  
installed on Tomcat
	• [MRM-896] - classifier is appended to pom filename after artifact  
upload

Improvement

	• [MRM-817] - Artifact information screen should indicate the name of  
repository in which the artifact resides

Thanks,
The Apache Archiva team

--
Brett Porter
brett@apache.org
http://blogs.exist.com/bporter/


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Best Practice for DLLs in Maven with Eclipse

[Jan Schoppenhorst <sc...@gdv.com>]

One of the many things I like about Maven is that the binaries are in 
repositiories and not in CVS. For normal Jars this works perfect but 
DLLs and .so files are often also packed in jars and then put into the 
repositories. These jars have to be unpacked before they can be used 
when running the Project within Eclipse. My old way to use these DLLs 
was to put them into the project root (single module) and then put 
everything in CVS. When s.o. was checking this out with Eclipse from CVS 
everything worked and the project could be run directly. I can do the 
same now with M2E projects but it feels wrong to put the DLLs in the CVS 
and to not use the repo for that. My question is how people are handling 
this "problem". The idea is that when someone joins the team he can 
checkout the project and start it right away (without the DLLs being in 
CVS).

 
****************************************************************
Jan Schoppenhorst
GDV
Gesellschaft für geografische Datenverarbeitung mbH
Binger Straße 49-51
55218 Ingelheim
Tel.:   06132/7148-19
Fax.:   06132/7148-28
www.gdv.com
www.gdv-mapbuilder.de

Sitz der Gesellschaft: Ingelheim
Amtsgericht Mainz HRB 23123
Gerichtsstand Mainz
Geschäftsführer: Thomas Riehl, Dirk Hübener 
****************************************************************