Re: Using Maven 3 with non-standard repository layout (Ivy)

I would guess that Ivy can work a lot better with Maven repositories than Maven can with Ivy repositories. I would investigate a one-shot scripted migration of your Ivy repo to a new Maven repo and force existing publishers to the Ivy repo to configure Ivy to publish to the new Maven repo. But I

Re: Using Maven 3 with non-standard repository layout (Ivy)

Thanks Robert, Digging around led me to this option as well: https://github.com/remis-thoughts/ivy-maven-plugin Doing this isn't ideal, but more of a necessary evil for a proof of concept. Thanks! Tim On Thu, May 24, 2018 at 1:50 PM, Robert Scholte wrote: > Maven 2 and

Re: Using Maven 3 with non-standard repository layout (Ivy)

Maven 2 and Maven 3 both use the same structure for repositories ( which is called a maven2 repo. Yes the name is a bit confusing ). If you want Maven to work with a different kind of repository, e.g. ivy to maven2, you need to use a repository manager. The only one I am aware of that

Re: Problem with exec-maven-plugin

In the interest of providing full reference in the list, I have come up with a workaround to achieve what I want: I list the dependencies in a profile that is active by default, then use another profile to run generate-sources with no dependencies active, like follows: Added in

Re: Maven extension's repository

what is exact URL of 'maven website'? -D On Wed, May 23, 2018 at 5:26 PM, Vivi An wrote: > Hi All, > > I’m using takari extension through extensions.xml file under ./mvn, it > downloads extensions from maven website. Wondering if we can change > configuration in some way so

Executing a script in maven release:perform

Hi all, In our project, we need to build a few native libraries before building the jar. I see that when release:perform is called it will checkout from git in a different workspace and rebuilds all over, this would not trigger the necessary build of the native libraries and hence break release.