[
https://issues.apache.org/jira/browse/MNGSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17933270#comment-17933270
]
Casper Roubos commented on MNGSITE-443:
---------------------------------------
Hi,
Thanks for your patience. It seems that some of your previous emails did not
get in through the email server.
I see that I did not correctly use the proper terms.
You are right: the item should not have been visible since it has not installed
of deployed in any repository. In mine case I build a plugin that uses the
output in the package phase of a previously packaged module in the same build,
so in mine description I meant 'in the reactor' .
Hope this clarification helps.
> Add setFile to Mojo Cookbook (website)
> --------------------------------------
>
> Key: MNGSITE-443
> URL: https://issues.apache.org/jira/browse/MNGSITE-443
> Project: Maven Project Web Site (Moved to GitHub Issues)
> Issue Type: Improvement
> Reporter: Casper Roubos
> Assignee: Matthias Bünger
> Priority: Major
> Labels: waiting-for-feedback
>
> Is it possible to add in the 'my first mojo', that you need to register the
> output-directory in the artifact with project.getArtifact().setFile(..).
> We are using a Jenkins muti-branch pipeline, and we found out that if you not
> build to install (e.q. process-test-classes) that the build will give an
> error because the dependency resolution can't find the artifact in the repo
> (because the first time it is not deployed yet).
>
> Hope that this addition will also others.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
