OK, I am trying this now.
I was actually confused by the compile automatically option...
I didn't actually see the option as it is not in the normal "project options"
screen, it is in the menu by itself.
Which begs the question...
what if you wanted to build automatically for one project but not another...
I guess you can not.
I think it would make more sense to make it a check box on the window settings
screen, with then a separate override for each project individually.
>>> Eugene Kuleshov <[EMAIL PROTECTED]> 09/19/08 2:07 AM >>>
Andy,
This sound like you have "Build automatically" turned off in Eclipse.
If so, the behavior you describing is consistent.
If I am not mistaken, we deliberately disabled building project before
launching Maven because usually it is already built by JDT. I don't
think mode when "build automatically" is disabled had been heavily
tested with m2eclipse.
Also note that m2eclipse does not propagate error markers from the
failed Maven builds. We don't want to duplicate functionality that is
already provided by JDT. With incremental autobuild disabled number of
other features in JDT may not work correctly, e.g. code completion and
search, because Java model would get out of synk.
regards,
Eugene
Andy Dingfelder wrote:
> I am experiencing an issue where sometimes my builds work and sometimes they
> do not.
>
> One thing I am seeing is that if I introduce a compile error into my code,
> and then launch my maven build, the build does fail, after about 15 seconds,
> but the "problems" tab in eclipse does not list my error.
>
> If I right click my project in the package explorer and select "build
> project" the compile immediately shows up in the problem tab in < 1 second.
>
> Of a bigger worry to me is that if I run the project, it does not do a build
> first, so If I run my project and see it is working, and then I fire off my
> install tool to package up my deployment area, and forget to fire off the
> build manually first, the install is not the latest code as the build did not
> occur.
> Is there any way to make "run" do a build first, but only if any source code
> has changed?
>
> Of the biggest concern though, is that sometimes (but not always) if I do a
> build, the code in the generated jar does not seem to get updated.
> I know this is not enough information to go on, I am just asking first if
> anyone has experienced anything like this before?
> I will start digging more tomorrow to see if I can get to the cause.
>
> Thoughts?
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Please consider the environment before printing this email
WARNING: This email and any attachments may be confidential and/or privileged.
They are intended for the addressee only and are not to be read, used, copied or
disseminated by anyone receiving them in error. If you are not the intended
recipient,
please notify the sender by return email and delete this message and any
attachments.
The views expressed in this email are those of the sender and do not
necessarily reflect
the official views of SirTrack. see http://www.sirtrack.com
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
