Re: Maven/Subversion/Eclipse/Subclipse Configuration
Simon Taylor-2 wrote: Were using Maven2, Subversion accessible via WebDAV, Eclipse with both Subclipse and Maven2Eclipse plugin. We created a new Maven2 project in Eclipse. We have an existing project structure that we want to convert to Maven 2 and check in to the repository so we can then check it out and work on it in Eclipse. In eclipse it seems you can only check out from the repository As a new project - if we do this then we don't get the Maven2 structure. One alternative is to create the Maven2 project structure import the src code from the filesystem and then commit the whole project to Subversion - but ths also commits the target dir and all the compiled classes which to my mind shouldn't live in the repository. Yes, I like the second approach, you simply unselect target and bin not to commit them, and you add the svn:ignore property on it. -- Régis -- View this message in context: http://www.nabble.com/Maven-Subversion-Eclipse-Subclipse-Configuration-tf4757978s177.html#a13623976 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 settings.xml
On 3/1/07, sarancse [EMAIL PROTECTED] wrote: Hi I am looking for a sample settings.xml file. Could anyone upload it to me? It will be very useful for Maven2 beginners. Hi, I also find uneasy to configure the settings.xml file. I have worked a little on a GUI to configure Maven2. I would be happy that you try the alpha-version and give me feedback. http://code.google.com/p/m2settings/ -- Régis http://regis.decamps.info/
Re: Splitting APT in multiple files
On 2/20/07, Dennis Lundberg [EMAIL PROTECTED] wrote: Roland Asmann skrev: Hi, I want to write an APT document, split over several files. Yes, I'd like to do that as well. Please see this link for more info on this subject: http://maven.apache.org/doxia/format.html Thanks for the link. I already read this doc, though. And it reads A longer document may be contained in a ordered list of text files. But I have no clue how to do that... A small example would be nice indeed. -- Régis http://regis.decamps.info/
Re: Assembly plugin in a multimodile project
On 2/14/07, Aliaksandr Radzivanovich [EMAIL PROTECTED] wrote: Suppose I have two modules in my project: module1 and module2, and the later depends on the former. When I execute command 'mvn assembly:assembly', maven compiles first module successfully. But when it proceeds to the second module, maven complaints with error that the module1 dependency cannot be resolved. This is because assembly plugin does not install module artifacts to the local repository. Sure, I can execute command 'mvn install assembly:assembly', but this one takes too much time because it compiles the whole project and executes unit tests twice: first when installing, then when assembling. I would prefer if maven would compile, test, package and assemble the whole project in one round. Is this possible? I imagine you can create a 3rd project (project3), which depends on project1 and project2, and has the assembly definition. As such, your assemblage process consists in: project1 - mvn install project2 - mvn install project3 - mvn assembly:assembly Can this work for you? -- Régis http://regis.decamps.info/
Re: [m2] Maven vs source control
On 2/14/07, lightbulb432 [EMAIL PROTECTED] wrote:
I have a question about how to combine the structure of source/resource
files
as required by Maven and as suggested by version control. Of course you're
familiar with the Maven structure, and the structure of the version
control
is often PROJECT/{trunk,branches,tags}
How would an example of the hierarchy of source folders and files
therefore
look in the version control repository for source? Would the first level
in
the hierarchy (topmost level) be PROJECT, or would it be
{trunk,branches,tags} further subdivided by project?
I suggest project
You check out $SVNROOT/project1/trunk as project1and your IDE should
handle it normally (it then knows how to tag, etc)
You use in there a standard layout for a maven project.
--
Régis
http://regis.decamps.info/
