[floechen]

Hello,

I’m using Maven4MyEclipse in a multi-project environment. The Web project I’m deploying with the “Project Deployments” feature depends on two other projects. Both other projects contain a beanRefFactory.xml in the root of the classes directory, as required by Spring’s SingletonBeanFactoryLocator.

Hitting “Project Deployments” / “Redeploy” for an exploded archive, both beanRefFactory.xml files are deployed. In this process, the second one overwrites the first one. This is okay as long as I can define which one is overwritten, but I can’t! Until a few days ago, the overwriting didn’t produce an error (obviously the “correct” one was overwritten), but since this week the overwriting order has changed somehow, and I’m facing ugly Spring exceptions. I didn’t make any updates, my MyEclipse installation is exactly the same.

Is there a possibility to define the order in which dependent Maven projects are deployed using the “Project Deployments” feature? Or can I excluded a file from being deployed with this feature? Or is there another solution for my problem?

Thanx in advance
Florian

[support-eugene]

Unfortunately, there’s no way to explicitly define the order. Are you sure there’s no way to have only one such file?

I would guess that you might have changed the order of dependencies in pom.xml. Or you could have changed the layout graph – i.e. made one project depend on another.

[floechen]

Unfortunately, we must define our Spring beans per project and therefore need several different instances of beanRefFactory.xml.

I’ll fiddle around with the dependencies and the layout graph.

[Author]

Posts