Open binduwavell opened 7 years ago
The above list is really just a jumping off point for thinking about what we should do. I'd like to invite @ohej and other folks in the community to join in on this discussion.
yo alfresco:doctor
could check if there are newer versions of common AMPs or possibly all remote AMPs (I'm not quite sure how that would work, but it would be cool if we can figure out what the latest version is of a maven (groupId,artifactId) pair.
@binduwavell regarding your last comment, it might be interesting to check out https://stackoverflow.com/a/1172805/2307988
Thanks @yregaieg I'll check that out.
FEATURE / ENHANCEMENT
SDK 3.0.0 has been out for some time now. Consider adding SDK 3 to the existing generator or making a new generator that is focused on SDK 3 and above.
The advantage to the latter is there are some workflows with SDK 3 we can't do with earlier versions. Like:
Also since SDK 3 defaults to JAR packaging but can also do AMP packaging there are use cases around switching the type of artifact being built that need to be considered.
Other SDK 3 specific things to consider:
Consider creating a
yo alfresco:doctor
that reviews things like, Node, Java and Maven versions. Provides guidance on upgrading to newer SDK when there is one.Consider creating a
yo run
in place of run.sh and run.bat. This could remember previous choices and allow triggering of prompts via a CLI option (this information would be printed each time the sub generator runs against remembered values.)