Mark, If you run:
svn ps svn:log --revprop -r1027526 "ARIES-446 AriesApplicationManager registers an application BundleRepository even when one already exists. Patch by Chris Wilkinson." It should update the svn:log to be correct. I wont sort the JIRA side of the story, but at least the svn log will be correct. Alasdair On 27 October 2010 19:41, Mark Nuttall (JIRA) <[email protected]> wrote: > > [ > https://issues.apache.org/jira/browse/ARIES-466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > Mark Nuttall updated ARIES-466: > ------------------------------- > > Comment: was deleted > > (was: Apologies for the accidental commit error. My October 11th svn commit > should have been against ARIES-466, not ARIES-446. ) > >> org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise >> implementation >> -------------------------------------------------------------------------------- >> >> Key: ARIES-466 >> URL: https://issues.apache.org/jira/browse/ARIES-466 >> Project: Aries >> Issue Type: Bug >> Components: JNDI >> Affects Versions: 0.2 >> Environment: all >> Reporter: David Schmitz >> Original Estimate: 0.5h >> Remaining Estimate: 0.5h >> >> org.apache.aries.jndi-0.2-incubating includes org.osgi.enterprise bundle >> implementations which causes problems when using >> <dependency> >> <groupId>org.osgi</groupId> >> <artifactId>org.osgi.enterprise</artifactId> >> <version>4.2.0</version> >> </dependency> >> as well. If used with org.osgi.enterprise one gets an error that the Initial >> JNDI Context Factory is already registered and aries JNDI can not work. >> I could get around this problem by using org.eclipse.gemini.naming.framework >> with org.osgi.enterprise + rest of aries. >> So my suggestion is simply remove org.osgi api implementation from >> org.apache.aries.jndi-0.2-incubating and use the one from reference >> org.osgi.enterprise bundle. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > > -- Alasdair Nottingham [email protected]
