Hi Jeffery, I think, we may stay for now just with README.md without a site? We do provide a src/changes/changes.xml, which could be retrieved by xdoc and build a maven site.
If we want a site, we may use just the same site generation mechanism as we do for the other components, but may need to create a git branch "asf-site" with the generated content (using a script or a manual), see https://blogs.apache.org/infra/entry/git_based_websites_available.). Infra then seems to be able to get this published after an initial announcement. We may end up with something like https://github.com/apache/turbine-archetypes/asf-site with the static generated files being there. As no site yet exists for turbine-archetype we may not even vote to change something, but would just do it IMO! An example, what to do, may be found here: https://issues.apache.org/jira/browse/INFRA-14105. There is also a wiki entry "Building and Deploying Web Sites with GitPubSub and Jenkins/Buildbot" (in progress) from INFRA but yet without much content: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=75964385. Best regards, Georg N.B. For Turbine core a fast and small step to be more git friendly would be to change README.txt in turbine-trunk to README.md and adapt to md-syntax. ;-) Von: Jeffery Painter <[email protected]> An: [email protected] Datum: 23.07.2019 20:51 Betreff: Q on publishing the archetype Hi Georg, Do you have any instructions on how to publish the turbine-archetype? I am not certain how this should be done compared to the other projects (same steps or not?) I think it is ready so that we can update it to start working with turbine 5.1 in svn. And push the fix you made with fulcrum-parser and pooling. Thanks! Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
