Re: doxia and docbook
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 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 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-site-plugin/examples/creating-content.html Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
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.2011 21:16 schrieb "M. Richey" : > > 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 modules to the current build from within my plugin or activate a profile defining these modules. > > Is this possible? How can it be done? Can modules be added to the current build or profiles being activated from a plugin? Any help is appreciated! > > Thanks in advance! > > Regards, > > Maik > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org >
Using Shade to create a full jar (like Spring full jar)
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 defined in the pom because I only want to jarjar the Spring jars. Can I use Shade instead to resolve this? Can I build a pom file of Spring dependencies and use Shade to jar together the Spring jars only and output a pom file that includes dependencies not added to the new jar? Thanks for the help, Jay -- View this message in context: http://maven.40175.n5.nabble.com/Using-Shade-to-create-a-full-jar-like-Spring-full-jar-tp4800558p4800558.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: doxia and docbook
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 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-site-plugin/examples/creating-content.html > > Kind regards > Karl Heinz Marbaise > -- > SoftwareEntwicklung Beratung Schulung Tel.: +49 (0) 2405 / 415 893 > Dipl.Ing.(FH) Karl Heinz Marbaise ICQ#: 135949029 > Hauptstrasse 177 USt.IdNr: DE191347579 > 52146 Würselen http://www.soebes.de > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
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 modules working. Otherwise, the pom versions won't get updated properly. So having modules appear and disappear in profiles breaks that. You can get around this by making sure that all of your profiles are activated whenever you use the release plugin, but I find that fragile. > > What about activating a profile directly (without properties) from within the > execution of my plugin then? I am nearly certain that no plugin can change the reactor content. No calls to plugins happen before the reactor is all set up. > > Regards, > > Maik > > > Original-Nachricht >> Datum: Tue, 13 Sep 2011 15:46:16 -0400 >> Von: Benson Margulies >> An: Maven Users List >> Betreff: Re: Adding modules from within a plugin? > >> 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 exactly is not working properly? >> >> There are documented limitations: I think that the relevant one is >> that you can't activate a profile based on a property value set >> *inside* a POM, only from a -D from command level. >> >> Maik, if you have any idea of ever using the maven-release-plugin, I >> strongly encourage you to find some solution other than changing the >> module list. You can use 'skip' configuration parameters to neutralize >> what happens in unwanted child modules instead. >> >> >> > >> >> > Wayne >> > >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir > belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Why artifact not found on local repository?
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/apis/google-api-services-discovery/v1-1.2.0-beta/google-api-services-discovery-v1-1.2.0-beta.pom
from [jboss-public-repository-group
(https://repository.jboss.org/nexus/content/groups/public-jboss/,
releases+snapshots), central (http://repo1.maven.org/maven2, releases)]
But the file exists: if I issue an ls command I get both .pom and .jar files
form local repository exactly with the shown name.
Any idea of what is going on?
___
Listing
mvn -X --offline compile
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /home/franco/programs/apache-maven-3.0.3
Java version: 1.6.0_23, vendor: Sun Microsystems Inc.
Java home: /home/franco/programs/java/jre1.6.0_23
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.35-30-generic-pae", arch: "i386", family:
"unix"
[INFO] Error stacktraces are turned on.
[DEBUG] Reading global settings from
/home/franco/programs/apache-maven-3.0.3/conf/settings.xml
[DEBUG] Reading user settings from /home/franco/.m2/settings.xml
[DEBUG] Using local repository at /home/franco/.m2/repository
[DEBUG] Using manager EnhancedLocalRepositoryManager with priority 10 for
/home/franco/.m2/repository
[INFO] Scanning for projects...
[DEBUG] Extension realms for project
net.cbsolution:ps.srvcr2:jar:1.0-SNAPSHOT: (none)
[DEBUG] Looking up lifecyle mappings for packaging jar from
ClassRealm[plexus.core, parent: null]
[DEBUG] === REACTOR BUILD PLAN
[DEBUG] Project: net.cbsolution:ps.srvcr2:jar:1.0-SNAPSHOT
[DEBUG] Tasks: [compile]
[DEBUG] Style: Regular
[DEBUG]
===
[INFO]
[INFO]
[INFO] Building ps.srvcr 1.0-SNAPSHOT
[INFO]
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] Lifecycle default -> [validate, initialize, generate-sources,
process-sources, generate-resources, process-resources, compile,
process-classes, generate-test-sources, process-test-sources,
generate-test-resources, process-test-resources, test-compile,
process-test-classes, test, prepare-package, package, pre-integration-test,
integration-test, post-integration-test, verify, install, deploy]
[DEBUG] Lifecycle clean -> [pre-clean, clean, post-clean]
[DEBUG] Lifecycle site -> [pre-site, site, post-site, site-deploy]
[DEBUG] === PROJECT BUILD PLAN
[DEBUG] Project: net.cbsolution:ps.srvcr2:1.0-SNAPSHOT
[DEBUG] Dependencies (collect): []
[DEBUG] Dependencies (resolve): [compile]
[DEBUG] Repositories (dependencies): [jboss-public-repository-group
(https://repository.jboss.org/nexus/content/groups/public-jboss/,
releases+snapshots), central (http://repo1.maven.org/maven2, releases)]
[DEBUG] Repositories (plugins) : [jboss-public-repository-group
(https://repository.jboss.org/nexus/content/groups/public-jboss/,
releases+snapshots), central (http://repo1.maven.org/maven2, releases)]
[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-resources-plugin:2.4.3:resources
(default-resources)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${encoding}
${maven.resources.escapeWindowsPaths}
${maven.resources.includeEmptyDirs}
${maven.resources.overwrite}
[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-compiler-plug
Re: doxia and docbook
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-site-plugin/examples/creating-content.html Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
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 > Datum: Tue, 13 Sep 2011 15:46:16 -0400 > Von: Benson Margulies > An: Maven Users List > Betreff: Re: Adding modules from within a plugin? > 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 exactly is not working properly? > > There are documented limitations: I think that the relevant one is > that you can't activate a profile based on a property value set > *inside* a POM, only from a -D from command level. > > Maik, if you have any idea of ever using the maven-release-plugin, I > strongly encourage you to find some solution other than changing the > module list. You can use 'skip' configuration parameters to neutralize > what happens in unwanted child modules instead. > > > > > > > Wayne > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
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 execution of my plugin which activates a profile then. Regards, Maik Original-Nachricht > Datum: Tue, 13 Sep 2011 14:37:42 -0500 > Von: Wayne Fay > An: Maven Users List > Betreff: Re: Adding modules from within a plugin? > > 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 > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurück-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
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 exactly is not working properly? There are documented limitations: I think that the relevant one is that you can't activate a profile based on a property value set *inside* a POM, only from a -D from command level. Maik, if you have any idea of ever using the maven-release-plugin, I strongly encourage you to find some solution other than changing the module list. You can use 'skip' configuration parameters to neutralize what happens in unwanted child modules instead. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Adding modules from within a plugin?
> 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Adding modules from within a plugin?
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 modules to the current build from within my plugin or activate a profile defining these modules. Is this possible? How can it be done? Can modules be added to the current build or profiles being activated from a plugin? Any help is appreciated! Thanks in advance! Regards, Maik -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
doxia and docbook
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
Re: Difference between build/extensions/extension and build/plugins/plugin/extensions?
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/extensions/extension is rather used to include jars (non-plugin) that declares additional components. In the example you gave, the plugin and the artifact declared in build/extensions/extension don't have the same coordinates, so they have likely different purposes. Vincent On Wed, Sep 7, 2011 at 17:13, Andreas Sewe < s...@st.informatik.tu-darmstadt.de> wrote: > Hi all, > > what is the difference between build/extensions/extension and > build/plugins/plugin/**extensions set to true. It seems somewhat redundant > (yes, I could use a property) to have to specify the plugin's version twice, > as in this snippet from the maven-archetype-plugin's site: > > >> ... >> maven-archetype >> ... >> >> >> >>org.apache.maven.**archetype >>archetype-**packaging >>2.1 >> >> >> >> >> >> >> org.apache.maven.**plugins >> maven-archetype-**plugin >> 2.1 >> >> >> >> >> >> > > And on a similar note: Are extensions "plugin-managed" or do I really have > to repeat the version twice in the above? The output of help:effective-pom > seems to suggest that extensions are not managed: if I leave out > build/extensions/extension/**version in the above, the effective POM also > lacks the version element. > > I hope that somebody can enlighten me. > > Best wishes, > > Andreas > > --**--**- > To unsubscribe, e-mail: > users-unsubscribe@maven.**apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
maven-assembly-plugin, built-in/shared descriptors and custom classifier
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 overridden, then it impacts use of custom shared descriptors ( http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html ) classifier seems to have been deprecated in favor of using assembly id but one can not specify assembly id of built-in or shared descriptors. Is there maybe a workaround to inherit somehow built-in or shared assembly descriptor? I know about component descriptors, but AFAIK assembly descriptors (built-in or shared) can not be referenced as component descriptors. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Non-resolvable parent POM - Maven 3 ignores mirror specification in settings.xml (for site generation)
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 no local POM @ line 5, column 10 The parent is a corporate parent pom declared in the project: com.acme.maven acme-pom-base 21.0 And the mirror specification in settings.xml (the configuration prevents any call to external repository effecitvelly): artifactory Artifactory http://repository.intranet.acme.com/artifactory/empty/ external:*,!local-repo1,!local-repo2 Where local-repo1 and local-repo2 are repositories defined in setttins.xml. It looks that during site generation Maven does not search for parent in all repositories defined in the settings.xml (local-repo1 and local-repo2). Perhaps, Maven tries to access central directly, and the rule external:* is applied -> redirect request to the http://repository.intranet.acme.com/artifactory/empty/. The error is thrown even if parent pom already exists in the local repository. And only site generation is affected, the project can be build (mvn install) without problems. Maven 2 is also error free. m-site-p version is: 3.0. maven version is: 3.0.3 Should I open bug issue? And where: m-site-p or maven core? -- Marcin Kuthan Maven For Enterprise - http://code.google.com/p/m4enterprise/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
