Re: Accessing child of using property syntax?
${project.licenses[0].url} should do the trick
On Thu, Jul 7, 2016 at 5:15 PM Andreas Sewe <
s...@st.informatik.tu-darmstadt.de> wrote:
> Hi,
>
> I vaguely recall having read the answer to this one years ago, but
> googling and searching through the Apache JIRA didn't turn it up again. :-(
>
> Is it possible to access a single child element of POM
> element using ${} property syntax? I tried
>
> ${project.licenses.1.url}
> ${project.licenses.1.license.url}
> ${project.licenses.license.1.url}
> ${project.licenses.0.url}
> ${project.licenses.0.license.url}
> ${project.licenses.license.0.url}
>
> but to no avail.
>
> Any pointers are greatly appreciated.
>
> Andreas
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
[ANN] doxia-module-textile 1.1.0
Hi, I'd like to announce the release of the Textile module for Doxia in version 1.1.0. The plugin allows users to write content in the Textile markup language. https://github.com/sebhoss/doxia-module-textile To use this module, just reference is as a plugin-dependency for the maven-site-plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId dependencies dependency groupIdcom.github.sebhoss/groupId artifactIddoxia-module-textile/artifactId version1.1.0/version /dependency /dependencies /plugin Release Notes - Added Sink implementation. Comments, issues, patches welcome!
Problem with changes-plugin and announcement-generate
Hey there, when trying to run mvn changes:announcement-generate I get the following stack trace: [INFO] Creating announcement file from JIRA releases... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Couldn't find the release '2.2' among the supplied releases. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find the release '2.2' among the supplied releases. at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Couldn't find the release '2.2' among the supplied releases. at org.apache.maven.plugin.announcement.AnnouncementMojo.getLatestRelease(AnnouncementMojo.java:468) at org.apache.maven.plugin.announcement.AnnouncementMojo.doGenerate(AnnouncementMojo.java:357) at org.apache.maven.plugin.announcement.AnnouncementMojo.doJiraGenerate(AnnouncementMojo.java:590) at org.apache.maven.plugin.announcement.AnnouncementMojo.execute(AnnouncementMojo.java:343) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more So it seems to be looking for a 2.2 release at JIRA and finds nothing even though I have specified fixVersionIDs to point to the 1.0.0 release. I also tried setting onlyCurrentVersion to true but the plugin is still looking for a version 2.2 so I looked into the source and I might know why now: At line 435 in AnnouncementMojo.java[1] there is a call to getVersion() which sets the pomVersion to whatever the call returns. However getVersion() does not return the projects version taken from the POM but the actual version of the plugin itself. That is why it is always looking for a 2.2 release. Later on it compares the found version with the versions from the list of given releases and since I don't have any 2.2 release it returns null and throws the MojoExecutionException. I'm running Maven 2.2.1 and changes-plugin 2.2. I also tried version 2.1 and 2.0 of the plugin but none works. 2.1 looks for its own version number too (in this case reporting that release 2.1 could not be found) and 2.0 talks about the correct version at least (1.0.0) but still says that it cannot find release 1.0.0 among the supplied releases. Has anybody seen this before? What version of the plugin are you guys running to send announcements to this list? Is there anything else I'm missing for it to work? Creating a static jira report along the usual mvn site goal works fine and the jira instance is running properly too. Greets! [1]: http://maven.apache.org/plugins/maven-changes-plugin/xref/org/apache/maven/plugin/announcement/AnnouncementMojo.html#434 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Alternative output directory for javadocs
Hey list! I'm trying to change the output directory for the generated javadocs from /apidocs to something like /api. According to the plugin documentation[1] this is easily achieved by specifying an alternative destDir. However when I'm using the alternative directory (name doesn't matter) the test documentation will not be created giving the following info: [INFO] Skipped Test JavaDocs report, file api/index.html already exists for the English version. The page mentioned at [1] talks about testDestDir as the way to specify the test javadoc location but the configuration option is missing from the javadoc:javadoc and javadoc:test-javadoc goals and thus does not work. Apart from that it labels the generated javadoc report for the main sources as Test JavaDocs but links to the main javadoc at (in my case) /api. So how do you specify alternative output directories for javadocs? Any help on that is appreciated :-) Greets, Sebastian P.S.: I'm using version 2.6.1 of the javadoc plugin and maven version 2.2.1. [1]: http://maven.apache.org/plugins/maven-javadoc-plugin/examples/output-configuration.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Alternative output directory for javadocs
On Fri, 20 Nov 2009 11:48:09 +0100 Sebastian Hoß m...@shoss.de wrote: Hey list! .. So how do you specify alternative output directories for javadocs? Any help on that is appreciated :-) Ah well, I've done it: Using reportSets you can specify the destDir for the javadoc:javadoc goal and the javadoc:test-javadoc goal independently [1]. So I ended up with something like this: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version reportSets reportSet idmain-html/id configuration destDirapi/destDir /configuration reports reportjavadoc/report /reports /reportSet reportSet idtest-html/id configuration destDirtestapi/destDir /configuration reports reporttest-javadoc/report /reports /reportSet /reportSets /plugin That gives me the desired result but I still think that the plugin documentation mentioned in my last mail is wrong.. [1]: http://maven.apache.org/plugins/maven-javadoc-plugin/examples/test-javadocs.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Alternative output directory for javadocs
On Fri, 20 Nov 2009 12:03:26 +0100 Gajo Csaba csaba.g...@cosylab.com wrote: The example from the website worked fine for me, it placed the javadocs into an alternative directory, though maybe I didn't understand what exactly you're trying to archive. Well I simply wanted to change the default javadoc location. Using the example from the website gave me two problems: 1) No test javadocs were generated (no javadocs for the code under /test) 2) The main javadocs were placed in the correct directory but the link pointing to them had the wrong label. It said Test JavaDocs but should have JavaDocs. In my last mail I explained the workaround I found for these problems. Is that any clearer? :-) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: DOAP Plugin issues
On Fri, 25 Sep 2009 11:37:40 +1000 Brett Porter br...@apache.org wrote: Would you mind submitting these to JIRA? http://jira.codehaus.org/browse/MDOAP If you can attach patches to correct them they can be applied and released relatively easily. - Brett Hey, I did not find any guidelines on how to properly produces patches so the ones I've created may need to be reworked (trivial since they change almost nothing). Anyway the issues are at: http://jira.codehaus.org/browse/MDOAP-22 and http://jira.codehaus.org/browse/MDOAP-23 Greets - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
DOAP Plugin issues
Hey,
wanted to try the DOAP plugin[1] but ran into some problems:
1) When you don't specify an developerConnection element inside your
POMs scm element you'll get a NullPointerException as follows:
[INFO] [doap:generate {execution: site}]
[INFO] Generating a pure DOAP file...
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at
org.apache.maven.plugin.doap.DoapMojo.writeSourceRepository(DoapMojo.java:1062)
at
org.apache.maven.plugin.doap.DoapMojo.writeSourceRepositories(DoapMojo.java:1009)
at
org.apache.maven.plugin.doap.DoapMojo.execute(DoapMojo.java:378)
...
The Code in question assumes that the developer connection is always
specified and therefore runs into trouble if it is not. Easiest way
around this is to specify the developer connection or on the code side
replace
String developerConnection = scm.getDeveloperConnection();
writeSourceRepository( writer, developerConnection );
with
String developerConnection = scm.getDeveloperConnection();
if (developerConnection != null) {
writeSourceRepository( writer, developerConnection );
}
This is (of course) just a proposal and it should/must be applied to
the anonymous SCM connection as well or you'll run into trouble again
if someone does not specify that.
2) The plugin documentation is wrong regarding the site integration[2].
It states that you have to add an additional meta tag which hrefs
${project.url}/doap_maven-doap-plugin.rdf
But the plugin calls the final .rdf file doap_${artifactId} so the
above line should read:
${project.url}/doap_${artifactId}.rdf
Apart from that, the plugin rocks!
Greets
[1]: http://maven.apache.org/plugins/maven-doap-plugin/
[2]:
http://maven.apache.org/plugins/maven-doap-plugin/examples/with-site-plugin.html
signature.asc
Description: PGP signature
Re: Just shoot me now and get it over with
Steve Cohen wrote: I am working in a sort of bastardized Eclipse-maven world for months now. I have had for months a M2_REPO variable in Eclipse pointing to a local Maven repository. I know this is not the approved Maven way, but it has worked for me for months without difficulty. As i'm doing the same here ever since - what is the approved Maven way? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
