Hide Forgot
Chapter 2, Installing the Repository: > > The result sections of procedure 2.1 and 2.2 say that they create two > directories called "jboss-eap-6.0.0.Alpha2-maven-repository.zip" and > "jboss-wfk-2.0.0-repository.zip". The directory names do not have ".zip" > at the end. > > > The first note on the page only applied to the Nexus installation. The > second one would appear to apply to the local file system and web server > installations (since you don't unzip anything for the Nexus install). > I'm not sure what it means anyway: > - > "Unzipping the JBoss Web Framework Kit zip into the same folder as the > JBoss Enterprise Application platform will replicate the configuration > changes for both repositories. > - > > > > The procedures also say "Unzip the files in the same directory on the > local file system". Is there any reason we want that? They work > perfectly fine in different locations, and when you are editing > settings.xml you need to point to both locations anyway. > > > In chapter 3, they give the example URL to use in settings.xml as > "file:///path/to/repo/jboss-wfk-2.0.0-repository/repository". That does > not match what we ship in the zip file, which does not have the final > "/repository". > > > In chapter 4, the example has: > <dependency> > <groupId>com.redhat.jboss.wfk.boms</groupId> > <artifactId>spring-3.0-import</artifactId> > <type>pom</type> > <version>1.2-SNAPSHOT</version> > <scope>import</scope> > </dependency> > > The artifactId is wrong, it should be "spring-3.0-bom", and version > number should be "2.0.0-redhat-1". > > The example also contains explicit version numbers for > org.aspectj:aspectjrt and org.aspectj:aspectjweaver. They should be left > out since the BOM declared them (and the version in the example is wrong > now too). > >
Gary, is this stuff useful to you?
Hi Bec, thanks. I'll file this.
Verified in ER3.