edgent-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dale LaBossiere (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
Date Mon, 11 Dec 2017 21:35:00 GMT

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

Dale LaBossiere commented on EDGENT-440:
----------------------------------------

Looking into the test-jar deploy issue, I see the maven-deploy-plugin lacks the necessary
configurability to achieve omitting the test-jar artifacts. As noted in 1, the solution is
to not create test-jars. However, edgent-parent/pom.xml includes config to generate test-jars
as they’re needed by the (retrolambda hackery? :-) for j7 test-class generation.

Don’t know if there's some other (sensible/maven) way to achieve generating j7 test-classes
w/o j8 test-jars.  But I’m willing to surrender on that, because Chris says he can/will
create a script to achieve the effect.

1 - https://stackoverflow.com/questions/8246136/maven-deploy-not-to-upload-test-jar

> Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
> ----------------------------------------------------------------------------------------
>
>                 Key: EDGENT-440
>                 URL: https://issues.apache.org/jira/browse/EDGENT-440
>             Project: Edgent
>          Issue Type: Task
>          Components: Miscellaneous
>            Reporter: Dale LaBossiere
>            Assignee: Dale LaBossiere
>
> The release process tooling/config for 1.2.0 uploaded some unwanted artifacts to Nexus
and they had to be manually removed before continuing the release.
> Adjust the “deploy” processing so as to upload only the desired artifacts to nexus
(no “test” jars, no “distribution” bundles, no “test projects)
> We really should have some “release validation” processing, that anyone can run as
part of validating a releasee, for checking the staged nexus artifacts
>     * have exactly the expected set of jars/wars/pom-only
>     * the jars have exactly the expected/required (jar/war dependent) LICENSE, NOTICE
and DISCLAIMER and contain a DEPENDENCIES



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message