Re: how to access development versions of non-plugin components from the repo?
Brett, You need to change the element in whichever plugin or project needs to use it, then reinstall them. Sorry for my dense-ness here but I do not understand this. I am playing with the javadoc plugin which is invoked by the maven-report-impl code. I have built dev versions of both. The javadoc plugin I am able to use no problem by including a ref to the dev SNAPSHOT version in in my project that I am test the javadoc:javadoc goal in, say "my-app". But when I put a dependency in my-app for maven-report-impl, maven still seems to select the 2.0 version. I will include the -X output for running in my-app the "mvn -X javadoc:javadoc" goal (ignore my debug stmts in the javadoc plugin) and also my pom for my-app. You can see that it selects maven-report-impl 2.0 for runtime after claiming at the top that it will select maven-report-impl 2.0.3-SNAPSHOT... Am I using the dependency right in here? When you said above "You need to change the element in whichever plugin or project needs to use it, then reinstall them" what does "them" refer to? Chris * * * my-app/pom.xml http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 com.mycompany.app my-app jar 1.0-SNAPSHOT Maven Quick Start Archetype http://maven.apache.org junit junit 3.8.1 test org.apache.maven.reporting maven-reporting-impl 2.0.3-SNAPSHOT runtime Maven Snapshots http://snapshots.maven.codehaus.org/maven2/ true false Maven Snapshots http://snapshots.maven.codehaus.org/maven2/ true false org.apache.maven.plugins maven-javadoc-plugin 2.0-beta-4-SNAPSHOT org.apache.maven.plugins maven-javadoc-plugin 2.0-beta-4-SNAPSHOT org.codehaus.mojo jdepend-maven-plugin 2.0-beta-1-SNAPSHOT * * * -X output * * * + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Chris\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'C:\PROGRA~1\Apache\MAVEN-~1.2\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'javadoc'. [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository Maven Snapshots [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] maven-javadoc-plugin: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: null:maven-javadoc-plugin:maven-plugin:2.0-beta-4-SNAPSHOT [DEBUG] maven-javadoc-plugin: using locally installed snapshot [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [javadoc:javadoc] [INFO] [DEBUG] com.mycompany.app:my-app:jar:1.0-SNAPSHOT (selected for null) [INFO] snapshot org.apache.maven.reporting:maven-reporting-impl:2.0.3-SNAPSHOT: checking for updates from Maven Snapshots [DEBUG] repository metadata for: 'snapshot org.apache.maven.reporting:maven-reporting-impl:2.0.3-SNAPSHOT' could not be found on repository: Maven Snapshots [DEBUG] Skipping disabled repository central [DEBUG] maven-reporting-impl: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: null:maven-reporting-impl:jar:2.0.3-SNAPSHOT [INFO] snapshot org.apache.maven.reporting:maven-reporting:2.0.3-SNAPSHOT: checking for updates from Maven Snapshots [DEBUG] repository metadata for: 'snapshot org.apache.maven.reporting:maven-reporting:2.0.3-SNAPSHOT' could not be found on repository: Maven Snapshots [DEBUG] Skipping disabled repository central [DEBUG] maven-reporting: using locally installed snapshot [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven.reporting:maven-reporting:pom:2.0.3-SNAPSHOT [INFO] snapshot org.apache.maven:maven:2.0.3-SNAPSHOT: checking for updates from Maven Snapshots [DEBUG] repository metadata for: 'snapshot org.apache.maven:maven:2.0.3-SNAPSHOT' could not be found on repository: Maven Snapshots [DEBUG] Skipping disabled repository central [DEBUG] maven: using locally installed snapshot [DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.3-SNAPSHOT (selected for runtime) [DEBUG] commons-validator:commons-validator:jar:1.1.4 (selected for runtime) [DEBUG] oro:oro:jar:2.0.7 (selected for runtime) [INFO] snapshot org.apache.maven:maven-project:2.0.3-SNAPSHOT: checking for updates from Maven Snapshots [DEBUG] repository metad
how to access development versions of non-plugin components from the repo?
Brett, > Building those libraries requires all the other Maven libraries - run > mvn install from the top level of "components/branches/maven-2.0.x". I did that and it all seemed to build ok. E.g., .\.m2\repository\org\apache\maven\reporting\maven-reporting-impl\2.0.3-SNAPSHOT go created. But when I run maven it seems to use an older version, to wit: [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven.reporting:maven-reporting:pom:2.0 [DEBUG] org.apache.maven.reporting:maven-reporting-impl:jar:2.0 (selected for runtime) How can I stimulate maven to use the SNAPSHOT version from the repo. If it was a plugin I'd just name it in but how to do this for a non-plugin component? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changing names of individual reports?
Brett, Please make a feature request for this feature. Done: Provide mechanism to change names of project (and possibly other) reports, etc. in site --- Key: MSITE-87 URL: http://jira.codehaus.org/browse/MSITE-87 Project: Maven 2.x Site Plugin Type: New Feature Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site/apidocs/apidocs/index.html of zero length (was Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?)
Brett, Right! Yes, I get the empty file too. I thought the problem was with apidocs/index.html which is fine. OK we are on the same page now - yeah! So just to repeat myself: 1) the site/apidocs/apidocs/... structure should not be created; and 2) index.html should not be zero-length These issues are probably related... Chris PS - Can you give me some clues on how to build maven-reporting/maven-reporting-impl so I can play along at home? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
site/apidocs/apidocs/index.html of zero length (was Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?)
Brett, I'm using a stock Maven 2.0.2 with javadoc installed. Does it work under the site? Using javadoc:javadoc? Don't let my subject confuse you and to that end I am changing it. My original message asked about the directory structure (which I am sorta no longer worried about) _AND_ also about javadoc:javadoc generating a zero-length apidoc/index.html file. It is the latter that I am investigating now... So pick any project you have, mvn clean to get rid of all, then mvn javadoc:javadoc. What I see (and you should see) after this is: ./target/site/apidocs/ | |-- apidocs/ | |-- index.html of zero-length | |-- com/ | |-- css/ | |-- images/ | |-- resources/ | |-- rest of javadoc html, stylesheet, etc. files I think all is expected here except the fact that a second apidocs/ directory is created and in it a zero-length index.html file is created, yielding this zero-length file: ./target/site/apidocs/apidocs/index.html - apidocs/ should not be created inside of apidocs/ - and a zero-length index.html should not be created (I think...)' Hence my interest in that method that returns "apidocs/index.html"... Chris PS - I tried building maven-reporting/maven-reporting-impl the same way as a plugin to miserable failure... Is this done a different way? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?
Brett,
Both have been fixed in the plugin's SVN. I believe the empty index
was already fixed in the previous release of the javadoc plugin.
I tried downloading, building and running the latest javadoc plug-in
from SVN and I am still seeing the zero-length apidocs/index.html in my
test environment. My test env is just the rebuilt javadoc plugin along
with snapshots of all else (i.e., I am not building all of maven and its
plugins from src, just the javadoc plugin). I don't think the javadoc
plugin is creating the zero-length file. I run the same javadoc command
as the plugin generates and it generates what you'd expect and not the
zero-length puppy. I know I am using the built plugin because I
instrumented it with some debug stmts that are getting executed.
I see a method in JavadocReport that looks interesting and I was
wondering if you give me a clue or three about its use and then I could
debug further:
/**
* @see org.apache.maven.reporting.MavenReport#getOutputName()
*/
public String getOutputName()
{
return "apidocs/index";
}
Also are there other related Maven or plugin sources that I should build
to test this with. I presume that you aren't seeing it and your
environment is probably more bleeding edge.
Thanks in advance.
Chris
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: changing names of individual reports?
Brett, I think a good general solution would be to allow you to feed overriding resources to the site plugin, and to document the properties used to internationalise the various pieces of text so that you can customise the site via that. WDYT? My Maven foo is not strong enough to give you meaningful commentary on this. Offhand though it sounds good to me. Please make a feature request for this feature. Will do. Which component are we talking about here. I will presume the site plug-in unless I hear otherwise. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: changing names of individual reports?
Allan, I think if you would change the artifactId in their pom. Why would you want to do that anyway? Two reasons... The first one is that I was trying to make a Maven2-generated site look "close" to a Maven1-generated site and these reports had different names between 1 and 2. The second is that there is a lot of inconsistency between the names and if you're an anal perfectionist (like I can be at times), you'd want more consistency. Just consider these names below: # Project Reports * Changes Report Plugin Says "plug-in"... only one that does... * JavaDocs * Maven Surefire Report Says "report"... only one that does... redundant with "Reports" in "Project Reports" * Source Xref I've also seen other report titles that are in lower case also, while these above are in upper case. Hey it's not really a big deal just inconsistency drives me nuts! Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?
Brett, Another post gave me the clue as to what I was doing wrong... In: 3) changed pom to call for new plugin ala: org.apache.maven.plugins maven-javadoc-plugin maven-javadoc-plugin-2.0-beta-4-SNAPSHOT I should have version "2.0-beta-4-SNAPSHOT" not what I specified above. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?
Brett, Both have been fixed in the plugin's SVN. I believe the empty index was already fixed in the previous release of the javadoc plugin. I wanted to try testing this so I tried to download and build from src... Having some trouble with Maven finding my newly built plugin... Can I review the steps I took with you to see if you see anything obviously wrong? 1) got src from http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin 2) built using mvn install. jars and what-not were created in ---\.m2\repository\org\apache\maven\plugins\maven-javadoc-plugin\2.0-beta-4-SNAPSHOT\ to-wit: - maven-javadoc-plugin-2.0-beta-4-SNAPSHOT (jar) - maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.pom - maven-metadata-local - maven-metadata-snapshots And in that higher level dir: ---\.m2\repository\org\apache\maven\plugins\maven-javadoc-plugin the file maven-metadata-local was created and reads: org.apache.maven.plugins maven-javadoc-plugin 2.0-beta-4-SNAPSHOT 2.0-beta-4-SNAPSHOT 2.0-beta-4-SNAPSHOT 20060209195302 I think all this looks right... 3) changed pom to call for new plugin ala: org.apache.maven.plugins maven-javadoc-plugin maven-javadoc-plugin-2.0-beta-4-SNAPSHOT 4) When I run maven to try to use this newly built artifact ala "mvn javadoc:javadoc" I get the following error: [ERROR] BUILD ERROR [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-javadoc-plugin Version: maven-javadoc-plugin-2.0-beta-4-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-javadoc-plugin:pom:maven-javadoc-plugin-2.0-beta-4-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) Does anything jump out at you here that I am doing wrong? (I'm still pretty new at this...) Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
changing names of individual reports?
I am generating some via the site goal. I get these as expected: # Project Reports * Changes Report Plugin * JavaDocs * Maven Surefire Report * Source Xref Is there a way to change the names of these in the resulting site? For example if I wanted "Maven Surefire Report" to be "Unit Test Report", is that possible? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Where are Maven2 command line args documented?
KC, Have you tried: mvn -help Yeah I had... I was hoping for a more detailed description. Especially around the area of the update-related arguments. Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Where are Maven2 command line args documented?
Where are Maven2 command line args documented? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Different dir structure for javadoc:javadoc vs. site goals - is this expected?
Brett, It's not intended - I fixed it in SVN the other day. Thx for commenting... Does that fix deal with the zero-length index.html as well? Is it available in a "snapshot" (or whatever you call it) plug-in? (When you guys say "fixed in SVN" it would be nice to know if it was Maven itself or a particular plugin so that if someone wants to d/l and build it they know what to get... imho anyway...) Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Different dir structure for javadoc:javadoc vs. site goals - is this expected?
Folks, Using the Maven Quick Start Archetype as a sample, when I run goal "javadoc:javadoc" it yields a directory called target/javadoc/ which inside it looks like this: my-app/target/javadoc/ |-- apidocs/ | |-- index.html (zero-length!) |-- com/ |-- css/ |-- images/ |-- resources/ |-- index.html (expected javadoc start pages) |-- other expected javadoc html |-- etc. 1. Is what's up with the zero-length apidocs/index.html file? When I use the same sample with goal "site" (and the javadoc plugin in ), it yields a directory structure without javadoc but with these same parts above spread around in other dirs like: my-app/target/site/ |-- apidocs/ | |-- com/ | |-- resources/ | |-- index.html (expected javadoc start pages) | |-- other expected javadoc html | |-- etc. |-- css/ |-- images/ |-- other maven project info reports 2. Is this the expected output directory structure for the javadoc? Thx in advance for any help on this? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
trouble getting some M1 navigation.xml to work in M2 site.xml
I'm having trouble getting Maven 1 features on the site to work in Maven 2 (I am using site.xml in M2 as opposed to the navigation.xml from M1). I know it's finding my site.xml because other changes to it are showing up... 1) Cannot get "external link" and "open in a new window" icons to work... On page http://maven.apache.org/maven-1.x/reference/plugins/xdoc/reference/navfile.html in the Menu section it notes: To open a link in a new window, use the "target" attribute. For example, for a menu item: XDoc automatically adds the "Opens in a new window" icon and "New Window" tooltip to links with the "target" attribute. XDoc also automatically adds the "External Link" icon and tooltip to links referring to external sites (actually, any absolute url). This is not working for me in Maven 2 (i.e., the icons are not getting added). Is this a known issue or maybe someone has hints for me? 2) Cannot get to work... I add the same footer definition I had in my navigation.xml for M1 into my site.xml: http://sourceforge.net/projects/xxx";> http://sourceforge.net/sflogo.php?group_id=118374"; border="0" alt="sf logo"/> Inside the body... and the create site does not show this footer. Again, is this a known issue or maybe someone has hints for me? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: downloading plug-ins from mojo (org.codehaus.mojo)?
Brain et al, Yes, but if you run it from the command line, you don't > need to put it in the pom. If it is in the pom incorrectly, > then that will cause problems. I tested it on a random > project with nothing in my pom for the plugin and it found > it ok. I did find that if I added this to the POM then I was able to get the jxr plugin automatically by Maven2: org.codehaus.mojo jxr-maven-plugin I was just under the impression as stated earlier that org.codehaus.mojo plug-ins would be found automatically... Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: downloading plug-ins from mojo (org.codehaus.mojo)?
Brian, Herve, Herve wrote: >> it's jxr-maven-plugin, not maven-jxr-plugin : I did the same mistake >> some time ago... The convention is not the same between >> org.apache.maven.plugins (maven-xxx-plugin) and org.codehaus.mojo >> (xxx-maven-plugin). Brian replied: Yes, but if you run it from the command line, you don't need to put it > in the pom. If it is in the pom incorrectly, then that will cause > problems. I tested it on a random project with nothing in my pom for > the plugin and it found it ok. I am not specifying the plug-in at all in the pom. So I'm not sure that your comment Herve is applicable to me :( Brain how can I try to reproduce the test you're running. I will note that I am a new Maven user so this 2.0.2 version is my very first install. Are we talking fresh install in your case as well? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: "predefined" descriptor IDs for assemblies?
Wendy, Last time I looked at it, the documentation was wrong. It's descriptorId, not maven.assembly.descriptorId. OK that worked. Thanks... Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: downloading plug-ins from mojo (org.codehaus.mojo)?
Brian et al, Hrm, works ok for me. What version of maven are you using? Maven 2: C:\blah> mvn --version Maven version: 2.0.2 > Try mvn -U jxr:jxr and see what happens. C:\blah> mvn --version Maven version: 2.0.2 C:\blah> mvn -U jxr:jxr [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'jxr'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-jxr-plugin: checking for updates from central ... [ERROR] BUILD ERROR ... [INFO] The plugin 'org.apache.maven.plugins:maven-jxr-plugin' does not exist or no valid version could be found No joy :( Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
downloading plug-ins from mojo (org.codehaus.mojo)?
Folks, Newbie here so be gentle please ;) I read in http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html in the section entitled "Configuring Maven to Search for Plugins" that: Maven will always search the following groupId's after searching any plugin groups specified in the user's settings: * org.apache.maven.plugins * org.codehaus.mojo So that led me to believe that if I wanted to use the mojo jxr plug-in all I had to do was access it from Maven (2) and since this was a org.codehaus.mojo plug-in, it would be found (I have had no probs getting plug-ins from org.apache.maven.plugins). When I tried a: mvn jxr:jxr I get the following error which leads me to believe this is not working as stated or I am misunderstanding how this works: C:\blah> mvn jxr:jxr [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'jxr'. [ERROR] BUILD ERROR [INFO] The plugin 'org.apache.maven.plugins:maven-jxr-plugin' does not exist or no valid version could be found Any ideas? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
"predefined" descriptor IDs for assemblies?
Folks, I get the impression from the assembly plug-in docs that you can create certain assemblies by using "pre-defined" descriptor IDs. I read this to mean that these descriptor IDs are defaults and I do not need to define them anywhere in my workspace. So when I try: C:\blah> mvn assembly:assembly -Dmaven.assembly.descriptorId=bin I get the following error which has me perplexed (not useful lines deleted): [INFO] [assembly:assembly] [ERROR] BUILD FAILURE [INFO] No assembly descriptors found. Any thoughts about what's causing this or what I am doing wrong? Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
