StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17181234
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-06-19T00:44:49.497
FavoriteCount
0
LastActivityDate
2013-06-19T01:17:15.497
LastEditDate
2013-06-19T01:17:15.497
LastEditorUserId
472153
OwnerUserId
472153
ParentId
11209382
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
<p><a href="https://github.com/evgeny-goldin/build-info/blob/3712d354f31d813c18c10a35dc07e9581979e61f/build.gradle#L360" rel="nofollow">Here's something</a> that worked for me:</p> <ul> <li>After compiling plugin's sources generate project's POM: <code>"install.repositories.mavenInstaller.pom.writeTo( 'pom.xml' )"</code></li> <li>Patch POM generated and provide plugin's coordinates and correct destination directories</li> <li>Run <code>"mvn org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor"</code></li> </ul> <p>This way <code>"build/classes/main/META-INF/maven/plugin.xml"</code> is created and then packed properly by <code>jar</code> task, which is all that's needed for a jar file to become a Maven plugin, AFAIK. Also, I believe, <a href="https://maven.apache.org/plugin-tools/maven-plugin-plugin/examples/using-annotations.html" rel="nofollow">"maven-plugin-annotations"</a> should be used in a plugin.</p> <pre><code>task pluginDescriptor( type: Exec ) { commandLine 'mvn', '-e', '-B', 'org.apache.maven.plugins:maven-plugin-plugin:3.2:descriptor' doFirst { final File pom = project.file( 'pom.xml' ) install.repositories.mavenInstaller.pom.writeTo( pom ) assert pom.file, "[$pom.canonicalPath] was not created" pom.text = pom.text. replace( '<groupId>unknown</groupId>', "<groupId>${project.group}</groupId>" ). replace( '<artifactId>empty-project</artifactId>', "<artifactId>${project.name}</artifactId>" ). replace( '<version>0</version>', """ |<version>${version}</version> | <packaging>maven-plugin</packaging> | <build> | <directory>\${project.basedir}/build</directory> | <outputDirectory>\${project.build.directory}/classes/main</outputDirectory> | </build> |""".stripMargin().trim()) } doLast { final pluginDescriptor = new File(( File ) project.compileGroovy.destinationDir, 'META-INF/maven/plugin.xml' ) assert pluginDescriptor.file, "[$pluginDescriptor.canonicalPath] was not created" println "Plugin descriptor file:$pluginDescriptor.canonicalPath is created successfully" } } project.compileGroovy.doLast{ pluginDescriptor.execute() } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBuild Maven plugins using Gradle
  singulars
  PostTypePostTypeId
  PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USEvgeny Goldin
UserOwnerUserId
1. USEvgeny Goldin
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. VO
  singulars
  PostPostId
  PO
  UserUserId
  This table or related slice is empty.
  VoteTypeVoteTypeId
  VTUpMod
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.