StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POMaven2: can we have dependency for a plugin thats used in the build section
primarykey
Id
19203721
data
AcceptedAnswerId
0
AnswerCount
3
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-05T23:18:18.977
FavoriteCount
0
LastActivityDate
2013-10-07T11:17:53.547
LastEditDate
LastEditorUserId
0
OwnerUserId
2051561
ParentId
0
PostTypeId
1
Score
0
ViewCount
161
LastEditorDisplayName
text
Body
I am using a project's open source that consists of a set a parent POM and several children POM. Those children POM represent libraries, arch-types and a plug-in. This plugin depends on various of these children modules and is used within the section of dependent projects like mine.I have imported this Maven project to my Eclipse workspace. In my own project's POM (also in Eclipse) I can reference those modules via dependencies without a problem. However I would also like to use the plug-in in the build section but it cannot be used due to the following Maven2 error: <code>Project build error: Unresolveable build extension: Plugin org.grouplens.lenskit:lenskit-eval-maven-plugin:2.1-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.grouplens.lenskit:lenskit-eval-maven-plugin:jar:2.1-SNAPSHOT</code> This is because I am accessing the POM's directly via Eclipse's "resolve dependencies from workspace projects" and of course this snapshot version has not been deployed to a repository so this is the only way I can actually use it. I tried: <ol> <li>Add any of the dependencies of lenskit-eval-maven-plugin: Their are several but I just added the only one of the project's module (others include stuff like maven-plugin-api): <pre><code><dependency> <groupId>org.grouplens.lenskit</groupId> <artifactId>lenskit-test</artifactId> <version>${project.version}</version> <scope>test</scope> </dependency> </code></pre></li> <li>placing a dependency for that plugin module before using the module in the section <pre><code><dependency> <groupId>org.grouplens.lenskit</groupId> <artifactId>lenskit-eval-maven-plugin</artifactId> <version>${lenskit.version}</version> </dependency> </code></pre></li> <li>adding a dependencies in the plug-in itself so: <pre><code> <build> <plugins> <plugin> <artifactId>lenskit-eval-maven-plugin</artifactId> <groupId>org.grouplens.lenskit</groupId>  <version>${lenskit.version}</version> <extensions>true</extensions> <dependencies> <dependency> <groupId>org.grouplens.lenskit</groupId> <artifactId>lenskit-eval-maven-plugin</artifactId> <version>${lenskit.version}</version> </dependency> </dependencies> </code></pre></li> <li>And using (0), (1) and (2) at the same time </li> </ol> Ok, so I realize that attempt (2) is pushing it. So my question is: is their any way I can use a plug-in in the build section that is also a dependency? If so how? If the use of solution (1) is correct, could this be an issue with Eclipse's method of resolving to local workspace first? TIA
Tags
<java><eclipse><maven><plugins>
Title
Maven2: can we have dependency for a plugin thats used in the build section
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USuser2051561
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. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
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.