[
http://jira.magnolia.info/browse/MPBUN-7?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gregory Joseph moved MAGNOLIA-1110 to MPBUN-7:
----------------------------------------------
Project: Magnolia Bundle Maven Plugin (was: Magnolia)
Key: MPBUN-7 (was: MAGNOLIA-1110)
Issue Type: Task (was: Improvement)
Workflow: jira (was: Copy of default jira wf)
> Cyclic dependency between maven-bundle-plugin and magnolia (reactor)
> --------------------------------------------------------------------
>
> Key: MPBUN-7
> URL: http://jira.magnolia.info/browse/MPBUN-7
> Project: Magnolia Bundle Maven Plugin
> Issue Type: Task
> Reporter: Gregory Joseph
> Assignee: Gregory Joseph
> Priority: Minor
>
> Magnolia can't be built (with reactor or just -core, for instance), without
> maven-bundle-plugin. But maven-bundle-plugin also needs magnolia-core to
> build itself.
> This only shows up if you're in offline mode and have none of these 2 in your
> local repo. It would also happen when trying to build a new version.
> Not sure how to resolve this though, but I'm suspecting the
> maven-bundle-plugin is only used/useful when actually building the bundles -
> i.e not from reactor but only through the bundle.sh script.
> If that's the case, then I don't think the maven-bundle-plugin needs to be
> referenced at all in magnolia's parent pom or it could just be activated in
> the magnolia module, and simply "registered" in the main pom using
> <pluginManagement> (and then be part of the reactor'd build)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
