Before starting the discussions, we want to settle two organizational issues first: - do we have the right group of people? - is email exchange the best medium?
As we are working with different organisations, e-mail is by far the easiest way to push things forward. We might also choose for a github project too. Both questions haven't been answered yet, but I can mention your response. It is up to that group to decide what works best. Thanks Robert -----Original Message----- From: Olivier Lamy <ol...@apache.org> Sent: maandag 21 oktober 2024 09:49 To: Maven Developers List <dev@maven.apache.org> Subject: Re: Module paths and tool integrations Hi Robert, Not sure to understand your response :) My question was, "Why wouldn't this group have open/public visibility?" A lot of people can be interested, not participating directly but maybe reading what is happening. Olivier On Mon, 21 Oct 2024 at 17:36, Robert Scholte <rfscho...@apache.org> wrote: > > The problem we're addressing here is where Maven projects have a different > result when executed via the IDE compared to execution directly via Maven > commandline. > Similar things can happen for Gradle projects. Hence the scope is the > integration of buildtools in IDEs. > This should not be a problem for a library, where the application is > responsible for the right module-path of class-path. > > I'm asking it on the dev-maven list, because it would make sense to have > second maven committer added to that group, not just a PMC member. > > Robert > > -----Original Message----- > From: Olivier Lamy <ol...@apache.org> > Sent: zondag 20 oktober 2024 21:52 > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: Module paths and tool integrations > > Why not a public group especially if the scope is opensoure tools? > And by the way you are mentioning this on a public mailing list. > > On Sun, 20 Oct 2024 at 11:39 pm, Robert Scholte <rfscho...@apache.org> > wrote: > > > Hi Claude, > > > > I don't want the group to be too big. The scope is currently on > > buildtools and IDEs. > > For libraries (you could consider maven-plugins as libraries too), > > there's already a library you can use: plexus-java [1] This should > > be good enough if you have access to all used jars and the root > > module descriptor. > > If not, just let me know. > > > > Thanks, > > Robert > > > > [1] > > https://codehaus-plexus.github.io/plexus-languages/plexus-java/locat > > io > > nmanager.html > > > > -----Original Message----- > > From: Claude Warren <cla...@xenei.com> > > Sent: zondag 20 oktober 2024 00:21 > > To: Maven Developers List <dev@maven.apache.org> > > Subject: Re: Module paths and tool integrations > > > > I would be interested in joining. I have a Java persistence > > annotation library for RDF that is in dire needs of updating and > > having such information would me most helpful. > > > > Claude > > > > On Thu, Oct 17, 2024 at 8:28 AM Robert Scholte > > <rfscho...@apache.org> > > wrote: > > > > > Hi, > > > > > > > > > > > > During Devoxx Nicolai Parlog shared his concerns about how > > > different tools solve the modulepath/classpath in their own way > > > (And he has a > > compliment: > > > Maven does it correct). > > > > > > We were able to talk with the Jetbrains developers that are > > > responsible for Java/Maven integration and we're setting up a > > > small group around this topic. > > > Maybe other tools might join too. > > > > > > I'll be joining on behalf of Maven, but is there somebody else who > > > would like to join? > > > > > > > > > > > > Thanks, > > > > > > Robert > > > > > > > > > > -- > > LinkedIn: http://www.linkedin.com/in/claudewarren > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > > additional commands, e-mail: dev-h...@maven.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For > additional commands, e-mail: dev-h...@maven.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org