Hi Georg,
I am fine with the README.md ... should we move the setup instructions
then that I wrote in src/main/resources/archetype-resources/README.txt
up to the main README.md that appears on the git page? I can do this if
you like since it would then be more visible.
I guess what I meant was how to you publish the archetype (not the
website) so that we can bump the revision number?
The older versions are here:
https://svn.apache.org/viewvc/turbine/maven/archetypes/
<https://svn.apache.org/viewvc/turbine/maven/archetypes/tags/>
I think we are on 1.0.3-SNAPSHOT still for turbine-webapp-5.0
Could we align the version number in the pom.xml of the archetype to
better match the version of turbine it is associated with? I don't care
one way or the other, just a thought.
How does version 1.0.3 get finalized, voted on and then made available
in the archetype catalog? That is the step I am missing :-)
Also, looks like that mysql connector update just came out. Do you have
an automated way that you monitor dependency updates or do you just
check them manually? I have sadly just been looking on maven repo
central to see what is new when I think about it.
Also - if/when I get some downtime, I can take a shot at updating the
README.txt files in turbine-trunk and fulcrum to markdown formatted files
Thanks!
Jeffery
On 7/24/19 7:52 AM, Georg Kallidis wrote:
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]
