You can run integration tests against that AMP using the embedded Tomcat server, but if you want to test the AMP with other AMPs, you have to deal with that manually. With the single-purpose archetypes, your goal is simply to build an AMP. It is able to pull in other AMPs as dependencies. However, there is an advantage the All-in-One archetype has over the other two. Usually, I feel like the All-in-One archetype is overkill. Second, on the vast majority of my client projects, that’s the setup I use. First, I think for most beginners, the smaller, more focused archetypes are less confusing. In my Alfresco Maven SDK Tutorial I use both the alfresco-amp-archetype and the share-amp-archetype but I don’t really talk about the All-in-One archetype at all. share-amp-archetype: This sets up a project that generates only a Share tier AMP.alfresco-amp-archetype: This sets up a project that generates only a repository tier AMP.alfresco-allinone-archetype: Referred to simply as “All-in-One”, this type, as the name implies, gives you a project that facilitates creating both a repository tier AMP and a Share tier AMP, plus it includes a working Solr installation.When you use the Alfresco Maven SDK Archetypes to bootstrap a project, you can select one of three project types: I’ve seen a few questions about how to configure an Alfresco project to depend on other add-ons when using the Alfresco Maven SDK, so I thought I’d do a quick write-up on that.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |