StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4991131
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2011-02-14T10:36:09.483
FavoriteCount
0
LastActivityDate
2011-02-14T10:36:09.483
LastEditDate
LastEditorUserId
0
OwnerUserId
256618
ParentId
4982485
PostTypeId
2
Score
11
ViewCount
0
LastEditorDisplayName
text
Body
Some open source modules include optional java doc jars. To remove them add a configuration mapping to each of your dependencies: <pre><code> <dependency org="junit" name="junit" rev="4.8.2" conf="default"/> </code></pre> The default configuration in ivy is equivalent to the the compile scope in a maven module. This is how the optional libraries can be automatically omitted. (Check their POMs). A better approach is to declare your own configurations and the default mapping as follows: <pre><code><configurations defaultconfmapping="compile->default"> <conf name="compile" description="Required to compile code"/> <conf name="test" description="Additional test dependencies" extends="compile" /> </configurations> </code></pre> Then in your ivy file you only need to declare the non-standard configurations: <pre><code><dependencies> <dependency org="org.hamcrest" name="hamcrest-library" rev="1.3.RC2" conf="test->default"/> <dependency org="junit" name="junit" rev="4.8.2" conf="test->default"/> <dependency org="org.mockito" name="mockito-core" rev="1.8.5" conf="test->default"/> <dependency org="javax.persistence" name="persistence-api" rev="1.0"/> </dependencies> </code></pre> In this case we only want the 3 test libraries to appear on the test configuration. Still confused? The magic of ivy configurations is when you use them to manage your build's class path <pre><code> <target name='dependencies' description='Resolve project dependencies and set classpaths'> <ivy:resolve/> <ivy:cachepath pathid="compile.path" conf="compile"/> <ivy:cachepath pathid="test.path" conf="test"/> </target> </code></pre> This is what Maven is doing when you declare a scope tag on a dependency, for example: <pre><code><dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>4.8.2</version> <scope>test</scope> </dependency> </code></pre> The scopes in Maven are fixed. In ivy you can have as many as you need.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POIvy appears to fetch javadoc jars only
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMark O'Connor
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POIvy appears to fetch javadoc jars only
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COBrilliant answer - thanks! I never understood Ivy scopes.
 singulars
 PostPostId
 PO
 UserUserId
 USMarty Pitt
2. COMy pleasure. Yeah, the ivy documentation recommends using configurations, but it's hard to understand why :-)
 singulars
 PostPostId
 PO
 UserUserId
 USMark O'Connor

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.