This is a long shot, but does anyone happen to know whether anything
changed with respect to pom installation between Maven 3.0 and 3.1? In
particular, I'm seeing in a test of the copy dependencies Mojo that
expanded-snapshot-2.0.pom
is written into the expected location but
expanded-snapshot-2.
On Mon 6 Jul 2020 at 17:48, Hervé BOUTEMY wrote:
> Le lundi 6 juillet 2020, 11:33:05 CEST Mark Derricutt a écrit :
> > Hervé,
> >
> > If you configure IntelliJ (projecting much Mark?) to use Maven
> > 3.7.0-SNAPSHOT as it’s maven version, does that work?
> keeping internal Maven version was givin
Le lundi 6 juillet 2020, 11:33:05 CEST Mark Derricutt a écrit :
> Hervé,
>
> If you configure IntelliJ (projecting much Mark?) to use Maven
> 3.7.0-SNAPSHOT as it’s maven version, does that work?
keeping internal Maven version was giving an impression of working, probably
due to cache given updat
Hervé,
If you configure IntelliJ (projecting much Mark?) to use Maven
3.7.0-SNAPSHOT as it’s maven version, does that work?
I tend to configure my IJ to use my built SNAPSHOT when testing out Maven
releases.
Mark
On 6 July 2020 at 8:21:57 PM, Hervé BOUTEMY (herve.bout...@free.fr) wrote:
What i
I just created a "buildconsumer" branch in Doxia [1] to have a live example of
the new simplified build POM that Maven 3.7.0 will allow [2]
As expected, this branch can't build with Maven 3.6.3, but can with Maven
3.7.0-SNAPSHOT.
And in my favorite IDE, as expected, dependency resolution does no
