we're using itext in 1 of our projects generate pdf reports, precisely version 4.2.1 because last free version.
<dependency> <groupid>com.lowagie</groupid> <artifactid>itext</artifactid> <version>4.2.1</version> </dependency> when cloned repository on new machine morning, faced lot of compiler errors, because maven redirects version 5.5.6 , imports failing. on our research, found out, pom-file in maven central changed last week. on, seems impossible add jar dependency did before.
can tell me, if there still way integrate itext in version 4.2.1 via maven?
as documented here, people published itext forks versions 4.x.y didn't follow the rules explained apache:
i have patched version of foo project developed @ foo.com, groupid should use?
when patch / modify third party project, patched version becomes project , therefore should distributed under groupid control project have developed, never under com.foo. see above considerations groupid.
they published unofficial version of itext using groupid led people believe using original version of itext, wasn't not true. error has caused confusion , frustration.
to stop confusion, itext group has reclaimed groupid no third party can introduce software infringes third part rights or malware code base (this risk take when allow maven automatically upgrade).
your allegation itext 4.2.1 the last free version incorrect. there serious issues itext versions prior itext 5, that's discussion , subject of conference talk @ javaone 2015 entitled ianal: developers should know ip , legal.
in case, easiest solution change dependecy to:
<dependency> <groupid>com.lowagie</groupid> <artifactid>itext</artifactid> <version>[1.02b,2.1.7]</version> <scope>compile</scope> </dependency> see this answer in answer dependency error in jasper-reports itext more background information.
Comments
Post a Comment