Re: [VOTE] Send IvyDE to the Apache Attic
+1 Martijn Op 20/11/2023 om 04:50 schreef Jaikiran Pai: On 19/11/23 11:09 pm, Stefan Bodewig wrote: ... So here is the formal vote: I hereby propose to create a board resolution that will send IvyDE to the Apache Attic. +1 -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Send IvyDE to the Apache Attic
On 19/11/23 11:09 pm, Stefan Bodewig wrote: ... So here is the formal vote: I hereby propose to create a board resolution that will send IvyDE to the Apache Attic. +1 -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: [VOTE] Send IvyDE to the Apache Attic
officially recording my own vote On 2023-11-19, Stefan Bodewig wrote: > So here is the formal vote: > I hereby propose to create a board resolution that will send IvyDE to > the Apache Attic. +1 Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[VOTE] Send IvyDE to the Apache Attic
Hi all, within the "Future of Ivy and IvyDE" thread[1] I started about three months ago to me it seemed as if people wouldn't be happy if IvyDE died but I also didn't sense there was a community willing to keep it alive. Consequently I now call for a vote to send IvyDE to the Apache Attic following the rules layed out in https://attic.apache.org/process.html The attic doesn't have to be a dead-end. If there are people who want to fork IvyDE outside of the ASF they are free to (and have always been). Basically it would resolve the Ant PMC of the duty of oversight over the code base. This vote will require either three PMC members to vote +1 to pass or alternatively less than three -1s - but I really hope we don't end up with not getting enough votes at all. If there is any -1 by a PMC member I'm willing to immediately cancel the vote and rediscuss. So here is the formal vote: I hereby propose to create a board resolution that will send IvyDE to the Apache Attic. This vote will stay open at least 72 hours and won't be closed before 2023-11-22 17:30 UTC - likely later. Cheers Stefan [1] https://lists.apache.org/thread/h372vt1ztd6gfmgmfkmqzrksx6fpw97g - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Trying my hands at an ivy-updatesite (was Re: Future of Ivy and IvyDE)
On 2023-09-05, Nicolas Lalevée wrote: > And we tried our best to be opened on how to build and release the > plugin and the updatesite, it is documented [2]. On my machine which > just have Ant and Java installed, I just tried and I have been able to > build of the updatesite with the last release of Ivy without much > effort. Many thanks for the pointer, Nicolas. In my case it immediately stopped with , | eclipse-startup-check: | | BUILD FAILED | /home/stefan/devel/ASF/ivy-updatesite/build.xml:39: An Eclipse install is needed to run the build. Set your Eclipse install dir into the baseLocation property. ` and I haven't got any idea of which version of Eclipse I'd need to install. So I went with 202309 and kept my fingers crossed. At least the build proceeded. https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivy-2.5.2.final_20230817170011/ is what I created. TBH I have no idea what I have created and signed - nor do I have any way of verifying it works. If anybody wants - and is able - to check what I've created, I'd be grateful. Even then I don't really feel comfortable calling for a vote on something I don't even trust myself. Cheers Stefan > [2] https://ant.apache.org/ivy/ivyde/history/latest-milestone/dev.html - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Issues with how Ivy processes maven dependency management dependencies compared to adding a classifier key
Hi Mark first of all please go and read https://lists.apache.org/thread/h372vt1ztd6gfmgmfkmqzrksx6fpw97g I very much doubt you will find any people who know Ivy's internals better than you do (by now) on this list. On 2023-11-17, Kittisopikul, Mark Andrew wrote: > Hello, > At the Howard Hughes Medical Institute Janelia Research Campus, we > encountered an issue with transitive dependencies when using the IJava [1] > Jupyter kernel that uses Apache Ivy for dependency resolution. > When adding the dependency org.janelia.saalfeld.lab.n5-ij [2] Ivy does not > correctly recognize net.imglib2.imglib2 [3] as a compile dependency. This is > because when processing the parent POM (pom-scijava [4]), Ivy only stores > extra information with a groupId__artifactId key without the classifier. > The initial fix I have produced is to modify the key to include the > classifier: groupId__artifiactId__classifierId. I have prototyped these > changes on a Github fork [5]. I would like to discuss how we might upstream > these changes to Apache Ivy. The changes are probably the same as in https://github.com/mkitti/ant-ivy/pull/1/files Before I'd try to understand the changes you've made I'd ask you to back out all changes that are not relevant to what you want to achieve. All changes to whitespace, ordering of imports or changes to the eclipse settings for example as they (1) are just noise when it comes to understanding your changes and (2) may hide changes that are overlooked when a reviewer thinks they can skip the changes as they "are just noise". This is not because I wouldn't trust you but rather because I don't trust myself as a reviewer. We've had more than one changeset in Ant that was big, looked good, and introduced subtle bugs that we overlooked. I vaguely recall having to change some classifier stuff in order to fix a bug a few months ago[A] so I am not surprised there are more issues lurking. Personally I'll be glad to review a PR and merge it - please open a JIRA issue as well. As for upstreaming the patch, even after we merged a PR we'd still have to cut a release. Even if we managed to get enough people interested in voting on that, I still want to point you at the thread linked from the top of the mail. Cheers Stefan [A] https://issues.apache.org/jira/browse/IVY-1642 - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Need help with Ant tests
Hi Claude On 2023-10-01, Claude Warren wrote: > I have been working on RAT-321 [1] and am trying to rework the ant tests > for the new structure. > My goal has been to get all options supported in any of the 3 configuration > interfaces (cli, Ant, Maven) to be supported in the ReportConfiguration > object. I think I have mostly achieved this. > I modified the Ant task to configure the o.a.r.ReportConfiguration and > herein lies my problem. I am not conversant in the internals of ant tasks > and the antunit library. There are 6 tests that fail, they are all in the > report-normal-operations.xml antunit library. [2] They are all commented > out and tagged with "FIXME" so they are easy to find and they broadly fall > into 2 categories: >1. Adding new elements based on either the IHeaderMatcher >orIHeaderMatcher.Builder implementations. >2. Detecting text in the Ant output when it is not sent to a file. > All of these tests work when executed using the BuildFileRule under the > o.a.r.anttasks.ReportTest.[3] > Is there anyone here that can take a look at the tests and see what I did > wrong? I would greatly appreciate it. Sorry for the delay. I have written the RAT Ant task a very long time ago and also written the tests. Unfortunately I no longer spend as much time on open source software as I did a few years ago, so it took quite some time to respond. I'll try to carve out some time to look into your changes an what to do about the tests in the coming days. Many thanks for trying to maintain the Ant integration of RAT. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
