Sorry, I misunderstood. Actually, making an archetype is on my todo list. I was looking at the generate-from-project goal on the maven archetype plugin:
http://maven.apache.org/plugins/maven-archetype-plugin/advanced-usage.html That may correctly infer the dependencies, etc to make a complete pom. If not, I'll fix it. Derek On Wed, Oct 8, 2008 at 4:07 PM, Charles F. Munat <[EMAIL PROTECTED]> wrote: > > Did you pull it out? It runs fine for me when I run it *inside* lift's > examples. But what I was doing is making a copy of the JPADemo, renaming > everything, and then converting it into an app for myself. > > The pom.xml file in the JPADemo references the master Lift pom.xml in > the examples directory, so I had to change that. I swapped in one from a > previous standalone and it worked. > > Does this make sense? The clean pull from github works fine. It was my > pulled-out version that didn't. > > On drawback to having the JPADemo pom.xml rely on the Lift Examples > pom.xml is that other people will probably want to do what I've done. If > I knew anything about Maven, I'd try to set it up as an archetype, so I > could just use one to generate a blank JPA version of Lift (well, it > would be nice if it had some basic RBAC, examples of one-to-many and > many-to-many relationships, CRUD pages, etc. installed by default so I > could just change them to what I need). > > I'll try to find time to look at Maven this weekend and will see if I > can figure out how that could be done. (But this is a hell week for me, > so I don't know how far I'll get.) > > Chas. > > Derek Chen-Becker wrote: > > This is really, really strange, since what's in Git works fine for me > > here. Can you do me a favor and wipe your maven repository, re-pull from > > github, do a mvn clean and then see if it works? I just did that and it > > compiles (and runs) fine... > > > > Derek > > > > On Wed, Oct 8, 2008 at 1:05 AM, Charles F. Munat <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > > > I took a different pom.xml from an older version of the demo and > copied > > it in, changing the artifactId, etc. and it worked. Not sure which > line > > did it. Here's what I'm using: > > > > <?xml version="1.0" encoding="UTF-8"?> > > <project> > > <modelVersion>4.0.0</modelVersion> > > > > <groupId>org.myapp</groupId> > > <artifactId>myapp-master</artifactId> > > <version>0.10-SNAPSHOT</version> > > <description>myapp master project</description> > > <inceptionYear>2008</inceptionYear> > > <packaging>pom</packaging> > > > > <modules> > > <module>myapp-app</module> > > <module>myapp-per</module> > > </modules> > > > > <!-- Master properties (inherited by modules) --> > > <properties> > > <scala.version>2.7.1</scala.version> > > </properties> > > > > <repositories> > > <repository> > > <id>scala-tools.org <http://scala-tools.org></id> > > <name>Scala-Tools Maven2 Repository</name> > > <url>http://scala-tools.org/repo-releases</url> > > </repository> > > <repository> > > <id>scala-tools.org <http://scala-tools.org></id> > > <name>Scala-Tools Maven2 Repository</name> > > <url>http://scala-tools.org/repo-snapshots</url> > > </repository> > > </repositories> > > > > <pluginRepositories> > > <pluginRepository> > > <id>scala-tools.org <http://scala-tools.org></id> > > <name>Scala-Tools Maven2 Repository</name> > > <url>http://scala-tools.org/repo-releases</url> > > </pluginRepository> > > </pluginRepositories> > > > > <dependencies> > > <dependency> > > <groupId>org.scala-lang</groupId> > > <artifactId>scala-library</artifactId> > > <version>${scala.version}</version> > > </dependency> > > <dependency> > > <groupId>javax.servlet</groupId> > > <artifactId>servlet-api</artifactId> > > <version>2.5</version> > > <scope>provided</scope> > > </dependency> > > <dependency> > > <groupId>commons-codec</groupId> > > <artifactId>commons-codec</artifactId> > > <version>1.3</version> > > </dependency> > > <dependency> > > <groupId>commons-httpclient</groupId> > > <artifactId>commons-httpclient</artifactId> > > <version>3.0.1</version> > > </dependency> > > <dependency> > > <groupId>commons-collections</groupId> > > <artifactId>commons-collections</artifactId> > > <version>3.2</version> > > </dependency> > > <dependency> > > <groupId>com.rabbitmq</groupId> > > <artifactId>rabbitmq-client</artifactId> > > <version>1.2.0</version> > > </dependency> > > <dependency> > > <groupId>junit</groupId> > > <artifactId>junit</artifactId> > > <version>4.4</version> > > <scope>test</scope> > > </dependency> > > </dependencies> > > > > <build> > > <sourceDirectory>src/main/scala</sourceDirectory> > > <testSourceDirectory>src/test/scala</testSourceDirectory> > > <plugins> > > <plugin> > > <groupId>org.scala-tools</groupId> > > <artifactId>maven-scala-plugin</artifactId> > > <executions> > > <execution> > > <goals> > > <goal>compile</goal> > > <goal>testCompile</goal> > > </goals> > > </execution> > > </executions> > > <configuration> > > <scalaVersion>${scala.version}</scalaVersion> > > </configuration> > > </plugin> > > <plugin> > > <groupId>org.mortbay.jetty</groupId> > > <artifactId>maven-jetty-plugin</artifactId> > > <configuration> > > <contextPath>/</contextPath> > > <scanIntervalSeconds>0</scanIntervalSeconds> > > </configuration> > > </plugin> > > </plugins> > > </build> > > > > <reporting> > > <plugins> > > <plugin> > > <groupId>org.scala-tools</groupId> > > <artifactId>maven-scala-plugin</artifactId> > > <configuration> > > <scalaVersion>${scala.version}</scalaVersion> > > </configuration> > > </plugin> > > </plugins> > > </reporting> > > > > </project> > > > > > > Chas. > > > > Oliver wrote: > > > I'm getting the error too :( rotten boot > > > > > > On Wed, Oct 8, 2008 at 4:47 PM, Charles F. Munat <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]> > > > <mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>> wrote: > > > > > > > > > I figured this out (sort of). The problem was in the master > > pom.xml. Not > > > sure what it was, though. > > > > > > Chas. > > > > > > Charles F. Munat wrote: > > > > I seem to have lost my boot. > > > > > > > > I copied the JPADemo out of the liftweb source code and > > changed > > > the poms > > > > and everything else to make it the basis for a new app I'm > > trying > > > to get > > > > online this week. > > > > > > > > Everything compiles just fine, and the site works (sort > > of), but the > > > > Boot class fails to load. Here is the error: > > > > > > > > ERROR - Failed to Boot > > > > java.lang.ClassNotFoundException: bootstrap.liftweb.Boot > > > > at > > java.net.URLClassLoader$1.run(URLClassLoader.java:200) > > > > at > java.security.AccessController.doPrivileged(Native > > > Method) > > > > at > > > java.net.URLClassLoader.findClass(URLClassLoader.java:188) > > > > at > > java.lang.ClassLoader.loadClass(ClassLoader.java:316) > > > > ... > > > > > > > > Here's the stripped down Boot class: > > > > > > > > package bootstrap.liftweb > > > > > > > > import java.util.Locale > > > > > > > > import javax.servlet.http.HttpServletRequest > > > > > > > > import > net.liftweb.util.{Can,Empty,Full,LoanWrapper,LogBoot} > > > > import net.liftweb.http._ > > > > import net.liftweb.sitemap._ > > > > import net.liftweb.sitemap.Loc._ > > > > import org.wsbg.model._ > > > > import S.? > > > > > > > > class Boot { > > > > def boot { > > > > > > > > // where to search snippet > > > > LiftRules.addToPackages("org.myapp") > > > > > > > > } > > > > } > > > > > > > > Everything has been changed from com.foo.jpademo to > org.myapp > > > > appropriately. Where can I look to determine why Boot > > isn't found? > > > > > > > > Thanks, > > > > Chas. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
