Hi all.
Is there any way of making automatically one project to be built if it's
parent has been changed
I mean, I have two projects, one of them is both parent and imported
from the other. My question is, supposing that the parent is updated and
built, if is it any way to make the child to
I can set user and group _mode_, but how do i set the user and group itself?
My assembly gets built as root:root, which is not what i want.
I checked the mailing list and the schema to no avail. Am i missing
something very obvious here?
--
View this message in context:
Hi,
at buildtime, we deploy a generic our-product.ear, containing a file
version.properties.
# Datum des Builds
build.startDate=${build.startDate}
# Buildversion
productVersion=${productVersion}
# Productname
productName=${productName}
At delivery time we need to patch the
Can you build from the parent project? That shold trigger the child project
to be built if you've set it up correctly. I haven't tested the idempontency
of Maven but I think it works like Ant, only building what needs to be
rebuilt unless you run a clean prior.
Carlos Alonso-2 wrote:
Hi all.
Torsten;
[EMAIL PROTECTED] schrieb:
# Datum des Builds
build.startDate=${build.startDate}
# Buildversion
productVersion=${productVersion}
I believe that maven resource filtering does pretty much what you want,
only I am not sure how / whether or not to determine things like
The release plugin works well with multi-modules projects.
But it breaks with this kind of layout.
To make your layout works, you surely had to add in modules poms a
relativePath tag to ../Parent, e.g :
parent
groupIdyourGroupId/groupId
artifactIdParent/artifactId
I have the problem when I also use the following:
parent-pom.xml:
modules
module..\test-module/module
/modules
So this is a known bug? Or should I raise an issue about this? It seems as
though the release plugin should be able to cope if a mvn install works ok.
Hi,
I know about filtering - but that´s not what I want exactly.
My problem is that we build (and deploy) the ear at one time (filtering is
done at build time), but the delivery of the ear into our product (ears,
wars, documentation and so on) is separated.
I need to patch the ear at delivery
I didn't find a bug in Jira. Think you should add one :
http://jira.codehaus.org/browse/MRELEASE
On Mon, Jul 14, 2008 at 3:01 PM, Richard Chamberlain
[EMAIL PROTECTED] wrote:
I have the problem when I also use the following:
parent-pom.xml:
modules
Oups I found it : http://jira.codehaus.org/browse/MRELEASE-6
It is closed and there is a lot of stuff.
On Mon, Jul 14, 2008 at 4:18 PM, Julien Lamandé [EMAIL PROTECTED] wrote:
I didn't find a bug in Jira. Think you should add one :
http://jira.codehaus.org/browse/MRELEASE
On Mon, Jul 14,
Hi,
ths feature doen't currently exist.
please consider opening a jira enhancement at
http://jira.codehaus.org/browse/ARCHETYPE
Thanks,
Raphaël
2008/7/13, sverhagen [EMAIL PROTECTED]:
I am making an archetype for my project. I added a requiredProperty named
serviceBaseName to make the
I would like to obfuscate the jar, war and ear packages so class, variables,
methods, attributes names are changed and Strings are encrypted.
-Mensaje original-
De: Wayne Fay [mailto:[EMAIL PROTECTED]
Enviado el: Viernes, 11 de Julio de 2008 11:05 a.m.
Para: Maven Users List
Asunto: Re:
Awesome. Thanks for looking. It seems as though there are two workarounds for
this on JIRA item http://jira.codehaus.org/browse/MRELEASE-261
-Original Message-
From: Julien Lamandé [mailto:[EMAIL PROTECTED]
Sent: 14 July 2008 15:21
To: Maven Users List
Subject: Re: release plugin
One of my artifacts takes a long time to generate sources (around 5
minutes).
I've noticed that when I use the release plugin to release this artifact it
performs that generation at least 3 times.
I am using the maven-source-plugin across all my projects. Maybe i'll
disable that..
Any other
One of my artifacts takes a long time to generate sources (around 5
minutes).
I've noticed that when I use the release plugin to release this artifact it
performs that generation at least 3 times.
I am using the maven-source-plugin across all my projects. Maybe i'll
disable that..
Any other
On Sun, Jul 13, 2008 at 2:33 PM, in the [ANN] Maven Site Plugin
2.0-beta-7 Released thread, Dennis Lundberg [EMAIL PROTECTED]
wrote:
Giovanni Azua wrote:
Many thanks! Yes the mvn help:effective-pom shows it is picking up the
2.0-beta-6 under pluginManagement section ...
Then you need to
Hi,
I am new to Maven so please excuse if my question is not very smart ;) (and
please excuted my english)
when I create several profiles for my environments (e.g. integration_test,
system_test, user_test, ...) and i perfrom the build, how do I seperate the
builds in my repository? (because
Hi,
it might not be the answer you are looking for, but we have placed that
functionality in our CI platform, which is Hudson in that case.
In fact it's a core feature of Hudson if you are defining Maven based jobs.
HTH
Andreas
Carlos Alonso schrieb:
Hi all.
Is there any way of making
On Mon, Jul 14, 2008 at 1:10 PM, fuppes [EMAIL PROTECTED] wrote:
when I create several profiles for my environments (e.g. integration_test,
system_test, user_test, ...) and i perfrom the build, how do I seperate the
builds in my repository? (because the packages {ear, war} are differend
We also use our CI (or Build Management System) to do this. Although we
do 'push' style and not 'pull' dependencies). We're CI so I know we have
a latest good build already but I can trigger a 'dependent' to build if
it's 'dependency' has built successfully.
===
-Curt
W: 860.702.9059
M:
Is there a way to prevent javadoc from occuring during release? I would also
like to prevent production of source JAR. Any ideas?
Hi there
I had to solve a similar problem, but not with an ear. My build process
produces a bunch of archives that
at some point need to deployed in a target environment (a proprietary
ESB in that case). I have done a prototype
that does the following (quite elaborate, but seems to be
Hi again
this is true for us as well. Whenever the master is buildt succesfully
it triggers the build
of the dependent projects. It's also the master pushing, not the
dependent projects pulling
for a change.
Andreas
Yanko, Curtis schrieb:
We also use our CI (or Build Management
Hi there,
you could do the following include the plugin configuration in a profile
and make sure that profile is only activated when you execute a module
build.
That would allow you to keep the build spec in just one place - the
master pom, but use it only for the modules (I assume that is
On windows xp, I am getting the following error. How can I fix it
D:\projects\oss\openejb3mvn -Dassemble clean install
[INFO] Scanning for projects...
[INFO]
[ERROR] FATAL ERROR
[INFO]
Here is the same thing in debug mode
D:\projects\oss\openejb3mvn -Dassemble clean install -X
+ Error stacktraces are turned on.
Maven version: 2.0.9
Java version: 1.5.0_15
OS name: windows xp version: 5.1 arch: x86 Family: windows
[DEBUG] Building Maven user-level plugin registry from:
Set MAVEN_OPTS= -XmX128m or some other size you want.
-Original Message-
From: Karan Malhi [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2008 5:25 PM
To: Maven Users List
Subject: Re: out of memory
Here is the same thing in debug mode
D:\projects\oss\openejb3mvn -Dassemble clean
On Tue, 15 Jul 2008 07:05:52 Kallin Nagelberg wrote:
thats hilarious did anyone else get three copies of that email ;-)
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL
Hi,
How are things going.
I finally managed to get onto a project that is working on reasonable
technology.
Rosco still working with you?
Ciao
Frank
On 13/07/2008, at 9:07 PM, Stephen Coy wrote:
In JEE5, jars in an EAR's lib directory do not need to be in the
EJB jar's manifest
Yes I appear to be plagued with duplication.
On Mon, Jul 14, 2008 at 5:35 PM, Michael McCallum [EMAIL PROTECTED] wrote:
On Tue, 15 Jul 2008 07:05:52 Kallin Nagelberg wrote:
thats hilarious did anyone else get three copies of that email ;-)
--
Michael McCallum
Enterprise Engineer
Doesnt help, still the same error
On Mon, Jul 14, 2008 at 5:34 PM, Brian E. Fox [EMAIL PROTECTED]
wrote:
Set MAVEN_OPTS= -XmX128m or some other size you want.
-Original Message-
From: Karan Malhi [mailto:[EMAIL PROTECTED]
Sent: Monday, July 14, 2008 5:25 PM
To: Maven Users List
Hi Dennis,
I did that and now all occurrences of site-plugin when running
help:effective show 2.0-beta-7, MSITE-274 fix still does not work for me
though :(
TIA,
Regards,
Giovanni
-Original Message-
From: Dennis Lundberg [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 13, 2008 11:33 PM
32 matches
Mail list logo