On 2017-01-30 17:29, Darran Lofthouse wrote:
On 30/01/17 15:36, Peter Palaga wrote:
> Hi Darran, inline...
> On 2017-01-26 13:56, Darran Lofthouse wrote:
>> What that means is that a file that can directly influence the outcome
>> of a local build is hidden from the engineer. There are already quite a
>> few things in out builds where when they go wrong we have to spend time
>> tracking them down, having a hidden configuration may not help this.
> If I heart this earlier, I'd most probably choose a non-hidden location.
> I perhaps do not see this as a problem, because I configure each of my
> Eclipse workspaces to show all .* resources because .mvn is not the only
> important file that is hidden: there is also .gitignore, .gitattributes,
> .travis.yml, .appveyor.yml and even .git and others that one wants to
> open from time to time.
> But now that srcdeps has some users, sorry, I do not think I find this
> important enough to break backwards compatibility.
But those files listed don't influence the local build.
Regarding backwards compatibility, what backwards compatibility are you
referring to as from what I understand the PRs into WildFly and WildFly
Core have not been merged yet.
srcdeps is used by other non-WF projects already and changing the
location where it looks for its configuration file would either break
those projects or require a migration. -- P