Downgrade phing

[stevenrombauts]

The upgrade to version 3.x in #124 breaks on all our build scripts, failing to create the zip files. Only 2.* seems to work. Either leave it out and only install when needed or downgrade anyway.

[yiendos]

Confirmed as still a problem running on the new version of the box:

Will start to look into compatible versions of phing for the new box

[yiendos]

Note to self:

Still hitting problems creating an installable package from the leadman repo within the box. Thinking this might be permission problems. The other thing is that the installer complains about files being updated in the future:

Warning: uninstall.sql modified in the future (1557393411 > 1557393410)

Although the system date seems to be configured properly:

$ date
Thu May  9 09:19:38 UTC 2019

$ sh pack.sh
Buildfile: /home/vagrant/Projects/leadman/scripts/build/build.xml
 [property] Loading /home/vagrant/Projects/leadman/scripts/build/build.properties

LEADman > build:

   [delete] Deleting directory /home/vagrant/Projects/leadman/scripts/build/tmp
     [copy] Created 66 empty directories in /home/vagrant/Projects/leadman/scripts/build/tmp
     [copy] Copying 96 files to /home/vagrant/Projects/leadman/scripts/build/tmp
     [move] Moving 1 files to /home/vagrant/Projects/leadman/scripts/build/tmp
     [copy] Warning: uninstall.sql modified in the future (1557393411 > 1557393410)
     [copy] Warning: script.php modified in the future (1557393411 > 1557393410)
     [copy] Warning: install.sql modified in the future (1557393411 > 1557393410)
     [copy] Warning: helper.php modified in the future (1557393411 > 1557393410)
     [copy] Warning:  modified in the future (1557393411 > 1557393410)
     [copy] Created 1 empty directory in /home/vagrant/Projects/leadman/scripts/build/tmp/resources/install
     [copy] Copying 4 files to /home/vagrant/Projects/leadman/scripts/build/tmp/resources/install
     [echo] Cloning com_ckeditor
     [copy] Created 51 empty directories in /home/vagrant/Projects/leadman/scripts/build/tmp/extensions/ckeditor
     [copy] Copying 173 files to /home/vagrant/Projects/leadman/scripts/build/tmp/extensions/ckeditor
   [delete] Deleting directory /home/vagrant/Projects/leadman/scripts/build/tmp/ckeditor_clone
     [echo] Cloning updater

BUILD FAILED
/home/vagrant/Projects/leadman/scripts/build/build.xml:65:67: Directory /home/vagrant/Projects/leadman/scripts/build/tmp/updater_clone/code/plugins/system not found.

Total time: 10.3226 seconds

Buildfile: /home/vagrant/Projects/joomlatools-framework/build.xml
 [property] Loading /home/vagrant/Projects/joomlatools-framework/build.properties
 [property] Unable to find property file: /home/vagrant/Projects/joomlatools-framework/build.properties... skipped

Joomlatools Framework > clone:

   [delete] Deleting directory /home/vagrant/Projects/joomlatools-framework/tmp
     [echo] Cloning Joomlatools framework

Joomlatools Framework > add_components:

   [delete] Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/files to delete.
   [delete] Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/activities to delete.
   [delete] Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/scheduler to delete.
   [delete] Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/migrator to delete.
   [delete] Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/tags to delete.
   [delete] Directory /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/files/.git does not exist or is not a directory.
   [delete] Directory /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/activities/.git does not exist or is not a directory.
   [delete] Directory /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/scheduler/.git does not exist or is not a directory.
   [delete] Directory /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/migrator/.git does not exist or is not a directory.
   [delete] Directory /home/vagrant/Projects/joomlatools-framework/tmp/clone/code/libraries/joomlatools-components/tags/.git does not exist or is not a directory.

Joomlatools Framework > build:


BUILD FAILED
/home/vagrant/Projects/joomlatools-framework/build.xml:88:64: Could not find file /home/vagrant/Projects/joomlatools-framework/tmp/clone/LICENSE.txt to copy.

Total time: 10.0748 seconds

Cloning into '/home/vagrant/Projects/leadman/scripts/build/installer'...
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
mkdir: cannot create directory ‘/home/vagrant/Projects/leadman/scripts/build/installer/payload’: No such file or directory
cp: cannot create regular file '/home/vagrant/Projects/leadman/scripts/build/installer/payload/manifest.json': No such file or directory
unzip:  cannot find or open com_leadman.zip, com_leadman.zip.zip or com_leadman.zip.ZIP.
unzip:  cannot find or open joomlatools-framework.zip, joomlatools-framework.zip.zip or joomlatools-framework.zip.ZIP.

zip error: Nothing to do! (try: zip -q -r com_leadman_installer.zip . -i installer)

[yiendos]

Note to self

Add ssh keys to personal account after regenerating a new box, otherwise git stuff fails

[yiendos]

@stevenrombauts okie great, been able to generate a leadman package from within the box. In terms of the option to leave out phing altogether, I find it useful to generate packages from within the box because my local pear and phing is fubar.

Installing this package within a site created on the box the install goes fine and the component renders as expected.

[stevenrombauts]

@yiendos Oki, sounds good. We just need to make sure that we can downgrade and upgrade the Joomlatools Console. Last year Phing prevented Composer from upgrading the Console because of a version mismatch of a shared dependency.

[stevenrombauts]

See: joomlatools/joomlatools-console#86 (comment)

[yiendos]

@stevenrombauts Think this is working as expected. Provision the box so that you have phing at the correct version:

$ phing -v
Phing 2.16.1

Then downgrade the existing joomla console command 1.5.0:

cd ~/.composer

nano composer.json

composer update

Quit out of the vagrant box

exit 

vagrant reload

Expected result

You receive notification about the console being out of date

And the updated install of the console goes without hitch

[yiendos]

@stevenrombauts tested on a brand new install of the vagrant box, can upgrade the JT console and build JT packages via phing and sh pack.sh.

[stevenrombauts]

@yiendos Thanks! This can be merged into master then.