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

Mark Nuttall resolved ARIES-812.
--------------------------------

    Resolution: Fixed

Aries build back to stable as of 
https://builds.apache.org/job/Aries/1331/testReport/
                
> Build break:  failures in 
> org.apache.aries.jpa.container.itest.JPAContainerDataSourceFactoryTest.testDataSourceFactoryXALifecycle
>  and elsewhere
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ARIES-812
>                 URL: https://issues.apache.org/jira/browse/ARIES-812
>             Project: Aries
>          Issue Type: Bug
>            Reporter: Mark Nuttall
>
> Investigations suggest that this test is failing because 
> org.apache.aries.jndi.core_0.3.2.SNAPSHOT and  
> org.apache.aries.jndi.url_0.3.2.SNAPSHOT are failing to resolve:
> org.osgi.framework.BundleException: The bundle 
> "org.apache.aries.jndi.url_0.3.2.
> SNAPSHOT [17]" could not be resolved. Reason: Missing Constraint: 
> Import-Package
> : org.apache.aries.util.log; version="[0.1.0,0.2.0)"
> This package is not exported by the version of org.apache.aries.util in the 
> test runtime:
> org.apache.aries.util_0.4.0 [9]
>   Id=9, Status=ACTIVE      Data 
> Root=C:\Users\mnuttall\AppData\Local\Temp\paxexa
> m_runner_mnuttall\equinox\org.eclipse.osgi\bundles\9\data
>   No registered services.
>   No services in use.
>   Exported packages
>     org.apache.aries.util; version="0.4.0"[exported]
>     org.apache.aries.util.tracker; version="0.4.0"[exported]
>     org.apache.aries.util.nls; version="0.3.0"[exported]
>     org.apache.aries.util.io; version="0.1.0"[exported]
>     org.apache.aries.util.service.registry; version="0.1.0"[exported]
>     org.apache.aries.util.manifest; version="0.1.0"[exported]
>     org.apache.aries.util.filesystem; version="0.1.0"[exported]
>   Imported packages
>     org.osgi.framework; version="1.6.0"<org.eclipse.osgi_3.7.0.v20110613 [0]>
>     org.osgi.util.tracker; version="1.5.0"<org.eclipse.osgi_3.7.0.v20110613 
> [0]>
>     org.slf4j; version="1.5.6"<org.ops4j.pax.logging.pax-logging-api_1.5.0 
> [4]>
>     org.osgi.service.framework; 
> version="1.0.0"<org.eclipse.osgi_3.7.0.v20110613
>  [0]>
>     org.osgi.framework.launch; 
> version="1.0.0"<org.eclipse.osgi_3.7.0.v20110613
> [0]>
>     org.eclipse.osgi.internal.loader; 
> version="0.0.0"<org.eclipse.osgi_3.7.0.v20
> 110613 [0]>
>     org.eclipse.osgi.framework.internal.core; 
> version="0.0.0"<org.eclipse.osgi_3
> .7.0.v20110613 [0]>
>     org.eclipse.osgi.framework.adaptor; 
> version="0.0.0"<org.eclipse.osgi_3.7.0.v
> 20110613 [0]>
>   No fragment bundles
>   Named class space
>     org.apache.aries.util; bundle-version="0.4.0"[provided]
>   No required bundles
> It looks like something bad has happened to org.apache.aries.util. 
> Investigations continue. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to