Eclipse Community Forums: IAM (Eclipse Integration for Apache Maven)

Home » Archived » IAM (Eclipse Integration for Apache Maven) » Disable Dependecy Path Update

Disable Dependecy Path Update [message #515671]

Fri, 19 February 2010 12:33

Eclipse User

Is there a way to disable automatic Maven dependency path update like the way one can disable automatic build? If not, could you add this feature?

Ideally, this feature should work at workspace level as well as per-project level. A menu command to *manually* update dependecy path will also be needed.

ISSUES I AM RUNNING INTO:

1. Unnecessary path updates.

After exiting Eclipse with workspace in working condition and nothing is changed, reopening the workspace still triggers path update. My expectation is that if a project's pom.xml file hasn't been changed, dependency path should not be updated yet it's happening.

2. Unreasonably slow path updates.

If the workspace is reopened within a few hours, path updates is *usually* fast (not always though). If the workspace is reopened much later (during which backup might have happened), path update is really slow even though workspace is configured to run Maven *offline* and with source download *disabled*.

3. Sporratic WTP related errors.

Often times, just switching to Servers tab or synching a deployed webapp triggers Eclipse errors. Restarting Eclipse (and waiting for everything to build which could take as much as 20 minutes in dependency path update) usually fixes this. I do have IAM Webtools support plugin installed.

Re: Disable Dependecy Path Update [message #516126 is a reply to message #515671]

Mon, 22 February 2010 14:32

Eclipse User

When the workspace is closed the state is supposed to be saved and
should be faster. How many projects do you have opened and do you see
something weird/something that takes too long time in the Maven Events log?

On 2/19/10 9:33 AM, Don Park wrote:
> Is there a way to disable automatic Maven dependency path update like
> the way one can disable automatic build? If not, could you add this
> feature?
>
> Ideally, this feature should work at workspace level as well as
> per-project level. A menu command to *manually* update dependecy path
> will also be needed.
>
> ISSUES I AM RUNNING INTO:
>
> 1. Unnecessary path updates.
>
> After exiting Eclipse with workspace in working condition and nothing is
> changed, reopening the workspace still triggers path update. My
> expectation is that if a project's pom.xml file hasn't been changed,
> dependency path should not be updated yet it's happening.
>
> 2. Unreasonably slow path updates.
>
> If the workspace is reopened within a few hours, path updates is
> *usually* fast (not always though). If the workspace is reopened much
> later (during which backup might have happened), path update is really
> slow even though workspace is configured to run Maven *offline* and with
> source download *disabled*.
>
> 3. Sporratic WTP related errors.
>
> Often times, just switching to Servers tab or synching a deployed webapp
> triggers Eclipse errors. Restarting Eclipse (and waiting for everything
> to build which could take as much as 20 minutes in dependency path
> update) usually fixes this. I do have IAM Webtools support plugin
> installed.
>

Re: Disable Dependecy Path Update [message #517351 is a reply to message #516126]

Fri, 26 February 2010 22:51

Eclipse User

In one I have around 10 projects. In another, about 20. Behavior is same for both.

Nothing really noticeable except sporadic build failures and WTP related errors.

Re build, it appears that projects are not building in proper order despite having both Maven dependencies and Eclipse dependencies to determine proper build-order. Build failures are always class not found which indicate maven dependency path update either failed or there is some sort of race condition between IAM builder and Java builder. Cleaning or rebuilding failed projects will remove all the errors.

Re WTP related errors, I am hoping new Eclipse 3.5SR2 update will fix them. If not, only suspect remaining is IAM's Webtools support since my Eclipse env is stock J2EE Eclipse dist + IAM.

Update: Forgot to add that WTP related errors are usually preceded by "Initializing Java Tooling" failure on startup.

[Updated on: Fri, 26 February 2010 23:32] by Moderator

Re: Disable Dependecy Path Update [message #517716 is a reply to message #517351]

Mon, 01 March 2010 14:38

Eclipse User

what do you mean by "having both Maven dependencies and Eclipse
dependencies"
when you enable IAM then you should not add any eclipse dependency,
everything is handled from IAM. Coud be one of the reasons your builds
are not in order

On 2/26/10 7:51 PM, Don Park wrote:
> In one I have around 10 projects. In another, about 20. Behavior is same
> for both.
>
> Nothing really noticeable except sporadic build failures and WTP related
> errors.
> Re build, it appears that projects are not building in proper order
> despite having both Maven dependencies and Eclipse dependencies to
> determine proper build-order. Build failures are always class not found
> which indicate maven dependency path update either failed or there is
> some sort of race condition between IAM builder and Java builder.
> Cleaning or rebuilding failed projects will remove all the errors.
>
> Re WTP related errors, I am hoping new Eclipse 3.5SR2 update will fix
> them. If not, only suspect remaining is IAM's Webtools support since my
> Eclipse env is stock J2EE Eclipse dist + IAM.

Re: Disable Dependecy Path Update [message #518417 is a reply to message #517716]

Wed, 03 March 2010 23:06

Eclipse User

Sorry if my reference to Eclipse dependency caused confusion. By that I meant cross-project dependencies which were added to remove various warnings. Without J2EE Module Dependencies, for example, webapps didn't generate Maven projects it depended on via pom. Is this no longer necessary with latest version?

Re: Disable Dependecy Path Update [message #518703 is a reply to message #518417]

Thu, 04 March 2010 09:28

Eclipse User

IAM will automatically find your POM dependencies in the workspace and
setup the appropriate links between projects if they are present

The only thing I'm aware is not working yet is EAR project deployments.

On 3/3/10 8:06 PM, Don Park wrote:
> Sorry if my reference to Eclipse dependency caused confusion. By that I
> meant cross-project dependencies which were added to remove various
> warnings. Without J2EE Module Dependencies, for example, webapps didn't
> generate Maven projects it depended on via pom. Is this no longer
> necessary with latest version?
>

Re: Disable Dependecy Path Update [message #572371 is a reply to message #515671]

Mon, 22 February 2010 14:32

Eclipse User