I believe I have found a bug with respect to the artifactId. I think the length of the artifactId will lead to this bug as the only ones that caused this problem were of character size: 38 and 42
Is there a bug limitation in how long artfactId's may be? Obviously maven/java itself would not impose this issue. After shortening the artfactId for the built artfacts in question, I was able to get around this issue. -- View this message in context: http://forums.jfrog.org/rpm-metadata-extraction-is-being-skipped-tp7578766p7578768.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
