http://stackoverflow.com/questions/22150209/maven-changes-the-order-of-plugins-of-different-profiles
https://issues.apache.org/jira/browse/MNG-2258
On April 25, 2017 at 22:33:58, Otto Fowler (ottobackwa...@gmail.com) wrote:
So, the copy resources configuration is still there, and not governed by
the profile.
Is it possible that since they both run in package, that they are out of
order?
On April 25, 2017 at 22:31:27, Otto Fowler (ottobackwa...@gmail.com) wrote:
Having said that, i see the problem.
I am very sorry
How do I go about resubmitting if I can fix it?
On April 25, 2017 at 22:29:56, Otto Fowler (ottobackwa...@gmail.com) wrote:
OK, I’ll take a look. Sorry - I thought they read out of the RPMS dir and
verified that they were produced both ways.
I am not sure how my change would change the target copy.
On April 25, 2017 at 22:25:04, Justin Leet (justinjl...@gmail.com) wrote:
The problem seems to be that full/quick dev rely on having the RPMs in the
/target folder
>From metron-deployment/roles/metron-rpms/defaults:
metron_rpm_glob: "{{ playbook_dir
}}/../packaging/docker/rpm-docker/target/RPMS/noarch/*.rpm"
However, that PR appears to no longer copy to the /target folder run as
expected, so quick and full dev are unable to find the RPMs.
On Tue, Apr 25, 2017 at 9:26 PM, Otto Fowler <ottobackwa...@gmail.com>
wrote:
> Ryan, did you see why it was not working?
>
>
> On April 25, 2017 at 18:17:29, Ryan Merriman (merrim...@gmail.com) wrote:
>
> A regression was introduced recently that breaks full dev. I've narrowed
> down the commit that introduced it and have submitted a PR to revert that
> commit: https://github.com/apache/incubator-metron/pull/549.
>
> Given there has been confusion recently over our deployment build process,
> I think it's appropriate that we discuss and come to a consensus and on
> how this should work.
>
> Ryan
>
