Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 60141 - Cannot emerge jboss-3.2.5 - build "succeeds" but fails to build
Summary: Cannot emerge jboss-3.2.5 - build "succeeds" but fails to build
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All All
: High major (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 64795
  Show dependency tree
 
Reported: 2004-08-12 08:06 UTC by Shevek
Modified: 2004-09-21 01:26 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Shevek 2004-08-12 08:06:08 UTC
>>> md5 src_uri ;-) jboss-3.2.5-src.tar.bz2
>>> Unpacking source...
>>> Unpacking jboss-3.2.5-src.tar.bz2 to /var/tmp/portage/jboss-3.2.5/work
>>> Source unpacked.
java.lang.InstantiationException: org.apache.tools.ant.Main
        at java.lang.Class.newInstance0(Class.java:293)
        at java.lang.Class.newInstance(Class.java:261)
        at org.apache.tools.ant.launch.Launcher.run(Launcher.java:196)
        at org.apache.tools.ant.launch.Launcher.main(Launcher.java:56)

>>> Install jboss-3.2.5 into /var/tmp/portage/jboss-3.2.5/image/ category www-servers
cp: cannot stat `build/output/jboss-3.2.5/bin/run.sh': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/bin/shutdown.sh': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/bin/run.jar': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/bin/shutdown.jar': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/server': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/lib': No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/client': No such file or directory
mv: cannot stat `/var/tmp/portage/jboss-3.2.5/image///usr/share/jboss/server/all': No such file or directory
mv: cannot stat `/var/tmp/portage/jboss-3.2.5/image///usr/share/jboss/server/default': No such file or directory
mv: cannot stat `/var/tmp/portage/jboss-3.2.5/image///usr/share/jboss/server/minimal': No such file or directory
cp: cannot create regular file `/var/tmp/portage/jboss-3.2.5/image//var/lib/jboss/all/conf/log4j.xml': No such file or directory
cp: cannot create regular file `/var/tmp/portage/jboss-3.2.5/image//var/lib/jboss/default/conf/log4j.xml': No such file or directory
cp: cannot create regular file `/var/tmp/portage/jboss-3.2.5/image//var/lib/jboss/minimal/conf/log4j.xml': No such file or directory
rmdir: `/var/tmp/portage/jboss-3.2.5/image///usr/share/jboss/server': No such file or directory
find: /var/tmp/portage/jboss-3.2.5/image///usr/share/jboss/client: No such file or directory
cp: cannot stat `build/output/jboss-3.2.5/docs/examples': No such file or directory
install: cannot stat `build/output/jboss-3.2.5/docs/dtd/*': No such file or directory
man:
prepallstrip:
strip: 
strip: 
>>> Completed installing into /var/tmp/portage/jboss-3.2.5/image/
root@silver /usr/portage/www-servers/jboss# qpkg -I -v ant
dev-db/oracle-instantclient-basic-10.1.0.2 *
dev-db/oracle-instantclient-sqlplus-10.1.0.2 *
dev-java/ant-1.5.4-r1 *
dev-java/antlr-2.7.3 *
Comment 1 Chris White (RETIRED) gentoo-dev 2004-08-12 08:13:51 UTC
If you have additional errors for the same package, it's best to post them
to the same bug to prevent somewhat duplicate bugs.

*** This bug has been marked as a duplicate of 60140 ***
Comment 2 Shevek 2004-08-12 08:38:53 UTC
The reason I reported two separate bugs is that they are two separate bugs with very different errors for different reasons on totally different version of the same package.

I am a programmer. I have looked into the two issues. As far as I can see, there is no relationship whatsoever between them. I did not find an obvious solution to either bug.

S.
Comment 3 Thomas Matthijs (RETIRED) gentoo-dev 2004-09-21 01:26:41 UTC
http://ant.apache.org/faq.html#InstantiationException
could it be ^

are your ANT_HOME && CLASSPATH clean
(check them in /etc/profile.env too since thats what portages uses)

i fixed to ebuild to fail to install