The Maven team is pleased to announce the release of the Maven
Surefire Plugin, version 2.12.4.
This release includes the maven-surefire-plugin, which executes the
unit tests of an application, the maven-surefire-report-plugin, which
parses surefire/failsafe test results and renders them to DOXIA
The Maven team is pleased to announce the release of the Maven Plugin
Testing, version 1.3 and 2.1
This release is Java7 compatible and updates all the dependencies of
plugin-testing,
especially easymock to version 2.5.2. Projects wishing to upgrade to
this version
will need to update their own
Without version ranges, how do I write a library that works with SLF4J
version 1.5.*, but does not work with SLF4J 1.6.*?
Do I depend on, say, version 1.5.11? Then when a user depends on my
library, and on slf4j-api directly, specifying slf4j-api version 1.6.0
in his pom, Maven will link in
Hi Laird,
I would guess that it is used by SCM's like CVS which takes an existing
tag as base for a new branch.
The explanation could be better as many of the other parameters
describes SVN specific usage.
/Anders
On Thu, 2012-09-27 at 19:16 +0200, Laird Nelson wrote:
On Thu, Sep 27, 2012 at
My point is really about exclusive upper bounds.
I expect that [1.7,1.8] should contains 1.7.0 and above (no snapshots
and prerelease for 1.7.0) and 1.8.* release versions. Having said that,
I dont really care too much about this use case and have not thought
much about it. I have thought
hi,
How to set the ActiveMQ redelivery policy in spring3 configuration ?
I have read http://activemq.apache.org/redelivery-policy.html, but can not find
the example.
I searched a answer from stackoverflow,
Sad but true.
An example:
There are projects which use 1.0-MR1 as Milestone Release
which gets released _before_ 1.0 final.
And there are other projects which use 1.0-MR1 as Maintenance Release
which obviously gets released _after_ 1.0 final.
Anything else than pure numbers is a candidate
On Fri, Sep 28, 2012 at 1:15 PM, Brett Porter br...@apache.org wrote:
Hi Terry,
On 28/09/2012, at 9:41 AM, Sposato, Terry terry.spos...@team.telstra.com
wrote:
Hi,
We currently use Nexus as our project’s local repository server which works
well.
We also have a Terminal server which
I created a project with maven-archetype-simple, and it creates a
project with a dependey to JUnit 3.8.1.
JUnit 3.8.1 is really old. In fact it's so old I've been unable to
google when it was released. The oldest relase I find is the release of
JUnit 4.5 in 2008 http://www.junit.org/node/401
Hi,
Agree it's old :-)
Jira project is here: http://jira.codehaus.org/browse/MARCHETYPES
2012/9/28 Steinar Bang s...@dod.no:
I created a project with maven-archetype-simple, and it creates a
project with a dependey to JUnit 3.8.1.
JUnit 3.8.1 is really old. In fact it's so old I've been
Hi,
Yes it is old, but it is the best JUnit :)
The 4 series jumped the shark for me·
Old != bad.
I am not trying to start a flame war here, but assumed that it was
3.8.1 deliberately,
as this is the best JUnit can get.
Not everyone uses annotations, the surefire plugin requires the JUnit
3.8.1
I agree it's a bit confusing as most of scm doesn't support
includes/excludes for checkout/export operations :-(
Maybe we could mimic that and deleting files/directories after the
whole checkout/export.
Again the reason of seeing that in the doc is because this field is in
AbstractScmMojo class
On 28/09/2012 3:17 AM, Jesse Long wrote:
Without version ranges, how do I write a library that works with SLF4J
version 1.5.*, but does not work with SLF4J 1.6.*?
Do I depend on, say, version 1.5.11? Then when a user depends on my
library, and on slf4j-api directly, specifying slf4j-api
Or is could create a tag for the release.
That would make sense, I think.
Ron
On 28/09/2012 3:34 AM, Anders Lindgren wrote:
Hi Laird,
I would guess that it is used by SCM's like CVS which takes an existing
tag as base for a new branch.
The explanation could be better as many of the other
I find this topic interesting for a couple of reasons. I was one of the
original posters of this topic and created some of the relevant JIRA issues
regarding it.
However one of the problems is that since this issue was never fixed...and
sadly seems never will be...we had to abandon the use of
On 28/09/2012 14:42, Ron Wheeler wrote:
On 28/09/2012 3:17 AM, Jesse Long wrote:
Without version ranges, how do I write a library that works with
SLF4J version 1.5.*, but does not work with SLF4J 1.6.*?
Do I depend on, say, version 1.5.11? Then when a user depends on my
library, and on
I'm currently doing work for Ericsson where we have a similar setup (Terminal
Server on windows and AFS on *nix).
The difficulty in this setup is not network access but limited user storage so
the goal is to try to share as much as possible among the users. This was such
a concern for Ericsson
On 28 Sep 2012, at 4:15 PM, Pascal Rapicault pas...@rapicault.net wrote:
I'm currently doing work for Ericsson where we have a similar setup (Terminal
Server on windows and AFS on *nix).
The difficulty in this setup is not network access but limited user storage
so the goal is to try to
On 28 Sep 2012, at 4:13 PM, Jesse Long j...@unknown.za.net wrote:
My library does clearly document the versions of slf4j it depends on - as a
version range in the pom.xml file. How else?
Never mind slf4j for the time being, this affects all libraries.
Please see http://semver.org/
The
On Fri, Sep 28, 2012 at 12:34 AM, Anders Lindgren
anders.lindg...@cinnober.com wrote:
I would guess that it is used by SCM's like CVS which takes an existing
tag as base for a new branch.
The explanation could be better as many of the other parameters
describes SVN specific usage.
Thanks;
+1 Laird, that is for sure the best thing. I guess we need to clean up a few
things in this area.
An attempt for a small historical summary:
* tag was useful in CVS (not in all operations but in most)
* tag is almost useless in SVN as you get a different directory for branches
and tags
* due
Tim Pizey tim.pi...@gmail.com:
Not everyone uses annotations, the surefire plugin requires the JUnit
3.8.1 naming conventions,
That doesn't seem to be the case:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html
Quote:
Surefire supports three different generations
note the feature -Dtest=MyTest#myMethod is not supported with 3.8
2012/9/28 Steinar Bang s...@dod.no:
Tim Pizey tim.pi...@gmail.com:
Not everyone uses annotations, the surefire plugin requires the JUnit
3.8.1 naming conventions,
That doesn't seem to be the case:
With one of my latest commits for the maven-release-plugin I've added an
extra AbstractMojo layer, which should contain all scm-related parameters.
Main reason is the update-versions goal [1]
It says: ... without making other modifications to the SCM such as tagging.
All scm-related won't be
Olivier Lamy ol...@apache.org:
Agree it's old :-)
Jira project is here: http://jira.codehaus.org/browse/MARCHETYPES
Thanks! And from the above URL I got to here:
http://maven.apache.org/archetype/maven-archetype-bundles/maven-archetype-quickstart/
quickstart, not simple.
Checking what I
Hi Steinar,
Thank you for this, no doubt you are right.
We now superstitiously continue with JUnit 3 naming conventions for
test classes and test methods,
whether we are using Junit3, 4 or TestNG (yes we use all three!)
It was indeed when TestNG was introduced that we had this problem.
For my
On Thu, September 27, 2012 1:49 pm, Karl Heinz Marbaise wrote:
Hi,
With e.g. 2.1.1-RC.1-SNAPSHOT
I've never seen a version marker like this..
It is definitely not common yet but imho it is actually better than the
below used version without the dot delimiter. More importantly this is
what
Hello,
I believe there is now a skinny war option in the ear plugin that could
help you to handle this case. I never used it so I cannot really tell you
more about it.
Another option would be to have 2 profiles to build your war. One with all
dependencies provided by the ear marked as provided,
I have a similar configuration in my project.
It is an EAR project with lots of WARs on their own. The goal was to provide a
way to be able to debug/develop the WARs standalone e.g. via mvn tomcat7:run.
In this situation you need all your dependencies (even platform JARs like
openwebbeans,
Steinar Bang s...@dod.no:
I haven't been able to list all Jira issues here yet. I think I will
try to instantiate a quickstart archetype from 5-SNAPSHOT and see what
happens.
If it's still 3.8.1, I'll file a bug.
Hm... that didn't work...?
I tried the command example on this page:
I have an interesting use case to pick everyone's brain on…
A developer came to my desk and said We want to allow other teams to put a
dependency on our tests jar for their test scope, but don't want to allow them
access to the non-tests jars in our project.
At first I said No problem. I can
On 28/09/2012 10:31 AM, Graham Leggett wrote:
On 28 Sep 2012, at 4:13 PM, Jesse Long j...@unknown.za.net wrote:
My library does clearly document the versions of slf4j it depends on - as a
version range in the pom.xml file. How else?
If you are selling or distributing your product, it should
On 28/09/2012 3:53 PM, Lyons, Roy wrote:
I have an interesting use case to pick everyone's brain on…
A developer came to my desk and said We want to allow other teams to put a
dependency on our tests jar for their test scope, but don't want to allow
them access to the non-tests jars in our
Yes..I always hardcoded those values in the descriptor...but the
maven-mar-plugin should reconfigure axis2.xml to include module
ref=addressing/
and any associated module specific parameters
cross posting to maven-users
feel free to go ahead and post your question
Martin Gainty
Steinar Bang s...@dod.no:
Steinar Bang s...@dod.no:
If it's still 3.8.1, I'll file a bug.
Hm... that didn't work...?
I have now filed a bug, in case anyone would like to vote on it:
https://jira.codehaus.org/browse/MARCHETYPES-41
(Note: 3.8.1 is *really* old... 10 years is over half the
Anything else than pure numbers is a candidate to be broken somehow.
yes
Maven defines some qualifiers: see [1] for exact list (notice the synonyms,
even
for the release, that can be ga or final)
I chose the qualifiers from what I could see that didn't have multiple
interpretations: yes, MR is
yes, https://jira.codehaus.org/browse/MNG-3092 is still here
I'm not comfortable with the idea of excluding SNAPSHOT from ranges: if we do
so, it's not a *range* any more but a range + a filter
(1.7.1-SNAPSHOT is in [1.7,1.8] range,in plain english)
and actual discussion helps me dig into other
Le vendredi 28 septembre 2012 09:52:50 Jesse Long a écrit :
My point is really about exclusive upper bounds.
ok, now I'm starting to see the precise idea and believe it can avoid breaking
subtle logic
[1.7,1.8) could exclude anything starting with 1.8: betas, alphas, alphas-
alphas, snapshots
38 matches
Mail list logo
