Philippe,
Use the maven-release-plugin
(http://maven.apache.org/plugins/maven-release-plugin/). It does everything
you need to release your artifacts, including automatically incrementing
your version to the next SNAPSHOT release, tagging your release and building
the release for you.
Regards,
(for example, for assembly, finalName${
project.artifactId}-${project.version}-r${buildNumber}/finalName),
just as Greg suggested. Need to make sure to invoke the plugin create goal,
for example mvn buildnumber:create assembly:assembly.
Thanks'
On 2/6/07, Greg Jones [EMAIL PROTECTED] wrote:
Kim
Kim,
You can use the maven-buildnumber-plugin to get a timestamp, as follows:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-buildnumber-plugin/artifactId
version0.9.4/version
configuration
format{0,date,-MM-dd HH:mm:ss}/format
understand why there would be this
dependency on an ear file to simply compile something in one of the main
applications.
I have a feeling this will be the straw that breaks the development camels
back.
-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February
The modules need to be downloaded since they are dependencies at compile
time (the default), even in an EAR package. Modules will never be picked up
from their target directories (part of the design of Maven). You need to run
'mvn install' on the other modules to ensure they are in your local
lifecycle phase?
-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 4:40 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?
The modules need to be downloaded since they are dependencies at compile
time
to run 'mvn compile' in an EAR module but you need your
dependencies to be available in your repository (local or remote).
-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 6 February 2007 10:05 AM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up
release
engineer forced to support maven 2).
Can I forcefully de-couple these two things?
-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:05 PM
To: 'Maven Users List'
Subject: RE: compile tries to bundle up the ear - should it?
It hasn't
file (or
war or ear) just to get your classes to compile. These things shouldn't
even be attempted until the package stage.
This seems like a shortcoming.
-Original Message-
From: Greg Jones [mailto:[EMAIL PROTECTED]
Sent: Monday, February 05, 2007 6:29 PM
To: 'Maven Users List'
Subject
Hi Ken,
Take a look at the options available for the maven-compiler-plugin at
http://maven.apache.org/plugins/maven-compiler-plugin/.
Regards,
Greg J.
-Original Message-
From: Ken Gallo [mailto:[EMAIL PROTECTED]
Sent: Monday, 5 February 2007 2:07 PM
To: users@maven.apache.org
Vaishoo,
The first thing that comes to mind is to check that you are actually using a
JDK, rather than a JRE and that your JAVA_HOME is pointing to a JDK root
directory, not the nin directory.
E.g.
JAVA_HOME=C:\Program Files\Java\jdk1.5.0_11
Or
JAVA_HOME=/usr/lib/j2se5.0-sun
The other thing
Hi Vidya,
Ignore the previous response. The server element in the jboss-maven-plugin
specifies which server definition to use for Jboss, not which (host) server
to use. In your case it is probably 'default' so leave it at that.
I suspect your problem stems from something else. Can you run Maven
[INFO] Finished at: Thu Feb 01 14:55:58 GMT+02:00 2007 [INFO] Final Memory:
2M/5M [INFO]
Greg Jones [EMAIL PROTECTED]
01/02/2007 13:41
Please respond to
Maven Users List users@maven.apache.org
To
'Maven Users List' users
filePermissions/filePermissions
directoryPermissions/directoryPermissions
configuration/configuration
/server
/servers
/settings
Greg Jones [EMAIL PROTECTED]
01/02/2007 15:41
Please respond to
Maven Users List users@maven.apache.org
To
'Maven Users
2007 2:35 AM
To: Maven Users List
Subject: RE: jboss-maven-plugin
Hi Greg,
I have tried that option as well. no luck! my config is very simple and
default
maven2 and jboss 4.0.5.
Regards,
Vidya
Greg Jones [EMAIL PROTECTED]
01/02/2007 17:16
Please respond to
Maven Users List users
Hi Jelle,
You may need to update to the 2.0.5 build to get dependencies in the correct
order. This was the case with plugins and it may be that they fixed this
problem at the same time.
Cheers,
Greg J.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent:
Phillip,
Have a look at the assembly plugin:
http://maven.apache.org/plugins/maven-assembly-plugin/
In particular, take a look at the predefined descriptors:
http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html
The src descriptor should be what you're looking for.
Bryce,
Take a look at the buildnumber plugin. I use it to generate a build date
each time I do a build, as follows:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdmaven-buildnumber-plugin/artifactId
version0.9.4/version
configuration
application.
Regards,
Greg Jones
-Original Message-
From: Steve Wells [mailto:[EMAIL PROTECTED]
Sent: Monday, 29 January 2007 9:51 AM
To: Maven Users List
Subject: Re: Searching for maven start plugin?
Try this:
http://mojo.codehaus.org/exec-maven-plugin/introduction.html
On 29/01/07, Martin
Sebastian,
You also need to add the repository as a plugin repository, as follows:
pluginRepositories
pluginRepository
idApache SNAPSHOTS/id
nameApache SNAPSHOTS/name
urlhttp://people.apache.org/repo/m2-snapshot-repository/url
releases
enabledtrue/enabled
and found a resolution?
Thanks in advance,
Greg Jones
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
21 matches
Mail list logo
