Hi,
I've got a question regarding dependency management -
I've got a project with a default "tree layout" - it uses subprojects,
which again are using subprojects which again...
Now, one of these subprojects defined a dependency scope as "compile".
It's "
check for project
dependency inconsistency)
Any ideas?
Sonia
--
View this message in context:
http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
I have a question that I hope isn't too basic. I've been trying to
reconcile the behavior of dependency management with my expectations. I'll
state in advance that I'm more than willing to admit that my expectations
might be unrealistic.
We've got a "home grown&qu
Hello all,
Is there a way to configure maven2 so that it loads classes from a
dependency that I specify rather than from the JVM? I guess that I need to
configure the class path so that my library is located in front of the
libraries from the JVM.
Cheers
Brian DePradine
Web Services Developme
Hi, I have a few questions about modules and dependencies. Does the
order of modules listed in the parent pom.xml matter? For example, if C
depends on A and B depends on C, then the correct order would be:A, C B
A
C
B
If I specify instead
A
B
C, will Maven pick up the right dependency order and
Hi,
I'm wondering which way maven is going in terms of dependency
management. In my scenario and most I'm aware of, I'd like to
distinguish between different types of dependencies to support e.g. a
clever distribution of the application.
I'm thinking of three types: compil
We're having problems building modules like this from scratch. If we
run process resources from the top most level, submodule.B complains
about not being able to find module1's artifacts (why would submodule.B
need module 1's jar artifact just to process resources?).
parent - version 1.0-SNAPSHO
Hi Alexander,
> Hi, I have a few questions about modules and dependencies. Does the
> order of modules listed in the parent pom.xml matter?
As said by others it does NOT matter for the dependency management.
It only matters for the ordering when the modules are rendered to the
menu
Hi!
On Thursday 25 June 2009 Peter Horlock wrote:
> Hi,
>
> I've got a question regarding dependency management -
> I've got a project with a default "tree layout" - it uses subprojects,
> which again are using subprojects which again...
>
> Now, one
thx! That thread Told me all I needed to know! :-)
Peter
, C)
that act as a facade around a legacy component D...so D is at the bottom of
the dependency graph.
However we really need D's dependency management to be at the top level
too. That is, lots of changes happen at the legacy component D and we don't
want to have to manually track dependen
Our project has about 65 dependencies listed. I just discovered that
one was listed twice. Is there a tool that will detect that for me?
Or, perhaps one that will sort the dependencies to make it easier to
scan for duplicates?
--
All religions are Scientology complete
-
t;
> Sonia
> --
> View this message in context:
> http://old.nabble.com/Dependency-Management-%2B-tp28366761p28366761.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To
d modules don't
>> use the same version of inter-project dependencies. (would check for project
>> dependency inconsistency)
>>
>> Any ideas?
>>
>> Sonia
>> --
>> View this message in context:
>> http://old.nabble.com/Dependency-Management
On 8/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
>
> I have a question that I hope isn't too basic. I've been trying to
> reconcile the behavior of dependency management with my expectations. I'll
> state in advance that I'm more than willing to
"Eric Redmond" <[EMAIL PROTECTED]> wrote on 08/21/2007 12:12:55 PM:
> On 8/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> wrote:
> >
> > I have a question that I hope isn't too basic. I've been trying to
> > reconcile the behavior of depend
[EMAIL PROTECTED] schrieb:
"Eric Redmond" <[EMAIL PROTECTED]> wrote on 08/21/2007 12:12:55 PM:
On 8/21/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]>
wrote:
I have a question that I hope isn't too basic. I've been trying to
reconcile the behavior of dependency
hat I hope isn't too basic. I've been trying to
> > > reconcile the behavior of dependency management with my expectations.
> I'll
> > > state in advance that I'm more than willing to admit that my
> expectations
> > > might be unrealistic.
> &
I'd like to thank you again for taking time to work with me on this. I
have been asked to address a production problem for now but I will attempt
to post a concrete example from home this evening or no later than
tomorrow morning (my TZ is GMT +5).
Robert Egan
Tim Kettler <[EMAIL PROTECTED]> w
As promised:
I wrote on 08/21/2007 03:13:21 PM:
> I'd like to thank you again for taking time to work with me on this. I
> have been asked to address a production problem for now but I will
attempt
> to post a concrete example from home this evening or no later than
> tomorrow morning (my TZ
I think what you really want is simply a on artifact1 and
artifact2 in your artifact3 pom, not ../artifact1.
I'm a little surprised that ../ notation is even allowed in the module
node, to be honest.
Then, when you build from the top, all of your projects will be built
in the proper order assumin
If you build from a3, Maven will use the most recently built (and
> installed into your local repo) files from a1 and a2. It will not go
> into a1 and a2 to rebuild those files, however.
>
> Wayne
I have also come to this conclusion. It is the correct approach to
dependency management, al
Hello,
In our project, we have two different modules separated into two eclipse
projects. We use ant for project compilation, packaging and deployment.
Dependency management is achieved using maven inside ant build.xml script.
One of the modules depends on the other, i.e. module B depends on
On 14/11/2007, Brian De Pradine <[EMAIL PROTECTED]> wrote:
>
> Hello all,
>
> Is there a way to configure maven2 so that it loads classes from a
> dependency that I specify rather than from the JVM?
could you explain which classes you'd want to load from a dependency rather
than
the JVM - and als
We have many interdependent projects
here. When someone releases a project upon which many other projects
depend we need some way of knowing automatically which projects will also
need to be retested.
is there a m2 plugin that manages reverse
dependency lookups? For simplicity I am really mostl
Hi Alexander,
2006/9/27, Morgovsky, Alexander (US - Glen Mills) <[EMAIL PROTECTED]>:
Hi, I have a few questions about modules and dependencies. Does the
order of modules listed in the parent pom.xml matter? For example, if C
depends on A and B depends on C, then the correct order would be:A,
2006 3:05 AM
> To: Maven Users List
> Subject: Re: Dependency management
>
> Hi Alexander,
>
> 2006/9/27, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]>:
> >
> > Hi, I have a few questions about modules and dependencies. Does the
> > order of mod
rsday, September 28, 2006 11:13 AM
To: Maven Users List
Subject: RE: Dependency management
Hi Alexander & Yann
I believe if you declare a dependency and don't have it specified as a
module, maven will try and download it from the repository.
Thanks
Lakshman
> -Original Message-
&
> -Original Message-
> From: Dominik Dahlem [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 10, 2004 12:20 PM
> To: [EMAIL PROTECTED]
> Subject: Dependency management
>
>
> Hi,
>
> I'm wondering which way maven is going in terms of dependency
> m
ECTED]
Sent: Tuesday, May 01, 2007 3:11 PM
To: Maven Users List
Subject: dependency management problems...
We're having problems building modules like this from scratch. If we
run process resources from the top most level, submodule.B complains
about not being able to find module1's artif
PROTECTED]
Sent: Tuesday, May 01, 2007 3:11 PM
To: Maven Users List
Subject: dependency management problems...
We're having problems building modules like this from scratch. If we
run process resources from the top most level, submodule.B complains
about not being able to find module1&#
need to be resolved if compilation
is not part of the build?
William
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 2 May 2007 1:24 PM
To: Maven Users List
Subject: Re: dependency management problems...
As far as I know, you can't. Maven re
-resources time)?
>
> -Original Message-
> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 01, 2007 3:11 PM
> To: Maven Users List
> Subject: dependency management problems...
>
> We're having problems building modules like this from scratch. If w
TED]
Sent: Friday, 4 May 2007 2:00 AM
To: Maven Users List
Subject: Re: dependency management problems...
So essentially you'd break up and move the monolithic "validate" phase
into a series of "mini-validates" that fire immediately before every
other lifecycle phase, to v
ss it amounts to the same thing.
William
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Friday, 4 May 2007 2:00 AM
To: Maven Users List
Subject: Re: dependency management problems...
So essentially you'd break up and move the monolithic "validate" phase
i
I know dependency management is inherited from parents, but is it also
used when the project is declared as a dependency of another project?
For example, lets say I have a dependency graph D->C->B->A. B depends on
A-1. C's dependency management section is set to use A-2. Assum
--
View this message in context:
http://www.nabble.com/Multiple-developer-dependency-management-tf3284959s177.html#a9137608
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
Yes, you could use the "import" scope at the top level to import dependency
management defined in another pom (which could be the ones in D).
http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies
/Anders
On Sat, Nov 7, 2009 at 15:42, David Hoffer wrote:
> We have
, 2009 at 9:10 AM, Anders Hammar wrote:
> Yes, you could use the "import" scope at the top level to import dependency
> management defined in another pom (which could be the ones in D).
> http://docs.codehaus.org/display/MAVEN/Importing+Managed+Dependencies
>
> /Anders
>
&g
maven now? Btw I use
> 2.1.0.
>
> Also what do you think about http://code.google.com/p/assimilate/mentioned
> in the bottom of this link?
>
> -Dave
>
> On Sat, Nov 7, 2009 at 9:10 AM, Anders Hammar wrote:
>
> > Yes, you could use the "import" scope at th
t is in maven now? Btw I use
>> 2.1.0.
>>
>> Also what do you think about http://code.google.com/p/assimilate/mentioned
>> in the bottom of this link?
>>
>> -Dave
>>
>> On Sat, Nov 7, 2009 at 9:10 AM, Anders Hammar wrote:
>>
>> > Ye
> >> 2.1.0.
> >>
> >> Also what do you think about
> http://code.google.com/p/assimilate/mentioned
> >> in the bottom of this link?
> >>
> >> -Dave
> >>
> >> On Sat, Nov 7, 2009 at 9:10 AM, Anders Hammar
> wrote:
>
; >>
> > >> Just to be clear, in that link it seemed to be a discussion of what to
> > >> possibly add to maven...are you saying that is in maven now? Btw I
> use
> > >> 2.1.0.
> > >>
> > >> Also what do you think a
es.
> > > >
> > > > /Anders
> > > >
> > > > On Sat, Nov 7, 2009 at 17:41, David Hoffer
> wrote:
> > > >
> > > >> That looks good.
> > > >>
> > > >> Just to be clear, in that link it seemed to be a discussio
t; > > /Anders
> > > > >
> > > > > On Sat, Nov 7, 2009 at 17:41, David Hoffer
> > wrote:
> > > > >
> > > > >> That looks good.
> > > > >>
> > > > >> Just to be clear, in that link it
s/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
>> > > > >
>> > > > > The import support is different that what the assimilate gives
>> you.
>> > The
>> > > > one
>> > > > > described abo
; >> > > > >
> >> > > > >
> >> > > >
> >> > >
> >> >
> >>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Importing_Dependencies
> >> > >
the to true for the other dependency.
You can’t control the framework distribution, so it misses the control of
the transitive dependency in the leaf tree.
What do you think about?
Thanks
--
Gregory BOISSINOT
--
View this message in context:
http://www.nabble.com/A-poor-dependency-management
Hi,
we got a software, which is devided into serveral sub projects.
We defined a parent pom, that, besides other shared items, contains a
dependency management section to ensure all sub projects are using the same
dependencies. Also, as the "software" we are talking about is actually
You could use the dependency management[1] report for that.
Hth,
[1]
http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependency-management-mojo.html
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Tue, Apr 21, 2009 at 8:15 PM
I like to use:
mvn dependency:tree
mvn dependency:analyze
On Tue, 21 Apr 2009 20:19:54 +0200, Nick Stolwijk
wrote:
> You could use the dependency management[1] report for that.
>
> Hth,
>
> [1]
>
http://maven.apache.org/plugins/maven-project-info-reports-plugin/dep
Hello,
I have what might be a basic question, but I haven't been able to find a
way to accomplish it using Maven. The project I am working on
(Braintrain: http://code.google.com/p/braintrain/) uses Maven as the
build framework. What I want to do is basically unzip 2 zip files and
move the c
Hey all,
I have a parent module with dependencies listed under the
dependencymanagement section. I now have two modules under this parent,
which are both pom packaging maven projects.
both the sub parent projects have common dependencies along with some
specific. If i put a dependencymanagement
replaced
by the new one.
Thanks anyway.
Eguzki Astiz Lezaun escribió:
Hello,
In our project, we have two different modules separated into two
eclipse projects. We use ant for project compilation, packaging and
deployment. Dependency management is achieved using maven inside ant
build.xml
Hi,
I was wondering if anyone knows or has experience with a system that would
track and consolidate dependencies on a project composed of several
sub-projects.
Assume a project P with 10 sub-projects (SP1...SP10). Each of those
sub-projects are located in its own space and have its own lifecycle
Hi Team,
Can somebody please explain me what is the difference between using a
dependency in dependency management and dependency in dependencies .?
We have one project where some dependencies in parent pom are defined
under the dependency management while other are defined under the
On 12/23/05, David Sag <[EMAIL PROTECTED]> wrote:
>
>
> We have many interdependent projects here. When someone releases a
> project upon which many other projects depend we need some way of knowing
> automatically which projects will also need to be retested.
is there a m2 plugin that manages re
This is actually a feature in the repository manager we've been discussing
on the dev list. It's not ready yet, but its an app on the repository that
you could use to browse such a relationship. A Maven plugin could query
that.
- Brett
On 12/24/05, David Sag <[EMAIL PROTECTED]> wrote:
>
>
> We ha
Hi!
Is there a way to configure dependencies so that you need not specify a
specific version but say "take any release greater than version x.y but
do not consider snapshot releases". I know that you can specify version
ranges but ranges include snapshot releases that might not be stable. Is
ther
Hello all,
I am going to have a m2 build system that contains lots of sub projects.
my daily build uses the same version of all sub projects. and the version is
incremented for each daily build.
In M1, I use one global version property in project.properties of the master
project root. For each
Hi All,
I would like to get some more insight on how maven find the jars in the
repository. For instance, I use mule 1.3.3 which has the following
dependency:
org.safehaus.jug
jug
2.0.0
asl
The jar downloaded is:
http://repo1.maven.org/maven2/org/safehaus/jug/jug/2.0.0/jug-2.0.0-asl.jar
Is th
I am using cruisecontrol to build a multimodule project.
The problem I am observing is that if projects A and B are checking in at
the same time and B depends on A the order that they are built in is not
set.
This means that if B builds before A then the build will fail.
I have had a look for
endency on A (A-1 or A-2) in D to
guarantee a specific version.
Wayne
On 5/23/07, Siegmann Daniel, NY <[EMAIL PROTECTED]> wrote:
I know dependency management is inherited from parents, but is it also
used when the project is declared as a dependency of another project?
For example, lets say
Siegmann Daniel, NY wrote on Wednesday, May 23, 2007 8:35 PM:
> I know dependency management is inherited from parents, but is it also
> used when the project is declared as a dependency of another project?
With M206, yes, with older versions, no!
> For example, lets say I have a d
I have a question about the behavior of the
portion of a POM as it relates to plugin dependencies.
Say I have:
...
GROUP
ARTIFACT
...
And in some project that inherits from this pom,
...
GROUP
ARTIFACT
...
will fail with a missing version.
Is t
Is there a way, or are there some features in planning, to manage
dependencies based on the license? What I would like is a report of
licenses used by all dependencies (transitives included) and perhaps a means
to reject (or warn the user about) certain license types, or only allow a
build with c
ent paths? Snapshot jars are installed on the shared
repository,
which would mean the two developers would interfere with each other. For
example, I would like to be able to set up a separate repository with full
isolation for each developer.
How can I create such an environment?
--
View this m
s-logging
> 1.1
> runtime
>
>
>
> The problem is that the common-logging maven descriptor is very poor.
> They should use for theirs dependency provided scope for "servlet-jar" that
> is not transitive or the to true for the other dependency.
>
> You
Gregory BOISSINOT wrote:
Hello,
I use Maven 2 for almost 2 years now.
The Maven distribution version succeeds one another and I don’t understand
why you always cannot choice to exclude transitive dependency for your
dependency framewok.
But you can do that. More on that below...
For examp
23:39:51 Peter Horlock wrote:
> Hi,
>
> we got a software, which is devided into serveral sub projects.
> We defined a parent pom, that, besides other shared items, contains a
> dependency management section to ensure all sub projects are using the same
> dependencies. Also, a
Could you be a bit more precise? (Just make it plain simple, this increases
the chance that I get it! ;-)
Thanks,
Peter
On Thu, 03 Jul 2008 00:44:20 Peter Horlock wrote:
> Could you be a bit more precise? (Just make it plain simple, this increases
> the chance that I get it! ;-)
I suppose
The things i do
1) parent version are always release versions
2) all depedencies are always release versions
3) release often
tifact level not just code level
Can you explain that in more detail?
>
> >Simple enough?
Much better, but I could stilll use some enlightment! :-)
Also, I feel, even though you gave me LOTS of good tips and tweaks, you
didn't really answer my question(s) - which was:
1. Use
Hi Michael,
well it seems everybody has some different scheme that works for him/his
company.
Michael McCallum wrote:
> On Thu, 03 Jul 2008 00:44:20 Peter Horlock wrote:
>> Could you be a bit more precise? (Just make it plain simple, this
>> increases the chance that I get it! ;-)
> I suppose
>
le versions have meaning outside the dev team, just like
revision numbers in source control don't matter as long as the pattern is
consistent and decipherable. Ranges let you be really specific about what any
project means. Using the hit and hope version def basically means you project
can end
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > hibernate.composite 7.x uses hibernate 3.2.6ga, uses ehcache
> > 3.0, uses
> > cglib... excludes commons-logging, excludes ehcache, excludes
> > cglib-full and all my projects the use hibernate use
> > hibernate.composite.[7,8-!)
>
> We make the
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 12) set up parents that define plugins for particular types
> > of projects i.e.
> > webapps, jars, parents,
>
> We setup the common settings in the pluginMgmnt of the global POM ... and
> lock down the plugin versions.
not quite what i was get
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 6) start version numbering 1.1 for new artifacts
> > * makes ranges work better
> > * who needs the extra .0 on the end, i save that for patches
>
> Why's that? Also remember that version 1 is implicitly 1.0.0.0
so that range [1,2-!) does incl
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > project.deployable uses implementation.[1,2-!) and consumer.[1,2-!)
> > obviously in the real world things aren't this simple and for
> > simple cases
> > this seems like excessive overhead
>
> We do not use ranges at all. Works great without.
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 8) use mvn dependency:resolve and mvn
> > depedendency:tree regularly to understand how things are working and
> > to catch any
> > transitions that i did not
> > expect
>
> Especially after upgrading version of 3rd party artifacts ;-)
Actually
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> project.deployable uses implementation.[1,2-!) and consumer.[1,2-!)
>>> obviously in the real world things aren't this simple and for
>>> simple cases this seems like excessive overhead
>>
>> We do not use ranges at al
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> hibernate.composite 7.x uses hibernate 3.2.6ga, uses ehcache
>>> 3.0, uses
>>> cglib... excludes commons-logging, excludes ehcache, excludes
>>> cglib-full and all my projects the use hibernate use
>>> hibernate.composi
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> 12) set up parents that define plugins for particular types of
>>> projects i.e. webapps, jars, parents,
>>
>> We setup the common settings in the pluginMgmnt of the global POM
>> ... and lock down the plugin versions.
Michael McCallum wrote:
> On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
>>> 6) start version numbering 1.1 for new artifacts
>>> * makes ranges work better
>>> * who needs the extra .0 on the end, i save that for patches
>>
>> Why's that? Also remember that version 1 is implicitly 1.0.0.0
>
asiest way to update the dependency management section -
otherwise, when someone changes the version of a submodule, one has to
change this version, as well as the version in dep. mgmt.
H, this is really hard to swallow, I can't really find THE one and only
solution of how to solve this d
2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>:
> Sorry, but our priority is to ensure that all artifacts are built with the
> same plugins and use the same artifact versions. In your model I have to
> duplicate all the versions for your individual service parents. That's what
> I call an anti-pattern
ion numbers as property values in
> the parent pom -
> I am still not sure this is the best way, especially not with
> project that
> are not really shared by others,
> but this is the easiest way to update the dependency
> management section -
> otherwise, when someone chang
> Neither Michael nor I did propose properties for the version. Simply define
> the version in the version depMgmnt itself and you're done.
No, I don't think so, my point is:
parent pom:
[...]
1.2.3
[...]
submodule:
[...]
1.2.3
[...]
So you will have to change it in two places (=duplicate c
Hi Peter,
Peter Horlock wrote:
> 2008/7/3 Jörg Schaible <[EMAIL PROTECTED]>:
>
>> Sorry, but our priority is to ensure that all artifacts are built
>> with the same plugins and use the same artifact versions. In your
>> model I have to duplicate all the versions for your individual
>> service par
Peter Horlock wrote:
>> Neither Michael nor I did propose properties for the version. Simply
>> define the version in the version depMgmnt itself and you're done.
>
>
> No, I don't think so, my point is:
>
> parent pom:
>
>
> [...]
> 1.2.3
> [...]
>
>
> submodule:
> [...]
> 1.2.3
> [...]
>
>
>
> Last point: The release plugin will fail to update the version of your
> current project if it is defined by a property.
>
Sorry, but what's the purpose of the release plugin anyway? It's site
doesn't really tell it:
http://maven.apache.org/plugins/maven-release-plugin/
If I got it right,
P.s.: It's really sad that there is no book / website that answers all these
kind of "best practice" answers.
The upcoming mvn book "the definitive guide" is great, yet imho it's more
focused on basics. :-(
Peter
Click on the release plugin goals from the page you linked to and the docs
describe exactly what it does... for example see:
http://maven.apache.org/plugins/maven-release-plugin/examples/prepare-release.html.
You'll start appreciating the release plugin when you have a multimodule
project with tens
On Thu, 03 Jul 2008 19:30:58 Jörg Schaible wrote:
> > 8) use mvn dependency:resolve and mvn
> > depedendency:tree regularly to understand how things are working and
> > to catch any
> > transitions that i did not
> > expect
>
> Especially after upgrading version of 3rd party artifacts ;-)
Actually
On Fri, 04 Jul 2008 02:29:07 Jörg Schaible wrote:
> >
> > I can release any artifact any time... i live on the ready to release
> > to production rather than beginning of build cycle line. Subtle but
> > fundamental difference. And the overhead is minimal.
>
> The overhead is that you produce a lot
Hm, but for such analysis, isn't that what subversion is for?!
As I asked you before -
when using version ranges, how can you ensure an upcoming 2.4 dependency
will not break your build that was working with 2.3 ?!
Thanks,
Peter
On Fri, 04 Jul 2008 10:08:44 Peter Horlock wrote:
> As I asked you before -
>
> when using version ranges, how can you ensure an upcoming 2.4 dependency
> will not break your build that was working with 2.3 ?!
there are a few ways but mostly its development process
0) communication
0) planning
rsion being that of some obscure plugin... very annoying.
> but this is the easiest way to update the dependency management section -
> otherwise, when someone changes the version of a submodule, one has to
> change this version, as well as the version in dep. mgmt.
see previous post on
On Fri, 04 Jul 2008 03:59:29 Peter Horlock wrote:
> Sorry, but what's the purpose of the release plugin anyway? It's site
> doesn't really tell it:
> http://maven.apache.org/plugins/maven-release-plugin/
Very good question and simple to answer...
release-prepare - the release plugin will build an
1 - 100 of 298 matches
Mail list logo
