Roy Krishna (Inactive) added a comment - 10/Jul/2012 7:07 AM Thanks for everyone's feedback, JIRA 5.1 was released today. https://confluence.atlassian.com/display/JIRA/JIRA+5.1+Release+Notes

Andy Brook (Javahollic Software) added a comment - 02/Jul/2012 11:04 AM Yup, well spotted, I had a bunch of spring dependencies, though I them with provided scope, so I would have thought they would not have caused a problem, well, all except spring-ldap-core... tnx

tier-0 grump added a comment - 02/Jul/2012 6:24 AM - edited javahollic - I've tried to replicate your problem, but am unable to. It looks to be a Spring version conflict from the limited info in the stack trace - maybe you have a dependency on Spring (maybe even transitively) in your plugin?

Andy Brook (Javahollic Software) added a comment - 01/Jul/2012 10:42 AM - edited I use AO, but my plugin, whilst compiling fine is failing to deploy on install due to the following, advice? org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'tx-processor' defined in URL [bundle://94.0:0/META-INF/spring/atlassian-plugins-components.xml]: Unsatisfied dependency expressed through constructor argument with index 0 of type [com.atlassian.activeobjects.external.ActiveObjects]: : Error creating bean with name 'ao': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: interface org.springframework.aop.IntroductionInfo is not visible from class loader; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'ao': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalArgumentException: interface org.springframework.aop.IntroductionInfo is not visible from class loader at org.springframework.beans.factory.support.ConstructorResolver.createArgumentArray(ConstructorResolver.java:591) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:193) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:925) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:835) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:440) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:880) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.registerBeanPostProcessors(AbstractDelegatedExecutionApplicationContext.java:551) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.registerBeanPostProcessors(AbstractDelegatedExecutionApplicationContext.java:486) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:336) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:132) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Is AO fully validated in RC3? I'm depending on 0.9.17 which is shipped with RC3 and I'm not depending on IntroductionInfo...

Malachi de AElfweald added a comment - 20/Jun/2012 9:45 PM Bryan - yes, thank you. It's an issue getting JIRA 5.0.6 with GH 5.10.3 - so I got redirected here by mistake (they thought I was using JIRA 5.10.3). Following up on the GHS bug.

Bryan Rollins added a comment - 20/Jun/2012 9:40 PM Malachi, thanks for letting us know. This EAP Feedback issue covers feedback on the JIRA 5.1 Early Access Program release (not bug fix releases like JIRA 5.0.6). The GreenHopper issue you mentioned is a story about sprint reports. Did you mean to include the issue key for a GreenHopper bug? If there's an issue with GreenHopper on a current release of JIRA, definitely file a bug against GreenHopper so we can look into it. (Or let us know if you meant something else entirely.)

Malachi de AElfweald added a comment - 20/Jun/2012 8:20 PM Greenhopper does not appear to work with JIRA 5.0.6 [see GHS-4766 for report]

Jon Sword added a comment - 20/Jun/2012 5:55 AM I just created JRA-28625 . Looking at my profile on http://jira.atlassian.com I noticed that the Summary on an issue in my activity feed did not match the issue.

Bryan Rollins added a comment - 29/May/2012 6:42 PM Stephan, thanks for the feedback. Unless the user is logged into your JIRA instance (i.e. has an active session), they will not see the link to the issue on your JIRA instance. I.e anonymous users don't see the link, they just see the thank you message. Is there anything else that you would want to edit in the template that you can't edit in the custom template today?

StephanS added a comment - 29/May/2012 4:51 PM The issue collector is great, but it's very important that all templates can be edited. For example: If I use this feature on a public website the user shouldn't know which Issue was created and how the link to my issue server.