StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
2241155
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-02-10T23:34:24.097
FavoriteCount
0
LastActivityDate
2010-02-10T23:34:24.097
LastEditDate
LastEditorUserId
0
OwnerUserId
237237
ParentId
2234124
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
As I understand it you are trying to keep the version up to date, while expecting the rest to stay the same. There are two alternatives. The first is to remove the version from the name so that the HTML need not change. You can see a practical example by searching for <code>archiva-applet</code> here: <a href="http://svn.apache.org/repos/asf/archiva/tags/archiva-1.3/archiva-modules/archiva-web/archiva-webapp/pom.xml" rel="nofollow noreferrer">http://svn.apache.org/repos/asf/archiva/tags/archiva-1.3/archiva-modules/archiva-web/archiva-webapp/pom.xml</a> In this example, since you don't want the applet in <code>WEB-INF/classes</code> anyway, it is omitted from the webapp, and then included via the Dependency plugin: <pre><code><plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-dependency-plugin</artifactId> <version>2.0</version> <executions> <execution> <id>copy</id> <phase>process-resources</phase> <goals> <goal>copy</goal> </goals> <configuration> <artifactItems> <artifactItem> <groupId>${project.groupId}</groupId> <artifactId>archiva-applet</artifactId> <version>${project.version}</version> <outputDirectory>src/main/webapp</outputDirectory> <destFileName>archiva-applet.jar</destFileName> </artifactItem> </artifactItems> </configuration> </execution> </executions> </plugin> </code></pre> If you are using Maven 2.1.0+ you can use the <code>prepare-package</code> phase and copy it straight to the output without modifying your source directory. You then refer to the applet in HTML with the single name. An alternative solution if you want to continue filtering and keep the version, is to use a shared property: <pre><code><properties> <applet.version>1.2.3</applet.version> </properties> </code></pre> ... <pre><code><dependency> <groupId>my.group</groupId> <artifactId>my.applet</artifactId> <version>${applet.version}</version> </dependency> </code></pre> ... You can then use <code>${applet.version}</code> in the HTML and still only have to change it in one place.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POMaven project variables for dependencies
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USBrett Porter
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
2. 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.