Hello,
I have a problem with my dependency pattern and I am not sure that maven
behaves correctly in this case.
Here is my case :
- I am using Maven 2.2.1.
- I have a project A which defines a dependency D with scope test.
- I have a project B whose parent is A and which defines D
As project A is a parent it's a pom project, right? IMHO a pom project
should NEVER have a dependency. Remove that dependency and state that
test scope dependency where it actually is a dependency instead.
Project A could however have dependencyManagement declared for D
stating test as default scop
Thanks for your answer,
But somehow I disagree with you : a pom project might have to define
dependencies.
IMHO defining such a dependency (besides defining its version and scope
in the dependency management) is legitimate if all of the projects
having this pom as parent should have this depen
Hi Graham,
Graham Crosmarie wrote:
> Thanks for your answer,
>
> But somehow I disagree with you : a pom project might have to define
> dependencies.
> IMHO defining such a dependency (besides defining its version and scope
> in the dependency management) is legitimate if all of the projects
> h
Well, I disagree with you. A pom project doesn't have a dependency. It
doesn't have any code and thus no dependencies.
Also, based on my experience, there will always be exceptions to the
rule "all children will have this dependency". A very common one is
thinking that all children will have a jun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
How do you use mvn command line to deploy an artifact to a remote
repository? it says it doesn't have a proper vagon provider for sftp/scp
so... and it doesn't autodownload it.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (MingW32)
Com
I have a multi-module project P, with modules P.Core, P.A, P.B.
Both P.A and P.B are different implementations of an API specified
in P.Core. In order to test that all implementations of P.Core have
the same semantics, P.Core exports a set of abstract classes containing
junit 4 tests which are the
Hi all...
a friend of mine and I have experienced a compilation error when we
have tried to compile this project:
prj.a:
public class A extends B{}
prj.b:
public class B extends C{}
prj.c:
public class C{}
where their pom are:
prj.a -> prj.b (provided scope)
prj.b -> prj.c (provided scope)
Yes, create a jar of the test classes:
http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html
There are some limitations in this though (test dependencies are not
transitive). Moving these test classes to a separate project solves
that.
/Anders
On Tue, Jul 17, 2012 at 2:39 PM, wro
On Tue, Jul 17, 2012 at 2:39 PM, wrote:
> I have a multi-module project P, with modules P.Core, P.A, P.B.
>
> Both P.A and P.B are different implementations of an API specified
> in P.Core. In order to test that all implementations of P.Core have
> the same semantics, P.Core exports a set of abst
On Tue, 17 Jul 2012 14:44:57 +0200
Anders Hammar wrote:
> Yes, create a jar of the test classes:
> http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html
>
> There are some limitations in this though (test dependencies are not
> transitive). Moving these test classes to a separate p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
What is the best way to do things like:
Some artifact exists in a central repository and it's a transitive
dependency of some of my project's direct dependencies.
Then, I have a really good reason to modify the artifact and store it in
my own
Hi!
In parent A, so you define scope in dependency or dependency management
section. If the latter, then it overrides scope of the transitive
dependency.
In which scope is dependency B? If it's in test scope, than its
dependencies will be in test scope, too.
It would be much easier if you could
I think it would depend on what kind of changes you make. But if it's
a patch or similar, you should just change the version to
a.b.c-PATCH123 or something (keep artifactId and groupId as the
original).
But if you make bigger changes to it, it would probably make sense to
put it under your groupId
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
But it would not work for transitive ependencies if I'll put it in a
different group id, I think. because they are different projects.
W dniu 2012-07-17 15:39, Anders Hammar pisze:
> I think it would depend on what kind of changes you make. But if it
If you exclude the stock version from the direct dependencies and add
your version as a dependency, you:
a) get the configuration that you want
b) you have documented in your POM, the exact configuration of software
bits and pieces that are required to build what you want (your friends
will som
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't want to add exclusions for everything that requires that.
W dniu 2012-07-17 15:57, Ron Wheeler pisze:
> If you exclude the stock version from the direct dependencies and add your
> version as a
dependency, you:
> a) get the configuration th
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
cont
-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 is the scope of changes between this artifact and the
> original...
>
> if all you are do
What happens if any dependencies are looking for that support?
Will they bomb out or fail gracefully?
I.O.W. if you can still drop it in as a generic replacement => version
change
If you cannot use it as a generic replacement => different artifact =>
change groupId
for example...
I have https:
Sometimes a best practice requires you to do things that you don't want
to do for short term reasons.
Why not add an exclusion for stuff you want Maven to exclude?
Ron
On 17/07/2012 10:02 AM, Michał Zegan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't want to add exclusions f
Hi there,
Try with mvn deploy:deployfile,
http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html
Thanks,
Krishna Kurnala
On Tue, Jul 17, 2012 at 4:28 AM, Michał Zegan wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello.
> How do you use mvn command line to d
A defines a dependency on D with scope test and is a pom project
B defines a dependency on D with compile (default) and is a jar project.
A is the parent pom of B.
When I run dependency:tree I get what I want for B : D with scope compile.
I have other projects (C) whose parent is A and which dep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
THere are many dependencies using that one as a transitive, so I don't
want to be in a situation when I would forget to exclude them.
Changing a version using dependency management works for all.
W dniu 2012-07-17 16:40, Ron Wheeler pisze:
> Sometim
I'm looking at Native compilation, particularly with NAR and want to make
some other extensions that will add sources for NAR to compile - if it is
being used already. For instance XSD code generation like XMLBeans.
For Java the MavenProject provides access to the
CompileSourceRoots/TestCompileSo
It is extremely unlikely that the Foundation will be interested in any
participation except to gratefully accept any unrestricted donations
your organization might happen to make. If you want to state on your
website that you are going to donate something to the ASF when the
issue is an ASF project
hi
I new to maven project and first time i to runand install maven
I followed the following steps which instruct by apache maven
1. Add the M2_HOME environment variable by opening up the system
properties (WinKey + Pause), selecting the "Advanced" tab, and the
"Environment Variables" butt
I believe what happens here is that the dependency declared closest to
your project wins. But you can control this through
dependencyManagement in your project.
/Anders
On Tue, Jul 17, 2012 at 5:06 PM, Graham Crosmarie
wrote:
> A defines a dependency on D with scope test and is a pom project
>
>
hi
i new to maven and try to create project structure with help of maven. I m
using Maven 3.0.4 version
Every time i try to run given command* C:\Program
Files\apache-maven-3.0.4\bin>mvn archetype:generate*
it ask :
- Choose a number or apply filter (format: [groupId:]artifactId, case
sensi
> *C:\Users\sahil>mvn --version*
> 'mvn' is not recognized as an internal or external command,
> operable program or batch file
>
> if the directory is changes to* C:\Program Files\apache-maven-3.0.4\bin>*
> then it runs .
Please do not install Maven (or really anything) under Program Files,
or an
Hi
Please run the command SET in a command window and paste the relevant
parts here, i.e. M2_HOME, M2, JAVA_HOME and PATH.
On 2012-07-17 22:01, rahul bhalla wrote:
> hi
> I new to maven project and first time i to runand install maven
> I followed the following steps which instruct by apache mave
hi
As you said i do and now it its running
*thanks for the help*
can please explain me the way how to create project structure/whole project
outside the bin folder of maven ??
--
Regards
Rahul Bhalla
Hi,
I'm pleased to announce the release of the gwt-maven-plugin version 2.5.0-rc1.
http://mojo.codehaus.org/gwt-maven-plugin/
To get this update, simply specify the version in your project's
plugin configuration:
org.codehaus.mojo
gwt-maven-plugin
2.5.0-rc1
Release No
Hello All
We are tryign to use Maven Versions Plugin(
http://mojo.codehaus.org/versions-maven-plugin/ ) as a automated way to
keep diff module versions in sync in our POM's.
The Real Challenge we face is when we decide to Revert/Roll-back from a
Release, we currently delete Artifacts from Nexus,
On Tue, July 17, 2012 4:40 pm, krishna chaitanya kurnala wrote:
> Hello All
>
> We are tryign to use Maven Versions Plugin(
> http://mojo.codehaus.org/versions-maven-plugin/ ) as a automated way to
> keep diff module versions in sync in our POM's.
>
> The Real Challenge we face is when we decide to
> can please explain me the way how to create project structure/whole project
> outside the bin folder of maven ??
First make sure "mvn -v" runs and outputs the proper information.
Until this is working properly, there is no point to proceed.
Make a new directory say c:\code.
cd to that directory
> The Real Challenge we face is when we decide to Revert/Roll-back from a
> Release, we currently delete Artifacts from Nexus, delete tags etc which is
> cumbersome.
>
> Wondering if there is an easy way out Reverting/Roll-back Releases using
> this Plugin or Kindly suggest any other easier way.
On Wed, Jul 18, 2012 at 11:57 AM, Wayne Fay wrote:
>> can please explain me the way how to create project structure/whole project
>> outside the bin folder of maven ??
Have you tried one of the freely available books at
http://maven.apache.org/articles.html?
Some of these should walk through exam
Don't forget that once released artifact is downloaded to the local
repository, Maven will not try to download it again, because it is assumed
that released artifacts never change.
Just my 0.02 €.
Regards,
htfv (Aliaksei Lahachou)
Am 18.07.2012 04:30 schrieb "Wayne Fay" :
> > The Real Challenge
39 matches
Mail list logo
