
| Key: |
WOL-979
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Kieran Kelleher
|
| Votes: |
4
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
File Attachments:
|
None
|
|
Image Attachments:
|
|
|
|
CURRENTLY is this for new WebObjects and Wonder applications:
<woapplication name="${build.app.name}" frameworksBaseURL="/WebObjects/${project.name}.woa/Frameworks"
SHOULD BE THIS:
<woapplication name="${build.app.name}" frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks"
project.name needs to be replaced with build.app.name, otherwise a custom build.app.name that is different to project.name will result in a non-working frameworksBaseURL that does not correspond to the custom name that applies to the woa bundle (both app and split bundles have the desired custom bundle name)
|
|
Description
|
CURRENTLY is this for new WebObjects and Wonder applications:
<woapplication name="${build.app.name}" frameworksBaseURL="/WebObjects/${project.name}.woa/Frameworks"
SHOULD BE THIS:
<woapplication name="${build.app.name}" frameworksBaseURL="/WebObjects/${build.app.name}.woa/Frameworks"
project.name needs to be replaced with build.app.name, otherwise a custom build.app.name that is different to project.name will result in a non-working frameworksBaseURL that does not correspond to the custom name that applies to the woa bundle (both app and split bundles have the desired custom bundle name) |
Show » |
|
There are no comments yet on this issue.
|
| |
|
|