Attribute value "${alfresco.db.datasource.class}" of type NMTOKEN must be a name token. jetty-env.xml

[GoogleCodeExporter]

What steps will reproduce the problem?
1. create alfresco war project from catalog archetype
2. import into eclipse as existing maven project
3.

What is the expected output? What do you see instead?
no errors

What version of the product are you using? On what operating system?

The error
Attribute value "${alfresco.db.datasource.class}" of type NMTOKEN must be a 
name token. jetty-env.xml

is given on jetty/jetty-env.xml

any help with removing the error will be appreciated

Original issue reported on code.google.com by daniele....@gmail.com on 13 Feb 2012 at 8:34

[GoogleCodeExporter]

Hi Daniele,
any news on this issue? Have you tried to relax your eclipse xsd schema 
validations (at least for jetty-related configuration), if possible at all?
I'm not sure if Maven can help here, I'm afraid this issue is something you can 
only solve with Eclipse settings.

Will mark the issue as Enhancement and (hopefully soon) we will document a way 
in the wiki (or docs) to get rid of the annoying red mark.

Let me know your thoughts.
Thanks!

Original comment by mauri...@session.it on 4 Apr 2012 at 7:38

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi Maurizio,

apparently this is an issue with many maven projects and Eclipse.

I don't know if this should somewhat be handled by the maven eclipse plugin or 
by eclipse itself.

I can tell you what I did:
1. Eclipse Preferences
2. Validation
3. Scroll down to XML Validator
4. Click on the three dots button
5. Select Exclude Group
6. Click on Add Rule
7. Choose project Nature
8. Maven Nature - org.eclipse.m2e.core.maven2Nature

I don't like the workaround because Eclipse is not warning me anymore if I do 
not close an XML tag by mistake.
The syntax highlighter helps a little on that.
Autocompletion (if DTD/XSD has been set) still works.

Actually I could have completely ignored the message: I can compile from 
command line and I always do that actually.

Furthermore there are other errors that eclipse keeps popping up on the target/ 
directory even if I tell it that the folder is derived.

So I learned to live on with those errors, sometimes when I'm bothered by them 
I open the Markers view, select them all and right-click-delete them.
They go away until the next time Eclipse compile, I found no way to tell 
eclipse to remember I don't want it to show me those marks.

hopefully I've been helpful sharing my though.

Regards,
Daniele

Original comment by daniele....@gmail.com on 5 Apr 2012 at 8:47

[GoogleCodeExporter]

Reported your comments here - 
https://wiki.alfresco.com/wiki/Maven_For_Dummies#Eclipse

Marking issue as Won't fix, but we can definitely (in the future) open a new 
issue to improve integration with Eclipse.

Original comment by mauri...@session.it on 5 Apr 2012 at 3:38

• Changed state: WontFix

[GoogleCodeExporter]

Hi Maurizio,

I've ready the wiki.

Actually the validation issue is in the jetty xml with maven properties in it.
the pom.xml is fine. ;)

Original comment by daniele....@gmail.com on 6 Apr 2012 at 1:40

[GoogleCodeExporter]

You're right, fixed documentation. feel free to re-comment or directly adjust 
it (my English sometimes is not 100% correct :-)

Original comment by mauri...@session.it on 6 Apr 2012 at 1:46