Jira (PUP-2839) Puppet 3.6.x future parser introduces dependency cycles

[Andy Parker (JIRA)]

Title: Message Title

Andy Parker commented on an issue   Re: Puppet 3.6.x future parser introduces dependency cycles I think what is happening here is that somehow that change has caused (See https://github.com/fadenb/puppet_futureparser_depency_cycle_bug/blob/master/modules/component/manifests/example.pp) anchor { 'component::example::begin': } -> class { '::example': } -> anchor { 'component::example::end': } to end up referring to Class component::example instead of ::example. Add Comment   Puppet / PUP-2839 Puppet 3.6.x future parser introduces dependency cycles In Puppet 3.6.0 the future parsers behavior changed resulting in dependency cycles with the 3.6.x version. I put some code illustrating the changed behavior into a repository: https://github.com/fadenb/puppet_futureparser_depency_cycle_bug Puppet 3.5.1 (everything working as expected): {code} puppet apply --graph --modulepath /vagrant/modules/ --... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.