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 copy; {inceptionYear}-{currentYear} {organizationName}. All
Rights Reserved.
But I can't figure
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...
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:
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
You only need to modify the port of http and xmlrpc services in
apps/continuum/conf/application.xml
Probably a stupid question: so I install a second copy of continuum?
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
We are running the same configuration as you describe. We have this running
for several months, and it runs really smoothly.
Hello,
I would like to configure our continuum server in such a way that continuum
starts building as soon as a CVS commit is completed. (or after a quiet
period of at least 30sec).
Is this possible with continuum, and how would you achieve that?
For the moment continuum is already set up, and
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
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
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
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
What are goals runned by your build definition?
clean deploy site site:deploy
Where do you have define this profile?
The profile listed is defined in the settings.xml in the maven distribution
(conf directory) and is activated in the settings.xml itself. This is the
maven installation on the
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
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:
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\58mvn
release:perform -e -s D:\javadev\tools\maven\maven-
2.0.4\conf\settings_continuum.xml
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
Just tried again by adding the following
-Darguments=-s path to my settings.xml file
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
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
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
20 matches
Mail list logo
