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

Push Java releases to public Maven repo #37

Closed
GoogleCodeExporter opened this issue Oct 24, 2015 · 5 comments
Closed

Push Java releases to public Maven repo #37

GoogleCodeExporter opened this issue Oct 24, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

Is there a particular reason why poly2tri should not be available in public 
Maven repos? Sonatype offers an easy no-effort way for OSS projects: 
https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage
+Guide


Original issue reported on code.google.com by marcel@frightanic.com on 11 Jan 2012 at 10:21

@GoogleCodeExporter
Copy link
Author

I took a look at that back when I released first version of Poly2Tri.
I think I read that dependencies needed to be available from Maven repos. 

poly2tri-core only has one dependency and that is a maven available lib. But 
the poly2tri-example had lwjgl and ardor3d which is not available thru maven. 

Well I never got around to figuring out how to just make poly2tri-core 
available thru maven.

Original comment by thahlen@gmail.com on 13 Jan 2012 at 8:54

@GoogleCodeExporter
Copy link
Author

this is not an issue.

Original comment by mason.gr...@gmail.com on 4 Feb 2012 at 9:10

  • Changed state: Invalid

@GoogleCodeExporter
Copy link
Author

What? Not an issue? Unless you're creating OSS just for yourself you must be 
darn ignorant to label requests "by the community" as invalid...*shaking my 
head in disbelief* 

Original comment by marcel@frightanic.com on 5 Feb 2012 at 6:53

@GoogleCodeExporter
Copy link
Author

When I release the next version of poly2tri for java I will try to make 
poly2tri-core available thru maven.

I guess mason saw this as an invalid issue since it's more of a request then a 
software issue.

Original comment by thahlen@gmail.com on 5 Feb 2012 at 7:32

@GoogleCodeExporter
Copy link
Author

Well...even if you consider it a request it's still a (IMO valid) issue. I 
guess that's why Google Code has issues of type 'defect' and 'enhancement'.

Original comment by marcel@frightanic.com on 6 Feb 2012 at 10:50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant