Core & plugins

[Lukasz Lenart <lu...@apache.org>]

Hi,

After latest burnings around plugins I wonder if it makes sense to
separate them from the Core and release them when required. It would
be the same approach as for Maven plugins, each one with a dedicated
version.

The problem I see is how to handle dependencies by users - right now
they have to define just one {struts2.version} in their pom.xml to
keep everything up-to-date. With plugins living their own release
cycle they will have to specify each version separately.


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: Core & plugins

[Stefaan Dutry <sd...@apache.org>]

> Hi,
>
> After latest burnings around plugins I wonder if it makes sense to
> separate them from the Core and release them when required. It would
> be the same approach as for Maven plugins, each one with a dedicated
> version.
>
> The problem I see is how to handle dependencies by users - right now
> they have to define just one {struts2.version} in their pom.xml to
> keep everything up-to-date. With plugins living their own release
> cycle they will have to specify each version separately.
>


I think that would make sense, because not every release requires a
change to every plugin.
So they could remain the same version when there's no change.

Given that there is a BOM project i don't think handling dependencies
should be a problem, since they can just specify that single BOM
dependency inside the dependencyManagement node.
It would just require the BOM project to be kept up to date at every
plugin release.

However i do see some possible problems.
- people not using the BOM need to keep up with all versions of all
plugins themselves for breaking changes
- updating struts version could become more effort resulting in more
people not updating and vulnerabilities not being addressed.
- Documenting compatible versions for every plugin for all releases is
going to be a challenge.

So i don't know think the benefits outweigh the downsides.

Regards,
Stefaan Dutry (sdutry)<div
id="DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2"><br /> <table
style="border-top: 1px solid #D3D4DE;">
	<tr>
      <td style="width: 55px; padding-top: 18px;"><a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank"><img
src="https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif"
alt="" width="46" height="29" style="width: 46px; height: 29px;"
/></a></td>
		<td style="width: 470px; padding-top: 17px; color: #41424e;
font-size: 13px; font-family: Arial, Helvetica, sans-serif;
line-height: 18px;">Virusvrij. <a
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail"
target="_blank" style="color: #4453ea;">www.avast.com</a> 		</td>
	</tr>
</table>
<a href="#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2" width="1" height="1"></a></div>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: Core & plugins

[Christoph Nenning <Ch...@lex-com.net>]

> Hi,
> 
> After latest burnings around plugins I wonder if it makes sense to
> separate them from the Core and release them when required. It would
> be the same approach as for Maven plugins, each one with a dedicated
> version.
> 
> The problem I see is how to handle dependencies by users - right now
> they have to define just one {struts2.version} in their pom.xml to
> keep everything up-to-date. With plugins living their own release
> cycle they will have to specify each version separately.
> 
> 


I would prefer to keep it as is. Because of the version number nightmare 
that would be introduced the other way. We would need to keep a 
compatibility matrix to state which versions of core and all plugins are 
compatible, and even which plugin versions are compatible to each other 
(if they interact).

I also see the benefit of being able to release a single plugin on it's 
own but I think in the end it causes more trouble.


Regards,
Christoph

This Email was scanned by Sophos Anti Virus