[
https://issues.apache.org/jira/browse/MNGSITE-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927495#comment-17927495
]
Matthias Bünger commented on MNGSITE-443:
-----------------------------------------
Having an additional look at the documentation, there is a section about
[Reading and Writing Text
Files|https://maven.apache.org/plugin-developers/common-bugs.html#Reading_and_Writing_Text_Files].
However, I doubt that what you describe has nothing to do with it.
{quote}
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).
{quote}
This sounds like a misunderstanding on your site. As long as a plugin (or any
other project you build) is not installed/deployed it's not considered
"released" / not visible for other projects. So it's not in the local/remote
repository where the dependecy resolution would find it.
Could you give me more information about your setup and what are you are trying
to do?
> 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
> Priority: Major
>
> 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)
