, on dev@ list
--benson
On Mon, Sep 24, 2012 at 4:41 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Markus,
perhaps you mis-understood my point.
this is a hard problem, that does not mean we should shirk away...
that does mean we have to solve it very close to right
Maven shade plugin can relocate all the classes into a different package
for you in minutes of config and seconds of build time
On 24 September 2012 13:43, Eric Czech eczec...@gmail.com wrote:
Hi everyone,
I'm continually running into issues with Guava dependencies where the
version of Guava
depend on Guava 13.0.1, how can I make sure that each is
referencing the correctly shaded version when they're built into a
jar?
On Mon, Sep 24, 2012 at 8:55 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Maven shade plugin can relocate all the classes into a different package
1. Maven is not just about java (though very java focused I admit) endorsed
does not make sense outside of java
2. Whether a dependency needs to be endorsed or not depends on the jvm
version it targets... A dep can be fine until it gets added to the jvm spec.
3. It should probably more correctly
answer
Best,
John
On Tue, Sep 18, 2012 at 10:34 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
There are some limits to this... perhaps due to some bugs in how Maven
handles this type of thing e.g.
This requires Maven 3.0 or newer to work. When you try to use this in
Maven
There are some limits to this... perhaps due to some bugs in how Maven
handles this type of thing e.g.
This requires Maven 3.0 or newer to work. When you try to use this in Maven
2.x you will get a error such as:
$ mvn eval
[INFO] Scanning for projects...
[INFO]
+1
On 16 September 2012 10:24, Robert Scholte rfscho...@codehaus.org wrote:
Hi,
The Mojo team is pleased to announce the release of the Mock Repository
Manager version 1.0-beta-1.
The Mock Repository Manager suite of projects are used to provide mock or
lightweight Maven Repository
Beware the gpg signatures. Also some people use properties in the depMgmt
section of a parent Pom to allow bulk dep changes, so inheritance can be
screwed over.
Tl;dr this is a hard problem that looks easy
On Thursday, 13 September 2012, Gebhardt, Joern wrote:
Hi,
I created a
I have used maven for CD on some projects... But I find CD to be less
useful than a simple release often approach.
The key take home of CD for me is that you always should be able to release
the master branch. That no long lived branches should exist is secondary.
Actually pushing releases every
On 29 August 2012 14:14, Thomas Broyer t.bro...@gmail.com wrote:
On Wed, Aug 29, 2012 at 12:43 PM, TarunKhandelwal
tarunkhandelwa...@gmail.com wrote:
Hi Brian,
Can you please elaborate what you meant because when i tried with
packaging
jar everything worked fine, but with par file its
They could follow the maven conventions though rather than hack the effects
in the way they have.
-S
On 23 August 2012 07:19, Aldrin Leal ald...@leal.eng.br wrote:
Github does have a plugin for this as well
https://github.com/github/maven-plugins
Easy to use, I think:
Probably, though you might want to ensure that you switch back the groupId
;-)
On 22 August 2012 23:22, Kathryn Huxtable kath...@kathrynhuxtable.orgwrote:
Should I be pulling that and deploying? -K
On Aug 22, 2012, at 7:12 AM, Stephen Connolly wrote:
Here is my fork https://github.com
TL;DR: No
Long version:
A custom phase can only be defined in the scope of a custom lifecycle.
The command line does not provide a mechanism to access the phases of
custom lifecycles directly.
It may be possible to reference a lifecycle from one plugin in a different
plugin, I have not
No.
On 23 August 2012 13:56, Pascal Rapicault pas...@rapicault.net wrote:
Hi,
I would like to know if there is a way to have a plugin be executed right
at the end of the build no matter what.
The situation I have is as follow. Early on in the build I rename a file
from a.txt.off to a.txt
You could add a second execution of the compiler, resources, etc plugins
with an alternative output directory... but that way madness lies.
A far far better approach is to just build your jars with the debug info
present always.
The use a separate tool to strip the debug info from the jars that
On 22 August 2012 13:03, Thomas Scheffler thomas.scheff...@uni-jena.dewrote:
Am 22.08.2012 12:48, schrieb Olivier Lamy:
Not very well supported currently natively by our own Apache maven stuff.
But have a look here
http://khuxtable.github.com/wagon-gitsite/usage.html
Thank you for
Here is my fork https://github.com/stephenc/wagon-gitsite which has support
for deploying multi-module projects (which is what I needed)
On 22 August 2012 13:09, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
On 22 August 2012 13:03, Thomas Scheffler thomas.scheff...@uni-jena.dewrote
On 22 August 2012 13:06, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
You could add a second execution of the compiler, resources, etc plugins
with an alternative output directory... but that way madness lies.
A far far better approach is to just build your jars with the debug info
mv ~/.m2/repository ~/.m2/repository.bak
mvn verify
rm -rvf ~/.m2/repository
mv ~/.m2/repository.bak ~/.m2/repository
That is the easiest with least risk of throwing away and custom deps that
you have installed locally and want to ensure they are deployed to your
repo manager
On Tuesday, 21
Rule #1. One consumable artifact per module
Rule #2. Active profiles should not affect the generated artifacts.
You are breaking both rules.
w.r.t. Rule #1
You generate an assembly and a .jar from the same module... Much pain will
ensue.
There are some circumstances where this rule seems to be
Scheffler thomas.scheff...@uni-jena.dewrote:
Am 17.08.2012 10:36, schrieb Stephen Connolly:
Why don't you bind add dependency:copy-dependencies to the site phase.
and
configure it to copy the zip you want. Much less dangerous
The ZIP file is build in the package phase and that's why I want to add
If by 'fixed' you mean RELEASE and LATEST no longer update, yes that
functionality is gone in 3.0 IIRC
On Saturday, 18 August 2012, Billy Newman wrote:
Out of curiosity is this 'fixed' in maven 3?
Thanks
Sent from my iPhone
On Aug 17, 2012, at 2:06 PM, Gandhi, Pawan
Why don't you bind add dependency:copy-dependencies to the site phase. and
configure it to copy the zip you want. Much less dangerous
On 17 August 2012 09:32, Thomas Scheffler thomas.scheff...@uni-jena.dewrote:
Hi,
I made a maven project where the assembly plugin creates a zip file. I
want
If we ever fix test-jar packaging the optional will make sense ;-)
On Tuesday, 14 August 2012, Laird Nelson wrote:
One other I've spent too much time on this question.
I've been working with Maven for years, so understand it pretty well. But
this particular combination of options has always
Surefire does not currently run tests in test-jar dependencies. The best
option for now is to use dependency:unpack-dependencies and
build-helper:attach-test-classes
On Friday, 10 August 2012, Ansgar Konermann wrote:
You could try this: configure m-surefire-p and replace the default,
ant-style
On 27 July 2012 01:59, John Rodriguez john.rodrig...@gmail.com wrote:
I just started using maven-failsafe-plugin and
maven-surefire-report-plugin so my apologies in advance...
For starters, I've configured maven-failsafe-plugin and
maven-surefire-report-plugin as such (respectively):
failsafe:integration-test will *never* fail the build, that is what it is
designed to do.
you are not understanding how to use it if you think invoking directly on
the cli is the way to go.
I suggest using a profile to bind the executions to the lifecycle
you'd then be typing
mvn
version ranges are not supported for plugins
On 3 August 2012 19:08, Garrison, Jim (ETW) jim.garri...@nike.com wrote:
According to
http://maven.apache.org/ref/3.0.3/maven-model/maven.html#class_plugin,
which is linked from the
build
plugins
plugin
...
One word: inheritance
If your parent has say foo.version=1.0 and declares multiple dependencies
with version${foo.version}/version then when your Pom wants to bump to
1.1 you are forced to re-declare all inherited dependencies.
Now I am not saying that is best practice, but there are good people
I don't know what Sonatype have decided with respect to polyglot.
From my personal PoV I see polyglot more as an experiment to find the best
v5 pom format rather than an on-going support for multiple formats.
Maven is supposed to be an opinionated build tool, with opinionated being a
feature...
1. you will need inheritedfalse/inherited on the execution
2. it aint going to work
On 1 August 2012 08:44, e92-33...@seznam.cz wrote:
Hello,
I am trying find out how to run some plugin (some aggregator) only once,
after the build finish.
I have tried this solution:
I suggest binding to the pre-integration-test phase as there is no
guarantee that the dependency plugin will always execute before failsafe if
you are binding to the integration-test phase
On 30 July 2012 11:12, Markus Karg k...@quipsy.de wrote:
Thanks to all for all the kind help!
In fact I
Cannot be classifiers, as he needs different dependencies.
May also want to use tool chains rather than hard coding Jdk paths
On Monday, 23 July 2012, Ron Wheeler wrote:
It sounds like you have 2 artifacts at the end.
One that is compiled and built with 1.5 and will run under 1.5 JVM and
hack any day over proper but
broken.
Kalle
On Thu, Apr 21, 2011 at 12:23 AM, Stephen Connolly
stephen.alan.conno...@gmail.com javascript:; wrote:
fyi that is a hack and may not work in future versions when the bug is
fixed
- Stephen
---
Sent from my Android phone, so random
What none of us know is the scope of changes between this artifact and the
original...
if all you are doing is rolling a cut from the latest SCM head because you
cannot wait for the next release = just change the version
if you are majorly refactoring in such a way that the API or behaviour
repo)
On 17 July 2012 15:09, Michał Zegan webczat_...@poczta.onet.pl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
For example recompiling to drop compatibility with unsupported jsr14
(namely osgi 4.3).
W dniu 2012-07-17 16:05, Stephen Connolly pisze:
What none of us know
The solution is to use a junit assumption to skip the test, e.g.
Assume.assumeThat(Test fails on windows,
System.getProperty(file.seperator.char), is(/));
Added to the start of each test method will cause them to be skipped on windows
but run elsewhere...
Note I am on my phone and memory is
On Friday, 13 July 2012, wrote:
Hi all,
I made some tests with the Versions Maven Plugin and the behaviour of the
goal versions:update-properties is different from my expectation.
I have two artifacts in my repository:
1. pom-projet-a with the version 1.4.0 and 1.5.0-SNAPSHOT
2.
On 13 July 2012 10:01, sandra.kosma...@de.rhenus.com wrote:
On Friday, 13 July 2012, wrote:
Hi all,
I made some tests with the Versions Maven Plugin and the behaviour of
the
goal versions:update-properties is different from my expectation.
I have two artifacts in my repository:
tidy-maven-plugin @ mojo (only a snapshot release) will apply the canonical
pom ordering but does not handle indenting (in fact it tries to keep all
the indenting the same
On 13 July 2012 14:49, Nord, James jn...@nds.com wrote:
Hi all,
I'm wondering if anyone knows of a command line formatter
the default wagons in Maven 3.0 were trimmed. you will need to add the
appropriate wagon as a build extension
On 13 July 2012 17:11, Thanos Kyritsis dj...@linux.gr wrote:
Hello,
I am trying to migrate from maven 2.2.1 to maven 3.0.4. My configuration
involves a private ssh/scp server acting
Each plugin invokation gets its own classloader as this is to allow for
different versions of the same plugin being used in a multi-module project,
also to allow for injecting different dependencies into a plugin.
On 12 July 2012 06:55, Oleg Estekhin oleg.estek...@gmail.com wrote:
HI, thanks
not see dependency/library classes that
are already initialized by the first class loader, and so it reloads and
initializes them for the second time.
-Исходное сообщение- From: Stephen Connolly
Sent: Thursday, July 12, 2012 12:42 PM
To: Maven Users List
Subject: Re: problem: Maven
Override back to ${arguments} -Psonatype-...
On Thursday, 12 July 2012, Todd Nine wrote:
Any idea how to merge the two? I obviously want command line arguments,
putting our S3 creeds into a public repo isn't a very good idea! ;)
--
Todd Nine
On Thursday, July 12, 2012 at 2:14 PM, Ansgar
yours since you don't control the parent
On 12 July 2012 22:35, Todd Nine tn...@apigee.com wrote:
Thanks Stephen!
Do I need to do that in the parent pom or in mine?
--
Todd Nine
On Thursday, July 12, 2012 at 2:33 PM, Stephen Connolly wrote:
Override back to ${arguments} -Psonatype
Hi everyone,
I just posted on my blog about an idea to get some more committers involved
in the Maven project:
http://javaadventure.blogspot.ie/2012/07/do-you-want-to-become-maven-committer.html
If you are interested sign up.
Also please consider tweeting, google+ing, facebooking, etc so we
Have you given a look at the ship-maven-plugin?
On 5 July 2012 15:12, hujirong jirong...@gmail.com wrote:
Hi
The objective is to achieve continuous delivery in my RTC/Maven
environment.
Up to now, we have a continuous build running all the time to generate and
upload the project ear files
you guess wrong. it just likes to work with non-SNAPSHOT versions, but that
can be overriden
On 5 July 2012 16:32, hujirong jirong...@gmail.com wrote:
Many people doesn't like the maven-release_plugin so we are not using that,
so I guess this ship plugin can't be used as well?
--
View this
On 3 July 2012 15:55, Dmitry Trunikov dmitry.truni...@zoral.com.ua wrote:
Hi All,
It seems that my question has an obvious answer. Unfortunately googling
didn't give me a good one.
Prerequisites:
I have a classical multi-module project. The root POM declares two
modules: 'api' and
On 4 July 2012 09:46, Dmitry Trunikov dmitry.truni...@zoral.com.ua wrote:
javac will only recompile classes that have changed. it does not do
dependency analysis, so a breaking change will only cause a compile failure
until you do clean
Thank you for clarification.
Is there any way
Keep in mind that the reactor in general resolves the jar within the
multi-module project... so you don't know which source files changed as
easily and therefore you don't know which .class files to remove
If you run with -DskipTests most builds are very fast anyway (hey I
regularly rebuild all
Toolchains is the maven way for such
On 27 June 2012 17:28, Bodhayan Chakraborty bodhay...@gmail.com wrote:
Hi,
I want to execute a maven plugin with a defined JDK irrespective of the JDK
that invoked the mvn command. I have developed a plugin which invokes a
API. That API can run only in 32
Sorry mis-read... nope you can't do that...
You could probably do some hook with toolchains to fork a maven
instance with the JDK pulled from toolchains though
On 28 June 2012 11:57, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
Toolchains is the maven way for such
On 27 June 2012
This will require you to write a plugin and venture into scary land!
On 28 June 2012 11:58, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
Sorry mis-read... nope you can't do that...
You could probably do some hook with toolchains to fork a maven
instance with the JDK pulled from
Hi,
The Mojo team is pleased to announce the release of Animal Sniffer version 1.8.
This is the sixth release of Animal Sniffer
(http://mojo.codehaus.org/animal-sniffer/) since it moved from
java.net to the mojo project at codehaus. We have fixed a
bug
Did you see if the artifact in the repo has an incorrect checksum deployed
to the repo? There are a couple of repos that did not enforce checksum
validation/repair... And maven 2.1.0 through 2.2.0 deploy incorrect
checksums to remote repos (which is why we say don't use those versions)
On
From what I recall, nobody has yet updated dependency:tree to query
aether's graph directly rather than go through the emulation of 2.x's API
for examining the dependency tree. When I last chatted on this with
Benjamin, he left me with the distinct impression that I should not rely on
the output
Animal-sniffer @ mojo is your man for that
On Monday, 4 June 2012, wrote:
Hi all,
Is there any issue with maven toolchains plugin?
It seems that nobody use it…
I would like to ensure that my build is compatible with a specific version
of the JVM even if the JVM that running
things just stay the
same there is nothing to change.
I would greatly appreciate it if this 'plan' could be inspected and
criticized/poked/verified/etc.
Thanks in advance
Rolf
On 29/05/2012 11:38 AM, Rolf Lear wrote:
On Tue, 29 May 2012 16:22:27 +0100, Stephen Connolly
Hi everyone,
So I have been working on my view of what JavaScript based web
application development should be like with Maven, to that end I have
created the JSZip set of projects. The first semi-ready piece of work
from that set of projects is the JSZip Maven Plugin.
This is very early code,
Doeth:
http://jszip.org
On 1 June 2012 10:13, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
Hi everyone,
So I have been working on my view of what JavaScript based web
application development should be like with Maven, to that end I have
created the JSZip set of projects
On 1 June 2012 15:19, Christopher Hunt hu...@internode.on.net wrote:
Hi Stephen,
Not sure if you know, but the JS Import project (1) can already utilise zip
files with a www classifier. The regular Assembly plugin can be used to
make these packages. The following type of dependency
Yes, though jars don't work as well for packaging... let's drop the
other mailing lists (left on BCC to let them know they are being
dropped ;-) ) and move to just jszip-...@googlegroups.com
On 1 June 2012 15:24, LeClaire Garvin garvin.lecla...@gmail.com wrote:
I think there is also some overlap
IIRC that is by design... IOW there is a random redundancy added to the password
On 31 May 2012 14:47, David Hoffer dhoff...@gmail.com wrote:
I had to change my password to log into our maven repo so I was
updating the password using --encrypt-password but it's returning a
different value each
elsewhere for the culprit.
Thanks,
-Dave
On Thu, May 31, 2012 at 8:03 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
IIRC that is by design... IOW there is a random redundancy added to the
password
On 31 May 2012 14:47, David Hoffer dhoff...@gmail.com wrote:
I had to change
On 29 May 2012 14:53, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Rolf,
Unfortunately, there are already some 'third party' packages that depend
on jdom 2.0.1, and thus, people using the new jdom2 2.0.2 will have two
different versions of the same jar right? ... which is perhaps worse
priority.
Thanks for the insights so far
Rolf
On Tue, 29 May 2012 15:00:54 +0100, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 29 May 2012 14:53, Curtis Rueden ctrue...@wisc.edu wrote:
Hi Rolf,
Unfortunately, there are already some 'third party' packages that
depend
On 29 May 2012 16:38, Rolf Lear j...@tuis.net wrote:
So what this does is
On Tue, 29 May 2012 16:22:27 +0100, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
On 29 May 2012 15:26, Rolf Lear j...@tuis.net wrote:
So, being inexperienced, my intention is to find some solution
you could push a relocation pom to the old GAV for the next couple of
2.0.x releases and then at 2.1 stop with the relocation poms...
that would give people with the 2.0.x deps a route but you are
kind of ool for now
On 28 May 2012 23:15, Rolf Lear j...@tuis.net wrote:
Unfortunately, there
On 24 May 2012 13:39, DK desmond.kirr...@gmail.com wrote:
Hi,
New to Maven and have a couple of questions around versioning.
Should all projects within a multi-module project have the same version?
Not required, but can usually be helpful.
Should all projects related to each other keep
it will prompt with that as the default next version, 1.0.0 as the
default release version, and artifactId-1.0.0 as the default tag
(where artifactId is the artifactId of the root pom you are running
release on) you unless you do -B in which case yes.
On 24 May 2012 15:23, DK
Another rule of thumb is how stable are the tests...
if you have a stable test suite that never fails randomly only to pass
again next run... you can have a 1 hour long build and release that...
it will take 2-3 hours for the release run to go through, but you know
it will go through...
If you
Keep in mind your conditional probability when dealing with flakey tests...
If you have 2 tests that each fail 1 time out of 5 you can end up with
near certainty that the release will fail as it has at least two test
runs to go through (add in site generation, and code coverage targets
and at
On Wednesday, 23 May 2012, hujirong wrote:
Hi
After working with Maven for a month, I am still not quite understand how
Maven works. Maybe just like Microsoft technologies, encapsulate too much.
One key issue is to understand the plugin.
For example, the following example, how can I see
MavenProject.getFile()
On Wednesday, 16 May 2012, Dreier Ruediger wrote:
Hello!
Is it somehow possible to get the name of the POM file (which might not be
POM.xml if Maven was called with –f) inside a POM file (e.g. as parameter
for other plugins)?
Thanks for any help,
i.A. Rüdiger
have a look at the failsafe maven plugin... (I know you will not be
using it)... but it explains how to do the type of thing you want to
do.
On 17 May 2012 12:35, alexbarter aprokof...@citc.ru wrote:
Hi all. I need seems strange case:
1) pax exam starting apache servisemix (or fuse esb)
2)
mvn help:effective-pom
in project b will tell you the answer
On 15 May 2012 13:29, Cédric Teyton cedric.tey...@gmail.com wrote:
Hi everybody,
I have a surely straightforward question for anyone with Maven knowledges,
but i can't manage to find the right answer.
Assume a project A under
http://svn.codehaus.org/mojo/trunk/mojo/ship-maven-plugin/src/it/plugin-deps/
is the closest to an example I have at this time.
It would be great if you could turn that into a patch for the plugin
docs to explain how it works
On 15 May 2012 21:18, Raketemensch li...@libertylost.org wrote:
Hi,
The Mojo team is pleased to announce the release of Mojo's Ship
Maven Plugin version 1.0-alpha-2.
Mojo's Ship Plugin is used when you have continuous deployment scripts that you
want to integrate with your Apache Maven build.
The plugin has the following goals.
* ship:ship Resolves the
Properties are not supported in the following XPath elements:
/project(/parent)?/(groupId/artifactId/version)
-Stephen
On 14 May 2012 13:42, RAJIV_S rajivbt...@gmail.com wrote:
I have a project structure like the below
School-parent
|
|
| services-parent
|
On 14 May 2012 14:26, RAJIV_S rajivbt...@gmail.com wrote:
version${project.version}/version
That is not a property but a reference to the pom.
I thought based on the above example, any property value should be supported
in version tag using ${...}
not in /project/version or
Hmmm. I wonder if I were to modify the ship-maven-plugin to allow ship
scripts to be pulled from the plugin's classpath rather than the
filesystem would that solve your issue.
On 9 May 2012 21:49, Raketemensch li...@libertylost.org wrote:
Well, that's why I'm asking for a best practice, I'm
I think I have made the modifications that would make your life
simpler... you probably still would need to change a parent pom, but
that would be the only change... fix will be in ship-maven-plugin
1.0-alpha-2
On 10 May 2012 09:39, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
Hmmm. I
Just so you know, a far far better way to do this is to use toolchains.xml
On 8 May 2012 17:36, jose.nunez-zul...@barclays.com wrote:
Works like a charm (tested with mvn -X), inside the pom:
project ...
nameX/name
build
plugins
plugin
On 9 May 2012 06:51, Iordanov, Borislav (CIAO) bo...@miamidade.gov wrote:
Hi,
I'm a relatively new Maven user. I found an exact description of my problem
on StackOverflow, but no solution:
The Mojo team is pleased to announce the release of Mojo's Cassandra
Maven Plugin version 1.1.0-1.
Mojo's Cassandra Plugin is used when you want to install and control a
test instance of Apache Cassandra from within your Apache Maven build.
The Cassandra Plugin has the following goals.
*
ahem...
are you running on a unix system?
you do know # is the comment start marker for most unix shells
you'd need to escape it with \ or quote the entire -D
On 1 May 2012 16:24, Laird Nelson ljnel...@gmail.com wrote:
I have a test class; let's call it TestCaseFoo.
When I run
On 1 May 2012 17:36, Laird Nelson ljnel...@gmail.com wrote:
On Tue, May 1, 2012 at 12:31 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
you'd need to escape it with \ or quote the entire -D
Yes, I am running on MacOS. Sorry; didn't indicate that I had done
On 1 May 2012 22:43, Laird Nelson ljnel...@gmail.com wrote:
On Tue, May 1, 2012 at 5:30 PM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
there is your #fail
mvn clean install -fae -Pminlog '-Dtest=TestCaseFoo#testBar'
Thanks again for your prompt response. I don't see
if you change your batch file to build up a classpath for you, it could add
in any jars in the patches directory onto the classpath first. You might
want to have a look at the batch files used to launch some of the common
Java apps, e.g. ANT and Maven. Also take a look at the batch files
generated
You need to see this page:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/system-properties.html
You will need to define system properties for each system property you want
to pass through.
Most likely your properties will look like
systemPropertyVariables
foo${foo}/foo
On 24 April 2012 03:02, Andrew Hughes ahhug...@gmail.com wrote:
OK, I found a way to confirm...
activeProfiles are always active Exactly what I wanted as documented
:)
However, the problem persisted... until...
I noticed that builds on the command line worked fine, as did 'install'
And in the interests of keeping ASF vendor neutral,
There are at leaste three repository managers equally capable of providing
95% of what people need (they disagree on the remaining 5% either being
needed or how to solve)
In alphabetical order, so as not to imply any preference:
Archivia by
My only use for versions specified by property is where the suite of
dependencies are all the same version. Properties is the only way right now
to handle that. Pom v5 should have something better when we get to it
shouldn't it, eh!
On Tuesday, 24 April 2012, Wayne Fay wrote:
way is a good
I often will create a local aggregator project which contains all the
related projects I am working on.
I don't check that local aggregator project into source control, and I
throw it away when I am done with that and ready to move onto something
else.
If you go with tis route, then the only
http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
On 19 April 2012 13:33, kenito a...@sneda.fr wrote:
hello everybody,
I want to check if my project contain snapshot dependencies exactly like in
the release:prepare goal. This goal is bind with a phase called
On 17 April 2012 05:16, Manfred Moser manf...@mosabuam.com wrote:
On Mon, April 16, 2012 2:13 pm, chad.da...@emc.com wrote:
Our build has a dependency on the JRE. In order to build our final
distribution artifact, we need a JRE. To me, this means that the JRE
should be managed as a maven
I use OpenEJB and just fire up a container per test or per test class
On 13 April 2012 16:03, Lucas Persson lucas.pers...@oracle.com wrote:
**
Hi
I am about to migrate some Ant build system to Maven and have run into the
JUnitEE ant task. I can not really find any up to date corresponding
Profiles per-se are “ok”
Adding dependencies in a profile is not.
The problem is when do those profiles get activated, and hence when will
the dependencies get pulled in.
When people have profiles activated by the presence of a file, and then
that pom is resolved from the local repo and not
Oh we all know what the issue is.
Hint: You don't know what a valid package name is and you don't understand
some basic concepts of Java.
Trust us, this *is* a java programming issue. This is *not* a maven issue.
On 12 April 2012 00:42, mike digioia mpd...@gmail.com wrote:
Thanks
I see you
701 - 800 of 2415 matches
Mail list logo
