[
https://issues.apache.org/jira/browse/DELTASPIKE-1091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15249623#comment-15249623
]
Matej Novotny commented on DELTASPIKE-1091:
-------------------------------------------
We have just incorporated this change into master and 2.3 branches.
ATM we are working on the 2.3.4.release and 3.0.0.Alpha16 will follow shortly
afterwards (within 2 weeks).
Obviously, DS test suite now fails with {{ClassNotFound}} as the dependencies
do not get pulled in.
You can try that yourself, if you build Weld from [2.3.4.Final
tag|https://github.com/weld/core/tree/2.3.4.Final] and then run your test suit
with {{mvn clean verify -PWeld -Dweld.version=2.3.4.Final}}.
DS needs to adjust to this. The simplest way would probably be to introduce
profiles for different Weld versions?
> Weld core BOM update in next 2.3/3.x release
> --------------------------------------------
>
> Key: DELTASPIKE-1091
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1091
> Project: DeltaSpike
> Issue Type: Improvement
> Components: Build
> Reporter: Matej Novotny
> Assignee: Rafael Benevides
>
> The next release of Weld 2.3 (2.3.4.Final) and 3.x (3.0.Alpha16) will also
> contain a refactored weld-core BOM files.
> This is per request in [WELD-2115|https://issues.jboss.org/browse/WELD-2115].
> BOM will no longer provide direct dependencies, but only
> {{dependencyManagement}} section. Looking at deltaspike dependencies, this
> will affect
> [{{parent/code/pom.xml}}|https://github.com/apache/deltaspike/blob/master/deltaspike/parent/code/pom.xml#L355]
> and will require changes.
> The PRs for BOM changes are:
> * 2.3 branch -> https://github.com/weld/core/pull/1295
> * master -> https://github.com/weld/core/pull/1296
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
