-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All-in-one archetype - Generate Share AMP file #179
Comments
From peter.mo...@alfresco.com on February 14, 2014 10:06:48 Emitting multiple assets from a single Maven project is a bit counter to how Maven works, and may not be easy to achieve. I suspect a better option is to have a multi-module project comprising a master pom project and 2 sub-projects (one for repo AMP, one for Share AMP). Do the archetypes already do this? I thought they did, but I'm not that familiar with them so might be misremembering... |
From nathan.m...@alfresco.com on February 14, 2014 10:14:58 That's kind of what I was getting at. The current all in one archetype creates a master pom project and multiple module subprojects (one of which is a repo-tier AMP). It would be great if it just created an additional AMP module, preconfigured to be applied to Share. |
From colum...@gmail.com on February 14, 2014 10:23:46 Labels: -Type-Defect Type-Enhancement |
From colum...@gmail.com on March 10, 2014 11:55:29 This is a common way of using the SDK so probably a multimodule archetype for that would be useful. I wonder if it would get confusing though to have 2 multi-module projects, similar in many ways. Labels: Milestone-Release-sdk-1.2.0 |
The 2.x version of the SDK will include a Share AMP archetype (outside of the all in one). So we'll have 3 archetypes:
I think we can close this since it's a duplicate of issue #70 |
From nathan.m...@alfresco.com on February 14, 2014 12:31:49
It would be great if the all-in-one archetype could generate two AMP files, one for the repository tier, and a separate AMP module for Share. Most customers are working with both components these days, and this would make jumpstarting a project spanning both tiers much easier for people that are new to Maven and our SDK.
Maybe instead of the single "amp" module, it could emit two, one named "amp-repo" and one named "amp-share", each configured to be applied to the right WAR file?
Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=179
The text was updated successfully, but these errors were encountered: