[
http://team.ops4j.org/browse/QI-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17048#comment-17048
]
Niclas Hedhman commented on QI-355:
-----------------------------------
Added HelloTest(2..4) to showcase for documentation that the same composite
type can be of any composite meta type in 2.0. These tests are @Ignore at the
moment, since this bug need to be fixed before it works.
> CompositeAssemblyImpl uses CompositeType instead of the aggregated types.
> -------------------------------------------------------------------------
>
> Key: QI-355
> URL: http://team.ops4j.org/browse/QI-355
> Project: Qi4j
> Issue Type: Bug
> Components: Core Runtime
> Affects Versions: 2.0 - Simply Productive!
> Reporter: Niclas Hedhman
> Assignee: Niclas Hedhman
>
> When resolving the mixin classes in
> org.qi4j.runtime.bootstrap.CompositeAssemblyImpl#mixinDeclarations, the
> composite type interface is used. But it must now use all the types, since if
> we are to allow declaration without the marker interfaces, we still need all
> the mixin and annotation information that comes from the marker interfaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://team.ops4j.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
