Hi Philipp,
I'm not used to the mvn mechanism and I don't know if you use eclipse
but when do we have to use this mvn command exactly.
It is before to do the mvn eclipse:eclipse or after.
Thanks,
CAPITAINE Harold
Philipp Bracher a écrit :
I do call mvn resources:resources to ensure that I don't have any
${project.version} in the descriptors.
This works nice and no support of ${project.version} is needed at all.
Philipp Bracher
The ${project.version} handling does not work. As mentioned by Harold
in MAGNOLIA-1676, it couldnt' parsed back, so you couldn't restart
Magnolia. I fixed this, but now you have to "update" such modules on
each restart, and I'm really unsure how to handle the whole thing.
Should not update occur at all for modules which are of version
"${project.version}" ? I'd be in favor of dropping the support for
this, and have people plug the resource maven phase in their eclipse
builds. (so that the update mech knows what to do with that version)
WDYT ?
g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
