You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ace.apache.org by "Karl Pauls (JIRA)" <ji...@apache.org> on 2011/09/26 15:08:26 UTC

[jira] [Resolved] (ACE-182) ace-deployment-verifier-ui doesn't compile from an IDE

     [ https://issues.apache.org/jira/browse/ACE-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karl Pauls resolved ACE-182.
----------------------------

       Resolution: Fixed
    Fix Version/s: 1.0.0

Done. Please close if it works for you.

> ace-deployment-verifier-ui doesn't compile from an IDE
> ------------------------------------------------------
>
>                 Key: ACE-182
>                 URL: https://issues.apache.org/jira/browse/ACE-182
>             Project: Ace
>          Issue Type: Improvement
>          Components: Maven Build
>            Reporter: Paul Bakker
>            Assignee: Karl Pauls
>            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.
For more information on JIRA, see: http://www.atlassian.com/software/jira