[Udo Held]

We have maven multi module projects.

Most of our modules are named after their artifactid so the project name in our pom.xml is:

<name>${project.artifactId}</name>

However this causes problems when checking out a project from subversion. The project will be named “${project.artifactId}” instead of the real project name. As the second module wants to create a new project with the same name the checkout will fail.

Maven itself handles such variable substitutions without problems.

Kind regards
clavis_uhe

[support-swapna]

clavis,

Sorry that you are seeing this issue with MyEclipse.I have escalated this issue to a dev team member. They will get back to you.

Can you clarify if you are working with MyEclipse Bling release 10 ?

[Udo Held]

Yes. We are using MyEclipse 10 Bling.

[support-tony]

clavis,

I’m sorry you’re seeing this issue. I’ve managed to replicate it and have raised a problem report. There is no easy workaround other than checking out projects individually and renaming before each checkout.

Apologies for the inconvenience.

[Udo Held]

Hi Tony,

thanks for you feedback. I already applied the mentioned work around. However I’d prefer using the variable in my poms in future again.

Kind regards
clavis_uhe

[support-tony]

Clavis,

Yes, you should be able to use variables and I hope we can get this fixed quickly. Sorry again for the inconvenience.

[Author]

Posts