Issue Details (XML | Word | Printable)

Key: APF-649
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Matt Raible
Reporter: wnqq
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
AppFuse

7 errors in eclipse for a webapp

Created: 15/Feb/07 05:30 AM   Updated: 30/Sep/08 02:45 PM   Resolved: 27/Feb/07 02:24 AM
Component/s: Installation
Affects Version/s: 2.0-M3
Fix Version/s: 2.0-M4

File Attachments: None
Image Attachments:

1. error1.JPG
(134 kB)

2. error2.JPG
(133 kB)

3. error5.JPG
(132 kB)

4. error7.JPG
(141 kB)

5. summary.JPG
(90 kB)
Environment:
appfuse 2.0M3
eclipse 3.2.1


 Description  « Hide
There are 7 errors when using eclipse for a webapp.

The major steps that I have done:

* mvn archetype:create -DarchetypeGroupId=org.appfuse -DarchetypeArtifactId=appfuse-modular-struts -DremoteRepositories=http://static.appfuse.org/repository -DarchetypeVersion=1.0-m3 -DgroupId=com.mycompany -DartifactId=myproject

* mvn integration-test

* take out all localized property files: *_zh*.properties

* mvn install:install-file -DgroupId=com.mycompany -DartifactId=myproject-core -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=target/myproject-core-1.0-SNAPSHOT.jar

* mvn war:inplace

* rm -r src/main/webapp/WEB-INF/lib
* rm src/main/webapp/WEB-INF/classes/struts.xml

* mvn install eclipse:eclipse

* import two projects (myproject-core and myproject-webapp) to eclipse

* Configure Maven2 (classpath variables: M2_REPO) for Eclipse

I will upload the screenshots for each of the 7 errors shortly.

Sort Order: Ascending order - Click to sort in descending order
wnqq added a comment - 15/Feb/07 05:31 AM
summary of 7 errors

Matt Raible added a comment - 15/Feb/07 06:18 AM
#1 is not fixable - it's an invalid error in Eclipse AFAICT.
#2 is probably fixable, but it's also an invalid error from Eclipse since the code works just fine.
#3 - this file is used in an entity include, another invalid error IMO.
#4 and 5 - we should be able to fix those.

Matt Raible added a comment - 27/Feb/07 02:24 AM
Fixed DWR comment issue. The <content> tag is not a valid tag, but it is for SiteMesh. Changing to <meta name="heading" content="<fmt:message key='foo'/>"/> will work, but then you end up with a <meta> tag in your <head> element. Here's an issue I filed for this a while back:

http://jira.opensymphony.com/browse/SIM-195

I don't know why there's an issue in dataAccessFailure.jsp. Changing the variable to ex2 turns the error into "there are two ex2 variables".

JSTL's expression language allows you to use double quotes and single quotes interchangeably (like JavaScript), so any warnings about that are invalid IMHO.