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

Implement pom.xml definitions for compliance with OSSRH #2

Closed
lewismc opened this issue Apr 21, 2015 · 8 comments
Closed

Implement pom.xml definitions for compliance with OSSRH #2

lewismc opened this issue Apr 21, 2015 · 8 comments

Comments

@lewismc
Copy link
Contributor

lewismc commented Apr 21, 2015

As part of consuming Unidata artifacts within the Apache Tika project, I've been working for some time to monitor the Unidata lists and shadow releases with aritfact publication to Maven central as per https://wiki.apache.org/tika/ThirdPartySonaType

Recently, when attempting to push the jj2000 artifact, I've found that OSSRH rejects the staging artifact due to a number of issue

  • pom validation: project name mising, URL missing, License Information missing, SCM URL missing and Developer Information missing
  • No sources.jar to accompany main jar
  • no javadoc.jar artifact to accompany main jar
@lewismc
Copy link
Contributor Author

lewismc commented Apr 23, 2015

@dopplershift can you please suggest a forum of mailing list where I can discuss 3rd party dependencies present within the Unidata software artifacts?

@dopplershift
Copy link
Member

Do you have a particular project in mind? Like netcdf-java?

@dopplershift
Copy link
Member

Ok, now that I've looked over the Tika project, I'd say for netcdf-java:

@lewismc
Copy link
Contributor Author

lewismc commented Apr 23, 2015

Well...
I have an issue with one of the dependencies contained within your
repository, namely this one
https://artifacts.unidata.ucar.edu/content/repositories/unidata-3rdparty/org/itadaki/bzip2/
It was not on Maven central until I published it 2 days ago.
It is no longer maintained in it's current repository, but one or more of
the UCAR dependencies depend upon it.
I submitted a patch which is not being merged because the library is
unmaintained.

https://code.google.com/p/jbzip2/issues/detail?id=3

I was wondering what the workflow uis for migrating away from these
projects. I was maybe thinking about forking the code base and maintaining
it myself.

On Thu, Apr 23, 2015 at 2:17 PM, Ryan May notifications@github.com wrote:

Ok, now that I've looked over the Tika project, I'd say for netcdf-java:


Reply to this email directly or view it on GitHub
#2 (comment).

Lewis

@dopplershift
Copy link
Member

Let's punt over to the github issues tracker for the thredds repo (which holds netcdf-java).

@lewismc
Copy link
Contributor Author

lewismc commented Apr 23, 2015

ACK

@lewismc
Copy link
Contributor Author

lewismc commented Apr 23, 2015

Where is it? Can you please reference?

@dopplershift
Copy link
Member

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