Hi,
After all apache-ivy is required by the new xmvn-connector-ivy- 0:4.0.0~20210707.d300ce6-1.fc35.src ??? and ant-contrib [1] ant-contrib is required by [2]
After find that in java the correct repo queries are done in repo rawhide-source with --arch=src , (we query the buildrequires)
So why we need xmvn-connector-ivy ? and can ant-contrib be retired ? https://en.wikipedia.org/wiki/Apache_Ivy maven seems that supersede and ivy seems to me that need java 1.7, not even 1.8 [3]
and I can't find a way to build apache-ivy in rawhide [4]
If we retire apache-ivy, we need also want retire ant-contrib, note that ant-contrib is complete dead upstream (last release is from 2008 , and we should inform the 4 projects that still requires ant- contrib ...
Note the main problem for me is I don't see how we will build apache- ivy
[1] dnf repoquery --disablerepo='*' --enablerepo=rawhide-source --arch=src --whatrequires apache-ivy
dnf repoquery --disablerepo='*' --enablerepo=rawhide-source --arch=src --whatrequires "mvn(org.apache.ivy:ivy)"
[2] dnf repoquery --disablerepo='*' --enablerepo=rawhide-source --arch=src --whatrequires ant-contrib eclipse-gef-0:3.11.0-16.fc34.src forbidden-apis-0:2.5-10.fc34.src java-sleep-0:2.1-22.fc34.src jmol-0:14.31.44-1.fc35.src
[3] [javac] warning: [options] bootstrap class path not set in conjunction with -source 7 [javac] /builddir/build/BUILD/apache-ivy- 2.5.0/src/java/org/apache/ivy/util/FileUtil.java:49: warning: [removal] Pack200 in java.util.jar has been deprecated and marked for removal [javac] import static java.util.jar.Pack200.newUnpacker; [javac] ^ [javac] Note: Some input files use or override a deprecated API. [javac] Note: Recompile with -Xlint:deprecation for details. [javac] 2 warnings
[4] init-ivy: [ivy:configure] impossible to define new type: class not found: org.apache.ivy.plugins.resolver.VfsResolver in [] nor Ivy classloader [ivy:configure] impossible to define new type: class not found: org.apache.ivy.plugins.resolver.SshResolver in [] nor Ivy classloader [ivy:configure] impossible to define new type: class not found: org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator in [] nor Ivy classloader [ivy:configure] impossible to define new type: class not found: org.apache.ivy.plugins.resolver.SFTPResolver in [] nor Ivy classloader [ivy:configure] :: Apache Ivy 2.5.0-local-19700112153424 - 19700112153424 :: https://ant.apache.org/ivy/ :: [ivy:configure] :: loading settings :: file = /etc/ivy/ivysettings.xml
BUILD FAILED /builddir/build/BUILD/apache-ivy-2.5.0/build.xml:55: impossible to configure ivy:settings with given file: /etc/ivy/ivysettings.xml : java.text.ParseException: failed to load settings from file:/etc/ivy/ivysettings.xml: impossible to define new type: class not found: org.fedoraproject.xmvn.connector.ivy.IvyResolver in [] nor Ivy classloader
On Sun, Jul 18, 2021 at 1:00 AM Sérgio Basto sergio@serjux.com wrote:
After all apache-ivy is required by the new xmvn-connector-ivy- 0:4.0.0~20210707.d300ce6-1.fc35.src ??? and ant-contrib [1] ant-contrib is required by [2]
After find that in java the correct repo queries are done in repo rawhide-source with --arch=src , (we query the buildrequires)
So why we need xmvn-connector-ivy ? and can ant-contrib be retired ? https://en.wikipedia.org/wiki/Apache_Ivy maven seems that supersede and ivy seems to me that need java 1.7, not even 1.8 [3]
and I can't find a way to build apache-ivy in rawhide [4]
If we retire apache-ivy, we need also want retire ant-contrib, note that ant-contrib is complete dead upstream (last release is from 2008 , and we should inform the 4 projects that still requires ant- contrib ...
Note the main problem for me is I don't see how we will build apache- ivy
I picked up ant-contrib when it was orphaned recently because jmol wants it. A little digging around shows that jmol uses it solely to support this construct:
<for list="${all.Jmol.languages}" delimiter="," param="current.Jmol.language"> <sequential> <!-- Do stuff with @{current.Jmol.language} --> </sequential> </for>
If that construct can be converted into vanilla ant somehow, I would be quite happy to drop ant-contrib into the laps of the eclipse-gef, forbidden-apis, and java-sleep maintainers. :-)
On Mon, Jul 19, 2021 at 8:36 AM Jerry James loganjerry@gmail.com wrote:
I picked up ant-contrib when it was orphaned recently because jmol wants it. A little digging around shows that jmol uses it solely to support this construct:
<for list="${all.Jmol.languages}" delimiter="," param="current.Jmol.language"> <sequential> <!-- Do stuff with @{current.Jmol.language} --> </sequential> </for>
That wasn't quite right. There is some usage of ant-contrib's <if> tag as well. I've managed to come up with a patch for jmol's build.xml to use only vanilla ant constructs and accomplish everything the current version does. It's quite ugly, so I'm not going to suggest it to upstream. But if ant-contrib is going to be broken by the retirement of apache-ivy, I have an option to keep jmol alive.
If that construct can be converted into vanilla ant somehow, I would be quite happy to drop ant-contrib into the laps of the eclipse-gef, forbidden-apis, and java-sleep maintainers. :-)
CCing the maintainers of the packages listed above. Are any of you interested in maintaining ant-contrib, and either removing its dependency on apache-ivy, or adopting apache-ivy as well?
Let's try this again with the right package maintainer email aliases.
On Mon, Jul 19, 2021 at 8:36 AM Jerry James loganjerry@gmail.com wrote:
I picked up ant-contrib when it was orphaned recently because jmol wants it. A little digging around shows that jmol uses it solely to support this construct:
<for list="${all.Jmol.languages}" delimiter="," param="current.Jmol.language"> <sequential> <!-- Do stuff with @{current.Jmol.language} --> </sequential> </for>
That wasn't quite right. There is some usage of ant-contrib's <if> tag as well. I've managed to come up with a patch for jmol's build.xml to use only vanilla ant constructs and accomplish everything the current version does. It's quite ugly, so I'm not going to suggest it to upstream. But if ant-contrib is going to be broken by the retirement of apache-ivy, I have an option to keep jmol alive.
If that construct can be converted into vanilla ant somehow, I would be quite happy to drop ant-contrib into the laps of the eclipse-gef, forbidden-apis, and java-sleep maintainers. :-)
CCing the maintainers of the packages listed above. Are any of you interested in maintaining ant-contrib, and either removing its dependency on apache-ivy, or adopting apache-ivy as well?
On Mon, 2021-07-19 at 16:50 -0600, Jerry James wrote:
Let's try this again with the right package maintainer email aliases.
On Mon, Jul 19, 2021 at 8:36 AM Jerry James loganjerry@gmail.com wrote:
I picked up ant-contrib when it was orphaned recently because jmol wants it. A little digging around shows that jmol uses it solely to support this construct:
<for list="${all.Jmol.languages}" delimiter="," param="current.Jmol.language"> <sequential> <!-- Do stuff with @{current.Jmol.language} --> </sequential>
</for>
That wasn't quite right. There is some usage of ant-contrib's <if> tag as well. I've managed to come up with a patch for jmol's build.xml to use only vanilla ant constructs and accomplish everything the current version does. It's quite ugly, so I'm not going to suggest it to upstream. But if ant-contrib is going to be broken by the retirement of apache-ivy, I have an option to keep jmol alive.
If that construct can be converted into vanilla ant somehow, I would be quite happy to drop ant-contrib into the laps of the eclipse- gef, forbidden-apis, and java-sleep maintainers. :-)
can maven-antrun-plugin replace ant builds ?
can you build the package with maven-antrun-plugin instead ?
CCing the maintainers of the packages listed above. Are any of you interested in maintaining ant-contrib, and either removing its dependency on apache-ivy, or adopting apache-ivy as well? -- Jerry James http://www.jamezone.org/ _______________________________________________ java-devel mailing list -- java-devel@lists.fedoraproject.org To unsubscribe send an email to java-devel-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/java-devel@lists.fedoraproject... Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Sun, Jul 18, 2021 at 9:00 AM Sérgio Basto sergio@serjux.com wrote:
Hi,
After all apache-ivy is required by the new xmvn-connector-ivy- 0:4.0.0~20210707.d300ce6-1.fc35.src
[...]
So why we need xmvn-connector-ivy ?
xmvn-connector-ivy is a dependency of ivy-local, which implements "local" mode and allows Ivy to resolve dependencies packaged as RPMs in addition or instead of dependencies from remote artifact repositories.
If apache-ivy is retired then xmvn-connector-ivy can be retired too.
-- Mikolaj Izdebski
java-devel@lists.fedoraproject.org
-
Jerry James -
Mikolaj Izdebski -
Sérgio Basto