Kusuma04-dev opened a new pull request, #97:
URL: https://github.com/apache/incubator-kie-website/pull/97

   **Issue:**
   
   Starting with 10.3.0, the RC release job produces a single 
apache-kie-10.3.0-incubating-sources.zip containing both repositories and the 
zip root is checked to contain exactly:
   
   BUILD  DISCLAIMER-WIP  LICENSE  NOTICE  incubator-kie  incubator-kie-tools
   
   The docs still described the old behavior:
   
   build-10.3.0.md said the SVN zip held only Tools (incubator-kie-tools). It 
told users to git clone --branch 10.3.0-rc1 incubator-kie separately.
   Its Tools build step ran cd apache-kie-10.3.0-incubating and git init . on 
the whole bundle. With the new layout that would init a git repo over both 
projects instead of just Tools.
   verify.md still said the Java code is "not a source ZIP in SVN".
   
   **Changes:**
   
   docs/community/devs/build-10.3.0.md, restructured to follow the 10.2 page:
   
   
   - Obtain the source code: download URL pattern with an rc1 example, a tip to 
verify signatures first, then unzip. The separate git clone of incubator-kie is 
removed.
   - Navigate to the source directory: cd apache-kie-10.3.0-incubating, with 
the zip contents listed (BUILD, DISCLAIMER-WIP, LICENSE, NOTICE, incubator-kie, 
incubator-kie-tools). It notes that incubator-kie must be built first, because 
Tools resolves Java artifacts from the local Maven repo.
   - Building individual components:
   - 1 incubator-kie: mvn clean install -DskipTests -Dfull, then cd ..
   - 2 incubator-kie-tools: cd incubator-kie-tools, so git init and pnpm 
bootstrap run in the right directory


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to