[jira] [Commented] (YETUS-776) build doesn't deploy all artifacts

["Allen Wittenauer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/YETUS-776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16775924#comment-16775924 ] 

Allen Wittenauer commented on YETUS-776:
----------------------------------------

Digging into this issue, I now know why this is broken.  One of the things the build does is attach some bits as an artifact so other parts of the build can use them.  As a result, there is a specific skip configured for the maven deploy plugin.  To fix this, we need to re-enable the deploy for that module.  If we do that, those other artifacts will also get uploaded to maven central.  In order to fix that, we need to split the module up or reconfigure how the distribution is built.

I'm leaning towards just letting those temporary artifacts get uploaded.

> build doesn't deploy all artifacts
> ----------------------------------
>
>                 Key: YETUS-776
>                 URL: https://issues.apache.org/jira/browse/YETUS-776
>             Project: Yetus
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 0.9.0
>            Reporter: Sean Busbey
>            Priority: Critical
>
> releasedocmaker and shelldocs now have jython build jars. we should make sure maven attaches them to the build so that they'll be included in a deploy (i.e. during a release to nexus). Also, audience-annotations-component is missing the source release zip.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)