-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
None
-
-
Empty show more show less
Due to how our parent poms are configured (because we want to deploy sites in a directory named after the project's version), combined with Maven's I-know-better-than-you attitude, sites get deployed in what seems like an unnecessary directory: the website for foobar-1.0 will get deployed under http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/foobar/1.0/foobar/
While that's fine for single-module projects, it's not so good for multi-module projects, because their modules are the seemingly spread around: http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/module-a/1.0/foobar/module-a/, http://nexus.magnolia-cms.com/content/sites/magnolia.public.sites/module-b/1.0/foobar/module-b/, and so on ...
- is causing
-
MAGNOLIA-5660 Links to submodules in ce-bundle documentation are wrong
- Closed
-
MGNLEE-355 Links to submodules in ee-bundle documentation are wrong
- Closed
-
MGNLREST-49 Links to submodules in magnolia-rest documentation are wrong
- Closed
- relates to
-
BUILD-155 Links to sub-sub-modules in sites of ce-bundle documentation are wrong
- Closed