CONNECT ERROR: Unsupported resource type

[marvinosswald]

Doesn't have that Issue with an extension I've packed with Magento Builtin Packager once, but my new one I've never packed with the builtin tools...

But as part of my deploy pipe I delete the files created with Builtin tools.. so they shouldn't matter.

I've I try packaging it with builtin tools it works like charm... any idea ?

https://gist.github.com/marvinosswald/bcd7fb4acf968d3afe58

[astorm]

Um, I'm not sure what you're talking about in this new issue?

[marvinosswald]

ok, let me try to explain... If I pack the new extension with MagentoTarToConnect and try to install it with Magento Connect it says: CONNECT ERROR: Unsupported resource type

[astorm]

OK, can you ungzip and untar the extension, find the package manifest file (package.xml) and compare with with an extension that's working?

[marvinosswald]

Finally had time to look into it, it appears that MagentoTarToConnect outputs another contents structure.

I guess I'm messing something up in my new ci env, have to do further investigations.

MagentoTarToConnect:

    <contents>
      <target name="mage">
        <dir name="app">
          <dir name="code">
            <dir name="local">

            </dir>
          </dir>
          <dir name="etc">

          </dir>
        </dir>
        <dir name="lib">
          <dir name="H2ODev">

          </dir>
        </dir>
      </target>
    </contents>

Builtin:

    <contents>
      <target name="magelocal">

      <target name="mageetc">

      </target>
      <target name="magelib">

      </target>
    </contents>

EDIT:

getTagetMap() should translate the structure for Magento, shouldn't it ?
Only difference to my last CI is that now I'm using the php file instead of the phar as my ci couldn't handle it for some reasons...

[astorm]

@marvinosswald still a little confused here as to what, exactly, the issue you're having is. Can you remove the build system from the equation and try using the tar to connect script stand alone? Assuming that it works stand alone, compare your built archives. If it doesn't work stand alone, there may be a bug, or you may have uncovered a change in a recent version of Magento we need to be aware of.