Bumped to version 1.2_beta1 as it is a jboss-jacorb dependency ! Added to "java-migration-overlay"
*** This bug has been marked as a duplicate of bug 128398 ***
The other bug was for a stable request !
added dev-java/picocontainer-1.2 too
Please, don't copy and commit all versions that are in main tree, into the overlay. Only version(s) you are adding. Thanks.
(In reply to comment #4) > Please, don't copy and commit all versions that are in main tree, into the > overlay. Only version(s) you are adding. Thanks. > Agreed. Also it seems that upstream is going to release 1.3 soon as they already have rc1 available so we might as well go with 1.3 directly if they release it soon assuming it is ABI compatible.
i removed the "beta" as it's useless. Don't know for 1.3, just relesead the 1.2 as it is the one required by JBoss. After that, if you continue with 1.3, please not remove the 1.2 in flavor of 1.3 before i tried to compile JBoss with.
1.1 -> 1.2 apicheck Package Summary: org.picocontainer: 100% good org.picocontainer.alternatives: 99.55% good, 0.44% missing org.picocontainer.defaults: 97.93% good, 0.12% bad, 1.93% missing dev-java/radeox (the only package depending on it in main tree) doesn't mind I see you are using ejavac/jar... tried to produce build.xml from maven instead?
Why, ejavac is just enought, isn't it? Maybe just a matter of taste or must i rewrite it with a build.xml ?
Probably enough for this simple library, OK. I just though getting build.xml from maven is easier than writing ejavac calls, but then I really don't have much experience with it, maybe betelgeuse would know better.
no, as it has only a few dependencies ( only 1 or two if i am right ) and don't use maven/ant plugins . Generating a build.xml, then rewriting classpath and related stuff (maven use some variables like maven.classpath (something like that) ) is a bigger effort and less maintenable IMHO. Please tell me if i am wrong.
Using ejavac may actually be less work and easier to maintain. Even if you generate the build.xml, you usually have to hack it quite a bit, like not to download stuff among other things. Other notes: src_unpack isn't needed since you don't do anything fancy. 'classes' is an idiomatic directlory to place compiled class files, as opposed to 'java' ejavac will die on it's own, no need to || die. Probably don't need to mkdir dist during src_install, since you create it during src_compile.
(In reply to comment #11) > Using ejavac may actually be less work and easier to maintain. Even if you > generate the build.xml, you usually have to hack it quite a bit, like not to > download stuff among other things. > The problem with ejavac and friends or hand written build.xml files is that they have caused bugs in the past when for example our installed jar file misses some xml file.
1.3 is out 1.2 breaks deskzilla... and doesn't seem like result of API change that would be catched during build, were deskzilla opensource... FATAL ERROR java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.picocontainer.defaults.DefaultPicoContainer$OrderedComponentAdapterLifecycleManager.start(DefaultPicoContainer.java:660) at org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:464) at org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:469) at z.gbf.e(ZZ:43) at com.almworks.platform.ComponentLoader.s(ZZ:385) at com.almworks.platform.ComponentLoader.b(ZZ:93) at com.almworks.platform.ComponentLoader.a(ZZ:30) at z.azs.run(ZZ:42) at java.lang.Thread.run(Thread.java:595) at z.gxk.run(ZZ:18) 20070424-064532.800 SEVERE FATAL ERROR java.util.ConcurrentModificationException at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:449) at java.util.AbstractList$Itr.next(AbstractList.java:420) at org.picocontainer.defaults.DefaultPicoContainer$OrderedComponentAdapterLifecycleManager.start(DefaultPicoContainer.java:660) at org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:464) at org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:469) at z.gbf.e(ZZ:43) at com.almworks.platform.ComponentLoader.s(ZZ:385) at com.almworks.platform.ComponentLoader.b(ZZ:93) at com.almworks.platform.ComponentLoader.a(ZZ:30) at z.azs.run(ZZ:42) at java.lang.Thread.run(Thread.java:595) at z.gxk.run(ZZ:18) ==========================================================================================
The HOMEPAGE domain seems dead now.
Ebuild removed from overlay.
Perfect, thanks.