mirror of
https://github.com/google/nomulus.git
synced 2025-05-21 19:59:34 +02:00
Make javadoc <p> style guide compliant
This led to confusion for an open source contributor about how to format code. We don't want to be like, "do as I say, not as I do." https://google.github.io/styleguide/javaguide.html#s7.1.2-javadoc-paragraphs ------------- Created by MOE: https://github.com/google/moe MOE_MIGRATED_REVID=122589700
This commit is contained in:
parent
4854f875b0
commit
6f4b059cc9
79 changed files with 395 additions and 386 deletions
|
@ -24,13 +24,13 @@ import javax.xml.bind.annotation.adapters.XmlJavaTypeAdapter;
|
|||
|
||||
/**
|
||||
* Represents the EPP application status.
|
||||
* <p>
|
||||
* These values are never read from a command and only used in responses, so, we don't need to model
|
||||
* anything we don't output. We don't model the CUSTOM status because we don't use it. This allows
|
||||
* us to also avoid modeling the "name" attribute which is only used with CUSTOM. We don't model the
|
||||
* "lang" attribute because we only support English and that's the default.
|
||||
* <p>
|
||||
* Given all of this, we can use {@link EnumToAttributeAdapter} to make this code very simple.
|
||||
*
|
||||
* <p>These values are never read from a command and only used in responses, so, we don't need to
|
||||
* model anything we don't output. We don't model the CUSTOM status because we don't use it. This
|
||||
* allows us to also avoid modeling the "name" attribute which is only used with CUSTOM. We don't
|
||||
* model the "lang" attribute because we only support English and that's the default.
|
||||
*
|
||||
* <p>Given all of this, we can use {@link EnumToAttributeAdapter} to make this code very simple.
|
||||
*
|
||||
* @see "http://tools.ietf.org/html/draft-tan-epp-launchphase-11#section-2.3"
|
||||
*/
|
||||
|
|
|
@ -26,9 +26,9 @@ import javax.xml.bind.annotation.XmlRootElement;
|
|||
/**
|
||||
* An XML data object that represents a launch extension that may be present on EPP domain check
|
||||
* commands.
|
||||
* <p>
|
||||
* This object holds XML data which JAXB will unmarshal from an EPP domain check command extension.
|
||||
* The XML will have the following enclosing structure:
|
||||
*
|
||||
* <p>This object holds XML data which JAXB will unmarshal from an EPP domain check command
|
||||
* extension. The XML will have the following enclosing structure:
|
||||
*
|
||||
* <pre> {@code
|
||||
* <epp>
|
||||
|
|
|
@ -34,9 +34,9 @@ import javax.xml.bind.annotation.XmlRootElement;
|
|||
/**
|
||||
* An XML data object that represents a launch extension that may be present on EPP domain create
|
||||
* commands.
|
||||
* <p>
|
||||
* This object holds XML data which JAXB will unmarshal from an EPP domain create command extension.
|
||||
* The XML will have the following enclosing structure:
|
||||
*
|
||||
* <p>This object holds XML data which JAXB will unmarshal from an EPP domain create command
|
||||
* extension. The XML will have the following enclosing structure:
|
||||
*
|
||||
* <pre> {@code
|
||||
* <epp>
|
||||
|
|
|
@ -34,8 +34,8 @@ import javax.xml.bind.annotation.XmlValue;
|
|||
|
||||
/**
|
||||
* The launch phase of the TLD being addressed by this command.
|
||||
* <p>
|
||||
* The launch phase refers to the various stages that a TLD goes through before entering general
|
||||
*
|
||||
* <p>The launch phase refers to the various stages that a TLD goes through before entering general
|
||||
* availability. The various phases are described below (in order that they usually occur).
|
||||
*/
|
||||
@Embed
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue