In Maven 3, they're going to be called pom-poms On Tue, Dec 30, 2008 at 8:31 AM, Charles F. Munat <[email protected]> wrote:
> > Here's what's in the master (below the groupId, etc): > > > <!-- Master properties (inherited by modules) --> > <properties> > <scala.version>2.7.2</scala.version> > </properties> > > <repositories> > <repository> > <id>scala-tools.org</id> > <name>Scala-Tools Maven2 Repository</name> > <url>http://scala-tools.org/repo-releases</url> > </repository> > <repository> > <id>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</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>com.petebevin.markdown</groupId> > <artifactId>markdownj</artifactId> > <version>0.3.0</version> > </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> > <dependency> > <groupId>javax.activation</groupId> > <artifactId>activation</artifactId> > <version>1.1</version> > </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> > <sIntervalSeconds>0</sIntervalSeconds> > </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> > > Then the webapp has this: > > <dependencies> > <dependency> > <groupId>org.mortbay.jetty</groupId> > <artifactId>jetty</artifactId> > <version>(6.1,]</version> > <scope>test</scope> > </dependency> > <dependency> > <groupId>javax.servlet</groupId> > <artifactId>servlet-api</artifactId> > <version>2.5</version> > <scope>provided</scope> > </dependency> > <dependency> > <groupId>net.liftweb</groupId> > <artifactId>lift-webkit</artifactId> > <version>0.10-SNAPSHOT</version> > </dependency> > <!-- for LiftConsole --> > <dependency> > <groupId>org.scala-lang</groupId> > <artifactId>scala-compiler</artifactId> > <version>${scala.version}</version> > <scope>test</scope> > </dependency> > <dependency> > <groupId>${pom.groupId}</groupId> > <artifactId>tales-per</artifactId> > <version>${pom.version}</version> > </dependency> > </dependencies> > > <build> > <plugins> > <plugin> > <groupId>org.mortbay.jetty</groupId> > <artifactId>maven-jetty-plugin</artifactId> > <configuration> > <contextPath>/</contextPath> > <sIntervalSeconds>5</sIntervalSeconds> > <connectors> > <connector > implementation="org.mortbay.jetty.nio.SelectChannelConnector"> > <port>9889</port> > <maxIdleTime>60000</maxIdleTime> > </connector> > </connectors> > </configuration> > </plugin> > <plugin> > <groupId>net.sf.alchim</groupId> > <artifactId>yuicompressor-maven-plugin</artifactId> > <executions> > <execution> > <goals> > <goal>compress</goal> > </goals> > </execution> > </executions> > <configuration> > <nosuffix>true</nosuffix> > </configuration> > </plugin> > <plugin> > > <artifactId>maven-surefire-plugin</artifactId> > <configuration> > <redirectTestOutputToFile>true</redirectTestOutputToFile> > </configuration> > </plugin> > </plugins> > </build> > > And the persistence project has this; > > <dependencies> > <dependency> > <groupId>geronimo-spec</groupId> > <artifactId>geronimo-spec-ejb</artifactId> > <version>2.1-rc4</version> > </dependency> > <dependency> > <groupId>org.hibernate</groupId> > <artifactId>hibernate-entitymanager</artifactId> > <version>3.3.1.ga</version> > <exclusions> > <exclusion> > <groupId>javax.transaction</groupId> > <artifactId>jta</artifactId> > </exclusion> > </exclusions> > </dependency> > <dependency> > <groupId>geronimo-spec</groupId> > <artifactId>geronimo-spec-jta</artifactId> > <version>1.0.1B-rc4</version> > <scope>provided</scope> > </dependency> > <dependency> > <groupId>postgresql</groupId> > <artifactId>postgresql</artifactId> > <version>[8.1-404.jdbc3,)</version> > </dependency> > </dependencies> > > <build> > <plugins> > <plugin> > <artifactId>maven-surefire-plugin</artifactId> > <configuration> > <redirectTestOutputToFile>true</redirectTestOutputToFile> > </configuration> > </plugin> > </plugins> > </build> > > > Josh Suereth wrote: > > Chas, > > > > Please send your poms. > > > > Note: > > Wiping the maven repo is the CTRL-ALT-DEL windows-style fix for > maven. > > You just delete the Lift directory (as long as you get the > meta-data > > poms associated with it) you should be ok. Once again, this > is more of > > a hack, than a fix. If you're in a jam, just do it. If > not, it's > > usually better to figure out why it's bombing so you not > run into > > the problem again. > > > > Also remember that if you"mvn install" something it goes into > your local > > repo. The mvn -U command tells maven to check the remote > repositories > > for newer versions /than the ones found in your local > repository/ (i.e. > > if you install locally, you will automatically use that version > and the > > -U will not do anything useful). > > > > > > > > One side note, please make sure you're not using ${pom.version} > in > > dependencies with snapshot pom versions... (see here: > > http://jira.codehaus.org/browse/MNG-2796 ) > > > > > > Cheers, > > -Josh > > > > On Mon, Dec 29, 2008 at 7:12 PM, Charles F. Munat < > [email protected] > > <mailto:[email protected]>> wrote: > > > > > > Is it necessary to wipe the whole repo, or just > net/liftweb? It seems a > > big pain to keep re-downloading everything every week or > so. > > > > Thanks for the help. I ended up downloading a clean > copy of lift and > > then running mvn install, which installed everything > nicely. So now, > > will it update itself when I run mvn with the -u > flag, or will I need to > > reinstall lift manually after each update? Maybe that's > the problem... > > > > Is this the way it's supposed to work, or is something > a bit broken with > > Maven? > > > > Thanks! > > > > Chas. > > > > Derek Chen-Becker wrote: > > > It should be able to pull lift-webkit from the > repos. I'm > > guessing you > > > already have, but just as a sanity check did you > wipe your maven > > repo? > > > > > > Derek > > > > > > On Mon, Dec 29, 2008 at 3:24 PM, Charles F. Munat > <[email protected] > > <mailto:[email protected]> > > > <mailto:[email protected] <mailto:[email protected]>>> wrote: > > > > > > > > > I am using the JPA demo as my basis and > have tried to change the > > > included pom.xml from one that inherits from > the main lift > > pom.xml to a > > > standalone pom.xml, but I am missing > something because I > > continue to get > > > the error below. anyone post a copy of a > good standalone > > pom.xml (or > > > all three) from a JPA/Lift site? Thanks! > > > > > > Failed to resolve artifact. > > > > > > Missing: > > > ---------- > > > 1) net.liftweb:lift-webkit:jar:0.10-SNAPSHOT > > > > > > Try downloading the file manually from > the project website. > > > > > > Then, install it using the command: > > > mvn install:install-file > -DgroupId=net.liftweb > > > -DartifactId=lift-webkit -Dversion=0.10-SNAPSHOT > -Dpackaging=jar > > > -Dfile=/path/to/file > > > > > > Alternatively, if you host your own > repository you > > deploy the > > > file there: > > > mvn deploy:deploy-file > -DgroupId=net.liftweb > > > -DartifactId=lift-webkit -Dversion=0.10-SNAPSHOT > -Dpackaging=jar > > > -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > > > > > > Path to dependency: > > > 1) > com.xxx:yyy-app:war:0.10-SNAPSHOT > > > 2) > net.liftweb:lift-webkit:jar:0.10-SNAPSHOT > > > > > > ---------- > > > 1 required artifact is missing. > > > > > > Chas. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- Viktor Klang Senior Systems Analyst --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
