DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Software Design and Architecture
  3. Performance
  4. Documentation-Patch Submission For Apache Issues

Documentation-Patch Submission For Apache Issues

Will Soprano user avatar by
Will Soprano
·
Aug. 26, 12 · Interview
Like (0)
Save
Tweet
Share
2.87K Views

Join the DZone community and get the full member experience.

Join For Free

 The following piece is authored by: Pushpalanka

Submitting a patch for a documentation issue is same as submitting a patch for a code issue. Only thing to be noticed is where the source code for sites resides. Here I am sharing the steps in a very basic level as helpful for a beginner, from identifying an issue to the submission of patch.
Note:The sample commands I am using here are for linux and for other environments the relevant commands should be applied for same functionality.

  • After identifying the issue from Apache issue navigator, check out the relevant files directory from apache SVN.
       eg : svn co  http://svn.apache.org/repos/asf/axis/axis2/java/core/trunk/src/site/xdoc/
  • Navigate to the relevant .xml files and do the improvements or corrections needed and make sure the xml validation is done and the document is presented as it is intended to be.
  • Lets see how the changes are applying. In the top level directory that includes all the changes and improvements enter the following command.

             eg: svn diff -x-p
          You will see something as follows,

 
                     - lines preceded with - are to be deleted
                     - lines preceded with + are to be added

  • Make sure those are the intended changes and then create the patch with the following command:
            svn diff ><the preferred name for patch file>
            eg: svn diff >AXIS2-4655.patch
  • Now submit the patch at the jira issue page as follows and add any meaningful comments.

Keep in touch for updates on the patch submitted. Keep contributing.
Patch (computing) code style Command (computing) Diff EGS (program) Directory COS (operating system) Documentation Linux (operating system)

Published at DZone with permission of Will Soprano. See the original article here.

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How and Why You Should Start Automating DevOps
  • How to Quickly Build an Audio Editor With UI
  • How To Use Terraform to Provision an AWS EC2 Instance
  • The Future of Cloud Engineering Evolves

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: