browse/MNG-6300
> >
> > Will report back tomorrow (EU TZ)
> > T
> >
> >
> > On Wed, Feb 7, 2024 at 7:48 PM Joseph Leonard <
> > joseph.leon...@alfasystems.com> wrote:
> >
> >> Hi Tamás,
> >> I have created a simple example
from the root works, running
mvn compile from the directory of B does not pick up classes from A's target
directory. it only picks up from M2 repo in that case.
On Thu, Feb 15, 2024 at 11:28 AM Joseph Leonard <
joseph.leon...@alfasystems.com> wrote:
> Hi Sid,
> It will resolve
Hi Sid,
It will resolve the classes directory of module A that will have been populated
during module A's 'compile' build.
Joe
On 2024/02/15 17:50:44 Siddharth Jain wrote:
> Hello,
>
> I am working on a multi-module Maven build. e.g., I have a root directory
> containing 3 sub-projects A, B, C
s out of it.
> To me, it sounds like you want one reactor, but where module-b is "out" and
> 'in", at the same time (within same session)
>
>
> T
>
> On Thu, Feb 8, 2024 at 1:27 PM Joseph Leonard <
> joseph.leon...@alfasystems.com> wrote:
>
>
ou do have an edge between app and module-b.
>
> Or to invert the question: what module-b JAR you want to have included in
> app WAR, when building? The one built, or the one from the local
> repository? If the latter, why are you building it in the first place?
>
> On Thu, Feb
org/jira/browse/MNG-8028 (funny thing, I created
> > this few weeks ago)
> > https://issues.apache.org/jira/browse/MNG-6300
> >
> > Will report back tomorrow (EU TZ)
> > T
> >
> >
> > On Wed, Feb 7, 2024 at 7:48 PM Joseph Leonard <
> > joseph.leon...
off attachments and images) for us to see
> this in action?
>
> Thanks
> T
>
> On Wed, Feb 7, 2024 at 6:29 PM Joseph Leonard <
> joseph.leon...@alfasystems.com> wrote:
>
> > Hi Tamás,
> > We have previously played around a bit with mvnd but not takari
art builder instead?
> https://github.com/takari/takari-smart-builder
>
> (note: smart builder is used by mvnd as well)
>
> The difference between the two can be seen here:
> http://takari.io/book/30-team-maven.html#takari-smart-builder
>
> On Wed, Feb 7, 2024 at 11:50 AM Jos
cause the Build Cache Extension should automatically determine which
> modules need to be built and for which ones previously cached artifacts can
> be used.
>
> Nils.
>
> > Op 6 feb 2024, om 15:11 heeft Joseph Leonard het
> > volgende geschreven:
> >
>
talk
> about here?
> In short: why would App start while ModuleB (upstream dep) is not done?
> Something is fishy here.
>
> T
>
>
> On Tue, Feb 6, 2024 at 11:40 AM Joseph Leonard <
> joseph.leon...@alfasystems.com> wrote:
>
> > Hi all,
> &
Note that my diagram formatting is very hard to read in the default formatting
on this mailing list. If you view my email in 'raw source' then it is easier to
understand!
On 2024/02/06 10:40:14 Joseph Leonard wrote:
> Hi all,
>
> It would be great to get any thoughts on whether the
could benefit from the Maven Build Cache Extension
> (https://maven.apache.org/extensions/maven-build-cache-extension/).
>
> Just my 2 cents.
>
> Nils.
>
> > Op 6 feb 2024 om 11:40 heeft Joseph Leonard het
> > volgende geschreven:
> >
> > Hi all,
> >
at instantiation throughout the
entire Maven build. This would mean, in the simple example above, that the
'App' would always resolves ModuleB from the external repo (regardless of
whether the reactor has built ModuleB or not in a separate 'dependency graph'
in the reactor).
Joseph Leonard
Manager
Alfa
13 matches
Mail list logo
