I don't think so. What exactly is the command you are running and what does the error message look like? Are you aware of the transitiveClassifiers settings? That contains a list of the strings to retrieve classifiers for and would fix a problem on sbt's side. I don't know if sbtidea hard codes "sources" or has some other way of selecting sources once resolved.
-Mar
> Cheers
>
> Jon
>
> There's no error unfortunately - and sbtidea does have appear to have
> sources/javadoc hardcoded (not unreasonably) - see
> https://github.com/mpeltonen/sbt-idea/blob/master/src/main/scala/org/sbtidea/SbtIdeaModuleMapping.scala
I'd be surprised if that does anything. I don't think ScalaInstance.extraJars ever contains sources/javadocs, although it may have in 0.7 and that code wasn't removed. This is the more likely part where sources/javadocs are extracted:
> I'm not having an issue getting the src jar's into my ivy repository,
> just wondering if there was any way I could associate our internal src/
> doc classifier with the sources/javadoc convention. We can internally
> fork sbtidea, but I'm trying to see if there's a solution which would
> work with all plugins expecting a standard repository layout.
Plugins should probably make the classifiers to search for be a setting, mostly because it shouldn't be too much work and because you aren't likely to be the only one. The IDE plugin authors can correct me if I've misjudged this.
-Mark
I'd be surprised if that does anything. I don't think ScalaInstance.extraJars ever contains sources/javadocs, although it may have in 0.7 and that code wasn't removed. This is the more likely part where sources/javadocs are extracted:
Plugins should probably make the classifiers to search for be a setting, mostly because it shouldn't be too much work and because you aren't likely to be the only one. The IDE plugin authors can correct me if I've misjudged this.