As a Liferay Marketplace Developer, it should be less time consuming and less error prone to identify and declare necessary PACL declarations

• Type: Story
• Status: Closed
• Priority: Critical
• Resolution: Completed
• Affects Version/s: 6.1.1 CE GA2
• Fix Version/s: 6.1.2 CE GA3, 6.1.30 EE GA3, 6.2.0 CE M5
• Component/s: Accessibility, Application Security > PACL, Security Vulnerability
• Labels: None
• Epic/Theme:
  • platform
  • release_planning
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/8622

When developing apps for Liferay's Marketplace, the official docs describe a process like this:

1. Develop app with PACL turned off
2. Turn PACL on
3. Run app, find a PACL error.
4. Try to figure out which PACL stanza will get you past the error. Add it to your liferay-plugin-package.properties
5. Re-deploy app
6. Return to step 3 until no more errors

This is very time consuming and error-prone. As a developer, I'd rather have a way for Liferay to tell me which PACL declarations I need, rather than me doing all the legwork.

See the numerous issues with fleshing out PACL declarations here:

http://www.liferay.com/forums/-/message_boards/message/17489093/maximized
http://www.liferay.com/forums/-/message_boards/message/17329080/maximized
... and others here: http://www.liferay.com/forums/-/message_boards/category/10919228/maximized