as documented here:
http://maven.apache.org/plugins/maven-site-plugin/faq.html#How_to_include_a_custom_Doxia_module_like_Twiki
and the directory names and extensions:
http://maven.apache.org/doxia/references/index.html
-Lukas
On 09/13/2011 11:22 PM, Benson Margulies wrote:
No, the folder n
Maybe you could convert your configuration data into a tailored aggregator
pom, containing the optional modules depending on this data. The aggregator
POM could then be used to fire off a maven build.
Not sure if this fits your use case, but it's at least an idea.
Best regards
Ansgar
Am 13.09.20
I have developers that receive the Eclipse 87 error because the classpath is
too long from too many jar files.
I want to recreate a Spring full jar like they used to in 2.5.6, the problem
is that if I used jarjar...I would have to build a pom so that all the
transitive Spring dependencies were def
No, the folder name is 'docbook' for the 'simple-docbook' format,
which is no the same thing as xdoc. It turns out that you have to add
a dependency to the site plugin. I've improved the doc.
On Tue, Sep 13, 2011 at 4:21 PM, Karl Heinz Marbaise wrote:
> Hi,
>>
>> adding src/site/docbook and putti
On Tue, Sep 13, 2011 at 4:12 PM, M. Richey wrote:
>
> Thanks for your reply Benson but what do you mean by saying "using the
> maven-release-plugin"? It is too hard changing the module list, right?
In a multi-module project, when you run the release plugin, you need
to have *all* of your module
I am trying to debug a strange case. The project needs an artifact that is
not on any online repository (a Google library), so I deployed on my local
repository. Still Maven seems unable to find it. and insistes in checking
online:
Verifying availability of
/home/franco/.m2/repository/com/google/a
Hi,
adding src/site/docbook and putting things in it seems to have no
effect. Do I need to add a plugin?
As far as i know you need to call the folder xdoc instead of docbook
add the doxia docbook format there if we are talking about
the maven-site-plugin...
http://maven.apache.org/plugins/maven
Thanks for your reply Benson but what do you mean by saying "using the
maven-release-plugin"? It is too hard changing the module list, right?
What about activating a profile directly (without properties) from within the
execution of my plugin then?
Regards,
Maik
Original-Nachricht
Setting a property in the plugin which is defined to activate a profile won't
activate it because profiles get activated before executing plugins and it is
still problematic activating profiles by properties not getting set via -D at
the beginning. So I couldn't set a property during the execut
On Tue, Sep 13, 2011 at 3:37 PM, Wayne Fay wrote:
>> Because activating a profile by properties is not working properly I would
>> like to either add the modules to the current build from within my plugin
>> or activate a profile defining these modules.
>
> Can you provide more details about what
> Because activating a profile by properties is not working properly I would
> like to either add the modules to the current build from within my plugin
> or activate a profile defining these modules.
Can you provide more details about what exactly is not working properly?
Wayne
Hello everybody,
we have some configuration information in XML files I wrote a plugin for. The
problem is, that depending on that configuration some modules should be
included in that build. Because activating a profile by properties is not
working properly I would like to either add the modul
adding src/site/docbook and putting things in it seems to have no
effect. Do I need to add a plugin?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
As far as I understand, specifying build/plugins/plugin/**extensions set to
true allows plugins embedding a components.xml to actually declare these
components as part of the context. In such case you don't need to repeat the
plugin declaration in the build/extensions/extension section.
The build/
Hello Maven users,
It seems that when using built-in descriptors there is no way to
specify custom classifier for produced assembly. single mojo has
classifier parameter but it is marked as deprecated.
http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html
If this can not be over
Hi,
I can not build project site with Maven 3, the following fatal error is thrown:
[ERROR] [FATAL] Non-resolvable parent POM: Could not find artifact
com.acme.maven:acme-pom-base:pom:21.0 in artifactory
(http://repository.intranet.acme.com/artifactory/empty/) and
'parent.relativePath' points at n
16 matches
Mail list logo
