Is there something special I need to do to get this all setup? I downloaded JBDS 6.0.0.GA and the quickstarts version 2.2.0.ER2 and did not see this warning, however I saw errors, which are not mentioned here in this bug.

I spoke with Max on IRC. He said they have many issues like this and it's an overactive warning detector. It has nothing to do with the quickstart.

Added a JBIDE ticket https://issues.jboss.org/browse/JBIDE-13765

My understanding is that this happens when JBDS detects JPA module. However, this JPA module is not configured as there is no JPA connection defined.

It can be easily fixed via:

Properties/Validators/ [Uncheck] JPA validator

This can be a part of the example:

.settings/org.eclipse.wst.validation.prefs content:

vals/org.eclipse.jpt.jpa.core.jpaValidator/global=FF01

I didn't think we were shipping with a .settings file, are we?

Jason - we have falled back to ship .settings files for cases where it is the only way.

For this specific issue i'm most inclined to say this warning is expected since no connection is specified thus JPA validation cannot validate any mappings used in here.

What could be great is that we dont activate JPA on this project but not sure how we can do that reliably when JavaEE allow usage of JPA even without a persistence.xml ?

Would a maven property like <m2e.jpa.activation>false</m2e.jpa.activation>, disabling the m2e/jpa connector be useful?

If we could do it with a simple maven property like Fred is suggesting, that would work very well.

See upstream feature request in m2e-wtp : https://bugs.eclipse.org/bugs/show_bug.cgi?id=406824

I should be able to hack something in the next couple days.

Great, will that make it into the whichever version we're targeting for WFK?

It'll be available in JBDS 7.0.0.Beta1, hopefully. In JBDS 7.0.0.GA for sure.

Pull Request sent to the jboss-as-quickstarts with the new property (https://github.com/jboss-jdf/jboss-as-quickstart/pull/524)

Now it's in upstream.

Jason, does that really require that property? see my comment https://bugzilla.redhat.com/show_bug.cgi?id=919366#c3

It seems that JBDS 6.0.1 and 7.0.0.Beta1 works without this property correctly now.

Hm, okay then. I may have misunderstood the commit / fix that was done to JBDS. If things are working correctly w/o the property then not a problem.

@Marek S.: i can see that JBDS 7.0.0.Beta1 and 6.0.1.GA is fixed in this particular issue. Please verify my experience.

You *need* that property if you don't want to enable JPA Support automatically.

You can see the same results if you manually disable JPA configuration in the workspace preferences though (maven > java ee integration), but that would not be the default behavior.

Fred, I am confused now. Why JBDS 7.0.0.Beta1 is not showing that Warning without that property used?

Is window > preferences > maven > java ee integration > jpa configurator disabled?

If you create a new html5 project for instance, you'll see the warning.

Make sure you import (as maven) your project without any local eclipse settings file (./setting/, .classpath, .project)

No it is enabled, look at http://download.englab.brq.redhat.com/scratch/mnovotny/Screenshot%20from%202013-06-13%2010:27:33.png and I did remove .classpath, .project and .settings before I tried that and wrote comment https://bugzilla.redhat.com/show_bug.cgi?id=919361#c18

If I import the deltaspike-beanmanagerprovider from the master branch of https://github.com/jboss-jdf/jboss-as-quickstart/ in JBDS 7 Beta1, JPA Activation is not active, due to https://github.com/jboss-jdf/jboss-as-quickstart/commit/88d1a8f63662f7c1149a0c69848a176f8386af35 

If you remove the m2e.jpa.activation property and update project configuration, JPA is enabled and the warning shows up.

BTW, I had to switch to <version.jboss.bom>1.0.7.CR4</version.jboss.bom>, as CR3 is missing from https://repository.jboss.org/nexus/index.html#nexus-search;gav~org.jboss.bom~jboss-javaee-6.0-with-tools~~~~kw,versionexpand. Projects fail to build OOTB

Fred, even upstream is important to check, WFK productized quicstarts are at
http://download.devel.redhat.com/devel/candidates/JBWFK/2.3.0.ER1/jboss-wfk-quickstarts-2.3.0.ER1-dist.zip

So please check the issue on extracted zip. There is not any warning/error.

I did that on clean empty new workspace.

And versions I have are:
Version: 6.0.1.GA
Build id: GA-v20130327-2052-B361
Build date: 20130327-2052

and 

Version: 7.0.0.Beta1
Build id: Beta1-v20130529-0631-B257
Build date: 20130529-0631

I would add that I should change 
"There is not such warning" from my comment #24 on JBDS 6.0.1.GA.

There is a related warning, but not the reported warning:
No connection specified for project. No database-specific validation will be performed.

I don't have jboss-wfk-2.3.0.ER1-maven-repository.zip  installed -yet- so the project won't compile, but that's irrelevant as the JPA Configurator is only based on persistence.xml detection

The JPA Facet is installed automatically and I DO see a "No connection specified for project. No database-specific validation will be performed." warning when importing from jboss-wfk-quickstarts-2.3.0.ER1-dist.zip into JBDS 7.0.0.Beta1 (same build as you).

I believe you have gremlins in your computer ;-)

Well, I was referencing that 

Console configuration "jboss-as-deltaspike-beanmanagerprovider" does not exist.	jboss-as-deltaspike-beanmanagerprovider		line 0	JPA Problem

from this issue description is gone and now there is 

No connection specified for project. No database-specific validation will be performed.

And that is a different warning ;-) although the result of the warning may be the same, the message of warning is changed, isn't it? 

And it is true that if you have that property set up like <m2e.jpa.activation>false</m2e.jpa.activation>, you can import the project without warnings, but that needs to be in pom.xml before importing.
In already imported project the warning won't disapper.

Ok so we had a warning mismatch :-)

I never saw the "Console configuration "jboss-as-deltaspike-beanmanagerprovider" does not exist" warning, neither in JBDS 6 nor 7.

After a bit of googling it appears this is caused by the hibernate tooling : http://stackoverflow.com/questions/11425932/eclipse-dali-jpa-error-console-configuration-does-not-exist. I need to look more into it.

For the "No connection specified for project" to disappear, you need to remove the JPA Facet manually in the project properties and do a clean build.

fixed by cherry picked Jason's commit https://github.com/jboss-eap/quickstart/commit/010253cf8401c3a59fe4849d600824e76f66f2ed

Verified.
The quickstart does not show the "Console configuration [..] does not exist" warning anymore, but still does show, and so do several other quickstarts, the "No connection specified for project. No database-specific validation will be performed" warning. I will file another issue for that.

Removing doc text, the issue will be release noted as part of bug 982193.