Thanks ! I've also contacted the javassist folks to have a look on your fix, so we can
use the latest javassist version instead of our own fork.
Best Regards
George Gastaldi
----- Original Message -----
From: "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com>
To: "forge-dev List" <forge-dev(a)lists.jboss.org>
Sent: Tuesday, May 14, 2013 2:17:37 AM
Subject: Re: [forge-dev] FORGE-897
Done.
---
Lincoln Baxter's Droid
http://ocpsoft.org
"Keep it Simple"
On May 14, 2013 1:13 AM, "Lincoln Baxter, III" < lincolnbaxter(a)gmail.com >
wrote:
Yep. I just forgot to release it from staging.
---
Lincoln Baxter's Droid
http://ocpsoft.org
"Keep it Simple"
On May 13, 2013 4:21 PM, < ggastald(a)redhat.com > wrote:
We just need to publish this atifact in the official maven repository, otherwise we'll
get a [ERROR] Failed to execute goal on project forge-proxy: Could not resolve
dependencies for project org.jboss.forge:forge-proxy:jar:2.0.0-SNAPSHOT: Could not find
artifact org.jboss.forge:forge-javassist:jar:1 in jboss-public-repository (
https://repository.jboss.org/nexus/content/groups/public/ ) -> [Help 1]
On 05/13/2013 04:20 PM, Lincoln Baxter, III wrote:
This issue has been resolved. Please verify that you do not get LinkageErrors in your
Eclipse Plugin Forge 2 runtime while creating new Forge Addon projects.
Steps to test are in the issue.
https://issues.jboss.org/browse/FORGE-897
Thanks!
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
George Gastaldi | Senior Software Engineer
JBoss Forge Team
Red Hat
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev