~ is your "Home" folder (you know, where your Desktop, Documents and
similar folders live). What I don't know is where the repository is on
your system, so I don't know if that is set correctly.
HTH,
Nathan
yuccaplant wrote:
I did that over and over again, didn't help. In Eclipse Classpath
Damn, I should have known that. I'm working on a Mac. I replaced it by the
path to my home folder. Everything is working now (except for errors on the
jsp-syntax).
Thanks a lot,
Pieter
Michael Horwitz wrote:
>
> It does on Unix - it points to the current user's home directory. Not sure
> if i
It does on Unix - it points to the current user's home directory. Not sure
if it will work on a Windows box though. What could help is if you create a
settings.xml file for Maven and put it in the appropriate place:
http://maven.apache.org/settings.html. Make sure it points to your
repository usin
I did that over and over again, didn't help. In Eclipse Classpath Variables I
see that M2_REPO is pointing to a non existent location... . I think I set
it once manually because the command above didn't work. I set it to
"~/.m2/repository" which obviously is wrong. Does the '~' has a special
meani
Looks like mvn -Declipse.workspace=
eclipse:add-maven-repo did not work? Perhaps you could try running it again.
Mike.
On 3/14/07, yuccaplant <[EMAIL PROTECTED]> wrote:
Sorry for the delayed answer, I'm not sure I understand what you both
mean.
The import cannot be resolved for:
javax.servl
Sorry for the delayed answer, I'm not sure I understand what you both mean.
The import cannot be resolved for:
javax.servlet
org.acegisecurity
com.opensymphony.clickstream
These imports are all situated in .jps's.
One of the missing resources where Eclipse barfs at is (com.opensymphony.
...
It does sound about right. There is still an outstanding issue with the
Eclipse project plugin, but this should not affect AppFuse end users who
simply depend on AppFuse jar files. I would suggest a check of the list of
libraries in the Eclipse project to see if the required ones are present to
sa
These errors are likely because Eclipse isn't reading the dependencies
from the WARs (using the warpath plugin). Does that sound right Mike?
A lot of the JSP errors that Eclipse reports are invalid, but it
sounds to me like it's barfing on imports.
Matt
On 3/12/07, yuccaplant <[EMAIL PROTECTED
Yes I did that (checked it again). Afterwards I did it the first time, there
were a lot of import errors gone. In fact Eclipse doesn't give
import-errors, but as far as I can see the errors are the result of missing
resources. If I go to preferences -> Java builth path, Eclipse gives a
warning: 57
Have you set up your Maven repository for use with Eclipse by running mvn -
Declipse.workspace= eclipse:add-maven-repo? You can find
details here: http://www.appfuse.org/display/APF/Eclipse or here
http://maven.apache.org/plugins/maven-eclipse-plugin/usage.html
Mike.
On 3/12/07, yuccaplant <[EM
I'm trying to start a simple struts2 project with appfuse, follow the
instructions on the Wiki. In console everything goes fine, no building
errors. I use Eclipse as my IDE, but when I import the project (after mvn
eclipse:eclipse), I get a bunch of building errors:
Clickstream cannot be resolved
11 matches
Mail list logo
