We have another question.
We've started seeing this error. Any ideas what this is about?
And a snippit for you:
[org.jboss.forge.furnace.container:cdi] Downloaded: http://repo1.maven.org/maven2/org/jboss/jboss-parent/12/jboss-parent-12.pom (0 B at 0.0 KB/sec)
[org.jboss.forge.furnace.container:cdi] WARN org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-12.pom.lastUpdated
Original Message -
From: "Tomaz Cerar" <firstname.lastname@example.org>
To: "Lincoln Baxter" <email@example.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
From: Lincoln Baxter firstname.lastname@example.org
Sent: Friday, November 22, 2013 8:49 PM
To: Tomaz Cerar
Cc: George Gastaldi
Subject: Forge Teamcity build linking
I have a question about Teamcity. We are experiencing new build failures
(apparently due to the addition of a new build module "Furnace - Container
How can we link the builds so that the Core - 2.0 build has access to the build
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 find an excuse."
forge-dev mailing list