Ok sure enough soon after I sent this email, I was able to narrow down the problem with some old pom's that were somehow in my repository. Probably from maven 1 days, so I think I am on the road to fixing the problem. Do read the email below, it might be worth a look to see if Taverna can log such info or to fix the repository.jboss issue.
<dependency> <id>????</id> <version>????</version> </dependency> cheers, Kevin On 16/09/2011 16:59, KevinBenson wrote: > Hi, > > I think the email labeled T2-1989 corrected an earlier problem I saw > with 2.3.0 before holidays. I do have another situation that I suspect > is my fault, I think somewhere I may have some incorrect pom in one of > the dependency libraries. > > Taverna is currently reporting in the logs and just stops trying to add > the plugin: > ERROR 2011-09-16 10:56:01,686 > (net.sf.taverna.t2.workbench.ui.impl.Workbench:117) - Uncaught exception > in Thread[Update Repository Progress,6,main] > java.util.NoSuchElementException > at java.util.AbstractList$Itr.next(AbstractList.java:350) > at > net.sf.taverna.raven.repository.impl.ArtifactImpl.getDependencies(ArtifactImpl.java:166) > at > net.sf.taverna.raven.repository.impl.LocalRepository.act(LocalRepository.java:521) > at > net.sf.taverna.raven.repository.impl.LocalRepository.update(LocalRepository.java:491) > at > net.sf.taverna.raven.plugins.PluginManager.addPlugin(PluginManager.java:220) > at > net.sf.taverna.raven.plugins.ui.PluginSiteFrame$4.run(PluginSiteFrame.java:426) > > I have gone through all the major plugin poms and seem correct, so I can > only think that it's an issue of some other dependency pom. I should > note the plugin screen seems to normally stop on 'Axis 1.3', > (group&artifact name 'axis'). But I suspect it is another pom raven is > trying, probably after 'axis' (reason I tried to change poms to 1.4 and > got a different name in the plugin screen). > > Is there a way for Taverna to tell me where it is having the problem, > hence which pom? I will keep looking just to make sure it is not > something silly. > > Also I suspect you might know already, that it seems by default to try a > http://repository.jboss.org/maven2/ url first (though I don't have it > defined) this always causes a 403 error and reporting exceptions in the > logs. It doesn't seem to hurt anything. > > cheers, > Kevin > > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > http://p.sf.net/sfu/rim-devcon-copy2 > _______________________________________________ > taverna-hackers mailing list > [email protected] > Web site: http://www.taverna.org.uk > Mailing lists: http://www.taverna.org.uk/about/contact-us/ > Developers Guide: http://www.taverna.org.uk/developers/ > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA http://p.sf.net/sfu/rim-devcon-copy2 _______________________________________________ taverna-hackers mailing list [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/ Developers Guide: http://www.taverna.org.uk/developers/
