Skip to content

Projeny validation fails when paths are involved #85

Open

Description

@decden

Hello

I am trying to configure a projeny project. I however always get a "Projeny validation failed" error when opening the generated project with unity.

I had a look at the validation function in the projeny.dll source code, and it seems to me like it expects everything in Assets/* and Assets/Plugins/* to be a junction. For me this is not the case since:

  • I use PluginsFolder: MyApp/MyPlugins in my ProjenyProject.yaml, causing the Assets/MyApp/MyPlugins folder to be created (which is not a junction)
  • I have dependencies of the form MyRepository/General/MyPlugin, which also cause the directory to appear at top level in Assets (again, not as junction).

Another detail which might be important is that I define the PackageFolders as '[ProjectRoot]/../../../'

At this point I am wondering why the project creation succeeded, but the validation failed. Am I using Projeny wrong, or is the validation not aligned to the directory layouts projeny can produce?

Thanks in advance for your help.

Activity

  1. changed the title [-]Projeny validation Fails when paths are involved[/-] [+]Projeny validation fails when paths are involved[/+] on Aug 14, 2018
  2. svermeulen commented on Aug 15, 2018

    @svermeulen
    Contributor

    Projeny was written with the assumption that the values given to PluginsFolder: and AssetsFolder: are package names and not paths. Which is why it assumes that all the junctions should be directly under Assets and Plugins

  3. decden commented on Aug 16, 2018

    @decden
    ContributorAuthor

    Thanks for the hints. I have restructured my project, so that I no longer use paths for PluginsFolder, AssetsFolder and Dependencies and the validation now succeeds.

    It would be nice though to get an error/warning during project creation instead.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions