jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
Signup
Maven 2.x Release Plugin
  • Maven 2.x Release Plugin
  • MRELEASE-141

Review Plugin Documentation

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Task Task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1
  • Fix Version/s: 2.0-beta-5
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Add examples and FAQs, pass docck, fix navigation and home page to conform with plugin documentation standards.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
John Tolentino added a comment - 18/Sep/06 1:16 AM

Done

Show
John Tolentino added a comment - 18/Sep/06 1:16 AM Done
Hide
Permalink
Natalie Burdick added a comment - 18/Sep/06 12:37 PM

below are my suggested edits, and a question on terminology

http://people.apache.org/~jtolentino/maven-release-plugin/index.html

Maven Release Plugin

This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project takes two steps: prepare and perform. [are these steps/goals or tasks?would be good to use consistent terms -- also in goals there are three listed and below under examples there are even more -- ]

Usage

Instructions on how to use the Maven Release Plugin can be found here.

Examples

To provide you with better understanding on some working scenarios for the Maven Release Plugin, you can take a look into the following examples:

  • Perform Release
  • Prepare Release
  • Generate Release POMs
  • Lock Files During Release
  • Run Additional Goals Before Commit

---------------------------
http://people.apache.org/~jtolentino/maven-release-plugin/faq.html - suggested text/language edits:

1. When releasing from a parent pom, will all the sub-project modules use the same release version and dev version as the parent?

When releasing from a parent pom, will all the sub-project modules use the same release version and dev version as the parent?

No, the Maven Release Plugin will prompt for each sub-project's version information.

[Key is whenever asking a question, don't use negative - 'won't', and always put the actual answer - 'No' in this case, in the response]

Show
Natalie Burdick added a comment - 18/Sep/06 12:37 PM below are my suggested edits, and a question on terminology http://people.apache.org/~jtolentino/maven-release-plugin/index.html Maven Release Plugin This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project takes two steps: prepare and perform. [are these steps/goals or tasks?would be good to use consistent terms -- also in goals there are three listed and below under examples there are even more -- ] Usage Instructions on how to use the Maven Release Plugin can be found here. Examples To provide you with better understanding on some working scenarios for the Maven Release Plugin, you can take a look into the following examples: Perform Release Prepare Release Generate Release POMs Lock Files During Release Run Additional Goals Before Commit --------------------------- http://people.apache.org/~jtolentino/maven-release-plugin/faq.html - suggested text/language edits: 1. When releasing from a parent pom, will all the sub-project modules use the same release version and dev version as the parent? When releasing from a parent pom, will all the sub-project modules use the same release version and dev version as the parent? No, the Maven Release Plugin will prompt for each sub-project's version information. [Key is whenever asking a question, don't use negative - 'won't', and always put the actual answer - 'No' in this case, in the response]

People

  • Assignee:
    John Tolentino
    Reporter:
    John Tolentino
Vote (0)
Watch (0)

Dates

  • Due:
    27/Jul/06
    Created:
    14/Jul/06 1:08 AM
    Updated:
    19/Apr/07 3:50 AM
    Resolved:
    18/Sep/06 1:16 AM

Time Tracking

Estimated:
1d 7h
Original Estimate - 1 day, 7 hours Original Estimate - 1 day, 7 hours
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
1d 8h
Time Spent - 1 day, 8 hours
  • Atlassian JIRA (v5.2.7#850-sha1:b2af0c8)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.