Archiva - Building Archiva

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-all-maven-3.x-jdk-1.6:

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

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 commu nity 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

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-all-maven-3.x-jdk-1.6:

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

Code Style

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 communi ty 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 )

References

Mailing list discussion regarding conventions

Getting Involved in the Archiva Project

Archiva is an open source project and relies heavily on an active community. If you need help, you should look to the community. Equally, please look for ways that you may contribute back.

This page provides some pointers for receiving help and contributing to the Archiva community.

Getting Help

There are a number of ways to find help if you have an issue.

Read the documentation
Read the user and administration documentation.
Search the Wiki
Search the Archiva Wiki. Lots of useful information has been contributed by users here.
Submit an issue
Search the Jira issue tracking system. The problem you are experiencing may be a known issue and others may have suggested work-arounds. If the issue is new, you should consider submitting a report.
Search the mailing lists
Search the mailing lists. Look here for a list of Archiva mailing lists. If you cannot find everything you need, ask a question on the appropriate list.

More Information

If you are new to Archiva (or Maven), there are a number of helpful resources on the Maven website which provide step-by-step guides to getting help, useful information regarding etiquette, and lots of other resources.

Check out:

How to Contribute

As with any open source project, there are several ways you can help:

Join a mailing list
Join a mailing list and answer other user's questions. You can also meet up with developers and users on #archiva on irc.codehaus.org
Fix bugs
Report bugs, feature requests and other issues in the Jira issue tracking system. Also, read up on how we do things in Archiva.
Build it
Check out the source code and build Archiva for yourself. Fix bugs and submit patches for reported issues (both those you find, or that others have filed).
Write documentation
Help with the documentation by pointing out areas that are lacking or unclear, and if you are so inclined, submitting patches to correct it. You can quickly contribute rough thoughts to the wiki, or you can volunteer to help collate and organise information that is already there.

Your participation in the community is much appreciated!

More Information

If you are new to Archiva (or Maven), there are a number of helpful resources on the Maven website regarding contribution back to the community.

Check out:

Getting Involved in the Archiva Project

Archiva is an open source project and relies heavily on an active community. If you need help, you should look to the community. Equally, please look for ways that you may contribute back.

This page provides some pointers for receiving help and contributing to the Archiva community.

Getting Help

There are a number of ways to find help if you have an issue.

Read the documentation
Read the user and administration documentation.
Search the Wiki
Search the Archiva Wiki. Lots of useful information has been contributed by users here.
Submit an issue
Search the Jira issue tracking system. The problem you are experiencing may be a known issue and others may have suggested work-arounds. If the issue is new, you should consider submitting a report.
Search the mailing lists
Search the mailing lists. Look here for a list of Archiva mailing lists. If you cannot find everything you need, ask a question on the appropriate list.

More Information

Check out:

How to Contribute

As with any open source project, there are several ways you can help:

Join a mailing list
Join a mailing list and answer other user's questions. You can also meet up with developers and users on #archiva on irc.codehaus.org
Fix bugs
Report bugs, feature requests and other issues in the Jira issue tracking system. Also, read up on how we do things in Archiva.
Build it
Check out the source code and build Archiva for yourself. Fix bugs and submit patches for reported i ssues (both those you find, or that others have filed).
Write documentation
Help with the documentation by pointing out areas that are lacking or unclear, and if you are so inclined, submitting patches to correct it. You can quickly contribute rough thoughts to the wiki, or you can volunteer to help collate and organise information that is already there.

Your participation in the community is much appreciated!

More Information

If you are new to Archiva (or Maven), there are a number of helpful resources on the Maven website regarding contribution back to the community.

Check out: