itext

25 views
Skip to first unread message

GodlessWonder

unread,
May 8, 2011, 2:10:10 PM5/8/11
to ivyroundup
Folks:
Itext has been broken for some time now. If you put this dependency
for ivyresolve: <dependency org="net.sourceforge.itext"
name="itext" rev="latest.release" />

you get a bunch of errors like this: FAILED DOWNLOADS
net.sourceforge.itext#itext;2.1.7!itext.jar

If you look at the resolution message for ivyroundup, I see this:
Can't get http://downloads.sourceforge.net/itext/iText-2.1.7.jar
to ...

If you check that link, you can see that the itext people have
reorganized their product listing, or something like that, because the
available versions are 5.0.0 to 5.1.0.

So, ivyroundup still lists 2.1.7 as latest release, but that version
no longer exists on source forge.

Please advise. I am willing to help with maintenance of the repo if
you wish.
Yours,
Dave Godbey

Archie Cobbs

unread,
May 8, 2011, 2:58:00 PM5/8/11
to ivyro...@googlegroups.com
Dave,

Thanks for your offer to help. Start by creating a bug in the issue tracker (it's fine to just cut & paste your email). Even better would be to submit a patch with the issue; read the wiki pages about how to create the patch. But even if you don't have time to create a patch if you file the issue, we'll get it fixed in the next few days.

Thanks,
-Archie


--
You received this message because you are subscribed to the Google Groups "ivyroundup" group.
To post to this group, send email to ivyro...@googlegroups.com.
To unsubscribe from this group, send email to ivyroundup+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ivyroundup?hl=en.




--
Archie L. Cobbs

Mark Thomas

unread,
May 9, 2011, 8:27:52 AM5/9/11
to ivyro...@googlegroups.com
We had itext 5.x in the repo before; however, those guys changed so much it caused conflicts with quite a number of projects depending on it so we removed it.  That's something to be wary of when working on this.  alternatively, i'm sure we can find 2.1.7 in a maven repo somewhere.

fyi, to find all projects that depend on itext you can run this:

find src/modules -type f -name 'ivy.xml' -print0 | xargs -0 grep -l itext

which yields

src/modules/org.jaspersoft/jasperreports/3.7.3/ivy.xml
src/modules/org.jaspersoft/jasperreports/3.5.3/ivy.xml
src/modules/org.jaspersoft/jasperreports/3.5.2/ivy.xml
src/modules/org.jaspersoft/jasperreports/3.5.1/ivy.xml
src/modules/org.jaspersoft/jasperreports/3.5.0/ivy.xml
src/modules/org.jaspersoft/jasperreports/4.0.1/ivy.xml
src/modules/org.primefaces/primefaces/2.2.M1/ivy.xml

Regards,

Mark Thomas
spatialguru.net@gmail.com
205.529.9013

"Commit to the Lord whatever you do,
    and your plans will succeed." - Proverbs 16:3

Archie Cobbs

unread,
May 9, 2011, 12:04:58 PM5/9/11
to ivyro...@googlegroups.com
Mark,

Maybe using force="true" in the <dependency> elements of the modules that depend on the older version of iText would be a way to handle this?

-Archie

Mark Thomas

unread,
May 9, 2011, 12:43:50 PM5/9/11
to ivyro...@googlegroups.com
that would work

Regards,

Mark Thomas
spatialguru.net@gmail.com
205.529.9013

"Commit to the Lord whatever you do,
    and your plans will succeed." - Proverbs 16:3


Reply all
Reply to author
Forward
0 new messages