If you run appfuse:full-source on your project, it should get rid of
most of these errors.
Matt
On Aug 5, 2009, at 7:06 AM, pasta <pasta.bologn...@gmail.com> wrote:
waw.... how did u do it ?
I am using Eclipse Galileo, did a fresh install, a run, a mvn
eclipse:eclipse, imported the new project in eclipse.... but still
get a lot
of errors:
Description Resource Path Location Type
Fragment "/common/messages.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/
messages.jsp
default.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2/
decorators
line 27 JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/src/main/webapp/common/taglibs.jsp menu.jsp
/blablabla/src/main/webapp/common line 1 JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
403.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2
line 1 JSP
Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
404.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2
line 1 JSP
Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
clickstreams.jsp /blablabla/target/war/work/appfuse-web-
common-2.0.2/admin
line 1 JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
default.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2/
decorators
line 4 JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
footer.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2/
common line 1
JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
header.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2/
common line 1
JSP Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
index.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2
line 1 JSP
Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
login.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2
line 1 JSP
Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
logout.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2
line 1 JSP
Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
viewstream.jsp /blablabla/target/war/work/appfuse-web-
common-2.0.2/admin
line 1 JSP Problem
Invalid character constant header.jsp
/blablabla/target/blablabla-1.0-SNAPSHOT/common line 3 JSP
Problem
Invalid character constant header.jsp
/blablabla/target/war/work/appfuse-spring-2.0.2/common line 3
JSP Problem
Invalid character constant header.jsp
/blablabla/target/war/work/appfuse-web-common-2.0.2/common line
3 JSP
Problem
Invalid character constant header.jsp /blablabla/target/work/
webapp/common
line 3 JSP Problem
The markup in the document following the root element must be well-
formed.
login.xml /blablabla/src/test/resources line 2 XML Problem
Fragment "/common/taglibs.jsp" was not found at expected path
/blablabla/target/war/work/appfuse-web-common-2.0.2/common/taglibs.jsp
menu.jsp /blablabla/target/war/work/appfuse-web-common-2.0.2/
common line 1
JSP Problem
tibi wrote:
i have no errors with a fresh appfuse install and eclipse 3.4
only sometimes it complains about stuff in my target dir. i delete
those
problems and for a while all is fine.
tibi
Ice-Man wrote:
Oh, that's really! It's something really annoying, but I think
that's a matter o Eclipse-Ganymedi. See it - for instance: When we
have a Project in Eclipse3.2, with zero erros and we migrate to
3.4 so
a lot of boring erros (red crosses) appears, get it?!!
Ice-Man
2009/8/3 tibi <t...@dds.nl <mailto:t...@dds.nl>>
jsp interpreters can't handle a lot of links
so they think there are errors but there aren't
annoying but I don;t think appfuse can fix that
tibi
pasta wrote:
Hi All,
is there any plan to give a FULL eclipse support ?
by FULL I mean without red simbols in eclipse !... as actually
it has a lot
of those in the JSP pages
thanks
---
------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
<mailto:users-unsubscr...@appfuse.dev.java.net>
For additional commands, e-mail: users-h...@appfuse.dev.java.net
<mailto:users-h...@appfuse.dev.java.net>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
--
View this message in context:
http://www.nabble.com/full-support-for-eclipse---tp24789243s2369p24826581.html
Sent from the AppFuse - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@appfuse.dev.java.net
For additional commands, e-mail: users-h...@appfuse.dev.java.net
