Re: Activating a profile if an executable exists on the path?

If you know where the file should be, certainly: path-to-dot-file ... You can specify either or depending on what you want the profile to do > On Oct 1, 2017, at 8:25 PM, Alex

Activating a profile if an executable exists on the path?

I've been using the umlgraph/graphviz/dot as a javadoc extension for a while now and i was wondering how i could support builds on machines whereby graphviz is not installed. I was thinking a profile with some activate rules would do it that would override the javadoc settings. Looking at the

Re: Updating from 3.3.9 to 3.5.0 causing strange unit test failures

after further investigation, it's probably not a maven issue. On Sun, Oct 1, 2017 at 11:15 AM, Alex O'Ree wrote: > I thought i had cleaned that up. One of those, if it's not broke don't fix > it, kind of things. > > > On Sun, Oct 1, 2017 at 10:24 AM, Karl Heinz Marbaise

Re: Updating from 3.3.9 to 3.5.0 causing strange unit test failures

I thought i had cleaned that up. One of those, if it's not broke don't fix it, kind of things. On Sun, Oct 1, 2017 at 10:24 AM, Karl Heinz Marbaise wrote: > Hi, > > On 01/10/17 15:35, Alex O'Ree wrote: >> >> Apache jUDDI PMC here. >> >> I just spent the better part of my

Re: unable to generate site with module-info defined

Thanks; I have filed https://issues.apache.org/jira/browse/MJAVADOC-498 > On Oct 1, 2017, at 4:05 AM, Hervé BOUTEMY wrote: > > ok > > with 3.4, you can see "Error generating maven-javadoc-plugin:3.0.0-M1:javadoc" > you're issue is only indirectly with maven-site-plugin,

Re: Updating from 3.3.9 to 3.5.0 causing strange unit test failures

Hi, On 01/10/17 15:35, Alex O'Ree wrote: Apache jUDDI PMC here. I just spent the better part of my weekend trying to update and revamp some code in Apache jUDDI and ran into a bit of strange situation that is reporting worthy. All of our previous release builds were ran using maven 3.3.9 on

Re: Updating from 3.3.9 to 3.5.0 causing strange unit test failures

Hi, On 01/10/17 15:35, Alex O'Ree wrote: Apache jUDDI PMC here. I just spent the better part of my weekend trying to update and revamp some code in Apache jUDDI and ran into a bit of strange situation that is reporting worthy. All of our previous release builds were ran using maven 3.3.9 on

Updating from 3.3.9 to 3.5.0 causing strange unit test failures

Apache jUDDI PMC here. I just spent the better part of my weekend trying to update and revamp some code in Apache jUDDI and ran into a bit of strange situation that is reporting worthy. All of our previous release builds were ran using maven 3.3.9 on windows with JDK7. I recently switched to

Re: unable to generate site with module-info defined

ok with 3.4, you can see "Error generating maven-javadoc-plugin:3.0.0-M1:javadoc" you're issue is only indirectly with maven-site-plugin, but more directly with maven-javadoc-plugin reproducing this issue is then best done with "mvn javadoc:javadoc", to directly use the offending plugin