Skip to content
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

Add profiles for Community and Enterprise #163

Closed
mindthegab opened this issue Jul 20, 2014 · 7 comments
Closed

Add profiles for Community and Enterprise #163

mindthegab opened this issue Jul 20, 2014 · 7 comments
Assignees
Milestone

Comments

@mindthegab
Copy link
Contributor

From pmo...@gmail.com on November 26, 2013 18:23:33

The pom.xml files generated by the AMP project archetype should include profiles for Community and Enterprise.

Original issue: http://code.google.com/p/maven-alfresco-archetypes/issues/detail?id=163

@mindthegab
Copy link
Contributor Author

From pmo...@gmail.com on November 26, 2013 15:23:43

Labels: Component-Amp-Archetype Milestone-Release-sdk-1.1.2

@mindthegab
Copy link
Contributor Author

From pmo...@gmail.com on November 26, 2013 15:58:34

Status: New
Owner: ---

@mindthegab
Copy link
Contributor Author

From maurizio...@alfresco.com on July 03, 2014 03:44:04

Hi Peter,

at the moment the default behaviour is to build the latest Community version (and its version is hard-coded into the src/main/resources/archetype-resources/pom.xml), therefore I dont think that we need a profile for Community.

In order to use Enterprise edition, you must perform the following manual operations:

  1. Define your repo credentials into ~/.m2/settings.xml
  2. Change the property <alfresco.version> to 4.2.2 (or similar)
  3. Change alfresco-public to alfresco-private (incl. url)

We could introduce a -Penterprise profile, defined into the alfresco-sdk-parent (therefore inherited by all archetypes), which contains:

  1. <alfresco.version>4.2.2</alfresco.version> => will have to be manually changed on every release, but would allow a continuous testing of the SDK with the Enterprise edition
  2. <repository
    alfresco-private
    https://artifacts.alfresco.com/nexus/content/groups/private

Step #1 would still have to be done manually; however, if not done, the user will be prompted with a well-known 401 status code (that should be mentioned by docs).

What's your opinion on this?
Thanks!

@mindthegab
Copy link
Contributor Author

From colum...@gmail.com on July 17, 2014 17:06:51

I'm OK if we want to do this for 2.0.0. Mau / Peter can you push this forward?

Status: Accepted
Labels: -Milestone-Release-sdk-1.1.2 Milestone-Release-sdk-2.0.0

@mindthegab mindthegab modified the milestone: Release-sdk-2.0.0 Jul 20, 2014
maoo added a commit that referenced this issue Jul 25, 2014
…oved it where unnecessary (while keeping junit in the test build scope)
@maoo maoo assigned mindthegab and unassigned maoo Jul 25, 2014
maoo added a commit that referenced this issue Jul 25, 2014
@mindthegab mindthegab modified the milestones: 2.0.0-beta-1, 2.0.0 Aug 22, 2014
@mindthegab mindthegab assigned maoo and unassigned mindthegab Sep 8, 2014
@mindthegab
Copy link
Contributor Author

@maoo I am OK with this. Can you send a pull request? Assigning to you in the meanwhile. @tbedford if we integrate this, we might need to update the doscs.

@mindthegab
Copy link
Contributor Author

This is resolved. Currently uses an internal alfresco repo (so doesn't work for non Alfrescans) since it uses Alfresco Enterprise internal SNAPSHOTs. But from an SDK standpoint it works.

Lastly: adapted to the new Enterprise naming (for the wars) of "share-enterprise" and "alfresco-enterprise".

@marcomancuso
Copy link

Please add enterprise dependencies for enterprise profile, it would be nice to have it even in SDK 1.2.x
Already discussed with @mindthegab

mindthegab added a commit that referenced this issue Dec 23, 2014
…ed to work in amp and aio in eclipse and cmd line
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants