You could start a release branch with the release plugin and start
releasing release candidates, like 1.2.3-RC1, 1.2.3-RC2, etc, until
you have a final release and release that as 1.2.3.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Fri,
Hi,
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: 13 November 2008 18:14
To: Maven Users List
Subject: Re: Tomcat projects
Google tells me there are a few tomcat plugins for Maven.
http://mojo.codehaus.org/tomcat-maven-plugin/
http://cargo.codehaus.org/
2008/11/14 [EMAIL PROTECTED]
Hi,
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: 13 November 2008 18:14
To: Maven Users List
Subject: Re: Tomcat projects
Google tells me there are a few tomcat plugins for Maven.
Hi all,
I have recently been doing some investigation into making Artifactory
Highly Available, and to be honest am having difficulty in finding an
acceptable solution. To date the only solution I have found is having a
'cluster' of 2 Artifactory repositories which are load balanced. Each
I know Artifactory is built upon Jackrabbit. Maybe you can cluster the
underlying Jackrabbit instance? Take a look at clustering,
http://wiki.apache.org/jackrabbit/Clustering.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Fri, Nov 14,
Whenever I do an mvn install, it creates a Xyz-sources.jar and takes a lot of
time creating that jar.
I am not interested in the sources jar. How do I avoid that step during the
install of a project ?
Thanks in Advance,
Chandresh
Hi
I need help with the ear plugin.
I have the following pom:
?xml version=1.0?
project xmlns=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;
parent
Hi Jack,
when you want to deploy an artifact to the remote repositories such as
Archiva
you will need to add an wagon extionsion to you build.
I have importe a maven project into Eclipse through: FileImportMaven
Projects.
Then, in order to execute some maven goals, I right-clicked on the
On Fri, Nov 14, 2008 at 4:59 AM, [EMAIL PROTECTED] wrote:
Whenever I do an mvn install, it creates a Xyz-sources.jar and takes a lot of
time creating that jar.
I am not interested in the sources jar. How do I avoid that step during the
install of a project ?
Put the configuration for the
I have a running configuration which uses:
org.codehaus.mojo:hibernate3-maven-plugin
everything works fine. but now I want to use another plugin from
org.codehaus.mojo:
the maven-buildnumber-plugin:
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html
thus I must add another
I have noticed this as well. If you try and excute a project with
m2eclipse, you need to specify a wagon. However, if you run the same
command from the command line, a wagon seems to already be defined, ever
if you don't have one specified in your POM. BTW, there are other
inconsistencies as
Nexus has a few users that are sharing the storage between separate
Nexus instances directly via some shared backend like a SAN. Since Nexus
uses just a regular m2 repo layout for storage, the options for
clustering them are much greater and simpler.
-Original Message-
From: Matthew
It has nothing to do with the EAR plugin. Your pom is wrong. The
default type for a dependency is jar. If you want to depend on a war,
you must specify it.
So
dependency
groupIdch.ildsoftware/groupId
artifactIdildContact/artifactId
version1.0-SNAPSHOT/version
typewar/type
Hello Kruno, This may be due to the layout of your repository, as you may
know the layout has changed between Maven 1.x (legacy) and Maven 2
(default).
Check your //project/distributionManagement/repository/layout
w
On Tue, Nov 11, 2008 at 4:55 PM, Kruno [EMAIL PROTECTED] wrote:
Hello,
I
Hello,
I have an EJB 2.1 project (the relevant POM snippets below). If I want to
compile it I get a Build Failure:
Compilation failure ..
symbol: method lookup(java.lang.String)
location: interface javax.ejb.SessionContext
Why ? What is wrong with the POM ? How do I have to reference the J2EE
Do you require the full release process with a tag for every
one of these versions, or would unique snapshots (with the
revision number baked inside) work for you?
We don't *require* tags at each iteration, but since its been our
practice to use the 'release' plugin to deploy, extra tags are
That's effectively what happens during the [internal] QA process. We
release 1.2.3-RC-1, ..., up to n, as needed. When its been qualified by
the QA folks, the artifact is re-released *without* the '-RC-x' suffix.
After some basic smoke tests, a request is made to deploy the artifact
into UAT
Edderd wrote:
I get the same output even if I disable my archiva repository and I'm
wide open.
Here's the output with -e:
Have a look at this link - it may help:
http://www.5341.com/msg/134177.html
Otherwise I have no idea myself, sorry.
Peter
--
View this message in context:
Hello,
This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No
other issues where identified in RC2 so hopefully this will become the
last RC.
Here's the list of issues fixed in 2.0.10:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112styleName
Hey everyone. I am bumping this and also including the maven users list
to see if anyone else has any further insite. I have been doing a
little bit of digging and I believe I understand the problem that Brian
and Igor were aluding to. I believe it has been referred to as the
inheritance
Hi Brian,
I've tried the RC3 but it seems to be the old RC2. I've downloaded
distinct packages (tar.gz and zip) on different browsers (Safari and
Firefox) to avoid any cache problems. :(
Following is the mvn -v output:
Maven version: 2.0.10-RC2
Java version: 1.5.0_16
OS name: mac os x
On Fri, 14 Nov 2008, Brian Fox wrote:
Hello,
This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). No
other issues where identified in RC2 so hopefully this will become the
last RC.
Here's the list of issues fixed in 2.0.10:
Guys,
I didn't find a way to do this, so just though to check and in my opinion if
we add this feature, it would be pretty handy in my opinion. Something which
my IT/RollOut team asked for when they were cutting a branch.
So what i am looking for is a way to quickly check/review the changes in
The version is correct but it does seem to have the wrong embedded
version. There must be a property in the pom that the release plugin
didn't update.
On the wagon-ssh, I'm not having issues, can you give more info on how
to reproduce it? Does 2.1M1 work for you? (I ported back the exact fix
from
24 matches
Mail list logo
