Apache Archiva Redback Repository
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
dependabot[bot] 477c8df913
SRC.OSSEZ.COM/archiva-redback-core/pipeline/head There was a failure building this commit Details
Bump spring-core from 5.3.19 to 5.3.20
Bumps [spring-core](https://github.com/spring-projects/spring-framework) from 5.3.19 to 5.3.20.
- [Release notes](https://github.com/spring-projects/spring-framework/releases)
- [Commits](https://github.com/spring-projects/spring-framework/compare/v5.3.19...v5.3.20)

- dependency-name: org.springframework:spring-core
  dependency-type: direct:production

Signed-off-by: dependabot[bot] <support@github.com>
1 year ago
.github Bump actions/setup-java from 3.2.0 to 3.3.0 1 year ago
idea.run.configuration Moving rest utility classes to components 2 years ago
redback-authentication Bump port-allocator-maven-plugin from 1.1 to 1.2 2 years ago
redback-authorization Switching to generics for cache implementation 1 year ago
redback-common Switching to new ehcache version 1 year ago
redback-configuration Adding refresh token for authentication 3 years ago
redback-integrations do not use jakarta package 1 year ago
redback-keys Switching to new ehcache version 1 year ago
redback-policy Moving to jakarta libraries 3 years ago
redback-rbac Switching to new ehcache version 1 year ago
redback-system Fix for JDK11 dependencies 3 years ago
redback-users use jetty bom and simplify code (#38) 1 year ago
src Set OpenJPA logging to commons 4 years ago
.asf.yaml Adding .asf.yaml file 1 year ago
.gitattributes add .gitattributes file 9 years ago
.gitignore Ignore Netbeans artifacts 7 years ago
Jenkinsfile use maven_3.8.5 1 year ago
README.adoc Refactoring of role API and new Role V2 REST service 3 years ago
checkoutSite.sh Migrating to staging branch for site publish 4 years ago
deploySite.sh Using help plugin for config retrieval 4 years ago
git-sparse-checkout-pattern Changes for site git migration 5 years ago
pom.xml Bump spring-core from 5.3.19 to 5.3.20 1 year ago


Archiva Redback - Documentation

== Update Information for 3.0

=== Database Schema Changes

==== org.apache.archiva.redback.rbac.Role

New fields:
id, modelId, isTemplateInstance, resource

Primary key changed from name to combined key id,name

== How to build and publish the pages for the archiva web content

This module and the children contain web content and project reports that can be published to the 
archiva web site: https://archiva.apache.org

The web content parts of this module and submodules are published to the path 


=== Use the script

There is a shell script +deploySite.sh+ which you can run to generate the site check and publish to 
the remote repository. It works only on Linux, on other platforms you have to go the next section.

The script is interactive, it asks you to confirm the publish after generation of the staging part.



All arguments are appended to the mvn calls.

=== Run the mvn steps manually

==== Building the pages

You need enough free disk space to publish the web content. The archiva web site repository is big, 
but the maven build will only checkout the necessary directories for this build (sparse checkout).

For all the commands you have to change to this archiva-modules directory:

  cd archiva/archiva-modules

.The following creates the site to the staging folder

  mvn clean site site:stage

The result can be checked in 


with your browser.

If you would like the use a local checkout of the archiva-web-content.git repository and not push directly
to the remote repository, you may add this parameter:


where +${path-to-your-local-archiva}+ is the path where a bare clone of the archiva-web-content.git is stored.

NOTE: You cannot use +mvn site:run+ because this will place the submodules into the same folder and 
      overwrite each other.

==== Publish the pages

.This command publishes to the git repository

  mvn scm-publish:publish-scm

After publishing to the git repository the gitpubsub mechanism is transferring it to the HTTP server.

If you would like the use a local checkout of the archiva-web-content.git repository and not push directly
to the remote repository, you may add this parameter:


=== Some notes about the build process

A sparse checkout of the git repository will be created in 


but only, if the directory +.site-content/.git+ does not exist.