-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crowd plugin 2.7.0 is reported as broken on Nexus 2.8.0-05 #14
Comments
yes nexus 2.8 introduces some breaking changes in their API and also they switched over their plugin systems and the maven versions. |
Hopefully next week - I'll be able to take a look into it... On 05/05/14 02:05, Patrick Roumanoff wrote:
|
Same problem encountered. Thanks for looking into it. |
Would you please update the zip download with the fix @ https://github.com/PatrickRoumanoff/nexus-crowd-plugin/wiki Thanks much! |
Hi, this is known to be broken in Nexus 2.8. You should build the master ------ Original Message ------
|
Hi flopma, Thanks and Regards, From: flopma [mailto:notifications@github.com] Hi, this is known to be broken in Nexus 2.8. You should build the master ------ Original Message ------
— |
Yay! It worked. Thanks. |
Yes. Thank you. Installation of the new snapshot did work. However, I'm seeing a 403 now in wrapper.log. I've verified that I set up the application link correctly. Did Sonatype change something else in the crowd-plugin.xml? Full disclosure, I'm using the embedded crowd within JIRA. If there's a better place for me to post this let me know. Trace: .xml |
I bet this is coming from your Crowd server. Check the logs there. Sent from my iPhone On Jun 25, 2014, at 8:11 PM, "sdazzo" <notifications@github.commailto:notifications@github.com> wrote: Yes. Thank you. Installation of the new snapshot did work. However, I'm seeing a 403 now in wrapper.log. I've verified that I set up the application link correctly. Did Sonatype change something else in the crowd-plugin.xml? Full disclosure, I'm using the embedded crowd within JIRA. If there's a better place for me to post this let me know. Trace: .xml https:/// — This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the email by you is prohibited. |
Like I said, not using a standalone crowd server but the embedded jira crowd. I looked into numerous jira logs but am not seeing anything related to nexus or the application link. |
AFAIK we have never tested the plugin with JIRA + embedded crowd - so there is no guarantee this will work. Probably better to raise a new issue with your logs of the error. |
Hi. I appreciate the very quick responses. I've created a new issue as requested. Thanks. |
@antongurov which version of nexus did you get it working with? Since I'm at the latest, I will downgrade if necessary. |
Nexus has made new changes to break crowd plugin 2.7.0 :(
The text was updated successfully, but these errors were encountered: