Thanks for the input Jesse.  I hope to create a really good Tapestry
centered Maven FAQ of this stuff, so the maven related queries can go
there for answers.

On one attempt at using maven through eclipse, it was complaining
about not finding lib\tools.jar .  I was sure the JDK was chosen for
the installed JREs.  It turned out that the vm used by eclipse was
some other plan JRE (not a jdk).  So I had to specify this in the
eclipse.ini and in my shortcuts to eclipse: -vm
C:\Java\jdk1.5.0_06\bin\java.exe

So my full eclipse shortcut looked like:
C:\eclipse\WTP1.5.3\eclipse\eclipse.exe -vm
C:\Java\jdk1.5.0_06\bin\java.exe -vmargs -Xverify:none -Xms90m
-Xmx512m -XX:MaxPermSize=90m -XX:MaxNewSize=40m

Some notes on the older post by Borut, which is here:
http://mail-archives.apache.org/mod_mbox/maven-users/200608.mbox/[EMAIL 
PROTECTED]

In step 5, of the steps above, src/main/webapp/WEB-INF/lib did not exist.
Create webapp/WEB-INF/lib under src/main/

After selecting the tapestry library in the Add Dependency section of
the maven plugin in Eclipse, I got a notice like this in the Console
window:
5/11/07 2:04:57 PM EDT: [INFO]
NOTE: Maven is executing in offline mode. Any artifacts not already in
your local
repository will be inaccessible.

So I made sure the POM was saved and manually did a "mvn install" from
the project's directory.  This downloaded the dependencies with no
problem.  Not sure why it wouldn't download within eclipse, as you
would expect.



In my case, I am using Eclipse 3.2.2 (WTP1.5.3) and Java 5 (1.5)  For
some reason I was getting this error:
"Java compiler level does not match the version of the installed Java
project facet."

The project settings were being set to Java 1.4 compliance, and would
not stay at Java 5 compliance.  So I added this to my POM:

<build>
 <plugins>
   <plugin>
     <groupId>org.apache.maven.plugins</groupId>
     <artifactId>maven-compiler-plugin</artifactId>
     <version>2.0</version>
     <configuration>
       <source>1.5</source>
       <target>1.5</target>
     </configuration>
   </plugin>
 </plugins>
</build>

After doing Maven2->Update Source Folders, that problem went away.



Daniel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to