[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16371922#comment-16371922 ] Dale LaBossiere commented on EDGENT-440: update: Chris's latest changes addressed the *tests.jar.asc issue. He said he'll look into the source-release file issue. > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370557#comment-16370557 ] Dale LaBossiere commented on EDGENT-440: These unwanted files are still present in a newly generated release snapshot: * .../*--tests.jar.asc # the signature file of the no longer present test jar files * edgent-parent/.../edgent-parent--source-release.* > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16362132#comment-16362132 ] Christofer Dutz commented on EDGENT-440: Ok ... I had Infra zap our repository and I then re-filled it ... now the test-jars are history :) > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361972#comment-16361972 ] Christofer Dutz commented on EDGENT-440: I just checked the job that handles the deployment of snapshots and it correctly stops deploying the test-jars: [https://builds.apache.org/view/E-G/view/Edgent/job/edgent-pipeline/job/develop/40/consoleFull] We might need a manual cleanup of the snapshots though to completely get rid of old test-jars. I just double-checked that and I do not seem to have permissions to delete snapshots. So I think we should ask infra to delete the entire Edgent branch of the "snapshot" repo. Then I'll re-deploy the new plugin and then with the next build the test-jars should be history. > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361965#comment-16361965 ] Christofer Dutz commented on EDGENT-440: The change doesn't delete what has been deployed, it just prevents new deployments. I even have a test-case that tests this in the integration-tests of the plugin itself. > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360939#comment-16360939 ] Dale LaBossiere commented on EDGENT-440: Chris believes publishing of the un-wanted test jars has been addressed via [https://github.com/apache/incubator-edgent/pull/344] I suspect the undesired edgent-parent jars noted above may still be present. Chris? > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326532#comment-16326532 ] Dale LaBossiere commented on EDGENT-440: Forgot to mention that I added buildTools/check_jars.sh. The script checks that LICENSE,... metadata are present in jars/wars. It can be run against a built workspace (e.g., pre-release) or against artifacts retrieved by samples/get-edgent-jars. What's missing is some tool that can pull down the full set of RC artifacts staged in Nexus to verify them, and to verify there are no missing or extra artifacts present. > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16326530#comment-16326530 ] Dale LaBossiere commented on EDGENT-440: As of 1/15/2018 a release:perform still uploads the following undesired items: * edgent-parent: edgent-parent--source-release.* * *-tests.jar throughout the j8, j7 and android platform artifacts > 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 >Priority: Major > > 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 (v7.6.3#76005)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[
https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289579#comment-16289579
]
Dale LaBossiere commented on EDGENT-440:
See related EDGENT-443 that will eliminate the undesired/unnecessary j7
{{edgent-api-topology--test-server.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)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286599#comment-16286599 ] Dale LaBossiere commented on EDGENT-440: PR-334 eliminated the staging of the edgent-test* projects https://github.com/apache/incubator-edgent/pull/334 > 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 > > 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)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ 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)
[jira] [Commented] (EDGENT-440) Adjust "release" processing so only desired artifacts are uploaded to Nexus/MavenCentral
[ https://issues.apache.org/jira/browse/EDGENT-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286402#comment-16286402 ] Dale LaBossiere commented on EDGENT-440: Chris's commit 465d076 eliminated "distribution bundles" from deploy to Nexus > 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 > > 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)
