You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@esme.apache.org by Ethan Jewett <es...@gmail.com> on 2010/10/30 13:33:35 UTC
Build broken for me - anyone else?
When I try to build locally I'm getting an error message:
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Unable to get dependency information: Unable to read local copy of metadata:
Cannot read metadata from
'/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
start tag not allowed in epilog but got h (position: END_TAG seen
<style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
org.slf4j:slf4j-api:jar:null
from the specified remote repositories:
scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
scala-tools.org (http://scala-tools.org/repo-releases),
central (http://repo1.maven.org/maven2),
scala-tools.releases (http://scala-tools.org/repo-releases),
compass-project.org (http://repo.compass-project.org),
Apache Repo (http://people.apache.org/repo/m1-ibiblio-rsync-repository),
Base (http://repo2.maven.org/maven2/),
Configgy (http://www.lag.net/repo),
scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
Path to dependency:
1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
2) net.liftweb:lift-util:jar:2.0
3) net.liftweb:lift-actor:jar:2.0
4) net.liftweb:lift-common:jar:2.0
I've tried fiddling with different versions of the slf4j-api in the POM.xml
and it doesn't seem to have an affect. Is this happening to anyone else or
just me? Suggestions?
Ethan
Re: Build broken for me - anyone else?
Posted by Ethan Jewett <es...@gmail.com>.
Ok, thanks! I think that puts me back in business. Will run through the
tests and then commit the pom with that repository, assuming it works.
Ethan
On Wed, Nov 3, 2010 at 12:32 PM, Richard Hirsch <hi...@gmail.com>wrote:
> Found it!!
>
> http://maven.twttr.com/com/twitter/
>
> http://maven.twttr.com/com/twitter/xrayspecs/
>
> On Wed, Nov 3, 2010 at 12:29 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> > Lag.net is associated with http://robey.lag.net/ - twitter developer
> >
> > Appears that there are a variety of things missing from the site -
> > http://www.lag.net/robey/key
> >
> > D.
> >
> > On Wed, Nov 3, 2010 at 12:23 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> >> The problem is that repository at http://www.lag.net/nest is down -
> >> that is where it is usually located.
> >>
> >> Trying to find it somewhere else.
> >>
> >> D.
> >>
> >> On Wed, Nov 3, 2010 at 12:17 PM, Ethan Jewett <es...@gmail.com>
> wrote:
> >>> xrayspecs
> >>
> >
>
Re: Build broken for me - anyone else?
Posted by Richard Hirsch <hi...@gmail.com>.
Found it!!
http://maven.twttr.com/com/twitter/
http://maven.twttr.com/com/twitter/xrayspecs/
On Wed, Nov 3, 2010 at 12:29 PM, Richard Hirsch <hi...@gmail.com> wrote:
> Lag.net is associated with http://robey.lag.net/ - twitter developer
>
> Appears that there are a variety of things missing from the site -
> http://www.lag.net/robey/key
>
> D.
>
> On Wed, Nov 3, 2010 at 12:23 PM, Richard Hirsch <hi...@gmail.com> wrote:
>> The problem is that repository at http://www.lag.net/nest is down -
>> that is where it is usually located.
>>
>> Trying to find it somewhere else.
>>
>> D.
>>
>> On Wed, Nov 3, 2010 at 12:17 PM, Ethan Jewett <es...@gmail.com> wrote:
>>> xrayspecs
>>
>
Re: Build broken for me - anyone else?
Posted by Richard Hirsch <hi...@gmail.com>.
Lag.net is associated with http://robey.lag.net/ - twitter developer
Appears that there are a variety of things missing from the site -
http://www.lag.net/robey/key
D.
On Wed, Nov 3, 2010 at 12:23 PM, Richard Hirsch <hi...@gmail.com> wrote:
> The problem is that repository at http://www.lag.net/nest is down -
> that is where it is usually located.
>
> Trying to find it somewhere else.
>
> D.
>
> On Wed, Nov 3, 2010 at 12:17 PM, Ethan Jewett <es...@gmail.com> wrote:
>> xrayspecs
>
Re: Build broken for me - anyone else?
Posted by Ethan Jewett <es...@gmail.com>.
That repository has been commented out in our pom for a while though. I
think it must have lived somewhere else in addition to the
lag.net/nestrepository.
Ethan
On Wed, Nov 3, 2010 at 12:23 PM, Richard Hirsch <hi...@gmail.com>wrote:
> The problem is that repository at http://www.lag.net/nest is down -
> that is where it is usually located.
>
> Trying to find it somewhere else.
>
> D.
>
> On Wed, Nov 3, 2010 at 12:17 PM, Ethan Jewett <es...@gmail.com> wrote:
> > xrayspecs
>
Re: Build broken for me - anyone else?
Posted by Richard Hirsch <hi...@gmail.com>.
The problem is that repository at http://www.lag.net/nest is down -
that is where it is usually located.
Trying to find it somewhere else.
D.
On Wed, Nov 3, 2010 at 12:17 PM, Ethan Jewett <es...@gmail.com> wrote:
> xrayspecs
Re: Build broken for me - anyone else?
Posted by Ethan Jewett <es...@gmail.com>.
Well, it looks like Configgy came back, but in the process of trying to fix
the issue I cleared out my locally repository cache and all of a sudden
vscaladoc 1.1-md3 was no longer available. The problem is described here:
http://riteofcoding.blogspot.com/2010/10/pain-of-dependency-management-thats-you.html
<http://riteofcoding.blogspot.com/2010/10/pain-of-dependency-management-thats-you.html>I've
added an exclusion to the pom.xml which seems to have solved that problem.
Problem #2: com.twitter:ostrich:jar:1.1.16 is missing.
Looks like the oldest version in the scala tools repository is now 1.1.18.
I've changed the POM to 1.1.26, plus the same exclusion on vscaladocs, and
.... now I'm stuck. xrayspecs is now a missing dependency and I can't find
it on any Maven repository anywhere.
Thoughts?
Ethan
P.S. Don't clear your local repository cache until we get this resolved! :-)
On Sun, Oct 31, 2010 at 2:26 PM, Ethan Jewett <es...@gmail.com> wrote:
> FYI, I published the post here:
> http://www.esjewett.com/blog/thoughts-on-whats-next-for-esme
>
> Cross-posting to the ESME blog would definitely be good. Do you want to do
> it? I can send the HTML directly to you, or you can give me access to the
> blog and I'll try to figure out how to do it myself :-)
>
> Ethan
>
>
> On Sat, Oct 30, 2010 at 7:04 PM, Richard Hirsch <hi...@gmail.com>wrote:
>
>> I'm always excited to hear new ideas - can't wait to read the blog.
>>
>> If you want you can also cross-post it to the esme blog.
>>
>> D.
>>
>> On Sat, Oct 30, 2010 at 6:37 PM, Ethan Jewett <es...@gmail.com> wrote:
>> > Works for me. I'm writing a blog on where I see ESME going (possibly -
>> if
>> > everyone agrees) instead of coding. Thanks for the pointers both of you
>> :-)
>> >
>> > Ethan
>> >
>> > On Sat, Oct 30, 2010 at 5:52 PM, Vassil Dichev <vd...@apache.org>
>> wrote:
>> >
>> >> I had a failed build yesterday for the ostrich libraries, which we're
>> >> using for JMX statistics. The author is the same as configgy though,
>> >> which is why it might be failing- the repo is probably also the same.
>> >>
>> >> Let's see if it comes back during the weekend, and if not, we'll
>> >> contact Robey Pointer.
>> >>
>> >> Vassil
>> >>
>> >>
>> >> On Sat, Oct 30, 2010 at 5:48 PM, Richard Hirsch <hirsch.dick@gmail.com
>> >
>> >> wrote:
>> >> > what about trying lift 2.1?
>> >> >
>> >> > If I remember correctly, configgy was used by the twitter.com code
>> not
>> >> lift.
>> >> >
>> >> > What about trying a different repository?
>> >> >
>> >> > On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com>
>> >> wrote:
>> >> >> When I try to build locally I'm getting an error message:
>> >> >>
>> >> >> [INFO]
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> [ERROR] BUILD ERROR
>> >> >> [INFO]
>> >> >>
>> ------------------------------------------------------------------------
>> >> >> [INFO] Failed to resolve artifact.
>> >> >>
>> >> >> Unable to get dependency information: Unable to read local copy of
>> >> metadata:
>> >> >> Cannot read metadata from
>> >> >>
>> >>
>> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
>> >> >> start tag not allowed in epilog but got h (position: END_TAG seen
>> >> >> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
>> >> >> org.slf4j:slf4j-api:jar:null
>> >> >>
>> >> >> from the specified remote repositories:
>> >> >> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
>> >> >> scala-tools.org (http://scala-tools.org/repo-releases),
>> >> >> central (http://repo1.maven.org/maven2),
>> >> >> scala-tools.releases (http://scala-tools.org/repo-releases),
>> >> >> compass-project.org (http://repo.compass-project.org),
>> >> >> Apache Repo (
>> http://people.apache.org/repo/m1-ibiblio-rsync-repository
>> >> ),
>> >> >> Base (http://repo2.maven.org/maven2/),
>> >> >> Configgy (http://www.lag.net/repo),
>> >> >> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
>> >> >>
>> >> >> Path to dependency:
>> >> >> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
>> >> >> 2) net.liftweb:lift-util:jar:2.0
>> >> >> 3) net.liftweb:lift-actor:jar:2.0
>> >> >> 4) net.liftweb:lift-common:jar:2.0
>> >> >>
>> >> >>
>> >> >>
>> >> >> I've tried fiddling with different versions of the slf4j-api in the
>> >> POM.xml
>> >> >> and it doesn't seem to have an affect. Is this happening to anyone
>> else
>> >> or
>> >> >> just me? Suggestions?
>> >> >>
>> >> >> Ethan
>> >> >>
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Twitter: http://twitter.com/vdichev
>> >> Blog: http://speaking-my-language.blogspot.com
>> >>
>> >
>>
>
>
Re: Build broken for me - anyone else?
Posted by Ethan Jewett <es...@gmail.com>.
FYI, I published the post here:
http://www.esjewett.com/blog/thoughts-on-whats-next-for-esme
Cross-posting to the ESME blog would definitely be good. Do you want to do
it? I can send the HTML directly to you, or you can give me access to the
blog and I'll try to figure out how to do it myself :-)
Ethan
On Sat, Oct 30, 2010 at 7:04 PM, Richard Hirsch <hi...@gmail.com>wrote:
> I'm always excited to hear new ideas - can't wait to read the blog.
>
> If you want you can also cross-post it to the esme blog.
>
> D.
>
> On Sat, Oct 30, 2010 at 6:37 PM, Ethan Jewett <es...@gmail.com> wrote:
> > Works for me. I'm writing a blog on where I see ESME going (possibly - if
> > everyone agrees) instead of coding. Thanks for the pointers both of you
> :-)
> >
> > Ethan
> >
> > On Sat, Oct 30, 2010 at 5:52 PM, Vassil Dichev <vd...@apache.org>
> wrote:
> >
> >> I had a failed build yesterday for the ostrich libraries, which we're
> >> using for JMX statistics. The author is the same as configgy though,
> >> which is why it might be failing- the repo is probably also the same.
> >>
> >> Let's see if it comes back during the weekend, and if not, we'll
> >> contact Robey Pointer.
> >>
> >> Vassil
> >>
> >>
> >> On Sat, Oct 30, 2010 at 5:48 PM, Richard Hirsch <hi...@gmail.com>
> >> wrote:
> >> > what about trying lift 2.1?
> >> >
> >> > If I remember correctly, configgy was used by the twitter.com code
> not
> >> lift.
> >> >
> >> > What about trying a different repository?
> >> >
> >> > On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com>
> >> wrote:
> >> >> When I try to build locally I'm getting an error message:
> >> >>
> >> >> [INFO]
> >> >>
> ------------------------------------------------------------------------
> >> >> [ERROR] BUILD ERROR
> >> >> [INFO]
> >> >>
> ------------------------------------------------------------------------
> >> >> [INFO] Failed to resolve artifact.
> >> >>
> >> >> Unable to get dependency information: Unable to read local copy of
> >> metadata:
> >> >> Cannot read metadata from
> >> >>
> >>
> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
> >> >> start tag not allowed in epilog but got h (position: END_TAG seen
> >> >> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
> >> >> org.slf4j:slf4j-api:jar:null
> >> >>
> >> >> from the specified remote repositories:
> >> >> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
> >> >> scala-tools.org (http://scala-tools.org/repo-releases),
> >> >> central (http://repo1.maven.org/maven2),
> >> >> scala-tools.releases (http://scala-tools.org/repo-releases),
> >> >> compass-project.org (http://repo.compass-project.org),
> >> >> Apache Repo (
> http://people.apache.org/repo/m1-ibiblio-rsync-repository
> >> ),
> >> >> Base (http://repo2.maven.org/maven2/),
> >> >> Configgy (http://www.lag.net/repo),
> >> >> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
> >> >>
> >> >> Path to dependency:
> >> >> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
> >> >> 2) net.liftweb:lift-util:jar:2.0
> >> >> 3) net.liftweb:lift-actor:jar:2.0
> >> >> 4) net.liftweb:lift-common:jar:2.0
> >> >>
> >> >>
> >> >>
> >> >> I've tried fiddling with different versions of the slf4j-api in the
> >> POM.xml
> >> >> and it doesn't seem to have an affect. Is this happening to anyone
> else
> >> or
> >> >> just me? Suggestions?
> >> >>
> >> >> Ethan
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> Twitter: http://twitter.com/vdichev
> >> Blog: http://speaking-my-language.blogspot.com
> >>
> >
>
Re: Build broken for me - anyone else?
Posted by Richard Hirsch <hi...@gmail.com>.
I'm always excited to hear new ideas - can't wait to read the blog.
If you want you can also cross-post it to the esme blog.
D.
On Sat, Oct 30, 2010 at 6:37 PM, Ethan Jewett <es...@gmail.com> wrote:
> Works for me. I'm writing a blog on where I see ESME going (possibly - if
> everyone agrees) instead of coding. Thanks for the pointers both of you :-)
>
> Ethan
>
> On Sat, Oct 30, 2010 at 5:52 PM, Vassil Dichev <vd...@apache.org> wrote:
>
>> I had a failed build yesterday for the ostrich libraries, which we're
>> using for JMX statistics. The author is the same as configgy though,
>> which is why it might be failing- the repo is probably also the same.
>>
>> Let's see if it comes back during the weekend, and if not, we'll
>> contact Robey Pointer.
>>
>> Vassil
>>
>>
>> On Sat, Oct 30, 2010 at 5:48 PM, Richard Hirsch <hi...@gmail.com>
>> wrote:
>> > what about trying lift 2.1?
>> >
>> > If I remember correctly, configgy was used by the twitter.com code not
>> lift.
>> >
>> > What about trying a different repository?
>> >
>> > On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com>
>> wrote:
>> >> When I try to build locally I'm getting an error message:
>> >>
>> >> [INFO]
>> >> ------------------------------------------------------------------------
>> >> [ERROR] BUILD ERROR
>> >> [INFO]
>> >> ------------------------------------------------------------------------
>> >> [INFO] Failed to resolve artifact.
>> >>
>> >> Unable to get dependency information: Unable to read local copy of
>> metadata:
>> >> Cannot read metadata from
>> >>
>> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
>> >> start tag not allowed in epilog but got h (position: END_TAG seen
>> >> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
>> >> org.slf4j:slf4j-api:jar:null
>> >>
>> >> from the specified remote repositories:
>> >> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
>> >> scala-tools.org (http://scala-tools.org/repo-releases),
>> >> central (http://repo1.maven.org/maven2),
>> >> scala-tools.releases (http://scala-tools.org/repo-releases),
>> >> compass-project.org (http://repo.compass-project.org),
>> >> Apache Repo (http://people.apache.org/repo/m1-ibiblio-rsync-repository
>> ),
>> >> Base (http://repo2.maven.org/maven2/),
>> >> Configgy (http://www.lag.net/repo),
>> >> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
>> >>
>> >> Path to dependency:
>> >> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
>> >> 2) net.liftweb:lift-util:jar:2.0
>> >> 3) net.liftweb:lift-actor:jar:2.0
>> >> 4) net.liftweb:lift-common:jar:2.0
>> >>
>> >>
>> >>
>> >> I've tried fiddling with different versions of the slf4j-api in the
>> POM.xml
>> >> and it doesn't seem to have an affect. Is this happening to anyone else
>> or
>> >> just me? Suggestions?
>> >>
>> >> Ethan
>> >>
>> >
>>
>>
>>
>> --
>> Twitter: http://twitter.com/vdichev
>> Blog: http://speaking-my-language.blogspot.com
>>
>
Re: Build broken for me - anyone else?
Posted by Ethan Jewett <es...@gmail.com>.
Works for me. I'm writing a blog on where I see ESME going (possibly - if
everyone agrees) instead of coding. Thanks for the pointers both of you :-)
Ethan
On Sat, Oct 30, 2010 at 5:52 PM, Vassil Dichev <vd...@apache.org> wrote:
> I had a failed build yesterday for the ostrich libraries, which we're
> using for JMX statistics. The author is the same as configgy though,
> which is why it might be failing- the repo is probably also the same.
>
> Let's see if it comes back during the weekend, and if not, we'll
> contact Robey Pointer.
>
> Vassil
>
>
> On Sat, Oct 30, 2010 at 5:48 PM, Richard Hirsch <hi...@gmail.com>
> wrote:
> > what about trying lift 2.1?
> >
> > If I remember correctly, configgy was used by the twitter.com code not
> lift.
> >
> > What about trying a different repository?
> >
> > On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com>
> wrote:
> >> When I try to build locally I'm getting an error message:
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Failed to resolve artifact.
> >>
> >> Unable to get dependency information: Unable to read local copy of
> metadata:
> >> Cannot read metadata from
> >>
> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
> >> start tag not allowed in epilog but got h (position: END_TAG seen
> >> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
> >> org.slf4j:slf4j-api:jar:null
> >>
> >> from the specified remote repositories:
> >> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
> >> scala-tools.org (http://scala-tools.org/repo-releases),
> >> central (http://repo1.maven.org/maven2),
> >> scala-tools.releases (http://scala-tools.org/repo-releases),
> >> compass-project.org (http://repo.compass-project.org),
> >> Apache Repo (http://people.apache.org/repo/m1-ibiblio-rsync-repository
> ),
> >> Base (http://repo2.maven.org/maven2/),
> >> Configgy (http://www.lag.net/repo),
> >> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
> >>
> >> Path to dependency:
> >> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
> >> 2) net.liftweb:lift-util:jar:2.0
> >> 3) net.liftweb:lift-actor:jar:2.0
> >> 4) net.liftweb:lift-common:jar:2.0
> >>
> >>
> >>
> >> I've tried fiddling with different versions of the slf4j-api in the
> POM.xml
> >> and it doesn't seem to have an affect. Is this happening to anyone else
> or
> >> just me? Suggestions?
> >>
> >> Ethan
> >>
> >
>
>
>
> --
> Twitter: http://twitter.com/vdichev
> Blog: http://speaking-my-language.blogspot.com
>
Re: Build broken for me - anyone else?
Posted by Vassil Dichev <vd...@apache.org>.
I had a failed build yesterday for the ostrich libraries, which we're
using for JMX statistics. The author is the same as configgy though,
which is why it might be failing- the repo is probably also the same.
Let's see if it comes back during the weekend, and if not, we'll
contact Robey Pointer.
Vassil
On Sat, Oct 30, 2010 at 5:48 PM, Richard Hirsch <hi...@gmail.com> wrote:
> what about trying lift 2.1?
>
> If I remember correctly, configgy was used by the twitter.com code not lift.
>
> What about trying a different repository?
>
> On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com> wrote:
>> When I try to build locally I'm getting an error message:
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve artifact.
>>
>> Unable to get dependency information: Unable to read local copy of metadata:
>> Cannot read metadata from
>> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
>> start tag not allowed in epilog but got h (position: END_TAG seen
>> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
>> org.slf4j:slf4j-api:jar:null
>>
>> from the specified remote repositories:
>> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
>> scala-tools.org (http://scala-tools.org/repo-releases),
>> central (http://repo1.maven.org/maven2),
>> scala-tools.releases (http://scala-tools.org/repo-releases),
>> compass-project.org (http://repo.compass-project.org),
>> Apache Repo (http://people.apache.org/repo/m1-ibiblio-rsync-repository),
>> Base (http://repo2.maven.org/maven2/),
>> Configgy (http://www.lag.net/repo),
>> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
>>
>> Path to dependency:
>> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
>> 2) net.liftweb:lift-util:jar:2.0
>> 3) net.liftweb:lift-actor:jar:2.0
>> 4) net.liftweb:lift-common:jar:2.0
>>
>>
>>
>> I've tried fiddling with different versions of the slf4j-api in the POM.xml
>> and it doesn't seem to have an affect. Is this happening to anyone else or
>> just me? Suggestions?
>>
>> Ethan
>>
>
--
Twitter: http://twitter.com/vdichev
Blog: http://speaking-my-language.blogspot.com
Re: Build broken for me - anyone else?
Posted by Richard Hirsch <hi...@gmail.com>.
what about trying lift 2.1?
If I remember correctly, configgy was used by the twitter.com code not lift.
What about trying a different repository?
On Sat, Oct 30, 2010 at 1:33 PM, Ethan Jewett <es...@gmail.com> wrote:
> When I try to build locally I'm getting an error message:
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Unable to get dependency information: Unable to read local copy of metadata:
> Cannot read metadata from
> '/Users/esjewett/.m2/repository/org/slf4j/slf4j-api/maven-metadata-Configgy.xml':
> start tag not allowed in epilog but got h (position: END_TAG seen
> <style>\n#adTacIntFr{display:none;}\n</style> \n<h... @4:3)
> org.slf4j:slf4j-api:jar:null
>
> from the specified remote repositories:
> scala-tools.snapshots (http://scala-tools.org/repo-snapshots),
> scala-tools.org (http://scala-tools.org/repo-releases),
> central (http://repo1.maven.org/maven2),
> scala-tools.releases (http://scala-tools.org/repo-releases),
> compass-project.org (http://repo.compass-project.org),
> Apache Repo (http://people.apache.org/repo/m1-ibiblio-rsync-repository),
> Base (http://repo2.maven.org/maven2/),
> Configgy (http://www.lag.net/repo),
> scala-tools.org.snapshots (http://scala-tools.org/repo-snapshots)
>
> Path to dependency:
> 1) org.apache.esme:esme-server:war:apache-esme-1.1-incubating
> 2) net.liftweb:lift-util:jar:2.0
> 3) net.liftweb:lift-actor:jar:2.0
> 4) net.liftweb:lift-common:jar:2.0
>
>
>
> I've tried fiddling with different versions of the slf4j-api in the POM.xml
> and it doesn't seem to have an affect. Is this happening to anyone else or
> just me? Suggestions?
>
> Ethan
>