-
Notifications
You must be signed in to change notification settings - Fork 100
Develop #21
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
base: main
Are you sure you want to change the base?
Develop #21
Conversation
habansal
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice consolidation under single branch :)
One question:
Is this migrated app commit a new one (new work in this PR) or picked from an existing branch: d0695c0
| </profile> | ||
| <!-- AEM 6.x Profile to include Core Components--> | ||
| <profile> | ||
| <id>classic</id> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We don't need to a similar profile for React ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@habansal react ...react/all/pom.xml does have the classic profile
Or are you referring to something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@davidjgonzalez I don't remember exactly what i noticed then.
But, looking at it again now, I see that there is indeed similar profile in React as well -
| <id>classic</id> |
Thanks!
Description
Add finished versions of React and Angular projects to a single branch to promote ease of use.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: