Re: Maven/Subversion/Eclipse/Subclipse Configuration

2007-11-07 Thread Régis Décamps


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]



Maven/Subversion/Eclipse/Subclipse Configuration

2007-11-06 Thread Simon Taylor
Were configuring our first Maven project and wondering if we have the
right approach.

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.

Whats the right way to use Maven2, Subversion and Eclipse.

Thanks

Simon

 

Simon Taylor
Service Tools Solutions (STS) Engineer
Nortel
Email [EMAIL PROTECTED]
Office +44.1279 402291 (ESN 6 742 2291)
Mobile +44.7740.533743 (ESN 748 3743)





Re: Maven/Subversion/Eclipse/Subclipse Configuration

2007-11-06 Thread Dave Feltenberger
I agree with you, Vanja.  And if the developers on the project are
definitely using Eclipse, you can create a Maven Builder for Eclipse
that hooks into the Eclipse build lifecycle.  See the
additionalBuildCommands tag here:
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html.
 You'd then check in the Builder/External Launcher configuration file
to SVN, and when a developer checks the project out and runs mvn
eclipse:eclipse on the project, the .project file will reflect the new
builder.  Then you can build (or filter resources) on incremental
builds or full clean/builds in Eclipse without having to invoke Maven
directly.

On Nov 6, 2007 9:08 AM, Vanja Petreski [EMAIL PROTECTED] wrote:
 Check config file for the subversion. There you can find global-ignores
 option, where you can set filtering for target and other non-maven files
 (like IDE specific files).

 I am following the procedure:

 1) Create Maven project structure
 2) Import to the Subversion (with mentioned global-ignores)
 3) Now everybody can checkout
 4) Every developer now can choose IDE (for example mvn eclipse:eclipse)

 I don't use Eclipse plugins for Maven at all, because no one is good enough
 for me.

 I am using Subclipse as the SVN client, but import and checkout I am doing
 manually (using svn command).

 Regards,
 Vanja



 On Nov 6, 2007 2:13 PM, Simon Taylor [EMAIL PROTECTED] wrote:

  Were configuring our first Maven project and wondering if we have the
  right approach.
 
  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.
 
  Whats the right way to use Maven2, Subversion and Eclipse.
 
  Thanks
 
  Simon
 
 
 
  Simon Taylor
  Service Tools Solutions (STS) Engineer
  Nortel
  Email [EMAIL PROTECTED]
  Office +44.1279 402291 (ESN 6 742 2291)
  Mobile +44.7740.533743 (ESN 748 3743)
 
 
 
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]