My favorites | Sign in
Project Home Downloads Wiki Issues Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 14: Finish maven2 build
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ----
Closed:  May 2007


 
Reported by oliver.lamy@gmail.com, May 2, 2007
Hi,
Please find here a patch which provide two other pom to setup maven2 build.

IMHO, some directories must be moved according to the maven2 standard
layout
(http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html).
Then the lib directories and eclipse files must be removed (and ignored
with svn) as it's easy to setup eclipse files with mvn eclipse:clean
eclipse:eclipse.

Let me know to send a patch with this changes or provide to me an access to
the svn repo (I can apply this in a branch).

--
Oivier
May 2, 2007
#1 oliver.lamy@gmail.com
Attach the patch.
If trouble send a email to olamy@codehaus.org.
jmesa-14
41.8 KB   Download
May 3, 2007
#2 extremec...@gmail.com
I worked with Maven2 just enough to know what it can do. I like it, but I wish it had
support for projects that are flat and not force a project to use a hierarchical
structure.

I use Eclipse for all my development and I do not have a really good way to check in
that top level pom.xml file. I would really have to set up the projects to be
hierarchical and then with Eclipse check them out separately. Even then I would have
to check out the whole hierarchy just to work with the top level pom.xml from
Eclipse. That is my understanding of Maven2 with Eclipse. How do you work with this
in Eclipse? Do you use a different client tool to work with Subversion?

I really like having the pom.xml file for the different projects though as it gives
developers that like Maven2 a way to work with them more easily. Unless there is an
easy way to work with the pom's from Eclipse I would rather keep the pom.xml files
separate.

If we can figure out how to make the tests run I would be tempted to make Maven2 a
first class citizen and not check in the lib folder. I do like the project structure
though and it would be tough to change the project to conform to a build tool.

May 3, 2007
#3 oliver.lamy@gmail.com
The only content which can be used with eclipse's svn plugin is the root pom.
But using eclipse is not very important in order to manage only an xml file.
Perso, I use svn cli (I have had some trouble with eclipse plugins for svn) and add
manually project to eclipse.
I only use eclipse for java content.
May 3, 2007
#4 extremec...@gmail.com
I appreciate your help!

I understand now. I am pretty tools orientated so I would want to be able to work
right from Eclipse easily. My plan is to make JMesa easy for people to check out and
get up and running as quickly as possible. By checking in the jar files and having
the pom.xml file right in the project it makes it that much easier for any developer
to get JMesa up and running pretty quickly. I love having the pom.xml file because
then people that want to use Maven can do that as well. 

Plus I am not that concerned about the web site. It is just a place to run the
examples. If your ok with that and would like to finish making up the jmesaWeb.xml to
just be for what the web project needs then I would include that as well. If not then
I will get to that at some point.

May 3, 2007
#5 oliver.lamy@gmail.com
Ok.
Because jmesaWeb is just a project to provide samples, we can remove the parent pom
and  add poms only for each projects.
The most important is the one in the api.
Concerning the jars in the svn repo, I don't really understand because it's very easy
to just do in a cli the simple : mvn eclipse:eclipse.
But as you want :-)

May 22, 2007
#6 extremec...@gmail.com
We have the pom for the jmesa project and all the tests pass now.
Status: Fixed

Powered by Google Project Hosting