Thanks! I've created https://issues.apache.org/jira/browse/ACE-500 for this issue
2014-12-04 16:55 GMT+01:00 Jan Willem Janssen <[email protected]> : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Bram, > > On 04/12/14 14:33, Bram Pouwelse wrote: > > No problem I was busy with other tasks anyway ;). See my comments > > inline below. > > See inline. > > >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > >>> > >>> Hi Bram, > >>> > >>> Sorry, totally overlooked your message. See my comments inline > >>> below. > >>> > >>> On 03/11/14 16:49, Bram Pouwelse wrote: > >>>>> I'm trying to figure out how to deploy configurations > >>>>> using Ace, a few old mailing list threads got me started. > >>>>> > >>>>> Yesterday I've tried to use the variable substitution > >>>>> using tags with the 2.0.1 release this didn't seem to work. > >>>>> But this seems to be fixed when using the latest version > >>>>> from svn. > >>>>> > >>>>> But when I update a tag value I get an exception on the > >>>>> target [1], after the failed deployment the target > >>>>> configuration is not updated. Is this a bug or am I > >>>>> missing something? > >>> > >>> I'm not sure you're missing something. Could you explain to be > >>> how you provision these configurations? Are these regular > >>> MetaType files that you provision along with an AutoConf > >>> resource processor? > >>> > > Provisioning configurations is new for me, now we're comfortable > > using Ace this is the next step. To get started I've picked the > > amdatu web demo project and added the bundles to Ace using the > > ContinousDeployer from the gogo shell in Ace. > > > > After that I've added a MetaType file to Ace using the Ace web ui > > and added the tag restpath with a value. I think I've added this > > tag on the distribution configuration but I'm not completely sure > > anymore. > > > > ... > > Looks find to me, if you also add the AutoConf resource processor from > Felix to your list of artifacts it should work. Not sure though about > the tags on both the distribution and target. > > That said, I've started investigating the code of the SnapshotCommand > from Felix DeploymentAdmin and found two rather severe issues (see > FELIX-4718 & FELIX-4719) one of which actually reproduces your > original issue. I've got a couple of fixes ready to be committed, once > the Apache SVN server comes back. After this we could try out a new > snapshot of the DeploymentAdmin in ACE to see whether it fixes all issues. > > Could you create an issue for the original stacktrace on the ACE JIRA > so we can relate this issue to the Felix ones? > > - -- > Met vriendelijke groeten | Kind regards > > Jan Willem Janssen | Software Architect > +31 631 765 814 > > /My world is revolving around INAETICS and Amdatu/ > > Luminis Technologies B.V. > Churchillplein 1 > 7314 BZ Apeldoorn > +31 88 586 46 00 > > http://www.luminis-technologies.com > http://www.luminis.eu > > KvK (CoC) 09 16 28 93 > BTW (VAT) NL8169.78.566.B.01 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > Comment: GPGTools - http://gpgtools.org > > iQIcBAEBAgAGBQJUgIPvAAoJEKF/mP2eHDc44EQP/0N2HU5U/sDlz7SDqYDG0hPs > t3+cXHZoD3fWaS2p0RMMlm9JQBxETtpoQOIfZsyoezPzihlmBVILb52T4WcJ8Ds+ > Ulr6SD+9ZDqmQb7GA2gFeh9GT1RlN3wOyjr8DMW/ZN65GmLGi9PIExVFNodW2xUQ > zECPnHdzydINWduWPC8Ge+TmViY0BmP5nssG/RNtfTn8k5uFjnh+gKFgkc2573fz > mVScr0499CDT5GTkJqEkAe8EzXVopOl2BI9881o7TcS+3aont0L3ettfzCqAQn/5 > a28AIO3mG2xgtX6h8Tfi6e6ttLGmJzlxYe6TSGHNusaCW/hben8oxVkSBEiyGgCd > 7tHCFEE8pTqwg7A0ttjMTg5cXall7Zi3mdtS2Q6dv2mrzq1kdXyuavlDRjKAuWNo > UDrGhOU9N3WQ2mFtFVNpLjmJUHvKE+pog10EZg+XeMIdn2+flTEvVeyKpODeqgam > gbYtJkWdnN8ptVbPrqTOj15Q2UYr27DfIUO6WU/8O1PnKfpGdcmTtE0mV/Pchf9Q > E0XpRrDC1bB8IhDsQfWbLUpqHFXHZLYElAi2ZK964zuS3bgqgjoKfBbWd3vZrGWN > 3SmyS5mt/K6whQF0uV37YMCnljyl4c4nayWXnVuNvtJc891OuU11ox0Y2ih/36t7 > aoZaASfpDXp46QcKKhLN > =2hNn > -----END PGP SIGNATURE----- >
