Adrian Shum wrote:
Maybe let me elaborate on my situation: It is because there are some
time consuming source generation tasks in my POM. In case m2eclipse
invokes process-resources, those source generation will be triggered
and cause eclipse works slow. Those source generation can in fact
omitted in eclipse. Those generation is in fact defined in a profile
which will be activated when certain properties is not equals to
false. (That's why the way Igor suggesting is not what I want because
I am not finding way to define global properties)
I'd rather not make another profile to deactivate that source
generating profile, as it makes the POM harder to maintain.
In fact I tried to put -Dprop=value at the "Goals to invoke on
resource change" and it *seems* working (by comparing the time of
workspace building when I change certain resource file), but I am not
sure if it is the right way to do.
It is certainly is not the right way. Right now it is working
completely by coincidence and we won't guarantee that it will continue
working in the future.
I still believe the right way is to use profiles, even so they seem to
make pom.xml look bigger, but they also explicitly state the intent, as
opposed to guessing some arbitrary property values. Besides, this
profile can be defined in a parent pom, or even in settings.xml if you
don't want to put it into pom.xml
It may make sense to allow to specify global and per-project Maven
properties, just to match Maven CLI features, but that would require us
to provide separate UI for specifying those (more just a single entry
field) and would generally make configuration in the IDE more
complicated. We may consider that in the future, especially if you
submit an enhancement request and it will collect few votes.
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
