Hi all,
I've a strange problem when I try to activate more than one profile
simultaneously, maven seems
to activate only the last one.
For example, I've two profiles one named ant-archive, and one other named
ant-common-archive.
If I type mvn -Pant-archive package or mvn -Pant-common-archive
Hi, all
There is a behavior of maven that I don't understand.
If I put a non relative href for menu item of the site.xml file, like this :
menu name=test-menu
item name=Fractal Homepage href=http://test-url.com/; /
/menu
I don't know why, when I generate the site (mvn site),
the href is
Hi all
I'm using maven filters to generate a build.xml file.
As everybody know build files have the same ${property} syntax.
So I would like to prevent overwriting of non wanted properties
by specifying in my assembly only the properties I want to overwrite.
something like this :
file
Hi,
It seems that the ${artifactId} ${version} etc...placed in the directory
tag
of fileset of a module set of a assembly makes a reference to the main .pom
and not to the current module .pom.
e.g
my main .pom which defines the maven-assembly-plugin has a version = 1.0
the fractal-libraries
-A.
Bye.
Yann
Yann Davin wrote:
Hi all,
I'm trying to generate my multi-modules website with the site:stage
command
from my root level. It's work,
but by default the default website path of a module-A which has a parent-A
which has a parent-B will be
stageDirectory/parent-B/parent-A/module
Hi all,
I'm trying to test doxia as a alternative to the docbkx maven plugin. But
when
i try to launch simply the example I've the followed error :
java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/site/manager/SiteModuleManager
at java.lang.Class.getDeclaredFields0(Native
:
What did you try to launch?
Please provide us with more details about what you are trying to do.
Yann Davin wrote:
Hi all,
I'm trying to test doxia as a alternative to the docbkx maven plugin. But
when
i try to launch simply the example I've the followed error
Hi all,
I'm trying to generate my multi-modules website with the site:stage command
from my root level. It's work,
but by default the default website path of a module-A which has a parent-A
which has a parent-B will be
stageDirectory/parent-B/parent-A/module-A
I would like to suppress this
