Edward Pring created EDGENT-439:
---
Summary: optionally specify TCP port for Jetty HTTP server in
console
Key: EDGENT-439
URL: https://issues.apache.org/jira/browse/EDGENT-439
Project: Edgent
Is
HI,
> +1 (binding)
>
> (Am I allowed to vote “binding” on an incubating project PPMC or do only the
> Incubator PMCs vote with binding? If this is the case, I vote “non binding”
> ;-) )
Only IPMC votes are binding. I’ll have time to take a look at the release
tomorrow.
Thanks,
Justin
Interesting re the sha. The updates regarding sha naming are pretty recent -
last 6months or so.
So, they’re just wrong / not compatible with the real world and/or nexus
generated info?
Actually, I suspect it’s OK to just ignore nexus with respect to this - i.e.,
it has it’s own naming
scheme
Hi All,
- I downloaded the release archive with the following command
../incubator-edgent/buildTools/download_edgent_asf.sh 1.2.0 1
The script successfully completed without any errors -> All Ok
- After that I successfully built Edgent using the following command:
./mvnw clean install -P platform
Ok … so I removed all the distribution and the „tests“-modules from the staging
repo.
Chris
Am 07.12.17, 10:00 schrieb "Christofer Dutz" :
Hi Dale,
I added the zip and then noticed that the tag.gz did have some “next” and
“current” pom copies inside. So, I had a look at my origin
Hi Dale,
I added the zip and then noticed that the tag.gz did have some “next” and
“current” pom copies inside. So, I had a look at my original and they didn’t
have them, so I updated the tar.gz and its hashes.
Also, I did rename the sha512 back to sha as SHA is the algorithm … you usually
enc
