Re: Suggestions for improvements of current maven version
Without breaking backwards compatibility, it could be a choice for the Pom. Sure that’s an addition, but it it not like the format can never change. It’s an excellent idea. On Thu, Nov 28, 2019 at 5:28 PM Robert Scholte wrote: > As mentioned by Elliotte this won't fit in the current pom model version. > And it will effect dependency resolution. The current order of > dependencies in the pom reflects the order on the classpath. > As long as there are no duplicate classes you should be fine, but the real > world shows us differently. > So with any proposal to regroup dependencies, people should be able to > control the final order. > > thanks, > Robert > On 28-11-2019 14:14:49, Elliotte Rusty Harold wrote: > It's not a bad idea if we were starting from a green field. I'm not > sure how the broader community would feel about changing the structure > of the pom.xml file at this point. These things are very broadly used, > and my gut is that the small improvement would not justify the pain of > the transition. > > On Wed, Nov 27, 2019 at 5:37 PM diku gabriell > wrote: > > > > Hello, > > > > My name is Gabriel Dicu.I am currently working with apache maven and I’d > like to make a suggestion about improving maven dependency structure.In my > opinion, dependencies should be organized better, because is difficult to > spot dependencies for different scopes.I think it is a good approach to > group dependencies by their scopes, thus having parent tags for each scope > like: > > > > > > > > … > > … > > … > > > > > > > > > > > > … > > … > > … > > > > > > > > > > … > > … > > … > > > > > > > > > > In this way you can organize better the dependencies and spot easily the > different scopes.It also can help identify the runtime/compile/etc.. > production dependencies and separate them from testing ones, which can be > less important in many cases. > > > > Thanks for taking the time for reading this, and if this approach can be > feasible, > > I can be reached at the following email address dikugabri...@yahoo.com > for more details. > > > > Sent from Mail for Windows 10 > > > > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > - > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Logging api in plugins
Hi, I'm writing some maven plugins - some for fun and with public code but more maven plugins I'm writing for job in my company. Maven from version 3.1.x use slf4j for logging. But plugin api still use simple logging api org.apache.maven.plugin.logging.Log. It will be useful to have access to more richer feature of logging task. What is the plan for future in this case? - extends org.apache.maven.plugin.logging.Log in order to support slf4j feature - stop using/deprecating org.apache.maven.plugin.logging.Log and use in plugins slf4j api for accesing loger. - maybe something else ... -- Best regards Sławomir Jaranowski
Re: Suggestions for improvements of current maven version
As mentioned by Elliotte this won't fit in the current pom model version. And it will effect dependency resolution. The current order of dependencies in the pom reflects the order on the classpath. As long as there are no duplicate classes you should be fine, but the real world shows us differently. So with any proposal to regroup dependencies, people should be able to control the final order. thanks, Robert On 28-11-2019 14:14:49, Elliotte Rusty Harold wrote: It's not a bad idea if we were starting from a green field. I'm not sure how the broader community would feel about changing the structure of the pom.xml file at this point. These things are very broadly used, and my gut is that the small improvement would not justify the pain of the transition. On Wed, Nov 27, 2019 at 5:37 PM diku gabriell wrote: > > Hello, > > My name is Gabriel Dicu.I am currently working with apache maven and I’d like > to make a suggestion about improving maven dependency structure.In my > opinion, dependencies should be organized better, because is difficult to > spot dependencies for different scopes.I think it is a good approach to group > dependencies by their scopes, thus having parent tags for each scope like: > > > > … > … > … > > > > > > … > … > … > > > > > … > … > … > > > > > In this way you can organize better the dependencies and spot easily the > different scopes.It also can help identify the runtime/compile/etc.. > production dependencies and separate them from testing ones, which can be > less important in many cases. > > Thanks for taking the time for reading this, and if this approach can be > feasible, > I can be reached at the following email address dikugabri...@yahoo.com for > more details. > > Sent from Mail for Windows 10 > -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Maven shade plugin: Duplicate entry in META-INF/service
Hi Maven :), I encountered an exception in my build and I'm not sure if there is something wrong with how I structure tasks in my pom.xml, or there is a room for improvement of the shade plugin. The symptoms are as follows: - mvn install works just fine - mvn deploy fails on 'duplicate error: META-INF/service/' while shading test jar The reason for that seems that it includes the regular (not test-jar), and that one already includes the shaded service. When shading with the other dependencies, this fails. I managed to fix this locally with [1], but I'm not sure if this is a proper fix. I didn't fill any JIRA yet, because I wanted to check with you what the best solution should look like. I also don't know when or how this broke, but at least somewhat in early 2019 this worked. I probably changed the shade plugin to latest version later this year. Thanks for comments and suggestions! Jan [1] https://github.com/apache/maven-shade-plugin/pull/32 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Suggestions for improvements of current maven version
It's not a bad idea if we were starting from a green field. I'm not sure how the broader community would feel about changing the structure of the pom.xml file at this point. These things are very broadly used, and my gut is that the small improvement would not justify the pain of the transition. On Wed, Nov 27, 2019 at 5:37 PM diku gabriell wrote: > > Hello, > > My name is Gabriel Dicu.I am currently working with apache maven and I’d like > to make a suggestion about improving maven dependency structure.In my > opinion, dependencies should be organized better, because is difficult to > spot dependencies for different scopes.I think it is a good approach to group > dependencies by their scopes, thus having parent tags for each scope like: > > > > … > … > … > > > > > > … > … > … > > > > > … > … > … > > > > > In this way you can organize better the dependencies and spot easily the > different scopes.It also can help identify the runtime/compile/etc.. > production dependencies and separate them from testing ones, which can be > less important in many cases. > > Thanks for taking the time for reading this, and if this approach can be > feasible, > I can be reached at the following email address dikugabri...@yahoo.com for > more details. > > Sent from Mail for Windows 10 > -- Elliotte Rusty Harold elh...@ibiblio.org - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
