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
the great pom migration of Maven 1 to Maven 2 left deep scars... because it
got some things wrong.
When we do the next
Folks,
Much electronic ink was spilt on the subject of POM5. One of the pools
of ink was created by my attempt, some months ago, to move the design
along.
I wish someone would propose a concrete next step.
--benson
On Mon, Sep 24, 2012 at 4:41 AM, Stephen Connolly
Hi,
There is a project called Apache James, it has sub modules.
Both the root project and sub modules have pom.xml s.
When i delete all the repositories in my /home/.m2/repository and run one
sub module's pom.xml, i get duplicated dependencies.
On 24 September 2012 12:58, Benson Margulies bimargul...@gmail.com wrote:
Folks,
Much electronic ink was spilt on the subject of POM5. One of the pools
of ink was created by my attempt, some months ago, to move the design
along.
I wish someone would propose a concrete next step.
Done, on
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
I am a bit concerned that this discussion seems to trying to integrate a
System Administration concern into a Software Development environment.
It seems that the original issue was raised to try to solve an
installation problem through software development.
It seems that what is needed is an
Thank you, that's exactly what I was looking for.
Is there a way to shade versions of an artifact in a particular way?
For example, if projects A and B depend on Guava r09 and projects C
and D depend on Guava 13.0.1, how can I make sure that each is
referencing the correctly shaded version when
shade via intermediate modules
On 24 September 2012 14:36, Eric Czech e...@nextbigsound.com wrote:
Thank you, that's exactly what I was looking for.
Is there a way to shade versions of an artifact in a particular way?
For example, if projects A and B depend on Guava r09 and projects C
and D
Is there no upward compatibility?
Can projects A and B execute using Guava 13.0.1?
Usually, you just exclude the lower versions in the dependency
specification for the third party library and run with the highest version.
If Guava is not upwards compatible and the third party libraries use
Is there something in my question that tells you that i try to download
modules one by one?
I download everything but try to run pom s individually because i want to
learn what the ugly thing causes duplicated jars.
2012/9/24 Karl Heinz Marbaise khmarba...@gmx.de
Hi,
There is a project
Then i have duplicated class error.
What should i do, can you advise something?
Also i require an advise about what to read why maven acts like this.
Probably you need to ask this question on the Apache James list, and
get their advice about what to do at this point, unless there is a
James
Your level of detail in the description of what you are doing is so
small that everyone is trying to guess about what is happening.
1) Tell us why you are building James at all. It is not something that
people outside the James project team would ever do.
2) What do you mean by causes
Thanks Ron but no unfortunately, they're not upwards compatible.
Entire classes are renamed or removed in later versions so artifacts
using the old version definitely can't just use the new one.
Having our own guava artifact with the code from 13.0.1 means that we
can use that version
On 24/09/2012 11:24 AM, Eric Czech wrote:
Thanks Ron but no unfortunately, they're not upwards compatible.
Entire classes are renamed or removed in later versions so artifacts
using the old version definitely can't just use the new one.
Having our own guava artifact with the code from 13.0.1
On Mon, Sep 24, 2012 at 5:24 PM, Eric Czech e...@nextbigsound.com wrote:
Thanks Ron but no unfortunately, they're not upwards compatible.
Entire classes are renamed or removed in later versions so artifacts
using the old version definitely can't just use the new one.
Only for @Beta
We have a 3rd party dependency whose distribution consists of a zip file with a
set of jars and native libraries. Our repository person has deployed this zip
for us. We are trying to process the zip into more consumable pieces. We'd
like to create another zip, containing only the native
In your repo, can you not upload the jars as maven-like artifacts?
Ron
On 24/09/2012 1:04 PM, Davis, Chad wrote:
We have a 3rd party dependency whose distribution consists of a zip file with a
set of jars and native libraries. Our repository person has deployed this zip
for us. We are
Stephen,
I did never suggest to modify the POM and said no word about any future form
of the POM, so I skip your comments about that and right go on with the idea
of a Platform:
I like some of your idea about the concept of a platform but this is
not as trivial as you think.
There is the
In your repo, can you not upload the jars as maven-like artifacts?
I can, or at least I can have someone, who is authorized, do that for me. I
was hoping to automate the process of converting the distribution zip into
useable maven pieces . . . perhaps that's just not very normal thing
In your repo, can you not upload the jars as maven-like artifacts?
I can, or at least I can have someone, who is authorized, do that for me. I
was hoping to automate the process of converting the distribution zip into
useable maven pieces . . . perhaps that's just not very normal thing to
On 24/09/2012 1:42 PM, Markus KARG wrote:
Stephen,
I did never suggest to modify the POM and said no word about any future form
of the POM, so I skip your comments about that and right go on with the idea
of a Platform:
I like some of your idea about the concept of a platform but this is
not
Using mvn 3.0.4, when a SNAPSHOT artifact is resolved from a remote repo
it seems that my local repository ends up with both a -SNAPSHOT artifact
and a timestamped version (the remote end has only timestamped versions).
I'm curious if I can rely on this behavior since I have other (non-maven)
code
22 matches
Mail list logo
