Upload to maven central about jackdaw HOT 5 CLOSED

Can't find mistake on my side, so I've just sent request to the author of Jitpack.io. I hope it will be fixed in the nearest future.

from jackdaw.

I assume you are installing them directly to your local repo, correct? This would cause you to never actually see a problem. Remotely we can't see jackdaw-apt or jackdaw-core, only the parent one. This is a problem since it needs to be declared separately at build time. In looking at the parent jar that was downloaded it was empty, so it might be a configuration problem.

from jackdaw.

Just to clarify: I checked it locally and even tried to remove directory ~/.m2/repository/com/github/vbauer before mvn clean install (to make clean test). As I said it works pretty fine on my side, but I have some problem with http://jitpack.io, so I still investigate this issue.

PS:

• Actually Jitpack.io should make the same 'mvn clean install', after 'git clone...'.
• "Parent jar" is not JAR archive at all, it has "pom" packaging, but all JAR modules should be installed correctly.

from jackdaw.

It looks like that we found temporary solution: #4

Could you please try to use jackdaw.jackdaw-core and jackdaw.jackdaw-apt instead of jackdaw-core and jackdaw-apt?

from jackdaw.

It would still be good to get Jackdaw into Maven Central. Having jackdaw in Central would make it available for other Maven Central projects (which can't have non-Central dependencies). (From a quick glance, it appears that all of Jackdaw's own dependencies are in Maven Central.)

OSSRH is good for getting projects into Central, perhaps combined with Travis for running the builds: http://central.sonatype.org/pages/ossrh-guide.html

from jackdaw.