After reading a bit of the debate I wonder a few things. I read stay away
from profiles a lot but I do find them to be very useful.
So what's the alternative on profiles? Assuming there is a modular project
with several jars, several wars and several ears. Each of those artifacts
can be
What are you trying to build?
The project will build one artifact and the assembly plug-in will build
another.
Are you sure you need 3 artifacts to be built?
We use maven to build web services which include both a client jar and a
war for the service but we only need 1 execution.
Ron
On
On 14 December 2010 08:06, fhomasp thomas.peet...@realdolmen.com wrote:
After reading a bit of the debate I wonder a few things. I read stay away
from profiles a lot but I do find them to be very useful.
So what's the alternative on profiles? Assuming there is a modular project
with
On 14/12/2010 3:06 AM, fhomasp wrote:
After reading a bit of the debate I wonder a few things. I read stay away
from profiles a lot but I do find them to be very useful.
So what's the alternative on profiles? Assuming there is a modular project
with several jars, several wars and several
I didn't mean huge changes for the different platform. The usual changes
for the specific environments switched with profiles are usually those
property files you're talking about.
So the codebase remains the same, but assuming I build my ear using property
files for the validation platform,
Hello,
Can I exclude test dependencies in the maven-dependency-plugin? I'm
using this plugin to copy all dependencies to a specific directory so the
izpack plugin can package them into an installation application. However, it
seems the dependency plugin is also copying the test
On 14 December 2010 08:50, fhomasp thomas.peet...@realdolmen.com wrote:
I didn't mean huge changes for the different platform. The usual changes
for the specific environments switched with profiles are usually those
property files you're talking about.
So the codebase remains the same, but
One other issue with rebuilding the artifacts is that you're going to have
problem if you want to do it the Maven way by deploying to a repo. As there
can only be one flavor of a specific version of an artifact, you can't
rebuild without bumping version. (Yes, you should never ever
Your rant makes sense Stephen and I'm already glad I asked :-)
I honestly have never been in a development environment where rebuilding an
artifact was a problem. But ok, I see the idea of keeping the build. But
if everything is the same, except for property files, what's the problem
with
Distributable zip files including readmes, shell scripts and a single jar with
all dependencies. I've got a jar coming from the project, then the assembly
plugin creates a jar with dependencies, and the two distributions. The only
difference between the two distributions are the names of the
On 14 December 2010 09:45, fhomasp thomas.peet...@realdolmen.com wrote:
Your rant makes sense Stephen and I'm already glad I asked :-)
I honestly have never been in a development environment where rebuilding an
artifact was a problem.
But did you ever ask why it was OK to rebuild the
http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html#excludeTransitive
On 14 December 2010 01:35, Erwin Mueller erwin.muel...@deventm.org wrote:
Hello,
Can I exclude test dependencies in the maven-dependency-plugin? I'm
using this plugin to copy all
Ok.. Thanks!
FYI all questions I ask are not posed to doubt your answers and
observations. Merely so I'd understand it better.
stephenconnolly wrote:
But did you ever ask why it was OK to rebuild the artifact in those
environments?
Actually, yes. The answer to that usually has
Hello everybody,
I don't see any way to be able to import a maven project of type war with
linked folder pointing to jsp.
M2Eclipse takes my definition of maven-war-plugin as input:
plugin
groupIdorg.apache.maven.plugins/groupId
My project depends on a 3rd party library for OpenGL + Java called JOGL
(http://jogamp.org/jogl/www/)
The library is currently not maven-ized and I'm trying to find the best
way to achieve that. My progress is documented at:
HI,
I'm trying to do the following:
My POM uses the exec-maven-plugin to start an external process.
This is used to install software after the build process created an
installer.
If this process can't finish the installation, my maven build fails.
That is how it should be.
In this case I
Hallo,
I did know about this but it's not what I want. I want to exclude all
dependencies in the test scope. I don't want to exclude transitive
dependencies.
But you pointed me in the documentation which I overlooked. I need
excludeScope. Thank you.
On Tuesday 14 December
Well, I can tell you how I deal with it..
I have all editions of our native libraries bundled inside a single jar file, I
created.
./win32/libsomething.dll
./win64/libsomething.dll
./unix/x32/something.so
etc
and unpacks that into lib (similar to what you did).
During test and execution we
Hi
I have a multi modules project with a jar module and war one.
Actually I don't want to deploy 2 of my jar module dependencies to the war,
so I put a scope provided in the jar module pom. But when I run mvn
install I get the following error :
[INFO]
Eric Haszlakiewicz wrote:
-Original Message-
From: cowwoc [mailto:cow...@bbs.darktech.org]
Wayne Fay wrote:
What do you recommend I do to work around this problem?
Don't use the ${swt.classifier} for now...
You may notice it was reported 5 years ago so if you actually want it
[ERROR] Failure executing javac, but could not parse the error:
An exception has occurred in the compiler (1.6.0_23). Please file a bug at
the Java Developer Connection (http://java.sun.com/webapps/bugreport) after
checking the Bug Parade for duplicates. Include your program and the
I don't see any way to be able to import a maven project of type war with
linked folder pointing to jsp.
directory../shared-jsps/src/main/webapp/directory
Currently what it does is to copy all the files contained in
shared-jsps/src/main/webapp... I don't find a solution to this issue.
Move
Is there any possibility to configure the exec-maven-plugin (or any other
existing plugin) in a way, that I can catch the maven build error of the
install-execute-process and use is as a trigger, that starts the
re-install-process?
I doubt this functionality exists in any current plugin. But
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
at the moment I am trying to figure out how to use the WebStart plugin.
Everything works fine, when I add the path to the keystore location and
the keystore password into the pom. But of course I'd prefer to store
those values within
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Think I have solved it:
sign
keystore${keystore.location}/keystore
storepass${keystore.pass}/storepass
alias${keystore.alias}/alias
/sign
On 12/14/2010 09:21 PM, Johannes Schneider wrote:
Hi
These replies have been incredibly helpful, thanks especially to Ron and
Stephen for your investment in them!
Very accidentally, I have fallen into the MV-SOA pattern. I am using Mule
for the services container with the VM connector for speed and ease of
iterative development, knowing that I
On 14/12/2010 4:10 PM, Brian Topping wrote:
These replies have been incredibly helpful, thanks especially to Ron and
Stephen for your investment in them!
Very accidentally, I have fallen into the MV-SOA pattern. I am using Mule
for the services container with the VM connector for speed and
antrun anyone
On 14 December 2010 17:15, Wayne Fay wayne...@gmail.com wrote:
Is there any possibility to configure the exec-maven-plugin (or any other
existing plugin) in a way, that I can catch the maven build error of the
install-execute-process and use is as a trigger, that starts the
I posted a reply to this on stackoverflow, since that's where you
included more details. The bottom line was that the properties are
*not* defined in A or B, only in *profiles* in A and B. And there's
the rub: those profiles do not apply when building C, and the property
is not defined anywhere
It's a strange error but possibly you have a direct dependency to jpa from
your classes in the war and you haven't declared it (but rather relied on a
transitive dependency to jpa for compilation, but now when that has been
removed compilation fails).
Always declare your (direct) dependencies.
30 matches
Mail list logo
