Hi, Oops. True, I stumbled upon this issue myself. I fixed it by just deploying the respective parent project to my local repository. I also wrote to the BSF-dev list about this.
It would probably be a good idea to go to bsf snapshot until the parent project is in the maven repos. Will do that right now. Regards Felix Am Montag, den 17.12.2007, 13:59 +0100 schrieb Bertrand Delacretaz: > On Dec 17, 2007 1:22 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > ...I just migrated microsling (was easy, actually) but did not run the > > integration tests yet.... > > Thanks - I tried to build the whole thing but sling/scripting/api fails: > > Failed to resolve artifact. > > GroupId: org.apache.bsf > ArtifactId: parent > Version: 3.0-beta2 > > Apparently the pom at > http://repo1.maven.org/maven2/org/apache/bsf/bsf-api/3.0-beta2/bsf-api-3.0-beta2.pom > refers to this "parent" artifact but that's not in the Maven > repository. > > Does it work for you with svn rev 604858? > > The sling-api build works for me if I use 3.0-SNAPSHOT for the bsf-api > dependency. > > -Bertrand
