Sorry, I came too late for the vote on this beta-3 release. Jira is in maintenance for now and I cannot check for issues.
For my personnal experiments, beta3 solves all the issues I got with archiva from a maven1 point of view. I'm using it (installed one hour ago) as my corporate repository for both maven1 and maven2, pointing to a single (m2) repo and proxying some public maven2 repositories. All works fine. Nico 2007/11/5, Arnaud HERITIER <[EMAIL PROTECTED]>: > > Nicolas, are there some issues opened to have a full m1 support ? > I don't have the time to check on Jira... > > Arnaud > > On Nov 5, 2007 5:34 AM, Dion Gillard <[EMAIL PROTECTED]> wrote: > > > Just wrt previous versions. > > > > Last time I tried Archiva as a replacement for maven-proxy, it was > > pretty hostile for maven 1 usage; I gave up after a few hours. > > > > I'll try the new beta and see how it goes. > > > > On 11/5/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > > On 04/11/2007, Dion Gillard <[EMAIL PROTECTED]> wrote: > > > > Is this one an easier to configure and get going for Maven 1.x? > > > > > > Were you wondering whether it is easier than something in particular, > > > or just previous versions? > > > > > > The last couple of betas have been working well WRT maven1 I believe - > > > Nicolas and Arnaud are pretty vigilant about that aspect :) > > > > > > Archiva should now be pretty seamlessly serving both maven1 and maven2 > > > clients from the same repository (it's best to store in maven2 format > > > if possible in this instance) > > > > > > - Brett > > > > > > > > > > > On 11/3/07, Maria Odea Ching <[EMAIL PROTECTED]> wrote: > > > > > Hi Everyone, > > > > > > > > > > The Maven Archiva team is pleased to announce the release of > Archiva > > 1.0Beta 3. > > > > > > > > > > Archiva is a build artifact repository manager for use with build > > tools such > > > > > as Maven, Continuum and Ant. > > > > > > > > > > It has features like repository search and browse, securing > > repositories, > > > > > identifying unknown artifacts and reporting of repository > problems. > > > > > > > > > > Aside from these, it can also act as a nearby (proxy) cache of > > popular > > > > > global repositories. > > > > > > > > > > > > > > > > > > > > The latest release is now available here: > > > > > > > > > > http://maven.apache.org/archiva/download.html > > > > > > > > > > > > > > > Below are the jira issues that were resolved for Archiva 1.0 Beta > 3: > > > > > > > > > > Release Notes - Archiva - Version 1.0-beta-3 > > > > > > > > > > ** Sub-task > > > > > * [MRM-527] - Create tests for discovering deleted artifacts > > > > > > > > > > ** Bug > > > > > * [MRM-128] - better handling of jar artifacts without a pom > > > > > * [MRM-142] - project builder cache needs to be configurable > to > > prevent > > > > > memory leaking > > > > > * [MRM-205] - Undesirable Tomcat configuration for .jspf files > > > > > * [MRM-213] - cannot undeploy archiva webapp > > > > > * [MRM-243] - 507 Insufficient Storage when deploying artifact > > with > > > > > webdav > > > > > * [MRM-265] - After removing a managed repository - > > Browse/Search still > > > > > see it > > > > > * [MRM-309] - relocated artifacts are not delivered > > > > > * [MRM-320] - ProxiedDavServer breaks update policy > > > > > * [MRM-323] - Managed repo in archiva cannot be accessed thru > > direct > > > > > webdav url even with valid credentials (Archiva deployed in > Tomcat) > > > > > * [MRM-333] - Tomcat deployment of archiva results in unstable > > instance. > > > > > * [MRM-396] - remove 'true' and 'false' from the descriptions > on > > the > > > > > repository admin page > > > > > * [MRM-398] - configure guest access by default for > > pre-configured > > > > > repositories > > > > > * [MRM-400] - tab appearance on view artifact page looks > > incorrect > > > > > * [MRM-428] - managed and remote repositories with same name > > causes > > > > > problems > > > > > * [MRM-432] - Proxy Connectors are unable to download > artifacts > > with > > > > > alpha numerical version numbers > > > > > * [MRM-437] - admin editing of proxy connectors fails in > > multiple > > > > > instances > > > > > * [MRM-444] - intermittent test failures on proxy > > > > > * [MRM-454] - Index not updated after repository purge > > > > > * [MRM-461] - Warning message for non existent resources > should > > include > > > > > what resource it failed to locate. > > > > > * [MRM-466] - NPE on DatabaseJob.execute() > > > > > * [MRM-470] - Test failures in BytecodeIndexTest due to NPE in > > > > > AbstractIndexCreationTestCase > > > > > * [MRM-477] - Missing ability to manage proxy order. > > > > > * [MRM-479] - metadata files in artifactId/version level are > not > > updated > > > > > during repository purge > > > > > * [MRM-481] - Artifact requests with a .xml.zip extension fail > > with a > > > > > 404 Error > > > > > * [MRM-482] - Saving a proxy connector after adding a new > > property > > > > > results to HTTP 500 error > > > > > * [MRM-486] - Can not deploy artifact > test.maven-arch:test-arch > > > > > * [MRM-487] - pom version is not resolved > > > > > * [MRM-488] - properties in pom are not resolved (at least > while > > > > > browsing) > > > > > * [MRM-489] - Repositories are read only even for repository > > managers > > > > > * [MRM-493] - Downloaded artifacts are stored in incorrect > > > > > archiva-managed repository > > > > > * [MRM-494] - leaving repository ID blank on the add > repository > > page > > > > > goes to the edit page where ID cannot be edited > > > > > * [MRM-500] - Failure in PathUtilTest under windows because > the > > test > > > > > uses slashes in path but test File.separator in PathUtil > > > > > * [MRM-501] - Saving configuration fails through the webapp. > > > > > * [MRM-503] - Metadata files need Pragma:no-cache response > > header. > > > > > * [MRM-509] - Adding the same repository twice will be > > redirected to an > > > > > Edit Repository page. > > > > > * [MRM-510] - In Repository Browse, the first unique snapshot > > version > > > > > clicked is getting persisted in the request resulting to 'version > > does not > > > > > match' error > > > > > * [MRM-512] - Unable to convert null repository config to > > archiva > > > > > repository. > > > > > * [MRM-517] - Some maven 2 requests are treated as maven 1 > > requests > > > > > * [MRM-518] - Changing the internal repository directory has > no > > effect > > > > > * [MRM-519] - fail to resolve artifactId for libs that contain > > > > > versionKeyword in artifactId, like "maven-test-plugin" > > > > > * [MRM-520] - Proxy Connectors are not deleted with the > deletion > > of a > > > > > Repository. > > > > > * [MRM-521] - No validation for the repository purge fields in > > repo > > > > > config > > > > > * [MRM-529] - Accessing a newly added repository via webdav > > results to a > > > > > 404 error > > > > > * [MRM-533] - Checksum files (sha1/md5) are not kept up to > date > > on > > > > > maven-metadata.xml files. > > > > > * [MRM-534] - Test failure in > RepositoryContentConsumerUtilTest > > > > > * [MRM-535] - metadata-updater is changing lastUpdating > > timestamp when > > > > > it shouldn't > > > > > * [MRM-543] - Versions (latest and release) wrong after > > regeneration of > > > > > maven-metadata.xml > > > > > * [MRM-546] - Duplicate repositories show up while editing. > > > > > * [MRM-551] - the default scan cron expression is once a day, > > should be > > > > > hourly > > > > > * [MRM-554] - Wrong generated links at root of repository > > browsing > > > > > * [MRM-555] - scanner checks timestamps, but some consumers > will > > want to > > > > > consume artifacts regardless > > > > > * [MRM-557] - repair or remove commented out test cases in > proxy > > module > > > > > * [MRM-558] - html problem on repositories admin page causes > > footer to > > > > > not be left aligned > > > > > * [MRM-559] - archiva version is not calculated correctly - > > always > > > > > "Unknown" > > > > > * [MRM-561] - Error 500 while deleting a proxy connector > > > > > * [MRM-562] - Artifact type "maven-plugin" is not detected > > correctly in > > > > > .toArtifactReference() methods. > > > > > * [MRM-563] - Proxy connector logic for getIfModified is > > backwards. > > > > > * [MRM-565] - Archiva 1.0-beta-3 fails in 404 on all legacy > > request. > > > > > * [MRM-567] - Unable to download plugin SNAPSHOT's from proxy. > > > > > > > > > > ** Improvement > > > > > * [MRM-37] - discover the deletion of artifacts > > > > > * [MRM-313] - archiva fails to serve maven2 plugin from legacy > > > > > repository > > > > > * [MRM-458] - the NOTICE file is overzealous in declaring > > dependencies > > > > > * [MRM-492] - repository failures can present as a 404 from > > proxy > > > > > * [MRM-525] - Typos on the hacking page > > > > > * [MRM-528] - just-in-time consumption of repository changes > > > > > > > > > > ** New Feature > > > > > * [MRM-476] - ability to use file protocol using UNC path for > > Managed > > > > > repository > > > > > > > > > > > > > > > > > > > > ** Wish > > > > > * [MRM-202] - Change the top-left logo to be an Archiva logo > > that goes > > > > > to the front page of the instance > > > > > * [MRM-203] - Reports should be public, not an administration > > feature > > > > > * [MRM-513] - Support remote repositories with passwords > > > > > > > > > > > > > > > The Maven Archiva team will be getting ready for the another beta > > release > > > > > and finally, a > > > > > 1.0 release. > > > > > > > > > > > > > > > Thanks, > > > > > Deng > > > > > > > > > > > > > > > > > -- > > > > dIon Gillard > > > > Rule #131 of Acquisition: Information is Profit. > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > Brett Porter > > > Blog: http://www.devzuz.org/blogs/bporter/ > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > dIon Gillard > > Rule #131 of Acquisition: Information is Profit. > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .......................................................... > Arnaud HERITIER > .......................................................... > OCTO Technology - aheritier AT octo DOT com > www.octo.com | blog.octo.com > .......................................................... > ASF - aheritier AT apache DOT org > www.apache.org | maven.apache.org > ........................................................... >
