openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [CONF] OpenJPA > Source Code
Date Fri, 20 Aug 2010 12:54:00 GMT
    <base href="">
            <link rel="stylesheet" href="/confluence/s/1810/9/5/_/styles/combined.css?spaceKey=openjpa&amp;forWysiwyg=true"
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
    <h2><a href="">Source
    <h4>Page <b>edited</b> by             <a href="">Donald
        <div id="versionComment">
        add link to automated builds<br />
                         <h4>Changes (1)</h4>
<div id="page-diffs">
            <table class="diff" cellpadding="0" cellspacing="0">
            <tr><td class="diff-snipped" >...<br></td></tr>
            <tr><td class="diff-unchanged" >Once you&#39;ve got the code you&#39;ll
probably want to build it; for instructions see [Building]. <br> <br></td></tr>
            <tr><td class="diff-added-lines" style="background-color: #dfd;">We
also have [Automated Builds] setup for several branches of OpenJPA. <br></td></tr>
            <tr><td class="diff-unchanged" > <br> <br></td></tr>
            <tr><td class="diff-snipped" >...<br></td></tr>
</div>                            <h4>Full Content</h4>
                    <div class="notificationGreySide">

<h1><a name="SourceCode-SourceCode"></a>Source Code</h1>

<p>OpenJPA uses <a href="" class="external-link" rel="nofollow">Subversion</a>
to manage its source code. Instructions on Subversion use can be found <a href=""
class="external-link" rel="nofollow">here</a>.</p>

<h3><a name="SourceCode-WebAccess"></a>Web Access</h3>

<p>The source code for OpenJPA can be freely browsed at <a href=""
class="external-link" rel="nofollow"></a>. The
source code can also be searched and browsed using Cenqua's FishEye product at <a href=""
class="external-link" rel="nofollow"></a>.</p>

<h3><a name="SourceCode-Anonymousaccess"></a>Anonymous access</h3>

<p>OpenJPA source can be checked out anonymously with this command:</p>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
<pre>$&gt; svn checkout openjpa

<h3><a name="SourceCode-DeveloperAccess"></a>Developer Access</h3>

<p>Everyone can access the OpenJPA Subversion repository via HTTPS, but OpenJPA Committers
must checkout the Subversion repository via HTTPS in order to make updates, which will prompt
for your ASF uid/pwd.</p>

<div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent
<pre>$&gt; svn checkout openjpa

<h1><a name="SourceCode-CompilingSource"></a>Compiling Source</h1>

<p>Once you've got the code you'll probably want to build it; for instructions see <a
href="/confluence/display/openjpa/Building" title="Building">Building</a>.</p>

<p>We also have <a href="/confluence/display/openjpa/Automated+Builds" title="Automated
Builds">Automated Builds</a> setup for several branches of OpenJPA.</p>

<h1><a name="SourceCode-SourceCodingStandards"></a>Source Coding Standards</h1>

<p>The community has agreed upon some common code formatting standards, which we request
that everyone follows when contributing patches and checking in changes to the svn repository.
 Some of these are enforced during the build, like 120 character line length by using the
Checkstyle plugin and checking for required ASL 2.0 source headers by using the apache-rat
plugin.  Please checkout the <a href="/confluence/display/openjpa/Coding+Standards" title="Coding
Standards">Coding Standards</a> page for more details.</p>

        <div id="commentsSection" class="wiki-content pageSection">
        <div style="float: right;">
            <a href=""
class="grey">Change Notification Preferences</a>
        <a href="">View
        <a href="">View
        <a href=";showCommentArea=true#addcomment">Add

View raw message