[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=16286599#comment-16286599 ] Dale LaBossiere commented on EDGENT-440: PR-334 eliminated the staging of the edgent-test*

[GitHub] incubator-edgent pull request #334: [Edgent-440] don't deploy edgent-test* p...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/334 ---

[jira] [Assigned] (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:all-tabpanel ] Dale LaBossiere reassigned EDGENT-440: -- Assignee: Dale LaBossiere > Adjust "release" processing so only desired artifacts are

[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=16286603#comment-16286603 ] Dale LaBossiere commented on EDGENT-440: Looking into the test-jar deploy issue, I see the

Re: FYI: I'm adding "don't deploy" to edgent-test* projects

> On Dec 11, 2017, at 3:15 PM, Christofer Dutz > wrote: > ... > One thing I have lernt in the last 8 years of using machen, it was: "If it's > dificult with maven you're doing it wrong. I don’t fully buy into that but I understand what you’re saying :-) Looking

[GitHub] incubator-edgent pull request #334: [Edgent-440] don't deploy edgent-test* p...

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/334 [Edgent-440] don't deploy edgent-test* projects to Nexus You can merge this pull request into a Git repository by running: $ git pull https://github.com/dlaboss/incubator-edgent

Re: FYI: I'm adding "don't deploy" to edgent-test* projects

I think we shouldn't omit any of the other artifacts. I have tried to configure things that way, but there wasn't an easy way. One thing I have lernt in the last 8 years of using machen, it was: "If it's dificult with maven you're doing it wrong. I would stongly suggest to leave the test-jars

FYI: I'm adding "don't deploy" to edgent-test* projects

Chris, FYI, following your changes to edgent-distribution/pom.xml I’m adding “skip deploy” to the edgent-test* projects (for EDGENT-440). Next I’ll see if I can identify how to (hopefully globally) omit all “test” configuration generated artifacts (hint welcome if you already know how) —

[GitHub] incubator-edgent pull request #333: update KEYS with Chris's release signing...

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/333 update KEYS with Chris's release signing key You can merge this pull request into a Git repository by running: $ git pull https://github.com/dlaboss/incubator-edgent update-KEYS

[GitHub] incubator-edgent pull request #333: update KEYS with Chris's release signing...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/333 ---

[GitHub] incubator-edgent pull request #332: update download script for LICENSE remov...

Github user asfgit closed the pull request at: https://github.com/apache/incubator-edgent/pull/332 ---

[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=16286402#comment-16286402 ] Dale LaBossiere commented on EDGENT-440: Chris's commit 465d076 eliminated "distribution bundles"

[GitHub] incubator-edgent pull request #332: update download script for LICENSE remov...

GitHub user dlaboss opened a pull request: https://github.com/apache/incubator-edgent/pull/332 update download script for LICENSE removal LICENSE no longer a separate staged file in the dev/release repo You can merge this pull request into a Git repository by running: $ git

Re: [DISCUSS] validating Apache Edgent (Incubating) 1.2.0 RC1

It was reported in the general incubator list that the sha files should be named sha1 or sha512 … a quick check of the man page of the sha-tool names 512 as algorithm version. So, I renamed the files to the sha512 dale suggested earlier. Chris Am 09.12.17, 22:43 schrieb "Christofer Dutz"

[RESULT] [VOTE] Apache Edgent (Incubating) 1.2.0 RC1

So, the vote passes with 3 +1 votes (1 of them binding) I’ll forward this to the incubator for approval. Chris Am 10.12.17, 18:15 schrieb "Dale LaBossiere" : +1 checked signatures/sums checked identical tar.gz / zip contents