| 1 |
# -------------------------------------------------------------------
|
| 2 |
# Copyright 2001-2005 The Apache Software Foundation.
|
| 3 |
#
|
| 4 |
# Licensed under the Apache License, Version 2.0 (the "License");
|
| 5 |
# you may not use this file except in compliance with the License.
|
| 6 |
# You may obtain a copy of the License at
|
| 7 |
#
|
| 8 |
# http://www.apache.org/licenses/LICENSE-2.0
|
| 9 |
#
|
| 10 |
# Unless required by applicable law or agreed to in writing, software
|
| 11 |
# distributed under the License is distributed on an "AS IS" BASIS,
|
| 12 |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
| 13 |
# See the License for the specific language governing permissions and
|
| 14 |
# limitations under the License.
|
| 15 |
# -------------------------------------------------------------------
|
| 16 |
|
| 17 |
report.dependencies.name=Dependencies
|
| 18 |
report.dependencies.nolist=There are no dependencies for this project. It is a standalone application that does not depend on any other project.
|
| 19 |
report.dependencies.title=Project Dependencies
|
| 20 |
report.dependencies.description=This document lists the projects dependencies and provides information on each dependency.
|
| 21 |
report.dependencies.intro=The following is a list of dependencies for this project. These dependencies are required to compile and run the application:
|
| 22 |
report.dependencies.column.groupId=GroupId
|
| 23 |
report.dependencies.column.artifactId=ArtifactId
|
| 24 |
report.dependencies.column.version=Version
|
| 25 |
report.dependencies.column.description=Description
|
| 26 |
report.dependencies.column.url=URL
|
| 27 |
report.dependencies.column.optional=Optional
|
| 28 |
|
| 29 |
report.dependencies.intro.runtime=The following is a list of runtime dependencies for this project. These dependencies are required to run the application:
|
| 30 |
report.dependencies.intro.compile=The following is a list of compile dependencies for this project. These dependencies are required to compile and run the application:
|
| 31 |
report.dependencies.intro.test=The following is a list of test dependencies for this project. These dependencies are only required to compile and run unit tests for the application:
|
| 32 |
report.dependencies.intro.provided=The following is a list of provided dependencies for this project. These dependencies are required to compile the application, but should be provided by default when using the library:
|
| 33 |
report.dependencies.intro.system=The following is a list of system dependencies for this project. These dependencies are required to compile the application:
|
| 34 |
|
| 35 |
report.transitivedependencies.title=Project Transitive Dependencies
|
| 36 |
report.transitivedependencies.nolist=No transitive dependencies are required for this project.
|
| 37 |
report.transitivedependencies.intro=The following is a list of transitive dependencies for this project. Transitive dependencies are the dependencies of the project dependencies:
|
| 38 |
report.transitivedependencies.column.groupId=GroupId
|
| 39 |
report.transitivedependencies.column.artifactId=ArtifactId
|
| 40 |
report.transitivedependencies.column.version=Version
|
| 41 |
report.transitivedependencies.column.description=Description
|
| 42 |
report.transitivedependencies.column.url=URL
|
| 43 |
|
| 44 |
report.mailing-lists.name=Mailing Lists
|
| 45 |
report.mailing-lists.nolist=There are no mailing lists currently associated with this project.
|
| 46 |
report.mailing-lists.title=Project Mailing Lists
|
| 47 |
report.mailing-lists.description=This document provides subscription and archive information for this project's mailing lists.
|
| 48 |
report.mailing-lists.intro=These are the mailing lists that have been established for this project. For each list, there is a subscribe, unsubscribe, and an archive link.
|
| 49 |
report.mailing-lists.column.name=Name
|
| 50 |
report.mailing-lists.column.subscribe=Subscribe
|
| 51 |
report.mailing-lists.column.unsubscribe=Unsubscribe
|
| 52 |
report.mailing-lists.column.post=Post
|
| 53 |
report.mailing-lists.column.archive=Archive
|
| 54 |
report.mailing-lists.column.otherArchives=Other Archives
|
| 55 |
|
| 56 |
report.team-list.name=Project Team
|
| 57 |
report.team-list.description=This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another.
|
| 58 |
report.team-list.title=Team list
|
| 59 |
report.team-list.intro.title=The Team
|
| 60 |
report.team-list.intro.description1=A successful project requires many people to play many roles. Some members write code or documentation, while others are valuable as testers, submitting patches and suggestions.
|
| 61 |
report.team-list.intro.description2=The team is comprised of Members and Contributors. Members have direct access to the source of a project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated.
|
| 62 |
report.team-list.developers.title=Members
|
| 63 |
report.team-list.nodeveloper=There are no developers working on this project.
|
| 64 |
report.team-list.developers.intro=The following is a list of developers with commit privileges that have directly contributed to the project in one way or another.
|
| 65 |
report.team-list.developers.id=Id
|
| 66 |
report.team-list.developers.name=Name
|
| 67 |
report.team-list.developers.email=Email
|
| 68 |
report.team-list.developers.url=URL
|
| 69 |
report.team-list.developers.organization=Organization
|
| 70 |
report.team-list.developers.organizationurl=Organization URL
|
| 71 |
report.team-list.developers.roles=Roles
|
| 72 |
report.team-list.developers.timezone=Time Zone
|
| 73 |
report.team-list.developers.actualtime=Actual Time (GMT)
|
| 74 |
report.team-list.developers.properties=Properties
|
| 75 |
report.team-list.contributors.title=Contributors
|
| 76 |
report.team-list.nocontributor=There are no contributors listed for this project. Please check back again later.
|
| 77 |
report.team-list.contributors.intro=The following additional people have contributed to this project through the way of suggestions, patches or documentation.
|
| 78 |
report.team-list.contributors.name=Name
|
| 79 |
report.team-list.contributors.email=Email
|
| 80 |
report.team-list.contributors.url=URL
|
| 81 |
report.team-list.contributors.organization=Organization
|
| 82 |
report.team-list.contributors.organizationurl=Organization URL
|
| 83 |
report.team-list.contributors.roles=Roles
|
| 84 |
report.team-list.contributors.timezone=Time Zone
|
| 85 |
report.team-list.contributors.actualtime=Actual Time (GMT)
|
| 86 |
report.team-list.contributors.properties=Properties
|
| 87 |
|
| 88 |
report.scm.name=Source Repository
|
| 89 |
report.scm.description=This is a link to the online source repository that can be viewed via a web browser.
|
| 90 |
report.scm.noscm=No source configuration management system is defined. Please check back at a later date.
|
| 91 |
report.scm.title=Source Repository
|
| 92 |
report.scm.overview.title=Overview
|
| 93 |
report.scm.clearcase.intro=This project uses {ClearCase, http://www-306.ibm.com/software/awdtools/clearcase/} to manage its source code. Informations on ClearCase use can be found at {http://www.redbooks.ibm.com/redbooks/pdfs/sg246399.pdf, http://www.redbooks.ibm.com/redbooks/pdfs/sg246399.pdf}.
|
| 94 |
report.scm.cvs.intro=This project uses {Concurrent Versions System, http://www.cvshome.org/} to manage its source code. Instructions on CVS use can be found at {http://cvsbook.red-bean.com/, http://cvsbook.red-bean.com/}.
|
| 95 |
report.scm.perforce.intro=This project uses {Perforce, http://www.perforce.com/} to manage its source code. Instructions on Perforce use can be found at {http://www.perforce.com/perforce/doc.051/manuals/cmdref/index.html, http://www.perforce.com/perforce/doc.051/manuals/cmdref/index.html}.
|
| 96 |
report.scm.starteam.intro=This project uses {Starteam, http://www.borland.com/us/products/starteam/} to manage its source code.
|
| 97 |
report.scm.svn.intro=This project uses {Subversion, http://subversion.tigris.org/} to manage its source code. Instructions on Subversion use can be found at {http://svnbook.red-bean.com/, http://svnbook.red-bean.com/}.
|
| 98 |
report.scm.general.intro=This project uses a Source Content Management System to manage its source code.
|
| 99 |
report.scm.webaccess.title=Web Access
|
| 100 |
report.scm.webaccess.url=The following is a link to the online source repository.
|
| 101 |
report.scm.webaccess.nourl=There are no online source repository listed for this project. Please check back again later.
|
| 102 |
report.scm.anonymousaccess.title=Anonymous access
|
| 103 |
report.scm.anonymousaccess.cvs.intro=This project's CVS repository can be checked out through anonymous CVS with the following instruction set. When prompted for a password for anonymous, simply press the Enter key.
|
| 104 |
report.scm.anonymousaccess.svn.intro=The source can be checked out anonymously from SVN with this command:
|
| 105 |
report.scm.anonymousaccess.general.intro=Refer to the documentation of the SCM used for more information about anonymously check out. The connection url is:
|
| 106 |
report.scm.devaccess.title=Developer access
|
| 107 |
report.scm.devaccess.clearcase.intro=Only project developers can access the ClearCase tree via this method. Substitute username with the proper value.
|
| 108 |
report.scm.devaccess.cvs.intro=Only project developers can access the CVS tree via this method. Substitute username with the proper value.
|
| 109 |
report.scm.devaccess.perforce.intro=Only project developers can access the Perforce tree via this method. Substitute username and password with the proper value.
|
| 110 |
report.scm.devaccess.starteam.intro=Only project developers can access the Starteam tree via this method. Substitute username with the proper value.
|
| 111 |
report.scm.devaccess.svn.intro1=Everyone can access the Subversion repository via HTTPS, but Committers must checkout the Subversion repository via HTTPS.
|
| 112 |
report.scm.devaccess.svn.intro2=To commit changes to the repository, execute the following command to commit your changes (svn will prompt you for your password)
|
| 113 |
report.scm.devaccess.general.intro=Refer to the documentation of the SCM used for more information about developer checked out. The connection url is:
|
| 114 |
report.scm.accessbehindfirewall.title=Access from behind a firewall
|
| 115 |
report.scm.accessbehindfirewall.svn.intro=For those users who are stuck behind a corporate firewall which is blocking http access to the Subversion repository, you can try to access it via the developer connection:
|
| 116 |
report.scm.accessbehindfirewall.cvs.intro=For those developers who are stuck behind a corporate firewall, {CVSGrab, http://cvsgrab.sourceforge.net/} can use the viewcvs web interface to checkout the source code.
|
| 117 |
report.scm.accessbehindfirewall.general.intro=Refer to the documentation of the SCM used for more information about an access behind a firewall.
|
| 118 |
report.scm.accessthroughtproxy.title=Access through a proxy
|
| 119 |
report.scm.accessthroughtproxy.svn.intro1=The Subversion client can go through a proxy, if you configure it to do so. First, edit your "servers" configuration file to indicate which proxy to use. The files location depends on your operating system. On Linux or Unix it is located in the directory "~/.subversion". On Windows it is in "%APPDATA%\\Subversion". (Try "echo %APPDATA%", note this is a hidden directory.)
|
| 120 |
report.scm.accessthroughtproxy.svn.intro2=There are comments in the file explaining what to do. If you don't have that file, get the latest Subversion client and run any command; this will cause the configuration directory and template files to be created.
|
| 121 |
report.scm.accessthroughtproxy.svn.intro3=Example : Edit the 'servers' file and add something like :
|
| 122 |
|
| 123 |
report.issuetracking.name=Issue Tracking
|
| 124 |
report.issuetracking.description=This is a link to the issue management system for this project. Issues (bugs, features, change requests) can be created and queried using this link.
|
| 125 |
report.issuetracking.noissueManagement=No issue management system is defined. Please check back at a later date.
|
| 126 |
report.issuetracking.overview.title=Overview
|
| 127 |
report.issuetracking.jira.intro=This project uses {Jira, http://www.atlassian.com/software/jira} a J2EE-based, issue tracking and project management application.
|
| 128 |
report.issuetracking.bugzilla.intro=This project uses {Bugzilla, http://www.bugzilla.org/}.
|
| 129 |
report.issuetracking.scarab.intro=This project uses {Scarab, http://scarab.tigris.org/}.
|
| 130 |
report.issuetracking.general.intro=This project uses an Issue Management System to manage its issues.
|
| 131 |
report.issuetracking.custom.intro=This project uses %issueManagementSystem% to manage its issues.
|
| 132 |
report.issuetracking.title=Issue Tracking
|
| 133 |
report.issuetracking.intro=Issues, bugs, and feature requests should be submitted to the following issue tracking system for this project.
|
| 134 |
|
| 135 |
report.cim.name=Continuous Integration
|
| 136 |
report.cim.description=This is a link to the definitions of all continuous integration processes that builds and tests code on a frequent, regular basis.
|
| 137 |
report.cim.nocim=No continuous integration management system is defined. Please check back at a later date.
|
| 138 |
report.cim.title=Continuous Integration
|
| 139 |
report.cim.overview.title=Overview
|
| 140 |
report.cim.continuum.intro=This project uses {Continuum, http://maven.apache.org/continuum/}.
|
| 141 |
report.cim.bugzilla.intro=This project uses {Bugzilla, http://www.bugzilla.org/}.
|
| 142 |
report.cim.general.intro=This project uses Continuous Integration System.
|
| 143 |
report.cim.access=Access
|
| 144 |
report.cim.url=The following is a link to the continuous integration system used by the project.
|
| 145 |
report.cim.nourl=No url to the continuous integration system is defined.
|
| 146 |
report.cim.notifiers.title=Notifiers
|
| 147 |
report.cim.notifiers.nolist=No notifiers is defined. Please check back at a later date.
|
| 148 |
report.cim.notifiers.intro=Configuration for notifying developers/users when a build is unsuccessful, including user information and notification mode.
|
| 149 |
report.cim.notifiers.column.type=Type
|
| 150 |
report.cim.notifiers.column.address=Address
|
| 151 |
report.cim.notifiers.column.configuration=Configuration
|
| 152 |
|
| 153 |
report.license.name=Project License
|
| 154 |
report.license.description=This is a link to the definitions of project licenses.
|
| 155 |
report.license.nolicense=No project license is defined for this project.
|
| 156 |
report.license.title=Project License
|
| 157 |
report.license.overview.title=Overview
|
| 158 |
report.license.overview.intro=Typically the licenses listed for the project are that of the project itself, and not of dependencies.
|
| 159 |
|
| 160 |
report.dependency-convergence.name=Dependency Convergence
|
| 161 |
report.dependency-convergence.description=This document presents the convergence of dependency versions across the entire project, and its sub modules.
|
| 162 |
report.dependency-convergence.title=Reactor Dependency Convergence
|
| 163 |
report.dependency-convergence.legend=Legend
|
| 164 |
report.dependency-convergence.legend.shared=All projects share one version of the dependency.
|
| 165 |
report.dependency-convergence.legend.different=At least one project has a differing version of the dependency.
|
| 166 |
report.dependency-convergence.stats.caption=Statistics
|
| 167 |
report.dependency-convergence.stats.subprojects=Number of sub-projects
|
| 168 |
report.dependency-convergence.stats.dependencies=Number of dependencies (NOD)
|
| 169 |
report.dependency-convergence.stats.artifacts=Number of unique artifacts (NOA)
|
| 170 |
report.dependency-convergence.stats.snapshots=Number of SNAPSHOT artifacts (NOS)
|
| 171 |
report.dependency-convergence.stats.convergence=Convergence (NOD/NOA)
|
| 172 |
report.dependency-convergence.stats.readyrelease=Ready for Release (100% Convergence and no SNAPSHOTS)
|
| 173 |
report.dependency-convergence.stats.readyrelease.success=Success
|
| 174 |
report.dependency-convergence.stats.readyrelease.error=Error
|
| 175 |
report.dependency-convergence.stats.readyrelease.error.convergence=You do not have 100% convergence.
|
| 176 |
report.dependency-convergence.stats.readyrelease.error.snapshots=You have SNAPSHOT dependencies.
|
| 177 |
report.dependency-convergence.convergence.caption=Dependencies used in sub-projects
|
Parent Directory
| 
Revision Log