I’ve updated the next branch to not have the -SNAPSHOT. Not sure really where 
that came from anyway.

Kind regards,

        Peter Kriens

> On 18 May 2017, at 17:54, BBrooks <brian.bro...@acm.org> wrote:
> 
> > It should be without the SNAPSHOT. Can you recall how the -SNAPSHOT got in 
> > there?
> 
> The "-SNAPSHOT" came from the osgi/workspace GitHub Repository.
> 
> When I did 
> 
> 1. Eclipse->File->New->Other
> 2. Eclipse shows New->Select a wizard"
> 3. Selected Bndtools->Bnd OSGi Workspace and clicked Next.
> 4. Eclipse shows "Setup Bnd Workspace".
> 5. Click Location->Create in->c:\dev\git\com.acme.prime and clicked Next.
> 6. Eclipse shows "Selecte Workspace Template".
> 7. Selected GitHub->osgi/workspace [https://github.com/osgi/workspace.git 
> <https://github.com/osgi/workspace.git> next] and clicked Next.
> 8. Eclipse shows Preview Changes.
> 9. Clicked Finish.
> 10. Eclipse creates a cnf project and switches to Bndtools Perspective.
> 
> The bnd project created by Eclipse already contains the erroneous "-SNAPSHOT" 
> in cnf/ext/enroute-distro.bnd.  I think it's getting downloaded from 
> 
> https://github.com/osgi/workspace/blob/next/cnf/ext/enroute-distro.bnd 
> <https://github.com/osgi/workspace/blob/next/cnf/ext/enroute-distro.bnd>
> 
> the current revision 
> https://github.com/osgi/workspace/commit/862f1d9bc0b6ad79ef578c85503ef17f54d60bda
>  
> <https://github.com/osgi/workspace/commit/862f1d9bc0b6ad79ef578c85503ef17f54d60bda>
>  has an -plugin.enroute.distro entry with the "-SNAPSHOT" text.  Doing Blame 
> on that file shows it has had that -SNAPSHOT for 7 months. 
> 
> Brian
> 
> 
> On Thu, May 18, 2017 at 10:16 AM, Peter Kriens <peter.kri...@aqute.biz 
> <mailto:peter.kri...@aqute.biz>> wrote:
> On the current workspace the bndpom repo looks like:
> 
> -plugin.enroute.distro = \
>       aQute.bnd.repository.maven.pom.provider.BndPomRepository; \
>               snapshotUrls=https://oss.sonatype.org/content/groups/osgi 
> <https://oss.sonatype.org/content/groups/osgi>; \
>               releaseUrls=https://repo1.maven.org/maven2/ 
> <https://repo1.maven.org/maven2/>; \
>               revision=org.osgi:osgi.enroute.pom.distro:2.0.0; \
>               name=Distro; \
>               location=${build}/cache/enroute-distro.xml
> 
> 
> 
> It should be without the SNAPSHOT. Can you recall how the -SNAPSHOT got in 
> there?
> 
> Kind regards,
> 
>       Peter Kriens
> 
> 
>> On 18 May 2017, at 16:11, BBrooks <brian.bro...@acm.org 
>> <mailto:brian.bro...@acm.org>> wrote:
>> 
>> I'm trying to follow the Enroute Quick Start Tutorial.  But I got stuck with 
>> this build error
>> 
>> Cannot find /error/osgi.enroute.base.api;version=0 Not found in [bnd-cache, 
>> Central, Local, Release, Distro]
>> 
>> I don't know how to fix this problem.  I think the root cause is that the 
>> Distro repository seems to be invalid.
>> 
>> What is the correct cnf/ext/enroute-distro.bnd?  The steps in the tutorial 
>> resulted in an enroute-distro.bnd that looks like
>> 
>> -plugin.enroute.distro = \
>>      aQute.bnd.repository.maven.pom.provider.BndPomRepository; \
>>              snapshotUrls=https://oss.sonatype.org/content/groups/osgi 
>> <https://oss.sonatype.org/content/groups/osgi>; \
>>              releaseUrls=https://repo1.maven.org/maven2/ 
>> <https://repo1.maven.org/maven2/>; \
>>              revision=org.osgi:osgi.enroute.pom.distro:2.0.0-SNAPSHOT; \
>>              name=Distro; \
>>              location=${build}/cache/enroute-distro.xml
>> 
>> I found some August 2016 information here 
>> https://disqus.com/home/discussion/osgi-enroute/forum_49/ 
>> <https://disqus.com/home/discussion/osgi-enroute/forum_49/> suggesting using 
>> the URL 
>> https://raw.githubusercontent.com/osgi/osgi.enroute/master/cnf/distro/index.xml
>>  
>> <https://raw.githubusercontent.com/osgi/osgi.enroute/master/cnf/distro/index.xml>.
>>   But using that location didn't work either.
>> 
>> ********Below I'm documenting what I did and some of the errors I'm 
>> noticing....*************
>> 
>> I noticed in this page
>> 
>> http://enroute.osgi.org/qs/200-workspace.html 
>> <http://enroute.osgi.org/qs/200-workspace.html>
>> 
>> this text
>> 
>> "WARNING: This is the BETA tutorial for OSGi enRoute 2.0.0. To use the right 
>> workspace template, go to Bndtools preferences and select Workspace 
>> Templates. You should edit the OSGi enRoute template and select the next 
>> branch."
>> 
>> In response to this text, I completed these steps.
>> 
>> 1. Eclipse->Preferences->Bndtools->Workspace Template->GitHub Repositories
>> 2. Click osgi/workspace
>> 3. Click Edit.
>> 4. In the Add Repository tab entered these values
>> Repository Name: osgi/workspace
>> Branch: next
>> 5. Click Validate.
>> 6. Eclipse confirms with "Validated! Clone URL is 
>> 'https://github.com/osgi/workspace.git 
>> <https://github.com/osgi/workspace.git>'. Default branch 'origin/master'"
>> 7. Click Save.
>> 8. Eclipse updates osgi/workspace to read "osgi/workspace; branch=next".
>> 
>> Then I executed the steps in the "Creating the bnd Workspace" section of 
>> 200-workspace.html.  After clicking "Finish" in the workspace creation 
>> Wizard.  I noticed that the Eclipse "Repositories" view contains a Distro 
>> that appears to have a problem.  Expanding the Distro repository reveals
>> 
>> Distro->org.osgi:osgi.enroute.pom.distro [!]->2.0.0.SNAPSHOT 
>> [java.lang.NullPointerException]
>> 
>> The Eclipse Error Log view contains
>> Failed to query repository Distro for bundle 
>> org.osgi:osgi.enroute.pom.distro version 2.0.0.SNAPSHOT.
>> 
>> Eclipse plugin: bndtools.core
>> Caused by: java.io.FileNotFoundException: For Maven artifact 
>> org.osgi:osgi.enroute.pom.distro:2.0.0-SNAPSHOT
>>      at aQute.maven.provider.MavenRepository$1.run(MavenRepository.java:140)
>>      at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>      at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>      at java.lang.Thread.run(Thread.java:745)
>> 
>> -- 
>> brian.bro...@acm.org 
>> <mailto:brian.bro...@acm.org>_______________________________________________
>> OSGi Developer Mail List
>> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
>> https://mail.osgi.org/mailman/listinfo/osgi-dev 
>> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> 
> _______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>
> https://mail.osgi.org/mailman/listinfo/osgi-dev 
> <https://mail.osgi.org/mailman/listinfo/osgi-dev>
> 
> 
> 
> -- 
> brian.bro...@acm.org 
> <mailto:brian.bro...@acm.org>_______________________________________________
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev

_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev

Reply via email to