StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19057100
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-27T17:52:25.123
FavoriteCount
0
LastActivityDate
2013-09-27T18:12:47.760
LastEditDate
2013-09-27T18:12:47.760
LastEditorUserId
679982
OwnerUserId
679982
ParentId
19054523
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The problem can not be treated with respect to <code>id</code> tag only but notice the different values of it through the examples. This has been tested with maven 3.0.5. Consider the following pom part: <pre><code> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-docck-plugin</artifactId> <version>1.0</version> <executions> <execution> <id>some-other-other-id</id>  <phase>pre-site</phase> </execution> <execution> <phase>pre-site</phase>  <goals> <goal>check</goal> </goals> </execution> <execution> <id>some-id</id>  <goals> <goal>check</goal> </goals> </execution> <execution> <id>some-other-id</id>  <phase>pre-site</phase> <goals> <goal>check</goal> </goals> </execution> </executions> </plugin> </code></pre> When run <code>mvn clean site</code> from command line it outputs the following: <pre><code>[INFO] --- maven-docck-plugin:1.0:check (default) @ MavenJavaApplication --- [INFO] Skipping unsupported project: MavenJavaApplication [INFO] No documentation errors were found. [INFO] [INFO] --- maven-docck-plugin:1.0:check (some-other-id) @ MavenJavaApplication --- [INFO] Skipping unsupported project: MavenJavaApplication [INFO] No documentation errors were found. </code></pre> Notice that the execution outputs are always in form of: <pre><code><plugin-name>:<plugin-version>:<phase> (<execution-id>) </code></pre> <h3>Case 1: No goal for execution is defined</h3> From <a href="http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics" rel="nofollow">Build lifecycle basics</a>: <blockquote> A plugin goal represents a specific task (finer than a build phase) which contributes to the building and managing of a project. It may be bound to zero or more build phases. A goal not bound to any build phase could be executed outside of the build lifecycle by direct invocation. (...) Moreover, if a goal is bound to one or more build phases, that goal will be called in all those phases. </blockquote> From <a href="http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Configuring_Build_Plugins" rel="nofollow">Guide to configuring plugins: Configuring build plugins</a>: <blockquote> But if the goal is not bound to any lifecycle phase then it simply won't be executed during the build lifecycle. </blockquote> From what is quoted, it may be concluded that the execution with id <code>some-other-other-id</code> can be ran from the command line, but that is not so, it can never be ran - it will be covered in the 5th example. <h3>Case 2: No id for execution is defined</h3> The definition of <code>goal</code> and a <code>phase</code> in the first execution is enough for it to get run so it gets <a href="http://maven.apache.org/guides/mini/guide-default-execution-ids.html" rel="nofollow">assigned a default execution id</a> of value <code>default</code> and it gets executed. <h3>Case 3: No phase for execution is defined</h3> Since the phase is not defined anywhere this execution does not get executed. It can be verified by the fact that the output does not contain the line with its execution id. <h3>Case 4: Both id and phase defined</h3> This execution defines all three: an <code>id</code>, a <code>phase</code> and a <code>goal</code> so it gets executed. <h3>Case 5: CLI execution</h3> If you run (read the syntax in the <a href="http://maven.apache.org/plugins/maven-docck-plugin/plugin-info.html" rel="nofollow">docck plugin documentation</a>): <pre><code>mvn docck:check -Doffline=true </code></pre> it will output: <pre><code>[INFO] --- maven-docck-plugin:1.0:check (default-cli) @ MavenJavaApplication --- </code></pre> From <a href="http://maven.apache.org/guides/mini/guide-default-execution-ids.html" rel="nofollow">Guide to configuring default mojo executions</a>: <blockquote> Starting in Maven 2.2.0, each mojo invoked directly from the command line will have an execution Id of default-cli assigned to it, which will allow the configuration of that execution from the POM by using this default execution Id </blockquote> You can provide the properties for the goal executed from CLI in three different ways: <ul> <li>in the command line directly</li> <li>in the plugin configuration</li> <li>in the execution tag with <code>id</code> of value <code>default-cli</code></li> </ul> Specifically, the above command is equivalent of running <pre><code>mvn docck:check </code></pre> with the pom containing: <pre><code> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-docck-plugin</artifactId> <version>1.0</version> <configuration> <offline>true</offline> </configuration> </plugin> </code></pre> or: <pre><code> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-docck-plugin</artifactId> <version>1.0</version> <executions> <execution> <id>default-cli</id> <phase>pre-site</phase> <goals> <goal>check</goal> </goals> <configuration> <offline>true</offline> </configuration> </execution> </executions> </plugin> </code></pre> This last part comes in handy if you want to keep the global configuration for some common properties in different executions, but you want a complete other set of properties for running from CLI. <h3>Case 6: The default execution</h3> Since the <code>maven-docck-plugin</code> has no default binding I'll cover it with the <a href="http://maven.apache.org/plugins/maven-compiler-plugin/index.html" rel="nofollow"><code>maven-compiler-plugin</code></a>. Consider an empty pom with <code>jar</code> packaging. If you run: <pre><code> mvn clean install </code></pre> it will trigger the <code>compile</code> phase also and you will see in output: <pre><code>[INFO] --- maven-compiler-plugin:2.3.1:compile (default-compile) @ MavenJavaApplication --- </code></pre> To cover the value of the <code>id</code> tag, from <a href="http://maven.apache.org/guides/mini/guide-default-execution-ids.html" rel="nofollow">Guide to Configuring Default Mojo Executions</a>: <blockquote> Likewise, each mojo bound to the build lifecycle via the default lifecycle mapping for the specified POM packaging will have an execution Id of default-<goalName> assigned to it, to allow configuration of each default mojo execution independently. </blockquote> If you run <a href="http://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html" rel="nofollow"><code>mvn help:effective-pom</code></a> you will find the default execution definition for compiler plugin in output: <pre><code><execution> <id>default-compile</id> <phase>compile</phase> <goals> <goal>compile</goal> </goals> </execution> </code></pre> It gets inherited from <a href="http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Super_POM" rel="nofollow">super POM</a> for the <code>jar</code> <a href="http://maven.apache.org/pom.html#Maven_Coordinates" rel="nofollow">packaging</a> type: <blockquote> When no packaging is declared, Maven assumes the artifact is the default: jar. The valid types are Plexus role-hints (read more on Plexus for a explanation of roles and role-hints) of the component role org.apache.maven.lifecycle.mapping.LifecycleMapping. The current core packaging values are: pom, jar, maven-plugin, ejb, war, ear, rar, par. These define the default list of goals which execute to each corresponding build lifecycle stage for a particular package structure. </blockquote> In other words, the above default execution definition is the consequence of a default lifecycle mapping (<a href="http://maven.apache.org/plugins/maven-compiler-plugin/index.html" rel="nofollow">documentation</a>, <a href="http://maven.apache.org/ref/3.1.0/maven-core/default-bindings.html#Plugin_bindings_for_jar_packaging" rel="nofollow">definition</a> ) for the <code>compiler-plugin</code>: <blockquote> The Compiler Plugin has two goals. Both are already bound to their proper phases within the Maven Lifecycle and are therefore, automatically executed during their respective phases. <ul> <li>compiler:compile is bound to the compile phase and is used to compile the main source files. </li> </ul> </blockquote> <h2>Uniqueness of an execution id tag</h2> From <a href="http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Using_the_executions_Tag" rel="nofollow">Guide to configuring plugins.html: Using the executions tag</a>: <blockquote> Note that while execution id's have to be unique among all executions of a single plugin within a POM, they don't have to be unique across an inheritance hierarchy of POMs. Executions of the same id from different POMs are merged. The same applies to executions that are defined by profiles. </blockquote>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POmaven, execution tag, id tag missing
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USlinski
UserOwnerUserId
1. USlinski
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.