Hi all,

You should see a JRebel configuration screen now with more recent versions. You 
can get to it from the bottom of the Eclipse help menu. Checking the box for a 
project updates the .project file. The VM arguments are not added automatically 
and I didn’t realize they were still necessary either. Testing now!

thanks Ted,

David








On Aug 8, 2014, at 3:55 AM, Theodore Petrosky <[email protected]> wrote:

> That’s it!!!!
> 
> it seems that when you use the JRebel tab, and check the enable logging, the 
> plugin adds the -Drebel.log=true ${jrebel_args} line to the VM Arguments of 
> the launch parameters, and probably the stuff to the .project file.
> 
> Are you using the newest versions? Do you have the JRebel tab as indicated in 
> the wiki?
> 
> Thank you. Do you think this should be added to the wiki? I realize that this 
> is a real hack, but I don’t know any other way to get JRebel working.
> 
> Ted
> 
> 
> 
> On Aug 8, 2014, at 3:56 AM, Dev WO <[email protected]> wrote:
> 
>> Hi Ted,
>> 
>> I have this in my VM arguments:  -Drebel.log=true ${jrebel_args}
>> And also the JRebel framework referenced in my classpath
>> and finally in my .project file:
>>              <buildCommand>
>>                      <name>org.zeroturnaround.eclipse.rebelXmlBuilder</name>
>>                      <arguments>
>>                      </arguments>
>>              </buildCommand>
>>      <natures>
>> 
>>              <nature>org.zeroturnaround.eclipse.jrebelNature</nature>
>>      </natures>
>> 
>> Xavier
>> 
>> On 8 août 2014, at 02:24, Theodore Petrosky <[email protected]> wrote:
>> 
>>> so yes, I paid for the license. It is installed however, and from the wiki:
>>> 
>>> http://wiki.wocommunity.org/display/documentation/Using+JRebel+%28previously+called+JavaRebel%29+with+WOLips
>>> 
>>> there used to be a tab on the run configuration where you would “turn on” 
>>> the agent and logging. this went away a long time ago, but I found that if 
>>> I added a launch parameter in the VM arguments, I could get JRebel working.
>>> 
>>> My problem is that my computer died and I replaced it. I am trying to 
>>> upgrade to Eclipse 4 but the run configurations do not come across to the 
>>> new version. I was hoping to find the run configurations in the old 
>>> workspace and do a little hacking to get JRebel to work.
>>> 
>>> I am still hoping to find someone that is using JRebel that can help.
>>> 
>>> oye!!!??
>>> 
>>> thanks anyway.
>>> 
>>> Ted
>>> 
>>> 
>>> On Aug 7, 2014, at 8:01 PM, Raymond NANEON <[email protected]> wrote:
>>> 
>>>> I didn’t configure JRebel. To use it, You must to activate it.
>>>> WOLips 4.4 needs JRebel for his build, so I Installed it but I don’t use 
>>>> it because I haven’t the license.
>>>> 
>>>>> Le 8 août 2014 à 00:37, Theodore Petrosky <[email protected]> a écrit :
>>>>> 
>>>>> I have that version. How are you configuring it?
>>>>> 
>>>>> 
>>>>> 
>>>>> On Aug 7, 2014, at 6:32 PM, Raymond NANEON <[email protected]> wrote:
>>>>> 
>>>>>> JRebel and Jprofiler is 4.4.0 too after the built.
>>>>>> But if you want to use JRebel of Eclipse market, the version is 5.6.1.
>>>>>> 
>>>>>> Ray
>>>>>> 
>>>>>>> Le 7 août 2014 à 23:36, David Holt <[email protected]> a écrit :
>>>>>>> 
>>>>>>> What version of JRebel are you using?
>>>>>>> 
>>>>>>> David
>>>>>>> 
>>>>>>> 
>>>>>>> On Aug 7, 2014, at 2:14 PM, Theodore Petrosky <[email protected]> wrote:
>>>>>>> 
>>>>>>>> anyone have any experience with JRebel.
>>>>>>>> 
>>>>>>>> I was using it in the old version 3.X. however I always had to 
>>>>>>>> manually add a line to my launch configuration because the jrebel 
>>>>>>>> stuff wasn’t working. Basically, I was manually adding the JRebel 
>>>>>>>> agent logging.
>>>>>>>> 
>>>>>>>> First, does anyone know the correct way to add JRebel to a wonder 
>>>>>>>> launch configuration, or B, is anyone else using this? and know how to 
>>>>>>>> turn it on?
>>>>>>>> 
>>>>>>>> Maybe I could dig through some old files. Where are the run 
>>>>>>>> configuration stored? Maybe I can hack through that.
>>>>>>>> 
>>>>>>>> Ted
>>>>>>>> _______________________________________________
>>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com
>>>>>>>> 
>>>>>>>> This email sent to [email protected]
>>>>>>> 
>>>>>>> 
>>>>>>> _______________________________________________
>>>>>>> Do not post admin requests to the list. They will be ignored.
>>>>>>> Webobjects-dev mailing list      ([email protected])
>>>>>>> Help/Unsubscribe/Update your Subscription:
>>>>>>> https://lists.apple.com/mailman/options/webobjects-dev/rnaneon%40me.com
>>>>>>> 
>>>>>>> This email sent to [email protected]
>>>>>> 
>>>>> 
>>>> 
>>> 
>>> 
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list      ([email protected])
>>> Help/Unsubscribe/Update your Subscription:
>>> https://lists.apple.com/mailman/options/webobjects-dev/webobjects%40anazys.com
>>> 
>>> This email sent to [email protected]
>> 
> 
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/programmingosx%40mac.com
> 
> This email sent to [email protected]

 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to