Jetty not reloading

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Jetty not reloading

Qbyte Consulting
I’m finding resources are not dynamically reloading. Jetty config below, what do I need to do?


<plugin>
                                <groupId>org.eclipse.jetty</groupId>
                                <artifactId>jetty-maven-plugin</artifactId>
                                <version>9.2.0.M0</version>
                                <configuration>
                                        <httpConnector>
                                                <port>9095</port>
                                        </httpConnector>
                                        <systemProperties>
                                                <systemProperty>
                                                        <name>tapestry.execution-mode</name>
                                                        <value>development</value>
                                                </systemProperty>
                                                <systemProperty>
                                                        <name>version</name>
                                                        <value>${project.version}</value>
                                                </systemProperty>
                                        </systemProperties>
                                </configuration>
                        </plugin>



Sent from my iPhone
---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Jetty not reloading

Dmitry Gusev
Hi!

Make sure you have tapestry.production-mode=true set in one of your
tapestry modules, or set in the system properties section in your pom.xml.

Execution mode only specifies a list of additional tapestry modules
(usually just one) for runtime configuration.

On Wed, Nov 28, 2018 at 6:12 AM Qbyte Consulting <[hidden email]>
wrote:

> I’m finding resources are not dynamically reloading. Jetty config below,
> what do I need to do?
>
>
> <plugin>
>                                 <groupId>org.eclipse.jetty</groupId>
>                                 <artifactId>jetty-maven-plugin</artifactId>
>                                 <version>9.2.0.M0</version>
>                                 <configuration>
>                                         <httpConnector>
>                                                 <port>9095</port>
>                                         </httpConnector>
>                                         <systemProperties>
>                                                 <systemProperty>
>
> <name>tapestry.execution-mode</name>
>
> <value>development</value>
>                                                 </systemProperty>
>                                                 <systemProperty>
>
> <name>version</name>
>
> <value>${project.version}</value>
>                                                 </systemProperty>
>                                         </systemProperties>
>                                 </configuration>
>                         </plugin>
>
>
>
> Sent from my iPhone
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Dmitry Gusev

AnjLab Team
http://anjlab.com
Reply | Threaded
Open this post in threaded view
|

Re: Jetty not reloading

Mats Andersson-2
Usually tapestry.production-mode is used to check for updates less often
so how can that help?

Maybe tapestry.file-check-interval is defined somewhere? Default is 1s
which should be enough in development. Also, make sure resources are
actually copied to the target directory when they are changed in the
souce. This is needed to make Tapestry aware of changes.


/Mats


On 2018-11-28 09:09, Dmitry Gusev wrote:

> Hi!
>
> Make sure you have tapestry.production-mode=true set in one of your
> tapestry modules, or set in the system properties section in your pom.xml.
>
> Execution mode only specifies a list of additional tapestry modules
> (usually just one) for runtime configuration.
>
> On Wed, Nov 28, 2018 at 6:12 AM Qbyte Consulting <[hidden email]>
> wrote:
>
>> I’m finding resources are not dynamically reloading. Jetty config below,
>> what do I need to do?
>>
>>
>> <plugin>
>>                                  <groupId>org.eclipse.jetty</groupId>
>>                                  <artifactId>jetty-maven-plugin</artifactId>
>>                                  <version>9.2.0.M0</version>
>>                                  <configuration>
>>                                          <httpConnector>
>>                                                  <port>9095</port>
>>                                          </httpConnector>
>>                                          <systemProperties>
>>                                                  <systemProperty>
>>
>> <name>tapestry.execution-mode</name>
>>
>> <value>development</value>
>>                                                  </systemProperty>
>>                                                  <systemProperty>
>>
>> <name>version</name>
>>
>> <value>${project.version}</value>
>>                                                  </systemProperty>
>>                                          </systemProperties>
>>                                  </configuration>
>>                          </plugin>
>>
>>
>>
>> Sent from my iPhone
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Jetty not reloading

Dmitry Gusev
Yeah, sorry, I wasn't clear, the tapestry.production-mode should be FALSE
in development mode.

On Wed, Nov 28, 2018 at 11:34 AM Mats Andersson <[hidden email]>
wrote:

> Usually tapestry.production-mode is used to check for updates less often
> so how can that help?
>
> Maybe tapestry.file-check-interval is defined somewhere? Default is 1s
> which should be enough in development. Also, make sure resources are
> actually copied to the target directory when they are changed in the
> souce. This is needed to make Tapestry aware of changes.
>
>
> /Mats
>
>
> On 2018-11-28 09:09, Dmitry Gusev wrote:
> > Hi!
> >
> > Make sure you have tapestry.production-mode=true set in one of your
> > tapestry modules, or set in the system properties section in your
> pom.xml.
> >
> > Execution mode only specifies a list of additional tapestry modules
> > (usually just one) for runtime configuration.
> >
> > On Wed, Nov 28, 2018 at 6:12 AM Qbyte Consulting <
> [hidden email]>
> > wrote:
> >
> >> I’m finding resources are not dynamically reloading. Jetty config below,
> >> what do I need to do?
> >>
> >>
> >> <plugin>
> >>                                  <groupId>org.eclipse.jetty</groupId>
> >>
> <artifactId>jetty-maven-plugin</artifactId>
> >>                                  <version>9.2.0.M0</version>
> >>                                  <configuration>
> >>                                          <httpConnector>
> >>                                                  <port>9095</port>
> >>                                          </httpConnector>
> >>                                          <systemProperties>
> >>                                                  <systemProperty>
> >>
> >> <name>tapestry.execution-mode</name>
> >>
> >> <value>development</value>
> >>                                                  </systemProperty>
> >>                                                  <systemProperty>
> >>
> >> <name>version</name>
> >>
> >> <value>${project.version}</value>
> >>                                                  </systemProperty>
> >>                                          </systemProperties>
> >>                                  </configuration>
> >>                          </plugin>
> >>
> >>
> >>
> >> Sent from my iPhone
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
Dmitry Gusev

AnjLab Team
http://anjlab.com
Reply | Threaded
Open this post in threaded view
|

Re: Jetty not reloading

Qbyte Consulting
In reply to this post by Mats Andersson-2
So it turns out IntelliJ doesn’t copy resources to the target folder. Gotta do a mvn compile.

Sent from my iPhone

> On 28 Nov 2018, at 15:34, Mats Andersson <[hidden email]> wrote:
>
> Usually tapestry.production-mode is used to check for updates less often so how can that help?
>
> Maybe tapestry.file-check-interval is defined somewhere? Default is 1s which should be enough in development. Also, make sure resources are actually copied to the target directory when they are changed in the souce. This is needed to make Tapestry aware of changes.
>
>
> /Mats
>
>
>> On 2018-11-28 09:09, Dmitry Gusev wrote:
>> Hi!
>>
>> Make sure you have tapestry.production-mode=true set in one of your
>> tapestry modules, or set in the system properties section in your pom.xml.
>>
>> Execution mode only specifies a list of additional tapestry modules
>> (usually just one) for runtime configuration.
>>
>> On Wed, Nov 28, 2018 at 6:12 AM Qbyte Consulting <[hidden email]>
>> wrote:
>>
>>> I’m finding resources are not dynamically reloading. Jetty config below,
>>> what do I need to do?
>>>
>>>
>>> <plugin>
>>>                                 <groupId>org.eclipse.jetty</groupId>
>>>                                 <artifactId>jetty-maven-plugin</artifactId>
>>>                                 <version>9.2.0.M0</version>
>>>                                 <configuration>
>>>                                         <httpConnector>
>>>                                                 <port>9095</port>
>>>                                         </httpConnector>
>>>                                         <systemProperties>
>>>                                                 <systemProperty>
>>>
>>> <name>tapestry.execution-mode</name>
>>>
>>> <value>development</value>
>>>                                                 </systemProperty>
>>>                                                 <systemProperty>
>>>
>>> <name>version</name>
>>>
>>> <value>${project.version}</value>
>>>                                                 </systemProperty>
>>>                                         </systemProperties>
>>>                                 </configuration>
>>>                         </plugin>
>>>
>>>
>>>
>>> Sent from my iPhone
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Jetty not reloading

Mats Andersson-2
It seems to be the same problem running the Jetty plugin in IntelliJ,
but a workaround if you edit the files inside IntelliJ is to

CTRL-s followed by CTRL-9

/Mats

On 2018-11-28 13:19, Qbyte Consulting wrote:

> So it turns out IntelliJ doesn’t copy resources to the target folder. Gotta do a mvn compile.
>
> Sent from my iPhone
>
>> On 28 Nov 2018, at 15:34, Mats Andersson <[hidden email]> wrote:
>>
>> Usually tapestry.production-mode is used to check for updates less often so how can that help?
>>
>> Maybe tapestry.file-check-interval is defined somewhere? Default is 1s which should be enough in development. Also, make sure resources are actually copied to the target directory when they are changed in the souce. This is needed to make Tapestry aware of changes.
>>
>>
>> /Mats
>>
>>
>>> On 2018-11-28 09:09, Dmitry Gusev wrote:
>>> Hi!
>>>
>>> Make sure you have tapestry.production-mode=true set in one of your
>>> tapestry modules, or set in the system properties section in your pom.xml.
>>>
>>> Execution mode only specifies a list of additional tapestry modules
>>> (usually just one) for runtime configuration.
>>>
>>> On Wed, Nov 28, 2018 at 6:12 AM Qbyte Consulting <[hidden email]>
>>> wrote:
>>>
>>>> I’m finding resources are not dynamically reloading. Jetty config below,
>>>> what do I need to do?
>>>>
>>>>
>>>> <plugin>
>>>>                                  <groupId>org.eclipse.jetty</groupId>
>>>>                                  <artifactId>jetty-maven-plugin</artifactId>
>>>>                                  <version>9.2.0.M0</version>
>>>>                                  <configuration>
>>>>                                          <httpConnector>
>>>>                                                  <port>9095</port>
>>>>                                          </httpConnector>
>>>>                                          <systemProperties>
>>>>                                                  <systemProperty>
>>>>
>>>> <name>tapestry.execution-mode</name>
>>>>
>>>> <value>development</value>
>>>>                                                  </systemProperty>
>>>>                                                  <systemProperty>
>>>>
>>>> <name>version</name>
>>>>
>>>> <value>${project.version}</value>
>>>>                                                  </systemProperty>
>>>>                                          </systemProperties>
>>>>                                  </configuration>
>>>>                          </plugin>
>>>>
>>>>
>>>>
>>>> Sent from my iPhone
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [hidden email]
>>>> For additional commands, e-mail: [hidden email]
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
--
---------------------- Mats Andersson | Ronsoft AB | +46(0)73 368 79 82