archiva

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
[maven-release-plugin] prepare for next development iteration

  1. … 56 more files in changeset.
[maven-release-plugin] prepare release archiva-2.1.0

  1. … 56 more files in changeset.
use a staged released parent

tomcat 7.0.54

add corigin/archiva-1.3.x

    • -0
    • +1
    /archiva-docs/.gitignore
1.7 mandatory with 2.1.0

add issues in release notes

    • -37
    • +22
    /archiva-docs/src/site/apt/release-notes.apt.vm
use staged release registry

spring 4.0.6

remove archiva-1.3.x excludes

master build will fail if you leave them around (RAT), so better to be

reminded to clean out when switching

update line endings

prevent build order issues

It seemed that whenever the release profile was enabled, the POM ordering was

not respected causing the antrun plugin to happen before the appassembler

plugin. Move them to different, more appropriate phases.

fix formatting

    • -0
    • +1
    /archiva-docs/src/site/apt/release-notes.apt
log4j2 rc2

fix version

[maven-release-plugin] prepare for next development iteration

  1. … 27 more files in changeset.
[maven-release-plugin] prepare release archiva-1.3.9

  1. … 27 more files in changeset.
release notes for 1.3.9

    • -4
    • +19
    /archiva-docs/src/site/apt/release-notes.apt
revert c648adb3061202572de0fa575150e48ce4c486de too

revert previous commit as 2.x was not affected in fact

fix POM after last release

upgrade to latest Struts

[MRM-1796] support artifacts larger than 4G

[MRM-1796] support artifacts larger than 4G

[MRM-1796] support artifacts larger than 4G [MRM-1796] support artifacts larger than 4G

fix unit

add comment

[MRM-1846] Regression in 2.0.1 : uniqueVersion false not supported

fix rat configuration

configure cxf logger