New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 895133 link

Starred by 5 users
Status: Archived
Owner:
█ lushnikov@chromium.org
Last visit 28 days ago
Closed: Dec 8
Cc:
viswa.karala@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

DevTools Workspace persistence with context path

Reported by vince.ea...@gmail.com, Oct 14 
DevTools failed to link network resource to filesystem.

Platform: Windows
Chrome version: 69.0.3497.100 (Official Build) (64-bit)

What are the details of your project?
- Source code: plain html or javascript file
- Build System: eclipse runtime
- HTTP server: Jetty with context path
- Our application will ultimately be deployed as a war with a context path.  E.g. someApp.war will be hosted at http://server/someApp
- files like index.html will be visible to the browser as: http://server/someApp/index.html
- on the filesystem, index.html will be in a folder like [project]/war/index.html

Problems:
- adding [project]/war to the DevTools > Sources > Filesystem > workspace will not resolve when the client loads /someApp/index.html
- using symlinks to /fakeContextRootFolder/someApp(symlink-to-war-folder) does not work either

Comment 1 by vince.ea...@gmail.com, Oct 14 

Using hard links via this windows shell extension works:

http://schinagl.priv.at/nt/hardlinkshellext/linkshellextension.html

It would be much preferred to setup these mappings in Chrome DevTools rather than hard links on the file system.

Ideal features would be:
- map /contextPath to [project]/war
- map /contextPath/include to [otherProject]/folder

Comment 2 by viswa.karala@chromium.org, Oct 15

Cc: viswa.karala@chromium.org
Labels: Triaged-ET
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for filing the issue!

Assigning it to lushnikov@ from similar issues:  796368 ,  794965  and  796251 .

Thanks!

Comment 3 by vince.ea...@gmail.com, Oct 15 

I would be happy to make a sample project or provide any assistance if needed just let me know.

Comment 4 by lushnikov@chromium.org, Dec 8

Status: Archived (was: Assigned)
Workspaces 2.0 is imperfect and there's no feasible way to make it work for everybody. Archiving since we currently don't have resources to allocate towards improving Workspaces story.
►

Sign in to add a comment