Skip to content
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

Repository element in jira extension #1

Open
kpiwko opened this issue May 21, 2015 · 4 comments
Open

Repository element in jira extension #1

kpiwko opened this issue May 21, 2015 · 4 comments

Comments

@kpiwko
Copy link
Member

kpiwko commented May 21, 2015

Could jira connector be replaced with one in Maven Central? If not, could a request to have it on Central be filled for authors?

https://github.com/arquillian/arquillian-governor/blob/master/jira/pom.xml#L111-L122

Very bad practice - should be avoided for released components - http://blog.sonatype.com/2009/02/why-putting-repositories-in-your-poms-is-a-bad-idea/#.VV2PrHM4Z4s

@kpiwko kpiwko changed the title Repository element in Repository element in jira extension May 21, 2015
@smiklosovic
Copy link
Member

@kpiwko

this artifact (1) seems to be the one we need and it is already released in Central hence there is a chance we can get rid of the repository element in the pom.xml.

I have already released 1.0.0.Alpha2 yesterday but it is still in staging hence we are lucky. In this special case I would not hesitate to release it once again and rewrite commit history.

(1) https://search.maven.org/#search%7Cga%7C1%7Ccom.atlassian.jira

@kpiwko
Copy link
Member Author

kpiwko commented May 21, 2015

whatever you'll find the most convenient ;-)

@smiklosovic nice profile picture update btw!

@smiklosovic
Copy link
Member

@kpiwko should be better now 4575a13

Already released and staged, I can push the button at will.

@smiklosovic
Copy link
Member

Even we do not have the repository element in the pom.xml, we are relying on an artifact which is in Maven Central but that artifact contains repository element itself, the same one we just deleted hence we just delegated this problem to the external party and we effectively solved nothing.

The proper solution would be to release Jira connector artifacts from Atlassian to Maven Central directly however the result of this request is questionable and out of scope of the alpha2 release because of the lack of time.

I leave this open for tracking purposes.

@smiklosovic smiklosovic reopened this May 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants