Yes, for Apex core it is only enabled for API and common libraries.
Additionally Malhar should inherit japicmp settings (and version) from
Apex core. I recently changed Apex core to include semantic version
check plugin into plugin management.
Thank you,
Vlad
On 12/2/15 11:00, Chandni Singh wrote:
Does it make sense to enable this plugin for only library and contrib and
ignore rest of the child modules like demos, apps, samples, etc?
On Wed, Dec 2, 2015 at 7:19 AM, Thomas Weise <[email protected]> wrote:
Samples should be excluded from the compare.
--
sent from mobile
On Dec 2, 2015 12:25 AM, "Gaurav Gupta" <[email protected]> wrote:
I don’t see malhar-samples on maven central
https://repo.maven.apache.org/maven2/org/apache/apex/.
Thanks
- Gaurav
On Dec 1, 2015, at 11:12 PM, Chandni Singh <[email protected]>
wrote:
Hi,
Observing this failure with travis pull request builds:
[ERROR] Failed to execute goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.5.3:cmp (default) on
project malhar-samples: Execution default of goal
com.github.siom79.japicmp:japicmp-maven-plugin:0.5.3:cmp failed:
Processing of jar file
/home/travis/.m2/repository/org/apache/apex/malhar-samples/3.2.0-incubating/malhar-samples-3.2.0-incubating.jar
failed:
/home/travis/.m2/repository/org/apache/apex/malhar-samples/3.2.0-incubating/malhar-samples-3.2.0-incubating.jar
(No such file or directory) -> [Help 1]
[ERROR]
I can see that it is not finding the previous jar to compare and is
therefore failing but don't know how to fix this.
Can anyone help?
Thanks,
Chandni
