karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@gmail.com>
Subject Re: [WARNING] Build Issue with dependency 'jline'
Date Tue, 14 Feb 2012 21:19:34 GMT
Great, so just changing the groupId to jline in our pom should do the trick.
Thx Jason !

On Tue, Feb 14, 2012 at 22:13, Jason Dillon <jason@planet57.com> wrote:
> I dropped the artifacts (well the meat of the artifacts) from the net.sf.jline 2.6-SNAPSHOT
bits, these are now in jline gid:
>
> https://oss.sonatype.org/content/repositories/snapshots/jline/jline/2.6-SNAPSHOT/
>
> I asked someone here @Sonatype who has perms on oss.sonatype.org to add gnodet to the
jline group.
>
> --jason
>
>
> On Tuesday, February 14, 2012 at 1:03 PM, Guillaume Nodet wrote:
>
>> I think the problem comes from the fact the groupId of jline has
>> changed back to jline instead of net.sf.jline, but I can't upload a
>> snapshot because of that change.
>>
>> On Tue, Feb 14, 2012 at 06:57, Jean-Baptiste Onofré <jb@nanthrax.net (mailto:jb@nanthrax.net)>
wrote:
>> > Hi,
>> >
>> > I raised:
>> >
>> > https://issues.sonatype.org/browse/OSSRH-2937
>> >
>> > for the Sonatype guys.
>> >
>> > The latest SNAPSHOT deployed (last Saturday) is not full (no jar, no
>> > sources, no cheksums, only the pom).
>> >
>> > Regards
>> > JB
>> >
>> >
>> > On 02/13/2012 11:08 PM, uromahn wrote:
>> > >
>> > > Hello,
>> > >
>> > > I just got the latest Karaf sources from trunk. While building it
>> > > constantly
>> > > failed because it was not able to download the jline dependency from any
>> > > of
>> > > the remote repos.
>> > >
>> > > After digging into it, I found out that the jline project decided to
>> > > change
>> > > the group ID from net.sf.jline back to jline. This change caused the
>> > > publish
>> > > into the nexus to only create the meta data but no real artifact (i.e.
no
>> > > JAR).
>> > >
>> > > So here is how I had to fix it:
>> > > 1. update the Karaf pom.xml and changed the artifact ID from
>> > > 'net.sf.jline'
>> > > to 'jline, and
>> > > 2. get the jline2 source from trunk (github) and build it myself so it
>> > > gets
>> > > inserted into my local repo (not available on any public repo).
>> > >
>> > > Hope that helps some folks to get over this hurdle.
>> > > -Uli
>> > >
>> > > --
>> > > View this message in context:
>> > > http://karaf.922171.n3.nabble.com/WARNING-Build-Issue-with-dependency-jline-tp3741802p3741802.html
>> > > Sent from the Karaf - Dev mailing list archive at Nabble.com (http://Nabble.com).
>> >
>> >
>> >
>> >
>> > --
>> > Jean-Baptiste Onofré
>> > jbonofre@apache.org (mailto:jbonofre@apache.org)
>> > http://blog.nanthrax.net
>> > Talend - http://www.talend.com
>>
>>
>>
>>
>>
>> --
>> ------------------------
>> Guillaume Nodet
>> ------------------------
>> Blog: http://gnodet.blogspot.com/
>> ------------------------
>> FuseSource, Integration everywhere
>> http://fusesource.com
>
>
>



-- 
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
FuseSource, Integration everywhere
http://fusesource.com

Mime
View raw message