I think this was intermittent issue that should be solved. I was doing some mentainence
work on few build agents
Where I also dropped local maven cache. Not sure how this permission issue could have
Btw brontes now has local nexus mirror to speed up building on clean local repositories.
You can configure to use it under maven build step settings. If not already configured.
From: Lincoln Baxter [mailto:firstname.lastname@example.org]
Sent: Tuesday, December 10, 2013 8:05 PM
To: Tomaz Cerar
Cc: Forge Dev List
Subject: Re: Forge Teamcity build linking
We have another question.
We've started seeing this error. Any ideas what this is about?
And a snippit for you:
12.pom (0 B at 0.0 KB/sec)
[13:38:57][org.jboss.forge.furnace.container:cdi] [main] WARN
org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to
write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-
parent/12/jboss-parent-12.pom.lastUpdated (Permission denied)
----- Original Message -----
From: "Tomaz Cerar" <tcerar(a)redhat.com>
To: "Lincoln Baxter" <lbaxter(a)redhat.com>
Sent: Monday, November 25, 2013 10:33:31 AM
Subject: RE: Forge Teamcity build linking
All you need to do is add dependencies under build configuration.
Ping me on IRC
> -----Original Message-----
> From: Lincoln Baxter [mailto:email@example.com]
> Sent: Friday, November 22, 2013 8:49 PM
> To: Tomaz Cerar
> Cc: George Gastaldi
> Subject: Forge Teamcity build linking
> Hey Tomaz,
> I have a question about Teamcity. We are experiencing new build failures
> (apparently due to the addition of a new build module "Furnace -
> How can we link the builds so that the Core - 2.0 build has access to the
> result artifacts of this build, like you did with the Furnace Runtime and
> Container CDI builds?
> I'm hoping we can learn enough to prevent the need for you to have to do
> this for us again in the future.
> Thanks very much!
> Lincoln Baxter, III
> JBoss, by Red Hat
> "If you want something, you'll find a way; if you don't, you'll