ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "J.W. Janssen (JIRA)" <>
Subject [jira] [Closed] (ACE-182) ace-deployment-verifier-ui doesn't compile from an IDE
Date Tue, 14 Aug 2012 09:07:38 GMT


J.W. Janssen closed ACE-182.

    Assignee:     (was: Karl Pauls)
> ace-deployment-verifier-ui doesn't compile from an IDE
> ------------------------------------------------------
>                 Key: ACE-182
>                 URL:
>             Project: ACE
>          Issue Type: Improvement
>          Components: Maven Build
>            Reporter: Paul Bakker
>            Priority: Minor
>             Fix For: 1.0.0
>         Attachments: pomfix.diff
> ACEVerifierExtension uses some classes only available in osgi.core 4.3.0. The dependencies
are correct but still give a compile error in both Eclipse and Intellij.
> ace-deployment-verifier and ace-deployment-verifier-ui have a compile time dependency
on osgi.core 4.3.0. ace-deployment-verifier has the following Maven dependency:
> <dependency>
>        <groupId>org.osgi</groupId>
>         <artifactId>org.osgi.core</artifactId>
>        <version>4.3.0</version>
> </dependency>
> This required packages are than exported:
> <export.package>
>        org.apache.ace.deployment.verifier;version=${project.version},org.osgi.service.log,org.osgi.framework.wiring
> </export.package>
> The ace-deployment-verifier-ui has the following dependency (without version):
> <dependency>
>        <groupId>org.osgi</groupId>
>        <artifactId>org.osgi.core</artifactId>
> </dependency>
> It will pick up the version exported by the the ace-deployment-verifier. This works well
in a command line build, but Eclipse and Intellij pick up 4.2.0 for this dependency because
the parent pom's version is used. This is an error in the IDEs but a problem during development
anyway. Setting the version to 4.3.0 and an explicit import seems to solve this while still
working correctly. I provided a patch with these changes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message