[FORGE-96] Nexus access request for Magnolia Advanced Personalization Created: 29/Nov/18  Updated: 06/Mar/19  Resolved: 06/Mar/19

Status: Closed
Project: Forge

Type: Project registration Priority: Neutral
Reporter: Thomas Duffey Assignee: Richard Gange
Resolution: Fixed Votes: 1
Labels: None

Project Name: Advanced Personalization
Project Short Name: advanced-personalization
Project Description: The Advanced Personalization module provides a more flexible way of defining the rules for matching page and component variations to a request using expressions. This allows for more complex targeting and potentially fewer variants to manage. In addition it provides two new traits out of the box that can be used immediately for matching against incoming request header and query parameters.
Project SCM: External (please specify)
Project Maven groupID: com.crescendocollective

 Comments   
Comment by Pat Hills [ 18/Dec/18 ]

Thomas, thanks for registering a new project at the Magnolia Forge !

A Jira project is available for you at https://jira.magnolia-cms.com/projects/ADVPERS/.

More details about the infrastructure are available for you at https://forge.magnolia-cms.com/.

Please reopen this issue if you have any question or if you encounter any issue.

Comment by Thomas Duffey [ 18/Dec/18 ]

Hi Pat, thanks for setting this up. I confirmed this morning that I can push artifacts to the Forge repo in your Nexus.

Our module is intended only for EE customers as it depends on Personalization features. It looks like Forge modules are available through the public view of your Nexus. Is this OK or is there something we should do to make it only available via the enterprise view?

Also quick question, do snapshots get removed periodically? I may be pushing a few snapshots until we get everything right here since we are renaming our module from `magnolia-advanced-personalization` to just `advanced-personalization` and would like to see the snapshots removed when I am finished.

Comment by Richard Gange [ 09/Jan/19 ]

Hello tduffey

It's perfectly fine to have a Forge module meant as enterprise only. If your module depends on other enterprise modules then obviously there is no way to avoid it. Forge is meant to be a place where people can share their Magnolia enhancements. Community or Enterprise.

I believe we keep the last 4 but I could be wrong. If you need something removed I can certainly help you with that. Open a support request directed at me when you are ready to have some things cleaned up.

Cheers
Rich

Comment by Christopher Zimmermann [ 01/Mar/19 ]

tduffey It looks like this is setup for you now, right? Can you close the ticket if so? Otherwise, just drop another comment.

Generated at Mon Feb 12 01:57:47 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.