Hi guys, I'm actually writing this lying in a sun bed at the beach on creta ;-)
You can test what happens during a release by doing a "mvn package -P release,apache-release". Then it should also build the source release artifacts. The only thing we need to do is that nexus is prepared for the iotdb group ID. Without that performing the releases would be a challenge 😉 But feel free to build a test - release with the apache-release profile enabled and check the contents of the artifacts. If you already did the release prepare, you can even manually build the release. I'll be traveling home tomorrow so I'll be more accessible to help from Friday on. Chris Holen Sie sich Outlook für Android<https://aka.ms/ghei36> ________________________________ From: Julian Feinauer <[email protected]> Sent: Wednesday, July 24, 2019 11:21:38 AM To: [email protected] <[email protected]> Subject: AW: Next steps for release 0.8.0-rc1 Hey, Indeed he made the build and i rely on the build setup we used in plc4x which he build the iotdb on as he told me. And I'm totally against reinventing the wheel for each project so I think the way we used it in plc4x is fine as you only need those artifacts for a release and then staging needs to be done also. Julian Von meinem Mobiltelefon gesendet -------- Ursprüngliche Nachricht -------- Betreff: Re: Next steps for release 0.8.0-rc1 Von: Justin Mclean An: [email protected] Cc: Hi, Or even better this [1] . My mvn internal knowledge is a little vague, but on most ASF projects you go mvn package and you end up with the source release in the target directory. Anyway Chris is the person to speak to about this, he probably knows what needs to be done. Thanks, Justin 1. http://maven.apache.org/plugins/maven-assembly-plugin/
