[ 
https://issues.apache.org/jira/browse/ARIES-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028284#comment-13028284
 ] 

John Ross commented on ARIES-640:
---------------------------------

After fixing previous issue, ran into the following while executing "mvn clean 
install" from the application directory.

[ERROR] Failed to execute goal on project 
org.apache.aries.application.runtime.isolated.itests: Could not resolve 
dependencies for project org.apache.
aries.application:org.apache.aries.application.runtime.isolated.itests:jar:0.3.1-SNAPSHOT:
 Failure to find org.apache.aries.application:org.apache.ari
es.application.runtime.repository:jar:0.3.1-SNAPSHOT in 
http://snapshots.repository.codehaus.org was cached in the local repository, 
resolution will n
ot be reattempted until the update interval of codehaus.snapshots has elapsed 
or updates are forced -> [Help 1]

Again, there is no jar within the 0.3.1-SNAPSHOT directory of 
org.apache.aries.application.runtime.repository. There is one, however, within 
the 0.4-SNAPSHOT directory.

Chaning the pom.xml within the application-itests directory to

        <dependency>
                <groupId>org.apache.aries.application</groupId>
                
<artifactId>org.apache.aries.application.runtime.repository</artifactId>
            <version>0.4-SNAPSHOT</version>
                <scope>test</scope>
        </dependency>

got past this issue.

Next up, after running "mvn clean install" again, was

Running org.apache.aries.application.runtime.itests.UpdateAppTest
Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 192.515 sec <<< 
FAILURE!
Running org.apache.aries.application.runtime.itests.IsolatedRuntimeTest
Tests run: 5, Failures: 0, Errors: 5, Skipped: 0, Time elapsed: 326.063 sec <<< 
FAILURE!

Looking within the test reports, both IsolatedRuntimeTest and UpdateAppTest 
showed

[Framework Event Dispatcher] DEBUG 
org.apache.aries.application.runtime.repository - FrameworkEvent ERROR
org.osgi.framework.BundleException: The bundle could not be resolved. Reason: 
Missing Constraint: Import-Package: org.apache.aries.application.utils.service; 
version=&quot;[0.4.0,1.0.0)&quot;
        at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1313)
        at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1297)
        at 
org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:309)
        at 
org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:370)
        at 
org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1068)
        at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:557)
        at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:464)
        at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:248)
        at 
org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:445)
        at 
org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:220)
        at 
org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:330)

Changing the packageinfo file in 
aries-test\application\application-utils\src\main\java\org\apache\aries\application\utils\service
 from 0.3.0 to 0.4.0 fixed this.

I then ran into

[ERROR] Failed to execute goal on project 
org.apache.aries.application.tooling.repository.generator: Could not resolve 
dependencies for project org.ap
ache.aries.application:org.apache.aries.application.tooling.repository.generator:bundle:0.1.0-SNAPSHOT:
 Failure to find org.apache.aries.proxy:org.apa
che.aries.proxy:jar:0.3.1-SNAPSHOT in http://snapshots.repository.codehaus.org 
was cached in the local repository, resolution will not be reattempted
until the update interval of codehaus.snapshots has elapsed or updates are 
forced -> [Help 1]

Changing the pom.xml within the application-tooling-repository-generator 
directory to

        <dependency>
            <groupId>org.apache.aries.proxy</groupId>
            <artifactId>org.apache.aries.proxy</artifactId>
            <version>0.4-SNAPSHOT</version>
        </dependency>

got past this issue.

"mvn clean install" now executes successfully from the application directory.

> application.utils imports aries.util version [0.4,1.0) but aries.util exports 
> version 0.3.1
> -------------------------------------------------------------------------------------------
>
>                 Key: ARIES-640
>                 URL: https://issues.apache.org/jira/browse/ARIES-640
>             Project: Aries
>          Issue Type: Bug
>          Components: Application
>    Affects Versions: 0.4
>            Reporter: John Ross
>
> Given the latest repo contents, I encounter the following error when 
> executing some junit tests.
> org.osgi.framework.BundleException: The bundle 
> "org.apache.aries.application.utils_0.4.0.SNAPSHOT [13]" could not be 
> resolved. Reason: Missing Constraint: Import-Package: org.apache.aries.util; 
> version="[0.4.0,1.0.0)"
>       at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1327)
>       at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1311)
>       at 
> org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
>       at 
> org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:389)
>       at 
> org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1130)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:559)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:544)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:457)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:438)
>       at 
> org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:1)
>       at 
> org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
>       at 
> org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> The manifest within org.apache.aries.application.utils-0.4-SNAPSHOT.jar 
> imports org.apache.aries.util;version="[0.4,1.0)" but 
> org.apache.aries.util-0.4-SNAPSHOT.jar exports 
> org.apache.aries.util;version="0.3.1". I've tried "mvn clean install" on 
> those two projects as well as just about everything else. Am I missing 
> something?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to