If you just need one for depdendency resolution, then you can use
Maven central.
However if you need a Nexus instance to deploy your own artifacts (and
i assume this is what you need since you possibly want to share your
artifacts with your colleagues), you can't use Maven central (except
you
Hi,
i'm using the Maven release plugin to release a project which is
stored in a Git repository. Everything works fine until the git tag
command. The debug Maven output says:
[INFO] Executing: cmd.exe /X /C git commit --verbose -F
C:\Windows\TEMP\maven-scm-1039630102.commit
this pull in?
I have used version 2.1 of the release plugin with git for a few weeks and
have not noticed any problems with it.
Lenni
On Mon, Jun 6, 2011 at 12:12 PM, Manuel Doninger man...@doninger.netwrote:
Hi,
i'm using the Maven release plugin to release a project which is
stored
Eclipse always hides the build results and /target/classes is defined
as build folder in the build path. This happens also with the /bin
folder in a standard Java project.
Besides, this is the wrong mailing list for m2eclipse, you can find
there the right adresses:
org.apache.maven.plugins
maven-eclipse-plugin
1.6
1.6
Well, you should use the maven-compiler-plugin as described in
http://maven.apache.org/plugins/maven-compiler-plugin/howto.html, not
the maven-eclipse-plugin.
Manuel
You can (and i think you should) use the assembly-plugin, if you want
to do that.
Manuel
On Thu, Apr 7, 2011 at 15:08, Rafael Vanderlei
rafaelvander...@gmail.com wrote:
'Course he must use Maven´s dependency management to include dependency jars
in classpath, but if for some reason of his he
install and deploy are redundant. If you look at the Maven lifecycle
(http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html),
then all targets before the one you selected will be executed.
So a deploy calls also call install before. If you choose deploy, then
you don't
I have a job (Maven2 type) which use the maven-release-plugin (it
calls just the targets release:prepare release:perform). Versions are
taken by default (current -SNAPSHOT becomes Release, next Snapshot
version is current + 0.0.1, e.g. 0.0.1-SNAPSHOT - 0.0.1 and
0.0.2-SNAPSHOT).
Batch mode is
You can find the m2eclipse mailing lists here:
http://m2eclipse.sonatype.org/project-information.html
Manuel
2011/3/29 Zbynek Vavros zbynek_vav...@cz.ibm.com:
Does this list also concerns eclipse integration?
Zbynek
Kind Regards / Mit
freundlichen Grüßen /
Üdvözlettel / S
I faced a similar issue some times. I think, it's a bug in m2eclipse,
thus i call mvn dependency:resolve on the command line, before opening
new big projects in eclipse. That prevents eclipse freezing.
Manuel
On Tue, Mar 29, 2011 at 23:47, Dave DaveLists dbfli...@gmail.com wrote:
Hello,
New
We have sometimes problems, if multiple builds on Jenkins use the same
local Maven repository and if those builds download new artifacts.
Then some artifacts are locked by one Maven process, and the other
process fails with an artifact not found error.
Manuel
On Mon, Mar 28, 2011 at 11:32, David
Hello,
i have the following problem: If i call mvn clean process-resources
and then ant directly on my build.xml, then the build is successful.
If i want to execute the antrun-plugin, with mvn compile, then the
build fails with the message
[ERROR] Failed to execute goal
Does the repository group server-devel contain the Maven Central repo
or another group with the Maven Central in its configuration?
If not, that could be the problem.
Manuel
On Wed, Mar 23, 2011 at 18:09, Hahn, Christopher (SAN DIEGO)
christopher.h...@hp.com wrote:
Is this the problem (from the
Description of release:branch: Branch a project in SCM, using the same
steps as the release:prepare goal, creating a branch instead of a tag
branchBase is per default the branches folder. If you want to create
the branch in the tag folder, then you have to provide the property
branchBase with
distributionManagement is the target for the Maven artifacts.
release:perform calls deploy as default, and deploy needs the
distributionManagement. If you do not want this (e.g. only install the
Maven artifact in the local repository), then you have to do something
like this:
plugin
Shouldn't it be C:\Program Files\Java\jdk1.6.0_16 (note the space
between Program and Files)?
On Sun, Mar 13, 2011 at 01:29, James Ahlum jfa...@lehigh.edu wrote:
Hello,
I am attempting to use Maven for the first time, and I'm having trouble
getting it to run. I follow
the installation
Eclipse says:
Embedded Runtime is always used for dependency resolution, but does
not use global settings when it is used to launch Maven.
So i think, there is just no global configuration file for this
runtime, because it doesn't use one.
You have to use the user configuration file or an
Hi,
i have the following constellation: I have a class Feature.java and a
class MapData.java in my folder src/main/java. The Feature contains
some work to do, and the MapData is contains a HashMap which is
populated with data from a database and their methods are called in
Feature. Now i want to
Hello,
I use Hudson with Maven for building my Java Application. I have one
Maven project, where i want to increment automatically the version of
the project in the pom-file everytime when a Hudson-build runs. The
Maven-Release-Plugin isn't suitable in this case because i don't use
On Fri, Oct 22, 2010 at 08:15, wasi_shez wasi_s...@hotmail.com wrote:
I am using XP Windows
1)Install Latest JRE
2)Download Maven 3.0
3)Set JAVA_Home for JRE
4)Set Path for Maven 3.0 upto BIN
Run Command to ensure the installation
mvn --v
Apache Maven 3.0 (r1004208; 2010-10-04
and
maven 3, same results at both instances.
Do you have any ideas?
Regards,
Manuel Doninger
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
21 matches
Mail list logo
