Bruno Melloni wrote:
> First, you are right... I misread. When I look at the maven plugins in
> pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1,
> surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1,
> project-info-reports=3.0.0. Still, it is > 2.0 so LATEST i
Hi,
Does yesterday dependency build on an other pc? Then it should be "deploy"
to your company central repository (Artifactory, Nexus, ...) to be fetched
from your pc.
Using version range and snapshot is not good idea. It's better to use
snapshot only.
If you want incremental version from you CI/
> Finally I opened app2-0.0.1-SNAPSHOT.jar and looked for the included
app1-0.0.1-SNAPSHOT.jar file.
What does this mean?
On Sat, 24 Sept 2022 at 00:05, Bruno Melloni wrote:
> First, you are right... I misread. When I look at the maven plugins in
> pluginManagement I see v2 and v3: clean=3.1
First, you are right... I misread. When I look at the maven plugins in
pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1,
surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1,
project-info-reports=3.0.0. Still, it is > 2.0 so LATEST is no longer
supported as a vers
Hi Bruno,
It’s not completely clear to me what your issue is exactly. Is ’the old cached
version from January’ that you refer to an artifact with a snapshot version or
a release version? If it is a snapshot version, it depends on the update policy
whether Maven will use a locally cached snapsho
> I have created a mvn plugin called "foo" that needs a jar file say
> "xyz.jar"
> in order to compile and run. in the pom file of plugin project foo I have
> provided xyz.jar with "provided" scope in the dependencies section.
That is most likely not correct. If your plugin requires the xyz arti
Plug-ins are not part of your code and stuff in the dependency section
has no affect on plug-ins.
If foo is "provided", you probably have to put it in the Java library
folder or the Maven folder.
You need to go back to the plug-in documentation and see how to include
libraries in plug-ins.
If a library A that you call, calls a method "mailme" in library B ,
you can not remove that library unless you are supplying a later version
of the library B with the "mailme" method through another dependency. If
"mailme" was deprecated and removed in the later version of B, you will
not be
On Mon, Oct 15, 2012 at 12:19 PM, Chris Conroy wrote:
> On Fri, Oct 12, 2012 at 11:22 PM, Barrie Treloar wrote:
>
>> If you are just serving it from jetty you could use
>>
>> http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
>> to copy the aggregate jar into
On Fri, Oct 12, 2012 at 11:22 PM, Barrie Treloar wrote:
> If you are just serving it from jetty you could use
>
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/copying-artifacts.html
> to copy the aggregate jar into the web directory?
>
> Trying to wedge dependencies into this
There's a real maven design problem here, if you ask me. Maven
overloads the 'type' of an artifact. A 'war' dependency is legitimate
and a different thing from a 'jar' dependency. Sadly, though, all jar
files are equally treated as the output of the standard java
lifecycle, suitable for classpath.
On Sat, Oct 13, 2012 at 6:29 AM, Chris Conroy wrote:
> Is there any way to specify that a dependency should not be on the build
> classpath?
>
> I am using the maven-javadoc-plugin to generate an aggregate javadoc jar
> for my top level project. In a sub-project, I have a dependency on the
> javad
On Fri, Oct 12, 2012 at 3:59 PM, Chris Conroy wrote:
> Is there any way to specify that a dependency should not be on the build
> classpath?
>
> I am using the maven-javadoc-plugin to generate an aggregate javadoc jar
> for my top level project. In a sub-project, I have a dependency on the
> javad
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
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
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
Scott and Stephen,
Thank you both for the quick responses. That seems to have worked for
me.
For archival purposes the steps that seem to have worked for me are:
1. Modified the configuration for the jar-plugin as specified here
http://maven.apache.org/guides/mini/guide-attached-tests.html
2. I
test-jar
test
On 5 July 2011 22:52, Jeremy Lewi wrote:
> Hi,
>
> I'm working on the apache avro project and I'm having a problem with
> maven that I was hoping to get some help with.
>
> My project consists of several modules, one of which is "mapred".
> Now I can build "mapred" just fine e.g by
fyi, I'll try to cut the release this weekend.
On Thu, Feb 3, 2011 at 2:31 PM, Wayne Fay wrote:
>> Good news. I delved into this last week and came up with an even
>> better patch, and the developer Brian Fox just applied it!
>
> Great job, Phillip. We need more people like you around. ;-)
>
> W
> Good news. I delved into this last week and came up with an even
> better patch, and the developer Brian Fox just applied it!
Great job, Phillip. We need more people like you around. ;-)
Wayne
-
To unsubscribe, e-mail: users-
>> On Wed, Jan 19, 2011 at 21:59, Phillip Hellewell wrote:
>>
>>> Has anyone else run into this? I run into it all the time. It
>>> appears to be because unpack-dependencies is not updating the
>>> timestamp on the marker files like it should.
>>>
>>> I found this bug which seems to be exactly m
Ok, I'll try to see if I can figure it out :)
On Wed, Jan 19, 2011 at 2:20 PM, Anders Hammar wrote:
> Briefly looking through the comments it looks like an integration test is
> missing for the patch to be accepted. Can you provide one?
>
> /Anders
>
> On Wed, Jan 19, 2011 at 21:59, Phillip Helle
Briefly looking through the comments it looks like an integration test is
missing for the patch to be accepted. Can you provide one?
/Anders
On Wed, Jan 19, 2011 at 21:59, Phillip Hellewell wrote:
> Has anyone else run into this? I run into it all the time. It
> appears to be because unpack-d
On Fri, Oct 8, 2010 at 6:45 AM, wrote:
> I work on a portlet project so some dependencies are provided by the portal
> (ie hibernate, spring etc...).
>
> My project has 2 modules :
> -parent
> |_services
> |_ui
>
> Hibernate is a dependency from the services module. The services module is a
>
We are building a large portlet project (60+ maven projects) and have
developed a pretty good methodology.
I have described it a few times in the forum.
It works well with Spring, Hibernate, MySQL, Jetspeed, CXF, and about 50
other common libraries from Apache and others.
Ron
On 08/10/2010 9
2010/10/8 :
> My project has 2 modules :
> -parent
> |_services
> |_ui
>
> Hibernate is a dependency from the services module.
With which scope? IIRC only if you have "compile" or "runtime" it
becomes a transitive dependency.
Antonio
Thanks; I will take a look at the release and versions plugin to see
if they can help.
Phillip
On Fri, Oct 1, 2010 at 4:57 PM, David Jencks wrote:
>
> On Oct 1, 2010, at 12:38 PM, Phillip Hellewell wrote:
>
>> On Fri, Oct 1, 2010 at 1:14 PM, David Jencks wrote:
>>>
>>> On Oct 1, 2010, at 11:25
Schor
An: Maven Users List
Betreff: Re: Dependencies between modules of a multi module project
m2eclipse supports both styles of dependency resolution -
1) resolving using normal maven dependency resolution (usually, the
prebuilt jar
in the .m2 local repository), or
2) from the current workspace (
2010/10/3 Iron Eagle :
> The only thing, that is still not working, is building module A (that depends
> on module B) within the directory of module A (and without having installed
> module B before). But if I understand it correctly, this is a design issue of
> maven.
A design *feature*, not a
(and without having installed
module B before). But if I understand it correctly, this is a design issue of
maven.
best reagrds
Original-Nachricht
> Datum: Sat, 02 Oct 2010 15:02:26 -0400
> Von: Marshall Schor
> An: Maven Users List
> Betreff: Re: Dependencies bet
m2eclipse supports both styles of dependency resolution -
1) resolving using normal maven dependency resolution (usually, the prebuilt jar
in the .m2 local repository), or
2) from the current workspace (allowing you to "pick up" changes there, even if
the other project(s) weren't built/installed.
2010/10/2 Iron Eagle :
> Some times, I use the command line (there its no problem). But most time, I
> use eclipse. I've searched for a tutorial for that problem, but the result
> doesn't really satisfy me.
If you use m2eclipse and you checkout the entire main pom project as
Maven project, the p
, but the result doesn't
really satisfy me.
How do you handle that problem? Is there a best practise?
best regards
Original-Nachricht
> Datum: Fri, 1 Oct 2010 21:35:58 -0400
> Von: Wendy Smoak
> An: Maven Users List
> Betreff: Re: Dependencies between mod
On Fri, Oct 1, 2010 at 8:08 PM, Jon Paynter wrote:
> I suspect we are missing something in the way maven was designed to work.
> How is multi-module development intended to work?
You have it right. Maven will not go build a sibling module, it will
use what's in the local repository.
Most IDEs
I run into the same problems...
running mvn install, puts module 'A' in your local repository where it can
be found when doing a compile for module 'B'
-but-
if im doing development on both modules.. I dont want the old version of
module 'A' to be used when im compiling module 'B' - I want it to p
Have you run mvn install?
david jencks
On Oct 1, 2010, at 4:12 PM, Iron Eagle wrote:
> Hi there,
>
> I have a multi module project with a parent, module A and module B. I
> configured each module pom with the parent and added the modules to the
> parent pom.
>
> Module B depends on module A,
On Oct 1, 2010, at 12:38 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 1:14 PM, David Jencks wrote:
>>
>> On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
>>>
>>> We are planning to make things consistent so that this automation will
>>> be possible, e.g.:
>>> 1. Each "component"
On Fri, Oct 1, 2010 at 1:14 PM, David Jencks wrote:
>
> On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
>>
>> We are planning to make things consistent so that this automation will
>> be possible, e.g.:
>> 1. Each "component" will live in a specific place in SVN (e.g.,
>> /components/COMPNAM
On Fri, Oct 1, 2010 at 12:55 PM, Justin Edelson wrote:
> On 10/1/10 2:25 PM, Phillip Hellewell wrote:
>> So I'll know exactly what to check out for that component just from
>> its name and version, which I can get from dependency:resolve.
>
> You'll also need to create a branch from the tag when y
On Oct 1, 2010, at 11:25 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>>> that would scan all the dependencies and print out their versions,
>>> that would suffice and I could do the c
On 10/1/10 2:25 PM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>>> that would scan all the dependencies and print out their versions,
>>> that would suffice and I could do the checking out
On Fri, Oct 1, 2010 at 12:02 PM, David Jencks wrote:
>> Cool, that's what I was hoping to hear. Even if I just had a plugin
>> that would scan all the dependencies and print out their versions,
>> that would suffice and I could do the checking out myself.
>
> does mvn dependency:tree do what you
On Oct 1, 2010, at 8:29 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 9:10 AM, Justin Edelson
> wrote:
>>
>> There's nothing in Maven or the core plugins that will do this for you
>> out of the box. But there's also nothing stopping you from writing a
>> plugin to do this yourself. The
On Fri, Oct 1, 2010 at 9:17 AM, Antonio Petrelli
wrote:
>
> I think all of this mess is solvable by using a private Maven
> repository, like Nexus.
> If I understand you correctly, you want to do this since you cannot
> access to a pre-built version of B. Deploy a repository, you'll
> (development
On Fri, Oct 1, 2010 at 9:10 AM, Justin Edelson wrote:
>
> There's nothing in Maven or the core plugins that will do this for you
> out of the box. But there's also nothing stopping you from writing a
> plugin to do this yourself. There are core Maven plugins which do parts
> of this (primarily dep
2010/10/1 Phillip Hellewell :
> On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
> wrote:
> I want Maven to help check out B for me (and other dependencies). I
> can check out A manually, but I want Maven's dependency mechanism to
> find B in the (local or remote) repository, and instead of copyi
On 10/1/10 11:03 AM, Phillip Hellewell wrote:
> On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
> wrote:
>> If you control B this is not necessary. Simply add a dependency to a
>> snapshot of B and, when you build B and, after it, build A, the latter
>> will get the latest build of B.
>> Or am I
On Fri, Oct 1, 2010 at 8:29 AM, Antonio Petrelli
wrote:
> If you control B this is not necessary. Simply add a dependency to a
> snapshot of B and, when you build B and, after it, build A, the latter
> will get the latest build of B.
> Or am I missing something?
Yes, of course I can check out B,
2010/10/1 Phillip Hellewell :
> In case I want to make changes to the dependency.
>
> This won't be the general workflow, but if I'm working on artifact A, which
> depends on artifact B, and I notice a change needs to be made to B, rather
> than have to manually checkout B and make changes there, I
In case I want to make changes to the dependency.
This won't be the general workflow, but if I'm working on artifact A, which
depends on artifact B, and I notice a change needs to be made to B, rather
than have to manually checkout B and make changes there, I want to make it
more seamless by provi
2010/9/30 Phillip Hellewell :
> The biggest question for me is in how these all fit together, e.g., is it a
> normal mechanism to want to fetch an artifact into the local repository,
> copying and extracting it to a subfolder, and then (if it includes source)
> compile it when compiling the "parent
Maven Golden Rule is that one project only has one primary artifact. For a
project, there is only one pom so all artifacts will share it. So having
more than one artifact from one project makes you experience these kind of
issues you're describing. It's as designed.
/Anders
On Wed, Jun 30, 2010 a
Hi Karl Heinz,
Karl Heinz Marbaise wrote at Montag, 12. April 2010 10:02:
[snip]
>
> But now i tried something different. I defined the dependency in m3.2's
> pom to use m4 as dependency:
>
>
>
> ${project.groupId}
> m2.1
> ${project.version}
>
>
> ${p
Does this help you?
http://maven.apache.org/guides/introduction/introduction-to-dependency-m
echanism.html#Importing_Dependencies
Subir
-Original Message-
From: Karl Heinz Marbaise [mailto:k...@soebes.de]
Sent: Monday, April 12, 2010 1:32 PM
To: users@maven.apache.org
Subject: Dependenci
On 4/12/10 4:02 AM, Karl Heinz Marbaise wrote:
>
...
> Maybe i misunderstand the usage of a module ...or do i have to give simply
> the modules m4.1...m4.5 as dependency instead of using m4?
>
> The m4 module is a aggregation of multiple modules (m4.1...m4.5) which are
> needed as dependency so i
By adding a dependency to m4, you simply add that dependency to all its
childs.
Said that, the m4.1 now contains dependency of himself, which is what the
system informed you.
without the dependency on m4, the system should work fine.
2010/4/12 Karl Heinz Marbaise
>
> Hi Harald,
>
> first of al
Hi Harald,
first of all thanks for your help...
Harald Entner-3 wrote:
>
> m4 does not have any dependencies to its submodules (it just aggregates
> them).
That seemed to be not the full truth...if i try to supplemental define a
dependency in my m4 module to make the dependency to m4.1 explic
Hi Karl,
m4 does not have any dependencies to its submodules (it just aggregates
them). so in order to build 3.2, it is sufficient that m4 is built first
(e.g. maven includes modules and dependencies defined in m4).
Does it built correctly if you delete your repository (at least the m*
entries? I
>>>If I simply add dependency in module "B"'s pom.xml -- it will use "A"
from repository, and if I did not do "mvn deploy" there would not be
one!
If you build from Top Parent then Reactor will know what to compile
first and second.
Don't try to compile module B directly, in which case B resolves
Don't worry, it will work as expected:
If you have a multi-level project (X) which contains 2 modules A & B,
and if you have B depends on A in POM, once you build X, it will
help u to build A first and then B, and it will use the local copy of
A when building B.
"Using A from repository" will hap
you can run the dependency plugin
http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht de
No... The test goal gets both the compile and test classpaths so
defining the module dependencies as compile scope will do the trick.
On 9/3/09, James Russo wrote:
> Hello,
>
> I have a module A, B and C. Module C requires both module A and B
> to compile and also test, do I need to include
> seems that with maven 2.1
> if I have a dependency in a pom.xml listed *twice* (or is it twice
> with differing versions?) the dependency is silently ignored.
I've never experienced that myself. Can you provide your pom along
with the output of "mvn help:effective-pom"? Post them on
www.pastebin
I realize that this post is quite old, but I am looking for similar
information. What we've experienced is that the aggregator pom does depend
on the target build directory and not the local repository. Is there a way
to reverse this? In our case, we are using a non-standard code structure
(whi
Well- I did not try yet this part, but I was not sure how it can be done?
For a specific dependency that you used to compile- how can you tell the
maven to also copy the third party, and how do you configure the target
location?
Thanks
Eyal
Wayne Fay wrote:
>
>> I am need to know how can I co
> I am need to know how can I copied some of the jars I need for compilation,
> so they will serve me also for runtime time.
You need to provide a lot more information, including specifics on
what you're already tried and why they did not work for you, what you
expect/need, etc.
Wayne
--
On Mon, Dec 1, 2008 at 9:45 AM, Ryan Cuprak <[EMAIL PROTECTED]> wrote:
> I've got a bunch of dependencies from some open source projects which are
> not available in a central Maven repository. Until those projects some day
> publish them to a repository I do a 'mvn install ' to populate my local
The recommended approach is to use an internal repository for your team.
You can do this with a repo manager like Nexus. See the thread this
weekend on "Third Party Jars" it covers this in more detail.
-Original Message-
From: Ryan Cuprak [mailto:[EMAIL PROTECTED]
Sent: Monday, December 0
Hello Simone and Graham,
Both options satisfy my needs. I prefer to deliver a ~/.m2/repository but I
think it will depend on the client...
Thank you
On Monday 03 November 2008 12:33:28 Simone Gianni wrote:
> Hi David,
> nobody said that a repository has to be remote, you can create a local
> fi
Hi David,
nobody said that a repository has to be remote, you can create a local
file repository, and install there (copying it from the main repo, or
using mvn deploy) all the dependencies you want, then configure this
repository in your pom, and ship it together with you project.
For example, yo
David Ojeda wrote:
So my question is: what can I do if I want to deliver give the source code and
the dependencies jars?
Here are some of my ideas:
- Maintain a private repository with dependencies and use the deploy:deploy-
file goal to add dependencies to it.
Problem: in the love/hate relati
It works!
It would be good if they would update the documentation to let this know.
There is no sign of any of those alpha or beta versions on the cargo
website.
regards & thank you again, you just made me very happy :)
Wim
2008/10/24 Nick Stolwijk <[EMAIL PROTECTED]>
> It can be found here:
>
See here : http://repo1.maven.org/maven2/org/codehaus/cargo/cargo-maven-plugin/
Wim Deblauwe a écrit :
> In what repo is that version?
>
> 2008/10/24 Marc Schneider <[EMAIL PROTECTED]>
>
>> Hello,
>>
>> I also use the cargo-maven2-plugin but don't need to specify all these
>> dependencies.
>>
>>
It can be found here:
http://repository.codehaus.org/org/codehaus/cargo/cargo-maven2-plugin
beta 1 is also available.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Fri, Oct 24, 2008 at 11:12 AM, Wim Deblauwe <[EMAIL PROTECTED]> wrote:
> In
In what repo is that version?
2008/10/24 Marc Schneider <[EMAIL PROTECTED]>
> Hello,
>
> I also use the cargo-maven2-plugin but don't need to specify all these
> dependencies.
>
> Btw I use cargo 1.0-alpha6.
>
> Here is my plugin configuration :
>
>
>org.codehaus.cargo
>cargo-mav
Hello,
I also use the cargo-maven2-plugin but don't need to specify all these
dependencies.
Btw I use cargo 1.0-alpha6.
Here is my plugin configuration :
org.codehaus.cargo
cargo-maven2-plugin
false
tomcat5x
How are you using the JAR exactly?
In other projects we deal with this by copying the file to a new
location with the version removed at the time it needs to be used.
- Brett
2008/10/4 Simon Trudeau <[EMAIL PROTECTED]>:
> I would like to add a dependency to my maven project but have it
> include
Ok thanks, will remove it.
> They shouldn't be added twice.
>
> Simply using test scope should do what you want... it will be on the
> classpath for compiling and tests, and will not be be transitive.
-
To unsubscribe, e-mail:
On Wed, Sep 17, 2008 at 10:32 AM, Johannes Schneider
<[EMAIL PROTECTED]> wrote:
> Those dependencies are necessary for the tests to run successfully. And
> I want them to be optional for the main sources.
> I have added them two times.
>
> What do you think about this? Is this a mistake? What is
Thank you very much for the fast and good help :)
Hal
Original-Nachricht
> Datum: Mon, 8 Sep 2008 10:01:26 +0200
> Von: "Guillaume Boucherie" <[EMAIL PROTECTED]>
> An: "Maven Users List"
> Betreff: Re: Dependencies on a HAR-F
Hi,
Did you try to use "jboss-har" for the type ?
And don't forget to declare the jboss-packaging-maven-plugin with extension
enabled.
org.codehaus.mojo
jboss-packaging-maven-plugin
true
...
Guillaume Boucherie
2008/9/8 hal arres <[EMAIL
James Carman wrote:
What is the "maven way" of doing this? Suppose a library you're
writing requires Spring. You write your library against an older
version of Spring (2.0) and you define it as a dependency. Now, when
other projects want to use your library, spring-2.0.jar will be
included in
I'm not sure what either of you mean here.
Normally, your lib's pom just declares a dependency on the "recommended"
version of the lib you want (Spring in this case), eg
2.0.4
When a project depends on your lib but doesn't otherwise use Spring,
then your "recommended" version is used. If the pr
provided
On Feb 16, 2008 7:05 PM, James Carman <[EMAIL PROTECTED]> wrote:
> What is the "maven way" of doing this? Suppose a library you're
> writing requires Spring. You write your library against an older
> version of Spring (2.0) and you define it as a dependency. Now, when
> other projects
>
>
> "it will be probably in a future version" - can you be more specific?
>
I don't think we'll can add it before the next major version 2.x. I don't
have a date for the release.
Emmanuel
Thanks, Emmanuel, I kind of guessed this was the case.
"it will be probably in a future version" - can you be more specific?
--
View this message in context:
http://www.nabble.com/Dependencies-in-builds-tp15455354p15456465.html
Sent from the Continuum - Users mailing list archive at Nabble.com.
Actually, it isn't possible to add some "build rules", it will be probably
in a future version.
A workaround for your issue would be to create only one shell project that
will run your 3 builds with a check of the result of each.
Emmanuel
On Feb 13, 2008 12:17 PM, Ken Turner <[EMAIL PROTECTED]>
problem solved! disregard message
Vytautas Čivilis wrote:
Hi,
I have an issue regarding two (at least) multi-project sets.
I have the similar layout:
modules.core...
...defines module core (which defines modules.core as it's parent)
modules.notCore...
...defines module wantCore (
thats just asking for pain... isn't system scope deprecated now?
On Tue, 11 Dec 2007 02:13:12 Andrew Williams wrote:
> system
>
> On 10 Dec 2007, at 12:52, Luis Roberto P. Paula wrote:
> > Hi All,
> >
> > Is there any way to set dependencies to a local classpath instead of a
> > package in a repos
system
On 10 Dec 2007, at 12:52, Luis Roberto P. Paula wrote:
Hi All,
Is there any way to set dependencies to a local classpath instead of a
package in a repository?
Thanks,
Luis
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
On Thu, 06 Dec 2007 10:12:27 Kallin Nagelberg wrote:
> You can always wrap certain sets of dependencies up in another POM with
> 'pom' packaging type to keep the dependencies aspect of your pom isolated
> from whatever else you're having it do.
yes this is the way to do it... however i use jars as
You can always wrap certain sets of dependencies up in another POM with
'pom' packaging type to keep the dependencies aspect of your pom isolated
from whatever else you're having it do.
One thing I wish the pom had was a way to perform composition from common
components instead of having to use in
refactoring, composition, encasulation, aggregation standard techniques for
making complex systems easier to understand...
On Thu, 06 Dec 2007 09:42:49 Marco Mistroni wrote:
> hi all,
> just a quick question to see best practices with maven projects.
> i have a pom which contains lot of dep
Not that I'm aware of. Why do you need to use "_" instead of "-"?
Wayne
On 11/1/07, Felix Knecht <[EMAIL PROTECTED]> wrote:
> Hi all
>
> I haven't found anything about this in the FAQs googling. Therefore my
> question.
>
> Can I have a dependency named foo.bar_1.0.0.jar?
> Note the underscore a
Yep, I did see that. There is an "install" task, but if I read the
documentation correctly, I need to create the pom by hand. "mvn
install:install-file ..." would take care of that automagically ...
Ok, it's not that hard to script the creation of a pom, but as maven
seems to know how to do it, I'
Right on the Maven homepage is: "Maven Tasks for Ant 2.0.7 (binaries,
documentation, release notes)". That should do it.
Wayne
On 10/29/07, Guillaume Lederrey <[EMAIL PROTECTED]> wrote:
> On 26/10/2007, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > Instead I would
> > build a little shell script that
On 26/10/2007, Wayne Fay <[EMAIL PROTECTED]> wrote:
> Instead I would
> build a little shell script that would analyze your pom, go out to
> your proprietary repo and download the necessary files and then use
> "mvn install:install-file -DgeneratePom=true -DcreateChecksum=true
> ..." to install eac
I didnt think about that, but it sounds like a great solution ! Thanks !
I'll have a look on monday ...
On 27/10/2007, Wayne Fay <[EMAIL PROTECTED]> wrote:
> On Windows, there is mavenrc_pre.bat and mavenrc_post.bat. Check the
> mvn.bat file to see the reference to those files.
>
> And you can e
On Windows, there is mavenrc_pre.bat and mavenrc_post.bat. Check the
mvn.bat file to see the reference to those files.
And you can easily customize your mvn.bat or mvn.sh file for your
corporate environment if you want to do "special stuff" in addition to
the normal Maven commands. You just need t
Wayne, Graham, thanks for your advices !
I will investigate a bit the system bug/feature (havent
really heard of it yet).
Is it possible to have maven run a script before dependency checking ?
That would allow us to have a script (or maven-plugin, or ant task,
or whatever) run as part of the buil
1 - 100 of 290 matches
Mail list logo
