[ https://issues.apache.org/jira/browse/NPANDAY-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932941#action_12932941 ]
Luca Di Stefano commented on NPANDAY-345: ----------------------------------------- I prefer the solution on the addin than the workaround. If the add in will use / instead of \ will solve the issue. A related issue to this one is that in several npanday plugins there is the assumption that file separator is fix \ . In other places will be used the constant File.separator that makes the things even more complex. i.e. in the class DefaultCompiler, for to split the path tokens, uses the following code: String[] sourceTokens = includeSource.split(File.separator+File.separator); this will never work on both unix and windows fixing this issue. I think, for the whole npanday project, paths must be normalized defining a fix path separator and where possible using the class File instead String. This will make projects written on visualstudio portable to other platforms. > avoid use of backslash in pom.xml > --------------------------------- > > Key: NPANDAY-345 > URL: https://issues.apache.org/jira/browse/NPANDAY-345 > Project: NPanday > Issue Type: Bug > Components: Visual Studio Add-in > Affects Versions: 1.2.1 > Environment: linux > Reporter: Luca Di Stefano > Attachments: maven-compile-plugin_backslashfix-1.patch > > > if backslash is used in pom like here below > <includeSource>Form1.cs</includeSource> > <includeSource>Form1.Designer.cs</includeSource> > <includeSource>Program.cs</includeSource> > <includeSource>Properties\AssemblyInfo.cs</includeSource> > <includeSource>Properties\Resources.Designer.cs</includeSource> > it will work only on windows > using the slash will be compatible with all platforms > in this case the last 2 sources will be not compiled -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.