[m2][javadoc-plugin] currentYear, inceptionYear
Hello,
from:
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html
I see that the default value for the 'botttom' parameter of the javadoc
plugin has the followig value:
Copyright © {inceptionYear}-{currentYear} {organizationName}. All
Rights Reserved.
But I can't figure out how these values are replaced: {inceptionYear},
{currentYear}, {organizationName}
Why isn't it ${propertyName}?
I assume {inceptionYear} is mapped on ${project.inceptionYear} (or
${inceptionYear}) that can be available in the maven POM.
What if it is not present? Where does the value come from, is it current
year?
Same for {currentYear}, is this replaced by maven, or is this part of the
javadoc tool itself?
And what about organizationName ?
Thanks
Re: Log in to Continuum after installation
The first time you start up the web interface, you have to configure some settings. One of them is the Admin password. You have to know the name of the server and the port continuum is running on. I don't remember the default port. You use 'continuum' as context root. So something like: http://:/continuum On 9/28/06, Gabriel Baños <[EMAIL PROTECTED]> wrote: Hi ! I have installed continuum 1.0.3 on my server but i can't find a way to log in through de web interace. which user and password should i use ? where can i configure it ? Could anyone help me? thank you ! -- Gabriel V. Baños http://flof.com.ar
maven LinkCheck plugin for maven2
Hello, I'm interested in using the Maven LinkCheck Plugin with Maven2. I have the impression that the plugin is only available for Maven 1. Is any support / maintenance planned for Maven 2 ? More info: http://maven.apache.org/maven-1.x/plugins/linkcheck/ Thanks...
continuum and settings.xml
Hello, I'd like to know how continuum (possibly maven) detect it's settings.xml. As I understand continuum prints out the location of settings.xml. This comes from our log file: INFO | jvm 1| 2006/09/05 08:54:34 | 2006-09-05 08:54:34,033 [WrapperSimpleAppMain] DEBUG MavenSettingsBuilder - Building Maven global-level settings from: 'D:\javadev\tools\continuum\continuum- 1.0.3\bin\win32\conf\settings.xml' INFO | jvm 1| 2006/09/05 08:54:34 | 2006-09-05 08:54:34,033 [WrapperSimpleAppMain] DEBUG MavenSettingsBuilder - Building Maven user-level settings from: 'C:\Documents and Settings\continuum\.m2\settings.xml' If the files are present or not, these lines arein the log files. Because I had some trouble I tried out following combinations: Location of settings.xml %MAVEN_HOME%\conf%CONTINUUM_HOME%\bin\win32\conf (1)not present not present (2)not present present (3)presentnot present (4)presentpresent 1,2 and 3 result in errors. 4 does not. So it seems the the settings.xmlfile must be present at both locations...? The errors (part of) are listed below. For your info: there is one master project, containing several modules. The modules have the master as parent POM, the master uses a company wide parent POM. The local repository is empty, this is tested with a clean installation of maven/continuum. (1) No settings.xml specified. Continuum Error Cannot build maven project from s:\TEMP\system\continuum\viewcvs\checkout\myproject\master\pom.xml (Cannot find parent: mycompany.common:common-masterpom for project: mycompany.myproject:myproject-master:pom:2.5-SNAPSHOT). INFO | jvm 1| 2006/09/01 15:47:17 | 2006-09-01 15:47:17,345 [WrapperSimpleAppMain] DEBUG MavenSettingsBuilder - Building Maven global-level settings from: 'D:\javadev\tools\continuum\continuum- 1.0.3\bin\win32\conf\settings.xml' INFO | jvm 1| 2006/09/01 15:47:17 | 2006-09-01 15:47:17,345 [WrapperSimpleAppMain] DEBUG MavenSettingsBuilder - Building Maven user-level settings from: 'C:\Documents and Settings\continuum\.m2\settings.xml' INFO | jvm 1| 2006/09/01 15:51:55 | 2006-09-01 15:51:55,704 [SocketListener0-1] ERROR MavenBuilderHelper - Cannot build maven project from s:\TEMP\system\continuum\viewcvs\checkout\myproject\master\pom.xml (Cannot find parent: mycompany.common:common-masterpom for project: mycompany.myproject:myproject-master:pom:2.5-SNAPSHOT). INFO | jvm 1| 2006/09/01 15:51:55 | INFO | jvm 1| 2006/09/01 15:51:55 | org.apache.maven.project.ProjectBuildingException: Cannot find parent: mycompany.common:common-masterpom for project: mycompany.myproject:myproject-master:pom:2.5-SNAPSHOT INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage( DefaultMavenProjectBuilder.java:1161) INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal( DefaultMavenProjectBuilder.java:674) INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal (DefaultMavenProjectBuilder.java:416) INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.project.DefaultMavenProjectBuilder.build( DefaultMavenProjectBuilder.java:201) INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject (DefaultMavenBuilderHelper.java:306) INFO | jvm 1| 2006/09/01 15:51:55 | at org.apache.maven.continuum.project.builder.maven.MavenTwoContinuumProjectBuilder.readModules (MavenTwoContinuumProjectBuilder.java:99) INFO | jvm 1| 2006/09/01 15:51:55 | Caused by: org.apache.maven.project.ProjectBuildingException: Error getting POM for ' mycompany.common:common-masterpom' from the repository: Error transferring file INFO | jvm 1| 2006/09/01 15:51:55 | mycompany.common:common-masterpom:pom:1.0.0 INFO | jvm 1| 2006/09/01 15:51:55 | INFO | jvm 1| 2006/09/01 15:51:55 | from the specified remote repositories: INFO | jvm 1| 2006/09/01 15:51:55 | central ( http://repo1.maven.org/maven2) <-- I think this is normal, default maven settings when nothing else specified. (2) settings.xml present in %CONTINUUM_HOME%\bin\win32\conf I this case adding the master project results in all projects being added to continuum. However the master project can not be built because the parent POM is not found. Apparently the settings from settings.xml are not taken into account. Our settings.xml overrides central so that our projects go to our internal (company) repository. But continuum seems to go to repo1.maven.org Error: INFO | jvm 1| 2006/09/01 16:06:02 | [INFO] Scanning for projects... INFO | jvm 1| 2006/09/01 16:06:02 | Downloading: http://repo1.maven.org /maven2/mycompany/common/common-masterpom/1.0.0/common-masterpom-1
Re: Mail notifications stopped working with Windows service
We are running the same configuration as you describe. We have this running for several months, and it runs really smoothly.
running multiple instances of continuum on one machine
Hey, I'm wondering if it is possible to run multiple instances of Continuum on the same machine? We have a lot of projects (each possibly having one or more modules), and this results in a long list of modules/projects. As far as I know it's not (yet?) possible to filter the last based on name or group. So I was thinking about running a second instance of continuum listening on another port. What would be the best way to do this? We run on windows, continuum installed as a service. Duplicate the whole continuum installation and change the config in that location to run on another port? Consequence of this is that the existing users are lost. Another solution is creating a second wrapper.config file. But I'm not sure what will be the result. MAybe we'll encounter threading/concurrency issues. Anyone already tried this out? Any suggestions? Thanks
Re: Maven best practices - company-wide local repository?
Oeps, seems like I've been a bit to fast. and I consider if we should use a common local repository - for instance over a network share. You're talking about a common local repository. I agree with Christian, this could slow down things a lot. And it makes it more difficult to experiment (though you always can changing the settings.xml you use.) I also strongly recommend to keep the LOCAL repository, really local, meaning on the developers workstation.
Re: Maven best practices - company-wide local repository?
Do you do anything similar? Are there drawbacks? What is the recommended approach? We do the same thing here, we have set up an internal repository for both library dependencies and plugin dependencies (1 central repo). We use maven-proxy instead of proximity to feed the internal repo. But developers use the network share to use the internal repo (we wanted to avoid that developers must have access to internet in order to perform a build). Management of the internal repo is done by a separate person/team with maven-proxy.
Re: [m2] snapshot repository: exploding size
It's a pity that this is not yet supported (cleaning of snapshot repo's). I assume I can simply remove old snapshot versions. Why does Maven keep old versions anyway? If you depend on a snapshot, you depend on the latest version of the snapshot, so why keep the old versions of a snapshot? I must be missing something
Re: strange problem - occurs after restarting continuum
OK, this seems to solve the problem (I copied the settings.xml file from maven conf, to continuum-1.0.3\bin\win32) Thanks a lot ! Isn't this a rather strange behavior, I mean continuum not looking at the maven/conf/settings.xml. Somewhere I can understand, that you want seperate settings, but by default you could take the maven one. Maybe a good idea to add this information also somewhere on the continuum documetation site, because I could not find this anywhere.
strange problem - occurs after restarting continuum
Hey all, we are running continuum 1.0.3 on a windows server (2003), and we have installed it as a service. We have the following project structure ROOT - master - module 1 - module 2 - module 3 When I restart continuum (restarting the service), I get the following error for the all modules: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut (MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute (UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build( DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask (BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run (ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:534) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from D:\javadev\tools\continuum- 1.0.3\bin\win32\..\..\apps\continuum\working-directory\62\pom.xml (Cannot find parent: mycompany.project:project-master for project: mycompany.project:project-common:jar:3.2.8-SNAPSHOT). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject (DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject (DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut (MavenTwoBuildExecutor.java:113) ... 5 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: mycompany.project:project-master for project: mycompany.project:project-common:jar:3.2.8-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage( DefaultMavenProjectBuilder.java:1161) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal( DefaultMavenProjectBuilder.java:674) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal (DefaultMavenProjectBuilder.java:416) at org.apache.maven.project.DefaultMavenProjectBuilder.build( DefaultMavenProjectBuilder.java:201) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject (DefaultMavenBuilderHelper.java:306) ... 7 more Caused by: org.apache.maven.project.ProjectBuildingException: POM ' mycompany.project:project-master' not found in repository: Unable to download the artifact from any repository mycompany.project:project-master:pom:3.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository( DefaultMavenProjectBuilder.java:513) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage( DefaultMavenProjectBuilder.java:1157) ... 11 more Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository mycompany.project:project-master:pom:3.2-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve( DefaultArtifactResolver.java:136) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve( DefaultArtifactResolver.java:63) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository( DefaultMavenProjectBuilder.java:467) ... 12 more Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to download the artifact from any repository at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact( DefaultWagonManager.java:260) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve( DefaultArtifactResolver.java:124) ... 14 more Once the master project has been build all the modules are building normally again. What's very strange is that Maven is trying to go to an external repository, while we have configured Maven to go to our internal repository: dfsprofile central file:///\\companyserver\repo true always warn false Snapshots central maven repository for snapshots file:///\\companyserver\snapshot false true always warn central central maven repository for plugins file:///\\companyser
[m2] snapshot repository: exploding size
Hey, we have set up continuum which publishes the artifacts. Our snapshotrepository is growing quickly in size. Every new snapshot is added to the repo, but the snapshot repository is never cleaned. Can maven be configured in any way to prevent this? In the snapshot repo you have a lot of files like: myArtifact-3.2.8-20060616.092442-11.pom myArtifact-3.2.8-20060616.092442-11.jar myArtifact-3.2.8-20060616.094800-12.pom myArtifact-3.2.8-20060616.094800-12.jar myArtifact-3.2.8-20060616.100110-13.pom myArtifact-3.2.8-20060616.100110-13.jar Is it possible to define some kind of rotation on the sequence number...? Any suggestions. Thx
Re: [m2] mvn deploy using file:// protocol
Try this: file:///\\my.server/repository Should work on windows.
Re: RE : [m2] bug? problem with release:perform, settings not propagated
Just tried again by adding the following -Darguments="-s " Does not seem to work, apparently this is caught explicitly by the release plugin, see the warning message. So this seems to be part of the release plugin to prevent that you customize the build. I can understand, because one of the requirements is probably that you must be able to rebuild the jar, with exactly the same parameters. Is preventing an alternate user settings files the best solution? What if the settings.xml file changes (default maven settings.xml)? Maybe I should contact the developers of this plugin, to get a better understanding of it. [INFO] Executing: mvn deploy --no-plugin-updates -s C:\javadevC:\javadev\tools\maven\maven-2.0.4\conf\settings_local.xml -P defaultprofile -DperformRelease=true WARNING: Alternate user settings file: C:\javadevC:\javadev\tools\maven\maven-2.0.4\conf\settings_local.xml is invalid. Using default path. [INFO] Scanning for projects... [INFO] [INFO] Building MyProject Common [INFO]task-segment: [deploy] [INFO] [INFO] artifact org.apache.maven.plugins:maven-resources-plugin:checking for updates from central [WARNING] repository metadata for: 'artifact org.apache.maven.plugins:maven-resources-plugin' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 21 seconds [INFO] Finished at: Mon May 29 14:20:20 CEST 2006 [INFO] Final Memory: 1M/3M [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error executing Maven: Maven execution failed, exit code: '1' [INFO]
Re: Internal plugin repository - how to populate?
I agree, it's not an easy job. I'm having the same problems right now. I hope the maven repository manager will solve some of those difficulties. See: http://maven.apache.org/repository-manager There not that much information available, as it's still under development. Another 'option' is to use the Maven-Proxy, this also eases the setup of an internal repository. See: http://maven-proxy.codehaus.org/ However it does not really solve the problem of initializing the internal repository. If you find any good solution to this, please let me know. It would help us also. On 5/29/06, ArneD <[EMAIL PROTECTED]> wrote: In many corporate environments it is unacceptable to let users download Maven plugins automatically and directly from the Internet (even not through a proxy). Therefore, it is necessary to set up an internal plugin repository. Question: Is there an easy way how to initially populate the internal repository with all the maven plugins needed? I considered the following ways: 1. mvn deploy:deploy-file for all the plugin jars. Problem: This seems to be a rather inconvenient approach with lots of manual work. 2. First popule a local repository by running all desired Maven goals, and then copy the local repository contents to the internal remote repository. Problem: As far as I understood, this wouldn't work, because a remote repository contains some extra XML definition files, that are not available in the local repository. Any other ideas? Thanks in advance, Arne -- View this message in context: http://www.nabble.com/Internal+plugin+repository+-+how+to+populate--t1697509.html#a4606575 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] bug? problem with release:perform, settings not propagated
Hello, I'm getting this problem when launching release:perform using the following command. D:\javadev\tools\continuum-1.0.2\apps\continuum\working-directory\58>mvn release:perform -e -s D:\javadev\tools\maven\maven- 2.0.4\conf\settings_continuum.xml -DconnectionUrl=scm:cvs:pserver:anonymous:@cvssrv.mycompany.com :/export/home/cvs/myProject:myProject/common As you can see in the trace below, this goal also launches: [INFO] Executing: mvn deploy site-deploy --no-plugin-updates -P continuum,defaultprofile,continuum -DperformRelease=true Problem is that the -s option specified at the command-line is not taken into account. Is this intentionaly done this way, or is it a bug. It took my quite some time to figure out why this didn't work. By renaming my settings_continuum.xml file to settings.xml (maven's default) the problem was solved. So I believe this is a bug? Details about the release:perform: + Error stacktraces are turned on. Maven version: 2.0.4 [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Default User\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\javadev\tools\maven\maven-2.0.4\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'release'. [DEBUG] Skipping disabled repository CodehausRepoSnapshots [INFO] org.apache.maven.plugins: checking for updates from mycompanySnapshots [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: mycompanySnapshots [INFO] org.apache.maven.plugins: checking for updates from mavenproxy [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: mavenproxy [INFO] org.apache.maven.plugins: checking for updates from central [DEBUG] Skipping disabled repository CodehausRepoSnapshots [INFO] org.codehaus.mojo: checking for updates from mycompanySnapshots [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: mycompanySnapshots [INFO] org.codehaus.mojo: checking for updates from mavenproxy [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: mavenproxy [INFO] org.codehaus.mojo: checking for updates from central [DEBUG] Skipping disabled repository CodehausRepoSnapshots [INFO] artifact org.apache.maven.plugins:maven-release-plugin: checking for updates from mycompanySnapshots [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-release-plugin' could not be found on repository: mycompanySnapshots [INFO] artifact org.apache.maven.plugins:maven-release-plugin: checking for updates from mavenproxy [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-release-plugin' could not be found on repository: mavenproxy [INFO] artifact org.apache.maven.plugins:maven-release-plugin: checking for updates from central [DEBUG] maven-release-plugin: resolved to version 2.0-beta-4 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::1 for project: null:maven-release-plugin:maven-plugin:2.0-beta-4 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for project: org.apache.maven.plugins:maven-plugins:pom:1 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project: org.apache.maven:maven-parent:pom:1 from the repository. [INFO] [INFO] Building myProject Common [INFO]task-segment: [release:perform] (aggregator-style) [INFO] [DEBUG] org.apache.maven.plugins:maven-release-plugin:maven-plugin:2.0-beta-4:runtime(selected for runtime) ... -- DEBUG about all plugin versions -- ... [DEBUG] Configuring mojo ' org.apache.maven.plugins:maven-release-plugin:2.0-beta-4:perform' --> [DEBUG] (f) basedir = D:\javadev\tools\continuum- 1.0.2\apps\continuum\working-directory\58 [DEBUG] (f) connectionUrl = scm:cvs:pserver:anonymous:@cvssrv.mycompany.com :/export/home/cvs/myProject:myProject/common [DEBUG] (f) project = [EMAIL PROTECTED] [DEBUG] (f) settings = [EMAIL PROTECTED] [DEBUG] (f) useReleaseProfile = true [DEBUG] (f) workingDirectory = D:\javadev\tools\continuum- 1.0.2\apps\continuum\working-directory\58\target\checkout [DEBUG] -- end configuration -- [INFO] [release:perform] [INFO] Checking out the project to perform the release ... [DEBUG] release.properties not found - using empty properties [DEBUG] cvsRoot: : pserver:[EMAIL PROTECTED]:2401/export/home/cvs/myProject [DEBUG] passFile: C:\Documents and Settings\Default User\.cvspass [DEBUG] cvsroot : pserver:[EMAIL PROTECTED]:2401/export/home/cvs/myProjectalready exist in C:\Documents and Settings\Default User\.cvspass. SKIPPED. [INFO] Executing: cvs -z3 -f -d :pserver:[EMAIL PROTECTED]:/export/home/cvs/myProject -q checkout -d checkout myProject/common [INFO] Working directory:
Re: specifying versions in sub-projects
This in discussed in the book Better Builds with Maven which you find here (for free): http://www.mergere.com/m2book_download.jsp See the following sections: p54: 3.4 Managing Dependencies p.57: 3.6 Resolving dependency conflicts I think those solutions are rather good. On 5/4/06, jerome lacoste <[EMAIL PROTECTED]> wrote: Hi. if I have P1 |- P2 Now P2 requires a particular version of a plugin, newer than the one taken by default by P1. After changing P2's pom, if I build from P2, then my P2 build will work. But if I build from P1, P2 will fail. My solution was to move the plugin-version specification in the root pom, but I found that counter intuitive. Comments? Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] setting up internal repository
Hey, I'm wondering what's the best way to set up an internal Maven repository. I know of the Maven Repository Manager (MRM), but when will it be available? We would like to control what's put in the internal repository. So one of the ideas was to create a maven project that contains only dependencies to 'allowed' libraries. The local repository of this project could then be used as The central internal repository. However this approach does not seem to work, because the maven-metadata.xml files are not created. Can anyone confirm that this approach indeed does not work? Anyone knows of good in-dept documentation on this (I've read the guidelines on the Maven site, and Better Builds with Maven (which is by the way a great introduction to maven))? Do there exist other tools to 'easily' manage maven repositories? Thanks..
