ivy
by Orion Poplawski
Has anyone dealt with any projects that use ivy? Appears to be similar
to maven and downloads jars automatically, so it's probably going to
need similar treatment to maven in the build system.
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years
Need help with maven poms
by Orion Poplawski
I've packaged up jempbox and fontbox, prereqs for pdfbox. Now trying to
build pdfbox I get:
Downloading:
file:///usr/share/maven2/repository/JPP/maven2/default_poms/org.apache.pdfbox-fontbox.pom
Downloading:
file:///usr/share/maven2/repository/JPP/maven2/default_poms/org.apache.pdfbox-jempbox.pom
...
Missing:
----------
1) org.apache.pdfbox:fontbox:jar:1.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.pdfbox
-DartifactId=fontbox -Dversion=1.0.0 -
Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=org.apache.pdfbox
-DartifactId=fontbox -Dversion=1.0.0 -Dp
ackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.pdfbox:pdfbox:bundle:1.0.0
2) org.apache.pdfbox:fontbox:jar:1.0.0
2) org.apache.pdfbox:jempbox:jar:1.0.0
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.pdfbox
-DartifactId=jempbox -Dversion=1.0.0 -
Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the
file there:
mvn deploy:deploy-file -DgroupId=org.apache.pdfbox
-DartifactId=jempbox -Dversion=1.0.0 -Dp
ackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.pdfbox:pdfbox:bundle:1.0.0
2) org.apache.pdfbox:jempbox:jar:1.0.0
I don't see
/usr/share/maven2/repository/JPP/maven2/default_poms/org.apache.pdfbox-fontbox.pom
or
/usr/share/maven2/repository/JPP/maven2/default_poms/org.apache.pdfbox-jempbox.pom
present, but there is /usr/share/maven2/poms/JPP-fontbox.pom:
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>org.apache</groupId>
<artifactId>apache</artifactId>
<version>6</version>
</parent>
<groupId>org.apache.pdfbox</groupId>
<artifactId>fontbox</artifactId>
<version>1.0.0</version>
<packaging>bundle</packaging>
I suspect I'm not packaging the pom correctly as part of the pdfbox
project, but not sure how to fix. Help please?
fontbox spec has:
cp -p pom.xml $RPM_BUILD_ROOT%{_datadir}/maven2/poms/JPP-%{name}.pom
%add_to_maven_depmap org.apache.maven %{name} %{version} JPP %{name}
Thanks!
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion(a)cora.nwra.com
Boulder, CO 80301 http://www.cora.nwra.com
14 years, 2 months
about updating itext
by Orcan Ogetbil
Hi all,
I have been thinking about updating itext from 2.1 7 to 5.0.1. It
sounds like a huge jump but in reality, there was only one version it
between, 5.0.0.
However, the 5.0.x update is not fully backward compatible. Here are
the changes:
1- Instead of com.lowagie.text, the new itext uses the path
com.itexpdf.text. This is easy to fix on dependent packages:
- pdftk (I am a comaintainer. I already made a patch for this)
- tuxguitar (I am the maintainer)
- libfonts
- liblayout
I don't maintain the last two but I can patch them up if it is okay,
2- We used to ship itext with xml support. This part of the code was
not in the itext-2.1.7 tree but we had ported this over from a 1.x
release [1]. I am not familiar with this part of the code and I was
told that this add-on was needed by maven. Is this still valid?
The issue is, itext-5.0.0+ dropped some other part of its code, which
our xml patch was depending on. In particular, the rtf support of
itext moved to a separate project [2]
Now we have a few options:
1- Package the new project separately. And move the xml patch to this package.
2- Drop rtf bits from our xml patch (I don't know if this is possible.
I didn't check. overholt?)
3- Don't update itext. Stick with 2.1.7 for now.
As I don't know what that xml patch does with maven, I hesitate
updating itext. By the way, why does maven not require itext?
Here is an initial attempt for the 5.0.1 update without xml support: [3]
Please share your ideas, potential problems, solutions, proposals etc.
Cheers,
Orcan
[1] http://cvs.fedoraproject.org/viewvc/rpms/itext/devel/itext-xmloutput.patc...
[2] http://sourceforge.net/projects/itextrtf
[3] http://oget.fedorapeople.org/review/itext-5.0.1-1.fc12.src.rpm
14 years, 2 months
Page update request
by Ankur Sinha
hi,
I was reading up on java stack traces etc when I came across this
page[1]. Can someone please take out a few minutes and update the page
please? It still speaks of FC5.
regards
[1] http://fedoraproject.org/wiki/JavaStackTraces
--
--
Ankur Sinha
- FAS : ankursinha
- franciscod @ Freenode
14 years, 2 months
Java Projects
by Rajmahendra
Hi all,
I am Raj from chennai. I am basically a Java/J2ee Software engineer.
Just wondering what are the Java projects going on in Fedora.
Meet you all soon
Raj
14 years, 2 months
jakarta-commons-lang 2.4
by Jerry James
I maintain findbugs, whose latest version needs jakarta-commons-lang
2.4. We currently ship 2.3. The upstream release notes [1][2] claim
that 2.4 has no incompatibilities with 2.3. On the other hand, I see
that jpackage (5.0) has both a jakarta-commons-lang (version 2.3)
package and a jakarta-commons-lang24 package, but I don't know why.
According to repoquery, these packages currently require jakarta-commons-lang:
directory-naming
eclipse-mylyn
findbugs
jakarta-commons-cli
jakarta-commons-configuration
jeuclid
maven2
maven2-plugin-changes
maven2-plugin-enforcer
maven2-plugin-gpg
maven2-plugin-jar
maven2-plugin-javadoc
openoffice.org-wiki-publisher
plexus-registry
Do the maintainers of any of these packages have any reason why
jakarta-commons-lang should not be upgraded from 2.3 to 2.4?
References:
[1] http://commons.apache.org/lang/upgradeto2_4.html
[2] http://commons.apache.org/lang/article2_4.html
--
Jerry James
http://www.jamezone.org/
14 years, 2 months
Looking Solution for Java Applet
by Umesh Sharma
Dear all
i am using fedora 11 . I am facing problem with Java applet all fonts
display are too small not readable. i tried jre 1.6,1.5 but same problem and
jre 1.3 feroda not accepting. my server having jre 1.1.4 ver. please suggest
me how can i solve this problem.thanks in advance..
Umesh
14 years, 2 months
