Re: Gradle eclipse task - classpath modification

Filed OFBIZ-11071 for the same. Best, Girish On Mon, May 27, 2019 at 1:21 AM Taher Alkhateeb wrote: > I see, sounds good. No harm in altering the exclusions. > > On Sun, May 26, 2019 at 10:01 PM Michael Brohl > wrote: > > > > Hi Taher, > > >

Re: Gradle eclipse task - classpath modification

I see, sounds good. No harm in altering the exclusions. On Sun, May 26, 2019 at 10:01 PM Michael Brohl wrote: > > Hi Taher, > > I find it extremely useful to start OFBiz from the IDE ;-) > > This way hot code replacement is supported which helps changing code at > runtime or while debugging. > >

Re: Gradle eclipse task - classpath modification

Hi Taher, I find it extremely useful to start OFBiz from the IDE ;-) This way hot code replacement is supported which helps changing code at runtime or while debugging. We add these two classpath entries by hand in Eclipse until now. I think there would be no problem to remove the two

Re: Gradle eclipse task - classpath modification

It might be more useful not to launch from the IDE. Instead run gradle "ofbizDebug" and hookup remotely with the debug port. This would maintain a consistent environment instead of being surprised (happened to me in the past). It would also make a consistent experience to development team

Re: Gradle eclipse task - classpath modification

So every IDE provides a shortcut (certain combination of keys) to execute any java file in a project as a java application, that in turn invokes *java *command on that class file. Eclipse applies all classpath entries (list of jar files from gradle dependency) as -classpath argument. Under the

Re: Gradle eclipse task - classpath modification

start how? what is the command? Are you trying to start _from_ eclipse. If yes why? On Sat, May 25, 2019 at 2:26 PM Girish Vasmatkar < girish.vasmat...@hotwaxsystems.com> wrote: > I realised Taher's reply after I had sent my response. > > Following's the command. > > *./gradlew eclipse* > > This

Re: Gradle eclipse task - classpath modification

I realised Taher's reply after I had sent my response. Following's the command. *./gradlew eclipse* This would do the job of setting up the eclipse workspace with all all gradle dependencies nicely set-up in the classpath. Then I would normally try to start OFBiz using Start.java. Not sure if

Re: Gradle eclipse task - classpath modification

There is a bit more to it ... When the system can't find cache.properties (as it's no more on the classpath), following happens - 1. Exception is thrown (which is obvious) 2. Code execution halts (which is fine), so no tomcat is launched. 3. Since execution stops, JVM should be terminated in my

Re: Gradle eclipse task - classpath modification

What is the exact command used to run? On Sat, May 25, 2019, 12:27 PM Girish Vasmatkar < girish.vasmat...@hotwaxsystems.com> wrote: > Hi Mathieu, > > With those entries missing from the classpath, you'd get the following > exceptions and warning - > > 1. For cache.properties (when

Re: Gradle eclipse task - classpath modification

Hi Mathieu, With those entries missing from the classpath, you'd get the following exceptions and warning - 1. For cache.properties (when /framework/base/config entry is missing) Exception in thread "main" java.lang.ExceptionInInitializerError at

Re: Gradle eclipse task - classpath modification

Hello Girish, Girish Vasmatkar writes: > When you run eclipse task it removes all unnecessary classpath entries > including the ones containing "config" and "dtd". This introduces a minor > inconvenience, in turn, because you do need two entries below in order for > OFBiz to start normally - >

Gradle eclipse task - classpath modification

Hi All When you run eclipse task it removes all unnecessary classpath entries including the ones containing "config" and "dtd". This introduces a minor inconvenience, in turn, because you do need two entries below in order for OFBiz to start normally - /framework/base/config /framework/base/dtd