Andy, Alexander, What is the gap between the custom language and the annotations? Has anyone proposed a tool to convert AsspectJ to annotations?
Tim On Thu, Apr 29, 2021 at 7:52 AM Alexander Kriegisch < alexan...@kriegisch.name> wrote: > Thanks all for your encouragement. > > Concerning "AspectK", I think that it is not going to happen anytime > soon or at all, given the developer resource situation and my currently > modest level of knowledge, especially concerning parsing, AST, > compilation. > > What makes it so hard to keep AspectJ up to date is the native syntax > support. AJC is an ECJ fork. Imagine a parallel Kotlinc fork on top of > that. Getting rid of native syntax altogether, only supporting > annotation-style AOP, would be the easiest to maintain according to > Andy. This is not even considering keeping IDE support up to date. For > Eclipse this is done in AJDT, which is a nightmare to maintain, and for > IntelliJ JetBrains implemented it themselves, but never really finished > the job IMO. But then we would lose both the elegant, expressive syntax > and several features which just do not work in @AspectJ style. Anyway, > focusing on the present situation, you do have options to apply aspects > to Kotlin code, using LTW or binary weaving. If Andy ever gets around to > supporting invokedynamic (think: intercepting lambdas), I think that it > would be a step forward for all of CTW, LTW and binary weaving. > > Bottom line: We need to prioritise. I am doing this for fun, so I am > going to do whatever strikes me as interesting and is within the range > of my current capabilities. I might be able to do more in the future, if > by some miracle Andy ever gets bored of his awesome daytime job and has > time to mentor me. ;-) > > Anyway, we sent a message that AspectJ is far from dead, even though not > exactly running like a race horse. > > Cheers > -- > Alexander Kriegisch > https://scrum-master.de > > > Matthew Adams schrieb am 28.04.2021 21:06 (GMT +07:00): > > > Awesome. I'm also a long-time AspectJ user and occasional supporter > (I'm a > > former SpringSource consultant from way back 2007-2008 and founding > > co-committer of Spring Data Cassandra). > > > > I've been working primarily in the Node.js space for the last 7+ years, > but > > have been keeping a little bit of an eye on developments in the Java > ecosystem. > > Kotlin has really caught my eye, and, after having been spoiled in Java > for so > > many years with AspectJ, I was hoping that I'd see first-class support > for AOP > > in Kotlin via "AspectK" or something, since, by the time we ceased Java > > development, ajc was our only compiler, if you can believe it. > > > > I know this is a lot to ask because I've felt Andy's been way > underresourced > > over the years and have truly feared the day Andy decides to hang it up, > but > > I'd really like to see a new compiler akc, similar to ajc, only for > Kotlin. > > > > Honestly, I don't understand why SpringSource/Pivotal/... doesn't > allocate more > > resources to such a crucial and awesome technology as AspectJ. Further, > given > > Spring's substantial adoption of Kotlin, why more effort hasn't gone > into a > > sister/twin effort for AOP in Kotlin (what I call "AspectK"). > > > > What will it take for AspectK to be recognized as necessary and resources > > allocated to it? > > > >> On Apr 28, 2021, at 2:43 AM, Alexander Kriegisch < > alexan...@kriegisch.name> > >> wrote: > >> > >> Hello AspectJ users community! > >> > >> You might know me as a fellow user who over the years asked or answered > >> questions, raised bugs or commented here. I also answer questions about > >> AspectJ and Spring AOP on StackOverflow, in order to unburden Andy > >> Clement as a maintainer from user support a little bit. > >> > >> Somewhat new is my role as an active contributor to the code bases of > >> ** AspectJ, > >> ** AJDT (AspectJ Development Tools) for Eclipse IDE, > >> ** AspectJ Maven Plugin. > >> > >> It all started with reading source code because I did not understand > >> something or wanted to know how to fix a tiny issue, then baby step by > >> step it somehow escalated into adding Java 15+16 support to AspectJ, > >> Java 13-16 support to AspectJ Maven and making AJDT work with the new > >> AspectJ version in its belly on Eclipse IDE 4.19 (2021-03). All of this > >> stuff is available for you to test, feedback is welcome. As I do not > >> have commit and deploy rights on Eclipse projects (yet), I just set up a > >> little Maven repository on my domain aspectj.dev. > >> > >> More details in this comment I posted on a recently merged GitHub pull > >> request: > >> > >> https://github.com/eclipse/org.aspectj/pull/41#issuecomment-826066012 > >> > >> Best regards > >> -- > >> Alexander Kriegisch > >> https://scrum-master.de > >> _______________________________________________ > >> aspectj-users mailing list > >> aspectj-users@eclipse.org > >> To unsubscribe from this list, visit > >> https://www.eclipse.org/mailman/listinfo/aspectj-users > > > > _______________________________________________ > > aspectj-users mailing list > > aspectj-users@eclipse.org > > To unsubscribe from this list, visit > > https://www.eclipse.org/mailman/listinfo/aspectj-users > > > > > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/aspectj-users >
_______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/aspectj-users
