[
https://issues.apache.org/struts/browse/SHALE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39803
]
Craig McClanahan commented on SHALE-391:
----------------------------------------
> There is one other thing that came to mind: When I made it I based it upon the
> lastest snapshot of Shale/Clay (1.1.0-SNAPSHOT). Should we fix it to a
> specific
> version instead (1.0.3)?
While the archetype is under construction, it should have a "-SNAPSHOT" version
number. That way, as you test out the archetype you'll always be pulling the
latest one. It would get switched to a non-SNAPSHOT version number as part of
a release process.
The interesting question is what should go before the SNAPSHOT. I can see the
following options:
* If it is intended to be released along with all the rest of 1.1,
then 1.1.0-SNAPSHOT would be appropriate.
* If it is intended to be released separately, it could just start
on its own series (1.0.0-SNAPSHOT) that gets incremented
at its own pace as releases occur.
* If there is a Shale version that is itself included by the archetype,
one could argue that using the corresponding version number
would make sense.
At the moment, I'm thinking we would tend to release archetypes independently
of Shale releases, so the first option isn't too compelling. I mildly lean
towards the second one over the third - the release notes for the archetype (no
matter what its own version is) would definitely need to discuss what Shale
version it includes by default, and what versions are supported, under any
circumstances.
What do you think?
> Clay starter Maven archetype
> ----------------------------
>
> Key: SHALE-391
> URL: https://issues.apache.org/struts/browse/SHALE-391
> Project: Shale
> Issue Type: New Feature
> Components: Clay
> Affects Versions: 1.0.3
> Reporter: Hermod Opstvedt
> Attachments: ClayStarterArchetype.patch,
> shale-clay-starter-archetype.zip
>
>
> A Maven Clay starter archetype. This creates a very simple Clay project
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
