Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with WAFileMetadataLibrary>>#deployFiles #735

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments
Closed

Problem with WAFileMetadataLibrary>>#deployFiles #735

GoogleCodeExporter opened this issue Mar 25, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

If the filepath of a WAFileLibraryResource object does not contain a path 
separator ('/') then the file is deployed in the wrong place.

For example the file mystyle.css in MyLib is exported to 
'MyLib/mystyle.css/mystyle.css'.

The correct location should be 'MyLib/mystyle.css'.

Seaside version 3.0.7 on Pharo 1.4

Original issue reported on code.google.com by [email protected] on 10 Aug 2012 at 2:51

@GoogleCodeExporter
Copy link
Author

Diego Lont is working on it at the sprint but doesn't have a Google account.

Original comment by [email protected] on 31 Aug 2012 at 12:11

  • Changed state: Started
  • Added labels: FileLibrary, Version-Seaside3.1
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Name: Seaside-Core-DiegoLont.776
Author: DiegoLont
Time: 31 August 2012, 2:41:42 pm
UUID: 093df74a-231e-46e3-9ff3-4f15da9dc8ab
Ancestors: Seaside-Core-pmm.775

Issue 735

Name: Seaside-Tests-Core-DiegoLont.260
Author: DiegoLont
Time: 31 August 2012, 2:45:27 pm
UUID: 1619fbc0-3f6f-4a9e-8466-1303c1dab0e6
Ancestors: Seaside-Tests-Core-pmm.259

Issue 735

Original comment by [email protected] on 31 Aug 2012 at 12:46

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant