[
https://issues.apache.org/jira/browse/JAMES-848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12637490#action_12637490
]
Bernd Fondermann commented on JAMES-848:
----------------------------------------
I can reproduce this.
The problem is that ${spring-deployment.target.lib.dir} on Windows contains
mixed slashes and backslashes like in
C:\my\working\dir\trunk\spring-deployment/target/james-server-spring-deployment-3.0-SNAPSHOT/
so <replace... > does not trigger (exe-classpath is all-backslashes) and this
lead to no relative paths at all.
The crippled paths are only a follow-up problem.
> run.bat and run.sh contain absolute entries to build path for runtime
> classpath
> -------------------------------------------------------------------------------
>
> Key: JAMES-848
> URL: https://issues.apache.org/jira/browse/JAMES-848
> Project: JAMES Server
> Issue Type: Bug
> Components: Deployment Modules
> Affects Versions: 3.0, Trunk
> Reporter: Stefano Bagnara
> Fix For: 3.0, Trunk
>
> Attachments: run.bat
>
>
> The run scripts will only work on the build machine until the build folder is
> there.
> The classpath should refer to the bundled lib folder, instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
