On 25 Feb 2009, at 14:40, Steve Cohen wrote:
I am thinking about this very carefully, and the option of not using
Maven at all is still in play. So is the option of using Maven ONLY
to grab third-party dependencies into a local repository.
I did this the other day, using the
Based on this discussion, I have a question here regarding uncommon
requirement.
Once my build is finished I need to copy all the generated artifacts as well
as portal components and some shell scripts/batch files from resources.
Copying is done to custom directory which acts as TestBed of the
The other thing is, and this may be an urban legend, that I think it's
better to not have the sub modules nested in the parent module's
directory. Make them parallel; siblings. This means using ../ with
relativePath when referring to the parent's pom:
This is due to the old eclipses not
Thanks, that's very good to know.
Brian E. Fox wrote:
The other thing is, and this may be an urban legend, that I think it's
better to not have the sub modules nested in the parent module's
directory. Make them parallel; siblings. This means using ../ with
relativePath when referring to the
Dependency:copy and/or dependency:copy-dependencies
-Original Message-
From: Ketan Khairnar [mailto:ketan.khair...@gmail.com]
Sent: Thursday, February 26, 2009 5:42 AM
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
Based on this discussion, I have a question
Sorry to get late into this conversation, but I am wondering if there
might be a way to do a gentler migration path.
For example, let's say you modify the current directory structure
bit-by-bit into the standard Maven directory structure, then once you
have setup in a way Maven likes it, convert
Thanks, Rusty.
I am thinking about this very carefully, and the option of not using
Maven at all is still in play. So is the option of using Maven ONLY to
grab third-party dependencies into a local repository. Another option
is to use Eclipse's build functionality headlessly, from the
I'm pretty sure you'll be able to continue doing all of the usual eclipse stuff
everyone is used to doing. I also use WTP and have a tomcat server running
under/in eclipse that I fire up to test my jsps and whatnot.
What bothers me about the m2eclipse plugin is that it's not obvious, to me at
Also remember that in eclipse you'll need to right click on the project and
select Properties; there are some important maven things in there.
Steve Cohen wrote:
Thanks, Rusty.
I am thinking about this very carefully, and the option of not using
Maven at all is still in play. So is the
Hmm, I don't usually click the build button. I typically live with
build automatically turned on. I live with the fact that this will
bomb out the WTP Tomcat if I'm not careful. But that's another can of
worms no? If we're not sure what build does, it's even scarier for
automatic build.
, and desperatly revert trunk.
You also want to tag a stable last version of your Ant built project.
-Original Message-
From: Steve Cohen [mailto:stevec...@comcast.net]
Sent: 24. februar 2009 01:53
To: Maven Users List
Subject: Mavenizing Existing Project Part Deux
OK, after extensive discussion
OK. Since we're skipping the ant phase on this project, never having
used it here, I'll go with your suggestions in #2. I'll start by making
a branch, using the least dependent project (which depends on no others)
for my first guinea pig. (I DO follow the trunk-branch-tag pattern).
However,
-Original Message-
From: Steve Cohen [mailto:sco...@javactivity.org]
Sent: 24. februar 2009 14:34
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
OK. Since we're skipping the ant phase on this project, never having
used it here, I'll go with your suggestions
...@javactivity.org]
Sent: Tuesday, February 24, 2009 8:34 AM
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
OK. Since we're skipping the ant phase on this project, never
having used it here, I'll go with your suggestions in #2.
I'll start by making a branch, using
+1
-Original Message-
From: Todd Thiessen [mailto:thies...@nortel.com]
Sent: 24. februar 2009 15:16
To: Maven Users List
Subject: RE: Mavenizing Existing Project Part Deux
Wow. There are 101 ways (perhaps 11) to do what you want. No one
specific way is best and there is no wizard
the trunk.
Mavenization comes in and after step 4.
Jon Georg Berentsen wrote:
-Original Message-
From: Steve Cohen [mailto:sco...@javactivity.org]
Sent: 24. februar 2009 14:34
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
OK. Since we're skipping the ant phase
what you never had.
And above all, enjoy ;-).
Yup.
---
Todd Thiessen
-Original Message-
From: Steve Cohen [mailto:sco...@javactivity.org]
Sent: Tuesday, February 24, 2009 8:34 AM
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
OK. Since we're skipping
4. Understand how multi-module projects are structured and how they
work. I made a dummy project for this before I even
considered porting
over the actual production code.
Yup, this is where I want to wind up. I am supposing that the
right thing is to get the individual projects
Todd Thiessen wrote:
4. Understand how multi-module projects are structured and how they
work. I made a dummy project for this before I even
considered porting
over the actual production code.
Yup, this is where I want to wind up. I am supposing that the
right thing is
you need:
- a top folder (parent pom)
- sub-folders with the modules (each refering the top pom and the
other modules dependencies - if any)
then in the top folder you type:
mvn install eclipse:eclipse
it will do the job
On Tue, Feb 24, 2009 at 4:29 PM, Steve Cohen sco...@javactivity.org
Do make your first Maven project a conversion. You will likely fail or
be extremely unhappy. I have seen this a hundred times now and trying
to wedge Maven into what you currently have is categorically not a
good idea.
Find a new, preferably small, project where you can try out Maven and
Wow. That's different advice from what others are saying, BUT, you're
the maven so I do appreciate your warning and take it seriously!
Was there a missing not in your first sentence? It seems to make more
sense that way.
I am prepared to fail the first few times, start with the simplest
?
Project size/complexity and skills matter?
Jon
-Original Message-
From: Jason van Zyl [mailto:jvan...@sonatype.com]
Sent: 24. februar 2009 16:32
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
Do make your first Maven project a conversion. You will likely fail
On 24-Feb-09, at 8:12 AM, Steve Cohen wrote:
Wow. That's different advice from what others are saying, BUT,
you're the maven so I do appreciate your warning and take it
seriously!
Was there a missing not in your first sentence? It seems to make
more sense that way.
Yes, a typo. Try
-Original Message-
From: Jason van Zyl [mailto:jvan...@sonatype.com]
Sent: 24. februar 2009 16:32
To: Maven Users List
Subject: Re: Mavenizing Existing Project Part Deux
Do make your first Maven project a conversion. You will likely fail or
be extremely unhappy. I have seen this a hundred times now
The one big concern I have is your plan of starting with eclipse and the
m2eclipse plugin. It's not that I'm old school and prefer the command line but
I find that the m2eclipse plugin does a lot of automagic stuff and you may not
realize when things are changing under you because of what the
OK, after extensive discussion in earlier thread about the best way to
go about Mavenizing Existing Project(s) in my, shall we say, unusual
environment (see that thread for details, don't want to recapitulate
them here) I have decided to try to move forward.
First I have to learn this tool.
27 matches
Mail list logo
