[
https://issues.apache.org/jira/browse/STANBOL-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13103570#comment-13103570
]
Suat Gonul commented on STANBOL-324:
------------------------------------
Reto, based on your suggestion I created an artifact packaged as
partialbundlelist as in the
http://svn.apache.org/repos/asf/sling/trunk/launchpad/test-bundles/pom.xml.
Then run the mvn install command on the partial list artifact. After that in
the full launcher pom, I added a dependency to full launcher like
<dependency>
<groupId>org.apache.stanbol</groupId>
<artifactId>org.apache.stanbol.cmsadapter.bundlelist</artifactId>
<version>0.9.0-incubating-SNAPSHOT</version>
<type>partialbundlelist</type>
</dependency>
instead of the bundles related with CMS Adaptor in the list.xml of full
launcher. But this dependency could not be resolved while building the
launcher. After mvn install command a jar file is created in the target but it
seems it's empty (containing only META-INF folder and empty manifest, licence,
etc files in it). Do you have any idea where I am doing wrong? And is this the
way you suggest?
> Put CMSAdaptor into full launcher
> ---------------------------------
>
> Key: STANBOL-324
> URL: https://issues.apache.org/jira/browse/STANBOL-324
> Project: Stanbol
> Issue Type: Task
> Components: CMS Adaptor
> Reporter: Suat Gonul
>
> CMS Adapter should be included in the full launcher so that it can be used
> when the full launcher is run. This operation will include removal of
> dependencies to Ontology Manager component.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
