Ok looks like I don't have enough privileges (or at least I've not set up my gpg keys) to do a deploy but I can run:
cd $felix-svn/framework mvn clean install org.apache.felix:maven-bundle-plugin:install This generates a file for me locally in ~/.m2/repository/repository.xml which is fine for me for the time being. Thx for the pointer. Regards, Dave On Wed, Aug 5, 2009 at 5:26 PM, Richard S. Hall<[email protected]> wrote: > On 8/5/09 12:15, David Savage wrote: >> >> Sure that makes sense to me. Is this something I can do - happy to go >> digging? >> > > I think it is just a step in the release process: > > http://felix.apache.org/site/release-management-nexus.html > > -> richard > >> Regards, >> >> Dave >> >> On Wed, Aug 5, 2009 at 5:13 PM, Richard S. Hall<[email protected]> >> wrote: >> >>> >>> I don't think it would cause any issues, so we could consider putting it >>> in, >>> but we would likely want to put in org.apach.felix.framework and >>> org.apache.felix.main. >>> >>> -> richard >>> >>> On 8/5/09 12:04, David Savage wrote: >>> >>>> >>>> Hi there, >>>> >>>> I've found the http://felix.apache.org/obr/releases.xml OBR >>>> repository, which is great it just plugs in neatly to sigil and I can >>>> pull binary dependencies from it into my development environment. >>>> However the one binary I can't pull from here is felix.jar. I >>>> understand in a runtime this makes no sense as the jar is already >>>> there but in sigil at development time it would be neat if I could >>>> just point my development environment at this file and have it link to >>>> the felix.jar to satisfy import package requirements. >>>> >>>> Thoughts? >>>> >>>> Regards, >>>> >>>> Dave >>>> >>>> >>> >>> >
