Suggestions for improvements of current maven version

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Suggestions for improvements of current maven version

diku gabriell
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:
<dependencies>
    <scope value=”runtime”>
   <dependency>
<groupId>…</groupId>
<artifactId>…</artifactId>
<version>…</version>
   </dependency>
    </scope>
<!—this is the default scope-->
    <scope>
<dependency>
<groupId>…</groupId>
<artifactId>…</artifactId>
<version>…</version>
   </dependency>
    </scope>
<scope value=”test”>
<dependency>
<groupId>…</groupId>
<artifactId>…</artifactId>
<version>…</version>
   </dependency>
 <scope>
</dependencies>

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 [hidden email] for more details.

Sent from Mail for Windows 10

Reply | Threaded
Open this post in threaded view
|

Re: Suggestions for improvements of current maven version

Paul Hammant
Great suggestion

On Wed, Nov 27, 2019 at 10:37 PM diku gabriell
<[hidden email]> 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:
> <dependencies>
>     <scope value=”runtime”>
>    <dependency>
> <groupId>…</groupId>
> <artifactId>…</artifactId>
> <version>…</version>
>    </dependency>
>     </scope>
> <!—this is the default scope-->
>     <scope>
> <dependency>
> <groupId>…</groupId>
> <artifactId>…</artifactId>
> <version>…</version>
>    </dependency>
>     </scope>
> <scope value=”test”>
> <dependency>
> <groupId>…</groupId>
> <artifactId>…</artifactId>
> <version>…</version>
>    </dependency>
>  <scope>
> </dependencies>
>
> 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 [hidden email]
> for more details.
>
> Sent from Mail for Windows 10
>
>