[
http://jira.amdatu.org/jira/browse/AMDATU-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12284#comment-12284
]
Bram de Kruijff commented on AMDATU-466:
----------------------------------------
Seems the bundle plugin supports the archiving convention. Not sure we really
need to exclude though. What may happen is a mismatch between what the
META-INF/maven metadata says and what the META-INF/Manifest says when wrapping
manipulates the latter but not the former.
There is no reason to expect any issue with this at runtime. However, when it
happens to publically released artifacts it doesn't look good. But even then it
feels like the wrappers responsibility not to blindly copy the wrappees maven
metadata. Not something we should globally configure in the build.
{code}
<configuration>
<archive>
<addMavenDescriptor>false</addMavenDescriptor>
</archive>
</configuration>
{code}
> Configure build to exclude META-INF/maven or post process them
> --------------------------------------------------------------
>
> Key: AMDATU-466
> URL: http://jira.amdatu.org/jira/browse/AMDATU-466
> Project: Amdatu
> Issue Type: Question
> Components: Amdatu Core
> Reporter: Bram de Kruijff
> Priority: Minor
> Labels: multitenancy
> Fix For: Sprint 2
>
>
> By default maven includes pom files in the META-INF/maven of release
> artifacts. This may conflict with changes we make to multitenant artifact.
> Maybe we just need to remove these files by configuration. Maybe we need to
> post process them. To be determined.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
