It is clear version ranges are used by some people and they do find them
useful including me. You cannot predict how and in what circumstances
specific features of maven will be used by the many people out there,
good or bad in your opinion.
I still would prefer making version range
+1
I agree with Jesse.
A version range like [1.7,1.8) should exclude any artifact that starts
with 1.8
Then maven (or aether) would respect semantic versioning rules.
We use version ranges/semantic versioning and API analysis to ensure our
artifacts are versioned correctly. Sometimes we
precisely
Regards,
Hervé
Le jeudi 27 septembre 2012 20:46:08 Paul French a écrit :
+1
I agree with Jesse.
A version range like [1.7,1.8) should exclude any artifact that starts
with 1.8
Then maven (or aether) would respect semantic versioning rules.
We use version ranges/semantic versioning
that has
issues... hence why I haven't pushed it further.
-Stephen
On 27 September 2012 22:19, Paul French paul.fre...@kirona.com wrote:
Okay I see the problem.
How about allowing a user to plugin a Version class that implements
Comparator
class MavenVersion implements ComparableMavenVersion
, Paul French paul.fre...@kirona.com wrote:
I would only want the same version rules applied to all artifacts, not on
a per artifact basis, that would be a nightmare! I understand that people
who produce artifacts have their own versioning rules. However we can take
that into account in our version
...@gmail.com
Well that is a recipe for disaster. rules only make sense within the scope
of the artifacts they apply to.
This is kind of why version ranges are next to useless from a practical PoV
anyway
On 27 September 2012 23:05, Paul French paul.fre...@kirona.com wrote:
I would only want the same
Yes go to Spring forums. But I thought Spring MVC 3 requires Spring
core 3 and there was artifact name change from spring 2 to 3
You could try removing the maven reference to spring core and see what
gets pulled in by spring mvc 3
*Paul French
Technical Lead/Research Development
* Kirona
Any idea what version of the aether libraries (1.12 or 1.13) will be
used in 3.0.4 and a guess on when 3.0.4 will be released?
We are using 3.0.3 with aether 1.13 libraries. It works really well
except maven crashes out when there is version conflicts in your POM.
Depending on your answer I
maven 3.0.3 has terrible performance and memory usage when using version
ranges. This has a knock on effect using m2e
It takes maven ages to update the maven dependencies.
I have a main project with a some version ranged dependencies which in
turn have versioned ranged dependencies. Outside
seconds.
Will build our own embedded runtime as instructed below now.
Thanks for everyone's help.
Any ideas when an official maven 3.0.4 release will happen as well as an
official maven 3.0.4 embedded runtime m2e connector ?
Paul French
Kirona Solutions Ltd
Tel: 07803 122 058
E-Mail: paul.fre
and fixes some recent issues that I'e been seeing with
resolutions so that might be a good place to look at.
Mark
On 28/09/2011, at 10:10 PM, Paul French wrote:
Is the dependency management code easy to understand? I'm happy to get my hands
dirty
to get
my hands dirty.
--
Paul French
Kirona Solutions Ltd
Tel: 07803 122 058
E-Mail: paul.fre...@kirona.com
Web: www.kirona.com http://www.kirona.com
This email and any attachments are confidential and should only be read
by those to whom they are addressed. If you are not the intended
Thanks for that.
Out of interest if I remove the snapshot repository and change my
version ranges to [8.0.0,9.0.0) instead of
[8.0.0.SNAPSHOT,9.0.0.SNAPSHOT) all works fine again even in eclipse.
For now we will live without snapshots.
On 22/06/2011 06:21, Kristian Rosenvold wrote:
From
Added the snapshot repo back in and it now has major problems. A build
that was fine before now fails with out of memory. - all version ranges
set to [8.0.0,9.0.0)
On 22/06/2011 09:39, Mark Struberg wrote:
humm, maybe the resolution mechanism sniffs _all_ snapshot timeshot versions
and not
:41 +0100
From: Paul French paul.fre...@kirona.com
Organisation: Kirona
To: users@maven.apache.org
CC: Ian Jones ian.jo...@kirona.com
Below is some filtered output from a maven build (showing maven meta
data being downloaded for one artifact). All my dependencies use version
ranges
To be clear the problem is in maven. I am running maven from the command
line.
Thanks
P
On 21/06/2011 11:16, Paul French wrote:
Can someone confirm on the maven users list that they have received
this email?
I did not but it does appear in the mail archive
Thanks
P
Original
Thanks for reply - see inline
On 21/06/2011 11:27, B Smith-Mannschott wrote:
On Mon, Jun 20, 2011 at 19:54, Paul Frenchpaul.fre...@kirona.com wrote:
Below is some filtered output from a maven build (showing maven meta data
being downloaded for one artifact). All my dependencies use version
On 21/06/2011 14:25, Ron Wheeler wrote:
500Mb is not a lot of memory for a Java program.
It is when all I can give eclipse is 900MB. Beyond that the JVM fails to
start. M2E as far as I know does not start a new JVM when building.
We have noticed that some libraries such as Apache's CXF
I forgot to mention that maven 3.0.3 is using more then 1024MB of heap
before it even gets to the compile stage. We will look into profiling it
later today.
On 21/06/2011 14:45, Paul French wrote:
On 21/06/2011 14:25, Ron Wheeler wrote:
500Mb is not a lot of memory for a Java program
Hello Ron,
thanks for your comments. See inline comments.
Cheers
On 21/06/2011 15:38, Ron Wheeler wrote:
On 21/06/2011 9:45 AM, Paul French wrote:
On 21/06/2011 14:25, Ron Wheeler wrote:
500Mb is not a lot of memory for a Java program.
It is when all I can give eclipse is 900MB. Beyond
Below is some filtered output from a maven build (showing maven meta
data being downloaded for one artifact). All my dependencies use version
ranges of the form [1.0.0.SNAPSHOT,2.0.0.SNAPSHOT)
In general the build fails with out of memory. I can increase the heap
size and the build is
ou require. The default behaviour
will be what I have outlined
My 10 pence
--
Paul French
Kirona Solutions Ltd
Tel: 07803 122 058
E-Mail: paul.fre...@kirona.com
Web: www.kirona.com
This email and any attachments are co
22 matches
Mail list logo
