[
https://issues.apache.org/jira/browse/OLINGO-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14589763#comment-14589763
]
Michael Bolz commented on OLINGO-694:
-------------------------------------
For all sample projects (maven sub-modules) it is necessary that they are not
deployed during build.
Therefore the {{maven-deploy-plugin}} with configuration {{skip = true}} has to
be added (see sample below).
{code}
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-deploy-plugin</artifactId>
<configuration>
<skip>true</skip>
</configuration>
</plugin>
</build>
{code}
> Refactor samples structure and add tutorials
> --------------------------------------------
>
> Key: OLINGO-694
> URL: https://issues.apache.org/jira/browse/OLINGO-694
> Project: Olingo
> Issue Type: Task
> Components: odata4-samples
> Affects Versions: (Java) V4 4.0.0-beta-03
> Reporter: Michael Bolz
> Assignee: Michael Bolz
> Priority: Minor
> Fix For: (Java) V4 4.0.0
>
>
> Put samples in Olingo git within the *samples* folder (e.g.
> _“samples/tutorials/read”; “samples/tutorials/write”; “…”_)
> and *do not include* the samples folder into the project pom for the common
> build process (e.g. build samples only “on demand / manual” via a maven
> profile setting -> see example below).
> This is based on
> [discussion|http://mail-archives.apache.org/mod_mbox/olingo-dev/201505.mbox/%3C8AD22C3C-F806-4FCA-82F4-9DF8B374B4F7%40sap.com%3E]
> and
> [decision|http://mail-archives.apache.org/mod_mbox/olingo-dev/201505.mbox/%3CF6085B2A-6582-4AE0-ACC6-E87E3EAD55C5%40sap.com%3E]
> on Olingo dev mailing list.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
