[MGNLEE-221] Provide CMIS bundle in add-ons folder Created: 06/Mar/12  Updated: 09/Mar/12  Resolved: 09/Mar/12

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: None
Fix Version/s: 4.5.1

Type: Improvement Priority: Neutral
Reporter: Ondrej Chytil Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLCMIS-2 Fix bundle Closed
is related to MAGNOLIA-4014 Allow easier adding projects with ext... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Comments   
Comment by Magnolia International [ 07/Mar/12 ]

Can you try the following, in the tomcat-bundle.xml file: instead of explicitly including the info.magnolia.cmis groupId (which isn't very maintainable - 1) you'll have to redo this sort of modification everytime a new groupId needs to be included - 2) it introduces differences between this file and the corresponding one in the CE bundle, which we've tried to keep the same as much as possible).

  1. either include both info.magnolia:* AND info.magnolia.*:*
  2. or, info.magnolia*:*

(with preference for the first idea)

If that works, please report it to the CE bundle as well, so that adding a dependency to the pom will be enough to add new add-ons in the bundle.

Comment by Ondrej Chytil [ 08/Mar/12 ]

info.magnolia.:* is not enough.
info.magnolia*:* also came to my mind originally but seemed much generic to me. Since you are ok with this let's have it there.

Comment by Magnolia International [ 08/Mar/12 ]

> info.magnolia.:* is not enough.

I meant "info.magnolia:* AND info.magnolia.:" - the stars were not visible and made the text bold. Edited now.

Comment by Ondrej Chytil [ 08/Mar/12 ]

Since Jira did swallowed some chars in Greg's post I'm re-opening and we'll go with suggestion 1.

Generated at Mon Feb 12 05:27:51 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.