Maybe a cleaner solution:
Step 1: Follow step 1 to 4 of Quarph
Step 1a: Make any adjustments to the pom, that you will need in your projects,
like parent pom and such.
Step 2: Run mvn archetype:create-from-project
Step 3: From the generated Archetype project, run mvn install or mvn deploy
Step
Try to add the source parameter to your aspectj plugin. [1]
[1] http://mojo.codehaus.org/aspectj-maven-plugin/compile-mojo.html#source
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: Ilya Ermolov
I have taken a look at the source and I'm wondering how property injection
works with maven? Is it calling the setVerbose method or does it set the
verbose parameter through reflection?
If it does the first it should work, if it does the second it doesn't work.
Could you try running with debug
The error says:
INFO] Searching repository for plugin with prefix: 'findbugs'.
What is the command you gave maven? Did you try running mvn findbugs:goalname
or mvn site? In the reporting section comes all plugins for site generation. If
you try to run findbugs directly, maybe you should add a
And to give a little more inside info. If maven cannot find a prefix, it will
automagically assume groupId org.apache.maven.plugins and artifactId
maven-$prefix-plugin, so that is where the message came from.
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS
In our super pom we have the following elements:
prerequisites
maven2.0.7/maven
/prerequisites
So each developer has at least the recommended version of maven.
Two profiles, one default on, which defines our artifactory as central and
takes care of the distribution management and one
On your first point, that checkstyle did not run when you execute mvn package,
that is completely true, since verify comes after package.
I don't know why it did not fail. Are you sure, you're using the latest version
of the checkstyle plugin. Always version your plugins in your pom. The latest
You have to restructure your project.
Like:
module-name-pkg1/src/main/java/com/abc/xyz/pkg1
module-name-pkg1/src/test/java/com/abc/xyz/pkg1
module-name-pkg1/pom.xml
module-name-pkg2/src/main/java/com/abc/xyz/pkg2
module-name-pkg2/src/test/java/com/abc/xyz/pkg2
module-name-pkg2/pom.xml
Can someone comment on this mail? Is the release:branch goal fitted to create a
branch from a tag and update the version numbers?
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: [EMAIL PROTECTED]
I am trying to create a branch from a tag with the release plugin. I have a
checkout from trunk and try the following command:
mvn release:branch -Dtag=TestProject-1.4 -DbranchName=TestProject-1.4.x s
-DupdateBranchVersions=true
I was expecting that a branch (/branches/TestProject-1.4.x) was
Hi,
Back in the days there used to be a piece of information on specifying a new
package on the maven web site. I found a backup at [1]. Also at [2] there is
issue with patch which adds a new packaging. So maybe you have to patch a
custom maven installation to provide your package type.
Hth,
It also works as a shorter version:
https://jira.codehaus.org/browse/MNG-3343
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: Andrew Madu [mailto:[EMAIL PROTECTED]
Sent: Fri 6/6/2008 14:22
To: Maven Users List
What you're seeing there is which plugin with which goal to run. As far as I
know there is no plugin which creates such .spring files. Are they any
special files?
One solution I see is to specify the assembly plugin there and provide a
default configuration in your company's parent pom. (Sort
Then the assembly plugin would be your friend.
http://maven.apache.org/plugins/maven-assembly-plugin/
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: Andrew Madu [mailto:[EMAIL PROTECTED]
Sent: Fri 6/6/2008
Could you give a more detailed error description by running the command with
the -e (exceptions) or even -X (debug) parameters?
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
-Original Message-
From: youhaodeyi
It would be something like:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
executions
execution
idlist-deps/id
phasegenerate-resources/phase
Looking at the dependencies of the maven deploy plugin [1] I think you have to
write your own plugin to do this. You could take a look at the
maven-deploy-plugin code to see how they accomplish it.
Another option would be the maven-antrun-plugin [2] or the Maven Exec Plugin
[3].
Hth,
Nick S.
It is not a part of the deploy plugin. The deploy plugin is used only to put
artifacts into a remote repository. Nothing else. To accomplish this, it uses
the different wagon artifacts. If you want to accomplish your task, you will
have to use one of the three options I gave you.
1) Create
You can add the plugins with version to the pluginManagement section of your
pom file.[1] (Or parent pom file if you want to reuse the list) This way maven
will always use the declared version (It will still download it, when the
declared version is not found in your local repository).
Only
Take a look at the multi module configuration section of the checkstyle plugin
documentation [1].
Hth,
Nick S.
[1]
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
-Original Message-
From: Ittay Dror [mailto:[EMAIL PROTECTED]
Sent: Tue
You could bind a plugin to the process classes phase [1] which is a phase after
compile but before packaging. If your class doesn't run as a plugin, you have a
few options:
1) Make a plugin, which runs your class. [2]
2) Use the antrun plugin to fire of your class [3]
Hth,
Nick S.
[1]
I missed that one, and I think that is the best short term solution. Delicious
tagged for future reference. ;)
With regards,
Nick S.
-Original Message-
From: Dirk Olmes [mailto:[EMAIL PROTECTED]
Sent: Fri 4/11/2008 10:03
To: Maven Users List
Subject: Re: How can I let Maven run a
What do you mean by a regular repository?
If you are using a filesystem on a server and deploying to there with mvn
deploy, you virtually have an inhouse repository like archiva offers, without
the management like snapshot purging, access control (who may read/write),
search for artifacts.
What's snapshot purging???
If you have an internal development team which uses the repository and you make
a new release of a component, most of the time the snapshots for that component
are no longer needed. Archiva can delete the snapshots for a specific version
or after a specific amount of
This is a very common pitfall Maven users can fall in.
You are using a local repository as remote repository. I thought there was some
information on the maven site about the differences between remote and local
repositories, but the most important one is:
A local repository stores snapshots
Doh... Note to self: Don't post when you're tired. ;)
But I see artifactory also can work with the webdav wagon. [1] Could you try
that?
Hth,
Nick S.
[1]
http://www.jfrog.org/confluence/display/RTF/Using+Artifactory#UsingArtifactory-CLIDeployment
-Original Message-
From: Brian E.
Take a look at the Maven Build Lifecycle page [1]. This page lists for each
type of packaging which plugins and goals are added automatically to the
lifecycle. All other goals you have to add yourself explicitly. Or in a parent
pom file if you need them for many projects.
Hth,
Nick S.
[1]
No, not the scm tag. As you can see here [1] the buildnumber-plugin uses the
scm-api and implementations of Maven.
Hth,
Nick S.
[1] http://mojo.codehaus.org/buildnumber-maven-plugin/dependencies.html
-Original Message-
From: DCVer [mailto:[EMAIL PROTECTED]
Sent: Thu 4/10/2008 13:23
This is configurable for each repository for releases and snapshots. Take a
look at [1] and the updatePolicy.
Hth,
Nick S.
[1] http://maven.apache.org/ref/2.0.7/maven-model/maven.html#class_releases
-Original Message-
From: youhaodeyi [mailto:[EMAIL PROTECTED]
Sent: Wed 4/9/2008
If I read [1] correctly, Maven will even by default try to update releases.
Hth,
Nick S.
[1] http://maven.apache.org/ref/2.0.8/maven-model/maven.html#class_releases
-Original Message-
From: VELO [mailto:[EMAIL PROTECTED]
Sent: Wed 4/9/2008 15:52
To: Maven Users List
Subject: Re: Why
Start by explaining the problem and the expected / actual result on the user
list. If it really is a bug, a lot of dev'ers are also reading there and will
redirect you to the jira system[1] and tell you which component it affects. The
dev list is more for the developers to communicate.
Hth,
And if you're wondering why install matches my surefire-it executions,
maven works with phases. If you execute a phase ( ie. compile, package or
install, all phases before that phase are run, and guess, integration-test is
between package and install. See [1].
Hth,
Nick S.
[1]
Maybe you can use Eclipse (m2eclipse [1]) or Netbeans(mevenide [2]) with their
maven plugin. Those plugins index the central repository and allow you to
search and add dependencies.
[1] http://m2eclipse.codehaus.org
[2] http://mevenide.codehaus.org
Hth,
Nick S.
-Original Message-
What I've done on my laptop:
I created multiple settings.xml (settings.xml.home, settings.xml.work, etc) and
with a script I make a symlink to the right settings.xml.x to settings.xml.
Just run the command once and I am set for that environment.
Hth,
Nick S.
-Original Message-
From:
It seems that version of the jira-plugin still uses maven 1 (You've got a
project.xml file, not a pom.xml file), so maven 2 will not work on that plugin.
The trunk of the plugin is using m2 instead of m1, so you could try that one (I
don't know how stable the trunk is) or you could try using
Otherwise, you could try the distribution of the plugin ;)
http://svn.atlassian.com/svn/public/contrib/jira/jira-calendar-plugin/distributions/
Hth,
Nick S.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Fri 3/28/2008 15:23
To: Maven Users List
Subject: RE:
You can add the javadoc plugin to the build section of your pom, to specify the
max memory. [1] Or you can add the arguments parameter to the release plugin to
specify the javadoc property. [2]
Hth,
Nick S.
[1]
http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#maxmemory
I know the tomcat plugin can turn your src/main/webapp into a exploded tomcat
project. So every change to jsp files will be picked up without having to do
anything.
Deploying an in-place WAR directory
To avoid copying resources to the build directory, the webapp source directory
can be
I don't know for certain if this is gonna work, but you can give it a try:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
executions
execution
idgenerate-buildnumber/id
Perhaps they overwrite each other (the inside of the profiles). What's inside
the profiles. If for example, you have two ant-run plugins, without id's I
think it will go wrong.
With regards,
Nick S.
-Original Message-
From: Yann Davin [mailto:[EMAIL PROTECTED]
Sent: Tue 3/11/2008
I can't repeat it often enough: do not copy a local repository to be used as a
remote repository. There is not the same information in your local repository
as in your remote repository.
Really, do use a Maven repository / mirror, like Archiva, Artifactory or
Nexus/Proximity.
Hth,
Nick S.
I would setup a maven repository, with mirrors for at least central and maybe
some other repositories. Also create inhouse repositories for your own release,
Snapshots and external dependencies. (3 different repositories)
Then set up your local maven to use the mirrors, and rebuild with an
Hi,
This is not possible to configure in your pom file. However, it should be
possible to adjust the maven Eclipse Plugin to execute the install phase. (Just
like surefire-reports execute the test phase) For this there should be a mojo
added to the Maven Eclipse Plugin. This sounds like a nice
You have a good point. Maybe it is better to let eclipse:eclipse do a resolve
dependencies. So you're sure to have all the jar files in the repository?
With regards,
Nick S.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thu 3/6/2008 11:15
To: Maven Users
The problem is, that eclipse:eclipse is the invocation of a goal and instead of
maven 1 preGoal and postGoal, maven 2 binds goals to phases and you can't chain
goals. You could prescribe the dev'ers to execute mvn install eclipse:eclipse
instead of mvn eclipse.
Hth,
Nick S.
-Original
You could create a Enforcer [1] custom rule[2] and use that. If you create an
new feature issue at the Enforcer jira [3] with unit tests and code it could
make it into the enforcer plugin.
Hth,
Nick S.
[1] http://maven.apache.org/plugins/maven-enforcer-plugin/
[2]
There is a solution for this problem. The deploy:deploy-file will automatically
generate a pom file.
So, remove the jars from your remote repository and deploy them again with mvn
deploy:deploy-file .
Perhaps if you make a list with the directories it should be possible to create
a little
You need file access to your continuum application. (Through ssh or on the
machine itself for example) Continuum uses a work directory where the checkouts
are made. Here lies the problem. (For every build the working copy is updated,
not recreated.)
As a side note for the dev'ers. Would it be
Add them to your local repository with install:install-file [1] and add them to
the pom file of project c as dependencies with scope 'test'.
Hth,
Nick S.
[1] http://maven.apache.org/plugins/maven-install-plugin/install-file-mojo.html
-Original Message-
From: Mikael Petterson
This is possible with the enforcer plugin [1] and esspecially the
requirePluginVersion rule [2].
Hth,
Nick Stolwijk
[1] http://maven.apache.org/plugins/maven-enforcer-plugin/
[2]
http://maven.apache.org/plugins/maven-enforcer-plugin/rules/requirePluginVersions.html
-Original
Take a look at Archiva or Artifactory. That way you can run your own
repositories. Deploy releases and snapshots in seperate inhouse repositories.
Deploy third party libraries that are for the moment not on central into a
third party repository. Will also mirror central for your development
I've updated our company pom to use surefire and surefire-report 2.4.1. We have
a project with 4 modules with not much source (Like 10 to 15 classes and 10 to
15 testclasses per module). We are running a mvn site-deploy and started to run
out of heap space. We have quite a few plugins running
Hi Pawan,
Try:
http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html
http://maven.apache.org/guides/getting-started/index.html
After that, go to:
Maven: The Definitive Guide
http://www.sonatype.com/book/
Better Builds with Maven
Thomas,
Most Maven modules which generate code add the generated code to the build
path. (Hibernate plugin adds /target/generated-sources/hibernate) If you want
to add your own folder (say src/generated/java) to the buildpath take a look at
the buildhelper plugin [1].
If I were you I would
I think the super-pom is the name for the concept of default settings and
there is no actual super pom.
The normal solution for your problem would be to create a corporate/company pom
and let all projects add it as their parent.
Hth,
Nick S.
-Original Message-
From: Marcelo
Ok, I've found it, it is under:
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/maven-project/src/main/resources/org/apache/maven/project/pom-4.0.0.xml
Hth,
Nick S.
-Original Message-
From: Gregory Kick [mailto:[EMAIL PROTECTED]
Sent: Fri 2/15/2008 17:35
To:
You are looking for the classifier of the dependency:
dependency
groupIdcom.my.company/groupId
artifactIdjava-proj/artifactId
version1.0-SNAPSHOT/version
classifiersources/classifier
/dependency
See
It seems the command executed has returned a non-succes code. What happens when
you execute the command from the commandline, thus: /bin/sh -c 'ssh -o
BatchMode yes [EMAIL PROTECTED] chmod -Rf g+w,a+rX /path/to/htdocs/hudson
Hth,
Nick Stolwijk
-Original Message-
From: Julien FOROT
You can add a property to your finalName and fill that with a profile, or use
the build definition inside a profile to add your finalName to.
Hth,
Nick Stolwijk
-Original Message-
From: amit kumar [mailto:[EMAIL PROTECTED]
Sent: Thu 2/14/2008 10:45
To: Maven Users List
Subject: Re:
We have a local repository where we put all the artifacts that we need in
our project.
Do you mean the local repository each developer has? Normally
user_home/.m2/repository . Or do you mean an internal remote repository on a
server? With what command did you install the artifacts into your
It was more a been there, done that story. Whenever I see someone talking
about we are using a local repository or such, horrid images from the past
gets in my head. ;)
If you try to get
http://ecm-maven-repo.itcnetworks:8081/maven_repo/org/apache/maven/plugins/maven-metadata.xml.sha1
from a
First, I see I forgot a space, so my url was bogus, it should be:
http://ecm-maven-repo.itcnetworks:8081/maven_repo/org/apache/maven/plugins/maven-metadata.xml.sha1
Second, do you use any repository software, like archiva or proximity, or is it
just a remote filesystem?
With regards,
Nick
I've looked at the metadata file and it is to map prefixes, like release,
eclipse, all the shorthand forms, to plugins. Could you compare
http://ecm-maven-repo.itcnetworks:8081/maven_repo/org/apache/maven/plugins/maven-metadata.xml
with
I know that central is also just a filesystem, and I once saw a few shell
scripts to repair metadata and checksums, IIRC. I don't know who had them or if
they still exist.
Some of maven 2 developers are often on IRC, maybe you could ask them if they
still have those scripts.
Hth,
Nick
The install page at ucalgary.ca is out of date. The buildnumber plugin has been
uploaded to central and is at:
dependency
groupIdorg.codehaus.mojo/groupId
artifactIdbuildnumber-maven-plugin/artifactId
version1.0-beta-1/version
/dependency
Which version are you trying to use?
Hth,
How did you configure your repository? Especially take a look at the
updatePolicy element in your snapshot repository. [1] If this one is omitted,
it will default to daily, so it is possible it won't take your newest
snapshot. You can use mvn -U to look for newer versions of the snapshot
The modules section is only used when building an aggregate project. It is not
used for dependencies in any way. If submodule b uses submodule a, you have to
give submodule b a dependency on submodule a. If multiple submodules depend on
submodule a, you can have submodule a in the
It is not very easy to find, but under Get involved on
maven.apache.org/archiva there is a page for the mailinglists. [1]
Hth,
Nick Stolwijk
[1] http://maven.apache.org/archiva/mail-lists.html
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Mon 2/11/2008
Try:
mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard
or whatever version you're using.
With regards,
Nick Stolwijk
-Original Message-
From: Nagesh, Srinivas (IS Consultant) [mailto:[EMAIL PROTECTED]
Sent: Thu 2/7/2008 4:03 PM
To: Maven Users List
Subject: RE:
My first suggestion would be to version all the plugins you use, maybe in a
parent pom. Otherwise, builds that work now, will fail in the future, even your
tags, because of updated plugins. Been there, done that, got the T-shirt.
Hth,
Nick Stolwijk
-Original Message-
From: Joshua
Use the -Dclassifier option of deploy:deploy-file [1]. As far as I know it's
just another classifier of the same artifact.
Hth,
Nick Stolwijk
[1]
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html#classifier
-Original Message-
From: Richard Chamberlain
Hi,
Did you take a look at the Maven Application Assembler Plugin? [1] This will
create the zip file you are asking for.
Hth,
Nick Stolwijk
[1] http://mojo.codehaus.org/appassembler/appassembler-maven-plugin/
-Original Message-
From: Alexander Petri [mailto:[EMAIL PROTECTED]
Sent:
Which rulesets are you using inside Eclipse? By default, the Maven PMD Plugin
only uses the rulesets basic.xml, unusedcode.xml and imports.xml.
Take a look here [1] and here [2].
Hth,
Nick Stolwijk
[1] http://maven.apache.org/plugins/maven-pmd-plugin/examples/usingRuleSets.html
[2]
Yes, there is. Take a look at the StatSCM Maven Plugin [1].
Hth,
Nick Stolwijk
[1] http://stat-scm.sourceforge.net/
-Original Message-
From: Thomas Tardy [mailto:[EMAIL PROTECTED]
Sent: Fri 2/1/2008 9:24 AM
To: Maven Users List
Subject: Count line of code
Hi all,
is there a
Hi folks,
I'm adjusting a maven-plugin, which is a wrapper around a library. This library
logs a lot at info level and I want to change that to only log when maven is in
debug mode (-X). When I ask the AbstractMojo.getLogger().isDebugEnabled() it
always returns false (hard coded). We're using
repository specified, but when I deploy snapshots, I want them to be stored
in another repository. Can I have 2 remote repositories specified in
pom.xml?
nicklist wrote:
If I understand you correctly, you're using the maven-install-plugin to
install files into the remote repository? This way
I guess your problem is caused by annotations:
Encountered @ at line 71, column 17.
What version of the plugin are you using? There seems to be a beta-1 and a
beta-2. The beta-2 has better annotation support.
Hth,
Nick Stolwijk
-Original Message-
From: Thomas Tardy [mailto:[EMAIL
I think this is the same problem as MJNCSS-16 [1], which has the following
comment:
Thanks for the report.
Unfortunatly, as of today, we can't do much since the problem lies within
javancss core library, beside sending a bug report to the original author of
javancss :
If you look at the report, you should see an explanation section, see also [1].
In short:
Non Commenting Source Statements (NCSS)
Statements for JavaNCSS are not statements as specified in the Java Language
Specification but include all kinds of declarations too. Roughly spoken, NCSS
is
.
If u have yahoo id then can u give me?
Please I need the solution very urgently.
nicklist wrote:
What goals or phase are you running from Continuum? The reporting
section is only used when generating a site (thus, running mvn site)
and not when running an install or deploy.
Hth
.
If u have yahoo id then can u give me?
Please I need the solution very urgently.
nicklist wrote:
What goals or phase are you running from Continuum? The reporting section
is only used when generating a site (thus, running mvn site) and not when
running an install or deploy.
Hth
This is the first time I see that a plugin transitive dependency makes it into
the final artifact. What versions of maven and the maven-war-plugin are you
using?
With regards,
Nick Stolwijk
-Original Message-
From: amit kumar [mailto:[EMAIL PROTECTED]
Sent: Thu 1/31/2008 11:56 AM
To:
Hmm, I don't know why your first example is working, because that is not a
valid layout for the POM. See [1].
Could you give us the output of mvn -e -P your-profile your-goal
With regards,
Nick Stolwijk
[1] http://maven.apache.org/ref/2.0.7/maven-model/maven.html
-Original Message-
Hmm, I've looked at the axis2 wsdl2code plugin and I see your problem: the
plugin is changing the dependencies. It has hardcoded groupId/artifactId
combinations and adds these to the project.
This is not a problem with the war plugin. The wsdl2code plugin should clean up
their changes or not
All Java files under src/main/java will be compiled into WEB-INF/classes in
your final war. (To be honest, all java files will be compiled to
target/classes, all resources from src/main/resources will be copied (and
filtered) to target/classes and finally target/classes will be copied to
Hi Howard,
If you are talking about the org.apache.maven.reporting:maven-reporting-api
artifact. It is up on central from version 2.0 to 2.0.8 with POM, sources and
javadocs. [1]
In the org.apache.maven.reporting:maven-reporting-impl I see an
AbstractMavenMultiPageReport, but I doubt it works
Take a look at the buildnumber plugin[1]. However, this will not be the
timestamp it will have in your remote repository. Just the timestamp (or
revision) of the moment you build.
Hth,
Nick Stolwijk
[1] http://mojo.codehaus.org/buildnumber-maven-plugin/
-Original Message-
From: news
A copy paste of my last mail, which was accidentally replied to th wrong
message.
I don't think you can get the timestamp generated in the deploy phase before
the package phase, in which the artifact is created. I suggest take a look at
the revision part of the buildnumber plugin. At least,
I think I reacted to the wrong message. Sorry for the disturbance.
With regards,
Nick Stolwijk
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tue 1/29/2008 11:29 AM
To: Maven Users List
Subject: RE: Make META-INF optional
I don't think you can get the
I don't think you can get the timestamp generated in the deploy phase before
the package phase, in which the artifact is created. I suggest take a look at
the revision part of the buildnumber plugin. At least, you will be able to see
from which revision your build was build.
Hth,
Nick
Try with scope 'provided'.
See [1] for a explanation of the different scopes.
Hth,
Nick Stolwijk
[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
-Original Message-
From: faisalloe [mailto:[EMAIL PROTECTED]
Sent: Mon 1/28/2008 10:08 AM
To:
If I understand you correctly, you're using the maven-install-plugin to install
files into the remote repository? This way the metadata in the remote
repository is not correctly being updated, so that causes the snapshot not to
be updated in the local repository. Use the maven-deploy-plugin for
I crosspost this to the Maven and Subversion list, because I really don't know
where this issue comes from.
Today a colleague of my tried to do a mvn release:prepare on his machine. This
failed, because of svn certificate errors. (I know, our certificate is not
really proper, but normally it
Yes, there are many reports with mvn.
For a first dive, try mvn site. Then, take a look at the chapter about site
generation. [1]
For dependency listing, add the following to your pom.
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
That is because you didn't install the pom file, but only the jar file. Try
giving -DgeneratePom=true with the install:install-file command.
Hth,
Nick Stolwijk
-Original Message-
From: Angelo Chen [mailto:[EMAIL PROTECTED]
Sent: Wed 1/23/2008 10:02 AM
To: users@maven.apache.org
For what it is worth, I've adjusted the svn_apply_autoprops.py script of
subversion to apply dos2unix to all files, which should have the svn:eol-style
property set. This clearly makes it much easier to clean your repository or
import code into your svn repository. Mind, the new script won't
Yes, that is correct, but
1) Your co-developer forget to set the autoprops, so a file was committed
without the property. If you set the property yourself, it will complain when
the eol's in the file are not correct. If you do this at large with the
svn_auto_props script, it will complain a
Just checked it with subversion 1.4.4 and it seems to work automatically now.
Is this a recent fix? I know I've had problems with it.
Hth,
Nick Stolwijk
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wed 1/23/2008 10:36 AM
To: Maven Users List
Subject: RE:
Jira issue and patch attached: http://jira.codehaus.org/browse/MPIR-83
See comment, but it is a first version.
With regards,
Nick Stolwijk
-Original Message-
From: Guillaume Lederrey [mailto:[EMAIL PROTECTED]
Sent: Wed 1/23/2008 11:43 AM
To: Maven Users List
Subject: Re: Report for
The original svn_auto_props works only on your working copy and the new script,
svn_apply_dos2unix the same. So no automatically changing anything, you have to
review and commit the changes yourself.
And on a sidenote to John: I know again why I needed that script, some of the
files had
1 - 100 of 160 matches
Mail list logo
