[
http://jira.magnolia-cms.com/browse/BUILD-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grégory Joseph updated BUILD-46:
--------------------------------
Description:
While we don't want to make the use of our parent pom mandatory, some projects
might want to use that, at least as a quickstart.
One of the problems is that our other parent poms define stuff like
"magnoliaEdition", "magnoliaLicenceStyle", and this might not be relevant for
these projects.
* {{magnoliaLicenceStyle}} might work (perhaps the property could be renamed),
as it just drives the configuration of some other plugins... (to be validated)
* {{magnoliaEdition}} seems to be only used when generating README, and only in
the context of pom, war, and installer packages...
Another issue has to do with license headers. Forge projects are not owned by
Magnolia International, and as such, their using our license header makes no
sense. The checkstyle rules checking those headers are driven by the above
{{magnoliaLicenseStyle}} property. Should we provide another set of headers, so
that forge modules can use our checkstyle rules if they want ? (Matt Dertinger
expressed interest) and/or should we add rules to enforce the non-usage of
these headers ?
*Need to investigate deeper to check if there are other implications*. If so,
we could also maintain such a pom at a higher level than our existing ones.
was:
While we don't want to make the use of our parent pom mandatory, some projects
might want to use that, at least as a quickstart.
One of the problems is that our other parent poms define stuff like
"magnoliaEdition", "magnoliaLicenceStyle", and this might not be relevant for
these projects.
* {{magnoliaLicenceStyle}} might work (perhaps the property could be renamed),
as it just drives the configuration of some other plugins... (to be validated)
* {{magnoliaEdition}} seems to be only used when generating README, and only in
the context of pom, war, and installer packages...
*Need to investigate deeper to check if there are other implications*. If so,
we could also maintain such a pom at a higher level than our existing ones.
> Figure out parent pom for Forge projects
> ----------------------------------------
>
> Key: BUILD-46
> URL: http://jira.magnolia-cms.com/browse/BUILD-46
> Project: Build
> Issue Type: Task
> Components: poms
> Reporter: Grégory Joseph
> Assignee: Grégory Joseph
> Fix For: POMs 18
>
>
> While we don't want to make the use of our parent pom mandatory, some
> projects might want to use that, at least as a quickstart.
> One of the problems is that our other parent poms define stuff like
> "magnoliaEdition", "magnoliaLicenceStyle", and this might not be relevant for
> these projects.
> * {{magnoliaLicenceStyle}} might work (perhaps the property could be
> renamed), as it just drives the configuration of some other plugins... (to be
> validated)
> * {{magnoliaEdition}} seems to be only used when generating README, and only
> in the context of pom, war, and installer packages...
> Another issue has to do with license headers. Forge projects are not owned by
> Magnolia International, and as such, their using our license header makes no
> sense. The checkstyle rules checking those headers are driven by the above
> {{magnoliaLicenseStyle}} property. Should we provide another set of headers,
> so that forge modules can use our checkstyle rules if they want ? (Matt
> Dertinger expressed interest) and/or should we add rules to enforce the
> non-usage of these headers ?
> *Need to investigate deeper to check if there are other implications*. If so,
> we could also maintain such a pom at a higher level than our existing ones.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
