Re: Problem reading package.properties value when deploying application via wildfly-deploy plugin
Its not the problem of plugin, its plugin's default behavior to do the
deployment to data dir, the option targetDir is not for where to deploy
but from where to get deployable, bit confusing. As i mentioned, there is
no other issue with struts2 application except labels are not coming.
One more thing i have noticed is, if package.properties are packaged inside
war then only this issue is coming, if its packaged inside a jar then no
issues.
I have no idea if its a wildfly-plugin problem or struts2 is unable to
locate package.properties if deployed in wildfly data directory.
On Wed, Jul 29, 2015 at 2:07 PM, Lukasz Lenart lukaszlen...@apache.org
wrote:
2015-07-29 10:30 GMT+02:00 Sreekanth S. Nair
sreekanth.n...@egovernments.org:
package.properties file values are not getting displayed while we deploy
our application in wildfly server using wildfly deploy maven plugin, but
at
the same time properties values are getting displayed properly if we
deploy
from eclipse or manual deployment. The only difference between manual and
wildfly-deploy plugin is wildfly deploy plugin will add WAR or EAR to
{WILDFLY_HOME}/standalone/data folder where as manual or eclipse
deployment
will add WAR or EAR to {WILDFLY_HOME}/standalone/deployment folder. Any
insight ?
but that's an issue with the plugin not Struts itself. Maybe you have
wrong 'targetDir' set?
https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#targetDir
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
Problem reading package.properties value when deploying application via wildfly-deploy plugin
package.properties file values are not getting displayed while we deploy
our application in wildfly server using wildfly deploy maven plugin, but at
the same time properties values are getting displayed properly if we deploy
from eclipse or manual deployment. The only difference between manual and
wildfly-deploy plugin is wildfly deploy plugin will add WAR or EAR to
{WILDFLY_HOME}/standalone/data folder where as manual or eclipse deployment
will add WAR or EAR to {WILDFLY_HOME}/standalone/deployment folder. Any
insight ?
Thanks
Srikanth
Re: Problem reading package.properties value when deploying application via wildfly-deploy plugin
2015-07-29 10:30 GMT+02:00 Sreekanth S. Nair sreekanth.n...@egovernments.org:
package.properties file values are not getting displayed while we deploy
our application in wildfly server using wildfly deploy maven plugin, but at
the same time properties values are getting displayed properly if we deploy
from eclipse or manual deployment. The only difference between manual and
wildfly-deploy plugin is wildfly deploy plugin will add WAR or EAR to
{WILDFLY_HOME}/standalone/data folder where as manual or eclipse deployment
will add WAR or EAR to {WILDFLY_HOME}/standalone/deployment folder. Any
insight ?
but that's an issue with the plugin not Struts itself. Maybe you have
wrong 'targetDir' set?
https://docs.jboss.org/wildfly/plugins/maven/latest/deploy-mojo.html#targetDir
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
