I've just seen the following issue in our JIRA. The problem is that there is no
version 1.0.0, but rather ${karaf.version} :). How do we like to handle this
problem? Set ${project.version} vars into the docu and pre-process them or
rather use ${karaf.version} as text-tag making this situation clear?kind regards, andreas On Thu, Feb 10, 2011 at 09:17:57PM +0000, jamie campbell (JIRA) wrote: > page 56 of the pdf lists a dependency for > org.apache.karaf.shell:org.apache.karaf.shell.console:1.0.0. There isn't one. > ------------------------------------------------------------------------------------------------------------------------ > > Key: KARAF-456 > URL: https://issues.apache.org/jira/browse/KARAF-456 > Project: Karaf > Issue Type: Bug > Components: documentation > Affects Versions: 2.1.3 > Environment: ubuntu 10.04 > Reporter: jamie campbell > > > in the pdf manual for 2.1.3, dependencies in "extending the console" lists > > <dependency> > <groupId>org.apache.karaf.shell</groupId> > <artifactId>org.apache.karaf.shell.console</artifactId> > <version>1.0.0</version> > </dependency> > > But the pom file shown above it in "Manual Creation" has no repositories > ilsted, which means it will grab from default, and the default repository > only has versions 2.0.0 ; 2.1.0 ; 2.1.1 ; 2.1.2 ; and 2.1.3 . Thus, the > dependency is not found. > > -- > This message is automatically generated by JIRA. > - > For more information on JIRA, see: http://www.atlassian.com/software/jira > >
pgpKMlnVoc4SS.pgp
Description: PGP signature
