You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chemistry.apache.org by "Florent Guillaume (Commented) (JIRA)" <ji...@apache.org> on 2012/02/10 18:01:00 UTC
[jira] [Commented] (CMIS-501) split
chemistry-opencmis-server-bindings into maven jar and war artifact
[ https://issues.apache.org/jira/browse/CMIS-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205550#comment-13205550 ]
Florent Guillaume commented on CMIS-501:
----------------------------------------
Actually they're not, they're available with classifier "classes", see:
http://repo1.maven.org/maven2/org/apache/chemistry/opencmis/chemistry-opencmis-server-bindings/0.6.0/
OTOH I agree that ideally this should be reversed, the basic classes should be in a standard no-classifier "jar" artifact, and the WAR should be separate and with a "war" classifier.
> split chemistry-opencmis-server-bindings into maven jar and war artifact
> ------------------------------------------------------------------------
>
> Key: CMIS-501
> URL: https://issues.apache.org/jira/browse/CMIS-501
> Project: Chemistry
> Issue Type: Improvement
> Components: opencmis-server
> Affects Versions: OpenCMIS 0.7.0
> Reporter: Gert Dewit
> Labels: maven
>
> The java classes for chemistry-opencmis-server-bindings are only available in a war artifact for maven users.
> The consequence of this is that when a dependent project wants to use these classes, they have to repackage the maven war artifact to a maven jar artifact. I think that alfresco does this.
> If you agree that this split up is a 'good thing' I'll be more than happy to do the work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira