On 03/09/2016 01:19 AM, Shawn McKinney wrote: > Hello, > > another problem: > > When I perform this step: > > ------ > Step 6 : Build the Site > $ cd target/checkout > $ mvn site > ------ > > It does not create the release packages. > > in other words when I run this search from realm’s package root: > find -name *source-release.zip* > > It comes up empty.
Quick check from my side: the pom.xml of realm project (1) skips the maven-assembly-plugin from the apache-release profile and (2) it's own configuration is commented out. I'm not sure if a custom assembly configuration is really needed, the one provided by the Apache parent work most of the time, you can just try to remove the <skipAssembly> from pom.xml. > There are -sources.jar’s underneath the /target folders, but I’m betting that > ain’t gonna cut it for a release. No, those are the Maven module sources and are uploaded to Nexus. > One red herring: > I had to re-run the release for realm because I had inadvertently run mvn > clean before uploading. This created yet another staging repo on nexus that > I have yet to close. I doubt this had anything to do with this problem but > worth mentioning. No problem, just drop the 1st repo and close the 2nd repo. Pro tip ;): For a release I often do another clean checkout at a different location that I then keep untouched during release and vote. Then I can just continue to work on the project without deleting release artifacts. > Two red herring: > The mvn package structure is different for realm. It has a parent pom and > two children (impl, proxy). The children (should) each will have a source > and binary dist packages. The binaries built fine, only the mvn site source > release package creation failed. mvn site is not mandatory for the release, ask yourself if it is useful for users. Kind Regards, Stefan
