This is where the "fragile" comes in..
In a multi-module build, ${basedir} is the dir of the current build.
Thus, if you have a jar that is needed by all the submodules, you'd have
to move it into all the subdirs. OR define a propery in each module
that gives it's relative location:
../..
On 04/10/2007, Robert Greig <[EMAIL PROTECTED]> wrote:
>
> On 04/10/2007, Rupert Smith <[EMAIL PROTECTED]> wrote:
>
> > By all means, write an alternative build in Ant, that does everything
> that
> > the Maven 2 one does. Once you are done, tell us how long it took, and
> how
> > nicely modular an
This is the thing I find amusing about Maven2. Maven means 'expert' and the
fundamental idea of maven is that is is an expert on how to build, and
provides that expertise in the form of plugins, to free us from having to
write the same code over and over in Ant for common build tasks. Someone
inven
On 04/10/2007, Rupert Smith <[EMAIL PROTECTED]> wrote:
> By all means, write an alternative build in Ant, that does everything that
> the Maven 2 one does. Once you are done, tell us how long it took, and how
> nicely modular and maintainable your script is, and what process you will
> put in plac
Or to use the jar without uploading...
Put it in a local directory that you check in under svn. In your
pom.xmlcreate a repository that references it. For example:
local.repo
Local Repository
file://${basedir}/mvn-repo
The trick is
On 03/10/2007, Robert Greig <[EMAIL PROTECTED]> wrote:
>
> On 03/10/2007, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> > One of the main points of using maven was to get artifacts into the
> > repositories in a way that other USERS can use them with their maven
> > builds.
>
> Other MAVEN USERS presu
On 03/10/2007, Robert Greig <[EMAIL PROTECTED]> wrote:
>
> On 03/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote:
> >
> > I think the following has come out of this thread.. (my view)
>
> > 1. we should make it a practice not to use snapshots
> > 2. if we decide to use one - it should be the only
I think that they key question, right now, for Qpid is .. does Maven add
more to our project as it currently stands than it costs to
maintain/manage/fit in with ? All opinions my own ...
The future is important, in terms of project uptake of Qpid, but we need to
focus on the now for a bit longer i
On 04/10/2007, Rafael Schloming <[EMAIL PROTECTED]> wrote:
> I wouldn't say dependency management is useless. Look at RPM if you want
> an example of how incredibly useful it can be. It's just that what maven
> does doesn't really qualify as dependency management in any real sense.
I agree with m
Rajith Attapattu wrote:
I totally agree that maven sucks in a lot of ways.
I am more upset about the attitude of some of the folks in the maven
community and their reluctance to listen to users.
(I saw most of the discussions my friend deepak had with some of the so
called maven stalwarts in the
Daniel Kulp wrote:
On Wednesday 03 October 2007, Robert Greig wrote:
Since you haven't done a release, the artifacts aren't there.
Once you do the release (providing it's done properly) and actually
start getting users that want to integrate Qpid into their builds,
this starts becoming increasin
I totally agree that maven sucks in a lot of ways.
I am more upset about the attitude of some of the folks in the maven
community and their reluctance to listen to users.
(I saw most of the discussions my friend deepak had with some of the so
called maven stalwarts in the maven community)
However
On 03/10/2007, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> For example: you are currently using mina version 1.0.0. I see 1.0.6
> was released yesterday. To see if qpid works, just update your top
> level pom to 1.0.6 and run. There's also a 1.1.3 released yesterday.
> Again, update and try it.
On Wednesday 03 October 2007, Robert Greig wrote:
> > Since you haven't done a release, the artifacts aren't there.
> > Once you do the release (providing it's done properly) and actually
> > start getting users that want to integrate Qpid into their builds,
> > this starts becoming increasingly im
On 03/10/2007, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> One of the main points of using maven was to get artifacts into the
> repositories in a way that other USERS can use them with their maven
> builds.
Other MAVEN USERS presumably.
> Since you haven't done a release, the artifacts aren't ther
I'll jump in now... :-)
On Wednesday 03 October 2007, Rafael Schloming wrote:
> Robert Greig wrote:
> > On 03/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote:
> >> I think the following has come out of this thread.. (my view)
> >>
> >> 1. we should make it a practice not to use snapshots
> >> 2
Robert Greig wrote:
On 03/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote:
I think the following has come out of this thread.. (my view)
1. we should make it a practice not to use snapshots
2. if we decide to use one - it should be the only option and with list
agreement.
I agree with thes
On 03/10/2007, Carl Trieloff <[EMAIL PROTECTED]> wrote:
>
> I think the following has come out of this thread.. (my view)
> 1. we should make it a practice not to use snapshots
> 2. if we decide to use one - it should be the only option and with list
> agreement.
I agree with these points.
I wou
I think the following has come out of this thread.. (my view)
1. we should make it a practice not to use snapshots
2. if we decide to use one - it should be the only option and with list
agreement.
Carl.
19 matches
Mail list logo
