Web module build

To developers,

It is now possible to run the maven jetty plugin with the "run" goal
(instead of the "run-war" goal) in trunk, which means jetty will read
source code files directly instead of assembling everything into a WAR
and deploy it.

This implies that changes you do to velocity templates, javascripts,
css files etc take effect immediately and there is no need to restart
the jetty plugin.

In other words you can now execute:

mvn jetty:run

This should save some development time. The problem was related to the
war-type dependency we have on the dhis-web-commons-resources project.
Maven jetty plugin version 6.1.12.rc2 + handles the problem of
multiple web app resource directories automatically through the war
dependency mechanism. In order to have Velocity find templates I have
added a short velocity.properties file to each web project which
points a file resource loader to the dhis-web-commons-resources
project directory (the current directory is searched by default).

Lars

awesome…

I always missed doing this and it was time consuming to do run-war

Should it also be looking at the webapp folder for any other webapp that is in dependency??

···

Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2012/1/25 Lars Helge Øverland larshelge@gmail.com

To developers,

It is now possible to run the maven jetty plugin with the “run” goal

(instead of the “run-war” goal) in trunk, which means jetty will read

source code files directly instead of assembling everything into a WAR

and deploy it.

This implies that changes you do to velocity templates, javascripts,

css files etc take effect immediately and there is no need to restart

the jetty plugin.

In other words you can now execute:

mvn jetty:run

This should save some development time. The problem was related to the

war-type dependency we have on the dhis-web-commons-resources project.

Maven jetty plugin version 6.1.12.rc2 + handles the problem of

multiple web app resource directories automatically through the war

dependency mechanism. In order to have Velocity find templates I have

added a short velocity.properties file to each web project which

points a file resource loader to the dhis-web-commons-resources

project directory (the current directory is searched by default).

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Ignore my last question…

It works as expected… Nice!!

···

Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2012/1/25 Saptarshi Purkayastha sunbiz@gmail.com

awesome…
I always missed doing this and it was time consuming to do run-war

Should it also be looking at the webapp folder for any other webapp that is in dependency??


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2012/1/25 Lars Helge Øverland larshelge@gmail.com

To developers,

It is now possible to run the maven jetty plugin with the “run” goal

(instead of the “run-war” goal) in trunk, which means jetty will read

source code files directly instead of assembling everything into a WAR

and deploy it.

This implies that changes you do to velocity templates, javascripts,

css files etc take effect immediately and there is no need to restart

the jetty plugin.

In other words you can now execute:

mvn jetty:run

This should save some development time. The problem was related to the

war-type dependency we have on the dhis-web-commons-resources project.

Maven jetty plugin version 6.1.12.rc2 + handles the problem of

multiple web app resource directories automatically through the war

dependency mechanism. In order to have Velocity find templates I have

added a short velocity.properties file to each web project which

points a file resource loader to the dhis-web-commons-resources

project directory (the current directory is searched by default).

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

Will this be done for the 2.6 branch??

···

Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2012/1/25 Saptarshi Purkayastha sunbiz@gmail.com

Ignore my last question…
It works as expected… Nice!!


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2012/1/25 Saptarshi Purkayastha sunbiz@gmail.com

awesome…
I always missed doing this and it was time consuming to do run-war

Should it also be looking at the webapp folder for any other webapp that is in dependency??


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2012/1/25 Lars Helge Øverland larshelge@gmail.com

To developers,

It is now possible to run the maven jetty plugin with the “run” goal

(instead of the “run-war” goal) in trunk, which means jetty will read

source code files directly instead of assembling everything into a WAR

and deploy it.

This implies that changes you do to velocity templates, javascripts,

css files etc take effect immediately and there is no need to restart

the jetty plugin.

In other words you can now execute:

mvn jetty:run

This should save some development time. The problem was related to the

war-type dependency we have on the dhis-web-commons-resources project.

Maven jetty plugin version 6.1.12.rc2 + handles the problem of

multiple web app resource directories automatically through the war

dependency mechanism. In order to have Velocity find templates I have

added a short velocity.properties file to each web project which

points a file resource loader to the dhis-web-commons-resources

project directory (the current directory is searched by default).

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp

No immediate plans…

···

On Jan 27, 2012 3:13 AM, “Saptarshi Purkayastha” sunbiz@gmail.com wrote:

Will this be done for the 2.6 branch??


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2012/1/25 Saptarshi Purkayastha sunbiz@gmail.com

Ignore my last question…
It works as expected… Nice!!


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com

You Live by CHOICE, Not by CHANCE

2012/1/25 Saptarshi Purkayastha sunbiz@gmail.com

awesome…
I always missed doing this and it was time consuming to do run-war

Should it also be looking at the webapp folder for any other webapp that is in dependency??


Regards,
Saptarshi PURKAYASTHA

My Tech Blog: http://sunnytalkstech.blogspot.com
You Live by CHOICE, Not by CHANCE

2012/1/25 Lars Helge Øverland larshelge@gmail.com

To developers,

It is now possible to run the maven jetty plugin with the “run” goal

(instead of the “run-war” goal) in trunk, which means jetty will read

source code files directly instead of assembling everything into a WAR

and deploy it.

This implies that changes you do to velocity templates, javascripts,

css files etc take effect immediately and there is no need to restart

the jetty plugin.

In other words you can now execute:

mvn jetty:run

This should save some development time. The problem was related to the

war-type dependency we have on the dhis-web-commons-resources project.

Maven jetty plugin version 6.1.12.rc2 + handles the problem of

multiple web app resource directories automatically through the war

dependency mechanism. In order to have Velocity find templates I have

added a short velocity.properties file to each web project which

points a file resource loader to the dhis-web-commons-resources

project directory (the current directory is searched by default).

Lars


Mailing list: https://launchpad.net/~dhis2-devs

Post to : dhis2-devs@lists.launchpad.net

Unsubscribe : https://launchpad.net/~dhis2-devs

More help : https://help.launchpad.net/ListHelp