Mikael, I am hosting the aspectj.dev update site on my private shared hosting webspace, being the owner of the domain. I never experienced that problem you report and can download the file it complains about by clicking on the link. Sometimes I see GitHub CI builds fail due to temporary glitches in site availability when using dependencies hosted on aspectj.dev. It seems as if my ISP is not doing the very best job there. Can you just try again? I think that should suffice. Eclipse or AJDT should not access sites when running, only when updating.
With regard to Eclipse support, I think the two add-ons discussed here should still work. They do for me, at least. As much as I love IntelliJ IDEA, they are also neglecting AspectJ, so it is not a perfect solution either. But it is working, also in connection with Maven. Syntax highlighting, intelli-sense and some native syntax features could use improvement, though. Also, IDEA sometimes complains about native AspectJ pointcut types used in Spring projects, because despite compiling and running the code just fine, the editor seems to assume that when using Spring, the AOP tool used is always Spring AOP, which only supports a subset of AspectJ features. I think, as long as your leading system is Maven and you use either the dev.aspectj variant of aspectj-maven-pluging - recommended with a bias, because I am maintaining it, but also because it has more features than the Mohjohaus version - or, if sufficient for you, the Mojohaus version, and Maven import in Eclipse and IDEA is still working, you should have no reason to despair or even give up on AspectJ. Cheers -- Alexander Kriegisch https://scrum-master.de Mikael Petterson schrieb am 10.09.2021 14:30 (GMT +02:00): > > Hi Alexander, > > Thanks for information. > Yes resources working with open-source is often a problem. This has been > an issue since we started to use aspectj ( very powerful tool) with our > project. > > > And it seems that without these two: > > > AJDT > m2e connector > > > aspectj will become rather useless in Eclipse ( not blaming you in > anyway). Do you have any advice if we stay with Eclipse. Maybe we need a > different approach on how to use it. Or leave Eclipse for IntelliJ IDEA 🙂 > > We installed it successfully but got this when running ( see below > excerpt) . > > > Does it access sites when running? > > > br, > > > //mike > > > !ENTRY org.eclipse.equinox.p2.core 4 0 2021-09-10 13:53:54.077 > !MESSAGE Provisioning exception > !STACK 1 > org.eclipse.equinox.p2.core.ProvisionException: Artifact not found: > https://aspectj.dev/eclipse/ajdt/419/content.xml.xz. > at > org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:430) > at > org.eclipse.equinox.internal.p2.repository.CacheManager.createCacheFromFile(CacheManager.java:136) > at > org.eclipse.equinox.internal.p2.metadata.repository.XZedSimpleMetadataRepositoryFactory.getLocalFile(XZedSimpleMetadataRepositoryFactory.java:60) > at > org.eclipse.equinox.internal.p2.metadata.repository.XZedSimpleMetadataRepositoryFactory.load(XZedSimpleMetadataRepositoryFactory.java:80) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:63) > at > org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:775) > at > org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:676) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:110) > at > org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:105) > at > org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.doLoad(LoadMetadataRepositoryJob.java:126) > at > org.eclipse.equinox.p2.ui.LoadMetadataRepositoryJob.runModal(LoadMetadataRepositoryJob.java:110) > at > org.eclipse.equinox.internal.p2.ui.sdk.PreloadingRepositoryHandler$1.runModal(PreloadingRepositoryHandler.java:84) > at > org.eclipse.equinox.p2.operations.ProvisioningJob.run(ProvisioningJob.java:190) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) > Caused by: java.io.FileNotFoundException: > https://aspectj.dev/eclipse/ajdt/419/content.xml.xz > at > org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:298) > at > org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:509) > at > org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:463) > at > org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:384) > at > org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:107) > at > org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:166) > at > org.eclipse.equinox.internal.p2.repository.CacheManager.updateCache(CacheManager.java:404) > ... 13 more > !SUBENTRY 1 org.eclipse.equinox.p2.transport.ecf 4 1200 2021-09-10 > 13:53:54.078 > !MESSAGE Artifact not found: > https://aspectj.dev/eclipse/ajdt/419/content.xml.xz. !STACK > 0 > > > ---------------------------------------- > > Från: aspectj-users <aspectj-users-boun...@eclipse.org> för Alexander > Kriegisch <alexan...@kriegisch.name> > Skickat: den 10 september 2021 08:36 > Till: aspectj-users@eclipse.org <aspectj-users@eclipse.org> > Ämne: Re: [aspectj-users] An internal error occurred during: "Computing > additional info". > org/eclipse/jdt/internal/core/hierarchy/HierarchyResolver$AjcClosure1 > > > Hi Mikael. > > What happens if you install a more recent AJDT build from update site > https://aspectj.dev/eclipse/ajdt/419 and m2eclipse-ajdt > from > https://repo.t5.fi/public/eclipse/m2eclipse-ajdt/eclipse-2020-12/? > > Sorry not to offer a more coherent picture with regard to Eclipse plugins, > but both AJDT and the m2e connector are no longer actively maintained by > the AspectJ core team due to lack of developer availability. I am trying > to keep AJDT alive (not really knowing its internals) and another guy is > trying the same with the m2e connector, hence the non-Eclipse update site > URLs. I am not sure at all whether upgrading those two components is going > to fix the problem for you, but you can give it a try. For me it works > fairly well that way, but I do build most of my AspectJ Maven projects > from IntelliJ IDEA these days. > > Regards > -- > Alexander Kriegisch > > https://scrum-master.de > > > Mikael Petterson schrieb am 10.09.2021 09:40 (GMT +02:00): >> >> >> Hi, >> >> >> We are trying to use Eclipse 2021-06 (4.20). We have the following >> plugins installed. >> >> >> Project is a maven multimodule with some modules containing aspects. >> Currently we cannot build in eclipse >> >> >> I have no change to provide a small example since there is dependencies >> between modules and project has company specific info I cannot disclose. >> >> >> Also there is no problem to build using: >> >> >> ‘mvn clean install’ >> >> Any ideas what this problem can be related to? >> >> >> Br, >> >> >> //mike >> >> _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/aspectj-users
