I'm sure it's something simple, but I've been unable to find the fix.

I updated my build.properties file accordingly and made sure any dependency versions in pom.xml match those I have installed.

Of note:  springmvc runs just fine going through a similar process as I've tried here with csns2.

I'm getting the following errors:

org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Illegal repetition near index 28

^csns\.importer\.parser\.(?!${app.school})\..*$

Offending resource: ServletContext resource [/WEB-INF/applicationContext.xml]

java.lang.IllegalStateException: BeanFactory not initialized or already closed - call 'refresh' before accessing beans via the ApplicationContext

It kind of looks like applicationContext.xml doesn't like the dollar sign symbol to call property "app.school", which is set in build.properties.

Any help on getting this up and running so I can study for the midterm?  Thanks everyone.

Did a Project::Clean and Project::Build Automatically is checked.

Still getting the same error...

That didn't work either.

If I hardcode csula instead of the placeholder I can connect, but then I get a runtime error where the postgresql driver can't seem to see the value of the ${db.url} placeholder (i.e. java.sql.SQLException: Driver:org.postgresql.Driver@73cb3d0e returned null for URL:${db.url}).

My build.properties file is a sibling of pom.xml (I also tried it as a sibling of applicationContext but that didn't work) and as far as I can tell it has all of the properties set correctly.

Is there a plugin/import I'm missing that helps application context read these placeholders?

No sir, tried the Clean Eclipse WTP Project Work Directory and double-checked the name and location of build.properties to no avail.

Maybe it's a classpath issue?

You can also package the whole project directory in a zip file and email it to me. I'll have a look at it.

It sounds like Eclipse deployed the project but the resource filtering step in Maven build was not performed. Assuming you checked out the project as a Maven project and didn't change pom.xml, I'd check the .project file and see if the Maven builder is in there (see attachment).

There are some changes in pom.xml, but they are mostly version changes of some dependencies and plugins, which shouldn't cause much problem.

.project looks fine.

I did a "mvn package" and the build worked fine with the resource files properly filtered.

The only thing I notice was that you didn't change app.file.dir and app.log.dir. Since you are using a Mac which uses Unix path, this resulted a folder _E in your project folder. This may have affected the build process in some way. So set app.file.dir and app.log.dir to valid directories and try again.

So something was wrong when Eclipse running Maven build.

I'd delete the project and redo the checkout and configuration process from the beginning. After creating build.properties and doing a Maven -> Update Project, right click on the project and select Properties -> Builders and make sure that the Maven Project Builder is checked.

If it fails again, there's nothing else I can think of. You'll have to manually put the values in build.properties into various configuration files - check every file under src/main/resources, src/test/resources, and src/main/webapp/WEB-INF.

Got it working.

Installed the m2e-wtp connector.

Don't know why that was all it took, but it was.

cysun wrote:

m2e-wtp is included in the Eclipse Luna release. You are probably using an old version of Eclipse.

Oh I have. Haha. I usually can figure them out.

At least now I know why it's been such a pain.