You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Christian Goos <ch...@web.de> on 2003/11/25 09:50:28 UTC
Organizing the development process with maven
Hi,
we am using Maven on a project with several subprojects.
We use Maven, Eclipse, CVS.
I implemented the recommended development process that
is described in the Maven documentation.
Although building and deploying with works fine, developers
still have problems with the development process.
Can anybody send me some advice how to use Maven in a
project where the subprojects are
a) under heavy development
b) changes to one subproject have to be available to other projects as fast as possible
I would be interested to know how you organize the development on your projects.
Thanks a lot for reading to the end and maybe helping me
Christian
______________________________________________________________________________
WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Organizing the development process with maven
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
>>>>> On Wed, 26 Nov 2003 00:34:10 +1000, Ben Walding <be...@walding.com> said:
> Basically, for what we do, I have all inter-project dependencies set
> to snapshot versions and then just have an external tool setup in
> eclipse to build the active project with jar:install-snapshot. I
> tried the mevenide plugin today, but it didn't work. It looks like
> it will simplify running goals in much the same way as we do now.
Does eclipse loose the ability to refactor across the project code in
this setup? Or perform searches across the workspace?
> If this is too slow, you'll need to switch the project dependencies
> in eclipse from being the jar in the repo to being the other project
> in eclipse. I try not to change my apis too frequently, but its only
> about a 30second turn around time when I absolutely must get the
> latest code / apis into a project. (select changed project,
> jar:install-snapshot, wait, refresh master project)
> Once I'm reasonably happy with all the code / other developers need
> access, I check it in, run an integration build on the server (fully
> mavenised build using reactors) and then let them know the code is
> good to go.
> I'm also looking at using a continuous integration system to build
> snapshots in our repository whenever a piece of code is committed.
> This will hopefully show up integration errors sooner.
I've been planning on setting up similar to this, having a succesful
cruisecontrol build install into a shared corporate repo that all our
maven projects would look at. Sounds reasonable.
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Organizing the development process with maven
Posted by Ben Walding <be...@walding.com>.
Sure, no problems. I only downloaded it yesterday and I was going to
grab the source today and have a tinker.
Cheers,
Ben
Gilles Dodinet wrote:
> Ben,
> it would be nice if you could report the issues you encountered with
> mevenide (it only works with 3.0 - M5 not tested yet - i think the
> last release still has an unneeded dependency on ajdt).
>
> -- gd
>
>
> Ben Walding wrote:
>
>> Basically, for what we do, I have all inter-project dependencies set
>> to snapshot versions and then just have an external tool setup in
>> eclipse to build the active project with jar:install-snapshot. I
>> tried the mevenide plugin today, but it didn't work. It looks like it
>> will simplify running goals in much the same way as we do now.
>>
>> If this is too slow, you'll need to switch the project dependencies
>> in eclipse from being the jar in the repo to being the other project
>> in eclipse.
>> I try not to change my apis too frequently, but its only about a
>> 30second turn around time when I absolutely must get the latest code
>> / apis into a project. (select changed project, jar:install-snapshot,
>> wait, refresh master project)
>>
>> Once I'm reasonably happy with all the code / other developers need
>> access, I check it in, run an integration build on the server (fully
>> mavenised build using reactors) and then let them know the code is
>> good to go.
>>
>> I'm also looking at using a continuous integration system to build
>> snapshots in our repository whenever a piece of code is committed.
>> This will hopefully show up integration errors sooner.
>>
>>
>> Cheers,
>>
>> Ben
>>
>> Christian Goos wrote:
>>
>>> Hi,
>>>
>>> we am using Maven on a project with several subprojects.
>>> We use Maven, Eclipse, CVS.
>>> I implemented the recommended development process that
>>> is described in the Maven documentation.
>>> Although building and deploying with works fine, developers
>>> still have problems with the development process.
>>>
>>> Can anybody send me some advice how to use Maven in a
>>> project where the subprojects are a) under heavy development
>>> b) changes to one subproject have to be available to other projects
>>> as fast as possible
>>>
>>> I would be interested to know how you organize the development on
>>> your projects.
>>
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Organizing the development process with maven
Posted by Gilles Dodinet <rh...@wanadoo.fr>.
Ben,
it would be nice if you could report the issues you encountered with
mevenide (it only works with 3.0 - M5 not tested yet - i think the last
release still has an unneeded dependency on ajdt).
-- gd
Ben Walding wrote:
> Basically, for what we do, I have all inter-project dependencies set
> to snapshot versions and then just have an external tool setup in
> eclipse to build the active project with jar:install-snapshot. I
> tried the mevenide plugin today, but it didn't work. It looks like it
> will simplify running goals in much the same way as we do now.
>
> If this is too slow, you'll need to switch the project dependencies in
> eclipse from being the jar in the repo to being the other project in
> eclipse.
> I try not to change my apis too frequently, but its only about a
> 30second turn around time when I absolutely must get the latest code /
> apis into a project. (select changed project, jar:install-snapshot,
> wait, refresh master project)
>
> Once I'm reasonably happy with all the code / other developers need
> access, I check it in, run an integration build on the server (fully
> mavenised build using reactors) and then let them know the code is
> good to go.
>
> I'm also looking at using a continuous integration system to build
> snapshots in our repository whenever a piece of code is committed.
> This will hopefully show up integration errors sooner.
>
>
> Cheers,
>
> Ben
>
> Christian Goos wrote:
>
>> Hi,
>>
>> we am using Maven on a project with several subprojects.
>> We use Maven, Eclipse, CVS.
>> I implemented the recommended development process that
>> is described in the Maven documentation.
>> Although building and deploying with works fine, developers
>> still have problems with the development process.
>>
>> Can anybody send me some advice how to use Maven in a
>> project where the subprojects are a) under heavy development
>> b) changes to one subproject have to be available to other projects
>> as fast as possible
>>
>> I would be interested to know how you organize the development on
>> your projects.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Organizing the development process with maven
Posted by di...@multitask.com.au.
Ben Walding <be...@walding.com> wrote on 26/11/2003 01:34:10 AM:
[snip]
> I'm also looking at using a continuous integration system to build
> snapshots in our repository whenever a piece of code is committed. This
> will hopefully show up integration errors sooner.
We're currently using CruiseControl, and the maven cruisecontrol plugin to
do this.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Organizing the development process with maven
Posted by Ben Walding <be...@walding.com>.
Basically, for what we do, I have all inter-project dependencies set to
snapshot versions and then just have an external tool setup in eclipse
to build the active project with jar:install-snapshot. I tried the
mevenide plugin today, but it didn't work. It looks like it will
simplify running goals in much the same way as we do now.
If this is too slow, you'll need to switch the project dependencies in
eclipse from being the jar in the repo to being the other project in
eclipse.
I try not to change my apis too frequently, but its only about a
30second turn around time when I absolutely must get the latest code /
apis into a project. (select changed project, jar:install-snapshot,
wait, refresh master project)
Once I'm reasonably happy with all the code / other developers need
access, I check it in, run an integration build on the server (fully
mavenised build using reactors) and then let them know the code is good
to go.
I'm also looking at using a continuous integration system to build
snapshots in our repository whenever a piece of code is committed. This
will hopefully show up integration errors sooner.
Cheers,
Ben
Christian Goos wrote:
>Hi,
>
>we am using Maven on a project with several subprojects.
>We use Maven, Eclipse, CVS.
>I implemented the recommended development process that
>is described in the Maven documentation.
>Although building and deploying with works fine, developers
>still have problems with the development process.
>
>Can anybody send me some advice how to use Maven in a
>project where the subprojects are
>a) under heavy development
>b) changes to one subproject have to be available to other projects as fast as possible
>
>I would be interested to know how you organize the development on your projects.
>
>Thanks a lot for reading to the end and maybe helping me
>Christian
>
>______________________________________________________________________________
>WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
>nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Organizing the development process with maven
Posted by di...@multitask.com.au.
Christian,
we use SNAPSHOTs, the multiproject plugin and
multiproject:install-snapshot to handle these situations, if I'm reading
you correctly.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
"Vincent Massol" <vm...@pivolis.com> wrote on 25/11/2003 11:35:01 PM:
> Christian,
>
> I'm available for consulting work... :-)
>
> Seriously, it would be best if you asked a specific question as your
> question is very broad and vague. You say "developers have problems".
> What problems are you talking about?
>
> -Vincent
>
> > -----Original Message-----
> > From: Christian Goos [mailto:christian.goos@web.de]
> > Sent: 25 November 2003 09:50
> > To: users@maven.apache.org
> > Subject: Organizing the development process with maven
> >
> > Hi,
> >
> > we am using Maven on a project with several subprojects.
> > We use Maven, Eclipse, CVS.
> > I implemented the recommended development process that
> > is described in the Maven documentation.
> > Although building and deploying with works fine, developers
> > still have problems with the development process.
> >
> > Can anybody send me some advice how to use Maven in a
> > project where the subprojects are
> > a) under heavy development
> > b) changes to one subproject have to be available to other projects as
> > fast as possible
> >
> > I would be interested to know how you organize the development on your
> > projects.
> >
> > Thanks a lot for reading to the end and maybe helping me
> > Christian
> >
> >
> ________________________________________________________________________
> __
> > ____
> > WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
> > nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Organizing the development process with maven
Posted by Vincent Massol <vm...@pivolis.com>.
Christian,
I'm available for consulting work... :-)
Seriously, it would be best if you asked a specific question as your
question is very broad and vague. You say "developers have problems".
What problems are you talking about?
-Vincent
> -----Original Message-----
> From: Christian Goos [mailto:christian.goos@web.de]
> Sent: 25 November 2003 09:50
> To: users@maven.apache.org
> Subject: Organizing the development process with maven
>
> Hi,
>
> we am using Maven on a project with several subprojects.
> We use Maven, Eclipse, CVS.
> I implemented the recommended development process that
> is described in the Maven documentation.
> Although building and deploying with works fine, developers
> still have problems with the development process.
>
> Can anybody send me some advice how to use Maven in a
> project where the subprojects are
> a) under heavy development
> b) changes to one subproject have to be available to other projects as
> fast as possible
>
> I would be interested to know how you organize the development on your
> projects.
>
> Thanks a lot for reading to the end and maybe helping me
> Christian
>
>
________________________________________________________________________
__
> ____
> WEB.DE FreeMail wird 5 Jahre jung! Feiern Sie mit uns und
> nutzen Sie die neuen Funktionen http://f.web.de/features/?mc=021130
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org