This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 175097 - Bad plugin installation implementation on nfs systems.
Summary: Bad plugin installation implementation on nfs systems.
Status: RESOLVED DUPLICATE of bug 166569
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: dlipin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-21 12:21 UTC by Michael Nazarov
Modified: 2009-10-26 20:27 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Nazarov 2009-10-21 12:21:31 UTC
As in last comment at previous issue 166254 was decided to open new one
instead of continue old this new was created.

Plugin installation on Solaris SPARC goes bad way again. First attemps
of plugin installation passed and silently skipped all downloaded modules
as described before. Second attempt failed with error about missing modules.
But finally I was able to install all plugins, I think because delay between
first download and last installation was longer then nfs time difference.

Well, I know SPARC platform seems to be not so popular as Windows and there
are no so many nfs bases confogurations with time problems so issue might
be just relnoted and downgraded to P2 as previous one. Actually I used P1
just to resolve this as faster as possible because of coming deadline.
Comment 1 Alexei Mokeev 2009-10-26 16:56:55 UTC
Could you please confirm:
Are the problems happening in case of significant time difference between NFS server and NetBeans execution host or is
it another problem ?

What it's the time difference between these 2 commands:
1. date
2. touch /some_nfs_dir/sample;ls --full-time  /some_nfs_dir/sample;rm /some_nfs_dir/sample
Comment 2 dlipin 2009-10-26 20:27:11 UTC
I guess that is the dup of another tracking issue.

*** This issue has been marked as a duplicate of 166569 ***