[MAGNOLIA-3518] Create a Maven plugin to generate module descriptors Created: 19/Jan/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-3517 Module descriptor additions Closed
is related to MGNLCAT-25 Missing optional dependency to scheduler Closed
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

With additions being made to the module descriptor, it's becoming obvious that we could generate module descriptors. Most of the current information is redundant with the pom (or deducible), and most new information (components, ...) can be derived from analyzing the sources. (annotations, interfaces)

Such a Maven plugin should ideally "merge" with a possibly existing module descriptor, so that one could still manually set some information in a module descriptor (properties, perhaps). OTOH, the plugin configuration will probably allow setting such values, so maybe that's not needed at all.

Deriving module name: use artifactId, if prefixed by magnolia-module-, remove prefix.
Finding components: we could use APT (Annotation Processor Tool: http://download.oracle.com/javase/1.5.0/docs/guide/apt/GettingStarted.html - there's actually a Maven plugin: http://mojo.codehaus.org/apt-maven-plugin/) to find @Component. Marking some of our interfaces with it might even reduce the need for the annotation (i.e we could mark ObservedManager with such an annotation)

http://wiki.magnolia-cms.com/display/DEV/Module+Descriptor+Generator+%28maven+plugin%29



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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