[
https://issues.jboss.org/browse/GTNPORTAL-3210?page=com.atlassian.jira.pl...
]
Peter Palaga resolved GTNPORTAL-3210.
-------------------------------------
Resolution: Rejected
I thought about this once again and I ended up holding the position that
"portlet" or "portal" in {{<artifactId>}}'s and
{{<name>}}'s of our quickstarts makes clear enough that they are related to
Portal product, thus rejecting this request.
Quickstart names in the POM files are often are not clear across
products
-------------------------------------------------------------------------
Key: GTNPORTAL-3210
URL:
https://issues.jboss.org/browse/GTNPORTAL-3210
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Reporter: Sande Gilda
Assignee: Peter Palaga
Now that we aggregate quickstarts from different repositories and for different products,
we need a better way to identify them. We often have quickstarts with the same name in
different repositories.
When you run `mvn clean install '-Pdefault,!complex-dependencies'` from the root
directory of the quickstarts, it often is not clear which quickstart is compiling.
As described in the CONTRIBUTING.md file, we would like the <name> in the
quickstart pom.xml file to follow the template:
JBoss <target-product> Quickstart: <quickstart-name> < -
optional-subfolder-name> where target-product is the Target Product metadata specified
in the README.md file, quickstart-name is the quickstart folder name, and
optional-subfolder-name is the name of any nested subfolder containing a pom.xml file.
This means the Portal cdi-generic-portlet would be:
<name>JBoss JPP Quickstart: cdi-generic-portlet</name>
I know you have concerns about changing this and we can certainly discuss it. :-)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira