Archiva - Building Archiva

; Thu, 26 Feb 2015 10:17:17 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1662408 [2/16] - in /archiva/site-content: ./ css/ developers/ errors/ js/ jsui/ Date: Thu, 26 Feb 2015 10:17:15 -0000 To: commits@archiva.apache.org From: skygo@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20150226101717.07737AC06FA@hades.apache.org> Modified: archiva/site-content/developers/archiva-idea-codestyle.xml URL: http://svn.apache.org/viewvc/archiva/site-content/developers/archiva-idea-codestyle.xml?rev=1662408&r1=1662407&r2=1662408&view=diff ============================================================================== --- archiva/site-content/developers/archiva-idea-codestyle.xml (original) +++ archiva/site-content/developers/archiva-idea-codestyle.xml Thu Feb 26 10:17:14 2015 @@ -1,172 +1,172 @@ - - - - - - - + + + + + + + Modified: archiva/site-content/developers/building.html URL: http://svn.apache.org/viewvc/archiva/site-content/developers/building.html?rev=1662408&r1=1662407&r2=1662408&view=diff ============================================================================== --- archiva/site-content/developers/building.html (original) +++ archiva/site-content/developers/building.html Thu Feb 26 10:17:14 2015 @@ -1,281 +1,283 @@ - - - - - - - - - - Archiva - Building Archiva - - - - - - - - - - - - - - - - - - - - - - - -

- - -

- -

- - - -

- -

Building Archiva

To build the very latest code available...

Check out the source code as described on the Source Repository page.
In the 'parent' directory, execute mvn clean install to build the parent pom. (only needed if we depend on a new parent)
In the 'archiva' directory, execute mvn clean install to build the Archiva modules and distribution.

After the build completes, you can find the Archiva distribution in archiva-jetty/target and the Archiva webapp in archiva-modules/archiva-web/archiva-webapp/target

Usually, it's that simple. :) Occasionally, Archiva may depend on a snapshot of another project such as Redback, and you may need to build that first, or configure a snapshot repository. If you're having trouble building Archiva, ask on the Development mailing list and we'll point you in the right direction.

Documentation

The version-specific documentation for the latest version of Archiva can be found in archiva/archiva-docs, and the top-level Archiva website --including the page you're reading now -- is in the site directory.

To work on the documentation, execute mvn site:run in one of these directories, and then visit http://localhost:8080 to view pages as you edit them. When you're done, submit a patch in the issue tracker.

git clone

git clone git://github.com/apache/archiva.git; cd archiva ; sh ./init-git-svn.sh
-or trough https
-git clone https://github.com/apache/archiva.git; cd archiva ; sh ./init-git-svn.sh

Running Javascript webapp with tomcat-maven-plugin

You can use tomcat-maven-plugin to run the webapp without installing the war in a container. With maven3 in the top directory :

mvn tomcat7:run -pl :archiva-webapp -am (use mvnDebug if you want to attach a debugger)
-or
-sh ./t7.sh (use sh ./t7-debug.sh if you want to attach a debugger)

Hit your browser : http://localhost:9091/archiva/index.html

- -

- - - + + + + + + + + + + Archiva - Building Archiva + + + + + + + + + + + + + + + + + + + + + + + +

+ + +

+ +

+ + + +

+ +

Building Archiva

To build the very latest code available...

Check out the source code as described on the Source Repository page.
In the 'parent' directory, execute mvn clean install to build the parent pom. (only needed if we depend on a new parent)
In the 'archiva' directory, execute mvn clean install to build the Archiva modules and distribution.

After the build completes, you can find the Archiva distribution in archiva-jetty/target and the Archiva webapp in archiva-modules/archiva-web/archiva-webapp/target

Documentation

git clone

git clone git://github.com/apache/archiva.git; cd archiva ; sh ./init-git-svn.sh
+or trough https
+git clone https://github.com/apache/archiva.git; cd archiva ; sh ./init-git-svn.sh
+

Running Javascript webapp with tomcat-maven-plugin

You can use tomcat-maven-plugin to run the webapp without installing the war in a container. With maven3 in the top directory :

mvn tomcat7:run -pl :archiva-webapp -am (use mvnDebug if you want to attach a debugger)
+or
+sh ./t7.sh (use sh ./t7-debug.sh if you want to attach a debugger)
+

Hit your browser : http://localhost:9091/archiva/index.html

+ +

+ + + \ No newline at end of file Modified: archiva/site-content/developers/how-we-do-things.html URL: http://svn.apache.org/viewvc/archiva/site-content/developers/how-we-do-things.html?rev=1662408&r1=1662407&r2=1662408&view=diff ============================================================================== --- archiva/site-content/developers/how-we-do-things.html (original) +++ archiva/site-content/developers/how-we-do-things.html Thu Feb 26 10:17:14 2015 @@ -1,289 +1,290 @@ - - - - - - - - - - Archiva - How We Do Things - - - - - - - - - - - - - - - - - - - - - - - -

- - -

- -

- - - -

- -

How We Do Things

Below are the conventions we follow in Archiva.

Continuous Integration

We use the Jenkins Apache instance for building Archiva (and redback dependencies) on scm changes.

See the tab with various builds: Archiva tab

You can test fresh builds with downloading from this Jenkins job archiva-master-build/:

standalone with embeded jetty (unzip then cd bin;./archiva start running on 8080)
war webapp js

Code Style

There isn't any code style that needs to be followed as long as it is consistent, can be checked in checkstyle, can be formatted in Eclipse, IDEA and NetBeans. And the following rules must be followed:

Use spaces, not tabs -
- 4 spaces for Java
- 2 spaces for XML
120 column wrap, not 80
Wrap on spaces, not on '.' in a method call -
You can use the existing codestyle files:
-
- idea
- eclipse

Versioning

It has been established in the community that the following style would be followed for the versioning of releases:

Milestones -> Final -> Patch releases (e.g. 1.1-M1, 1.1-M2, 1.1, 1.1.1, 1.1.2 )

As much as possible, the team is aiming for frequent releases. If the roadmap for the current development version is big, milestone releases can be applied until the final release. But if the roadmap is composed of just a small number of issues, we could proceed immediately to preparing a release candidate and push it out as the final release once it passes the vote.

References

Mailing list discussion regarding conventions

- -

- - - + + + + + + + + + + Archiva - How We Do Things + + + + + + + + + + + + + + + + + + + + + + + +