Hi all,
can you explain the role of buildProperties.xml file other than filter-*.properties?
Why should I use ant target as said in documentation pages other than maven commands to build and deploy project if I now it is mavenized?
Hi,
you could indeed use only maven commands (aside from the ant targets we use for an easy management of some tedious db-related tasks).
BTW, if you take a look at the buildTasks.xml where those targets are defined, you can see that a simple "ant WAR-build" is not a mere "mvn package".
It is a (Linux example):
export MAVEN_WORKING_MODE="production"; mvn -P !development-windows package -DskipTests
I personally find more comfortable to use a "ant WAR-build" for that :)
This applies also to other ant targets.
Their use it's optional, but very handy.
Can you give any advice on how to port webapp from entando 2.0.10 to 3.2.0?
That is a very long jump...
Your best bet would be creating a new portal from scratch, and then carefully adding a bit at a time, checking if everything is working as expected, if no --> fix it, if yes --> proceed further
Cheers,
William
--
William Ghelfi
Director of Research
entando Team
Direct: Italy +39 070 24 00 53
Twitter: @trumbitta | Skype: wiz_of_id | GitHub: trumbitta
Company: http://www.entando.com | Community: http://www.entando.org
Follow us! Twitter@entandosrl | Facebook/entando | Linkedin | Youtube