RE: MAVEN 2.0 and SCM-SVN
Gotcha thanks. Maybe I will write this up and post it for others to see since it side tracked me for a few days -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 1:10 PM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN ah, what you want is a CI server, checkout Continuum, Cruisecontrol, hudson, etc. -D On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I was planning on using the subversion hooks to trigger maven to > checkout > (refresh) its copy of src before building. I realize I can do this in > a shell script but thought Maven would do it naturally, it does just > to the wrong dir > > I recognize that it is standard for Maven to checkout to the > target/checkout dir but I guess I am unclear why this dir and not > under src? Would this not mean we have 2 copies of the source under > this circumstance? > > I have not tried to set the checkout dir in the SCM config section > would this suffice for me? > > Thanks for the link I own a few of those books and have been through > most of the English articles > > Phill > > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 11, 2007 11:53 AM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > I am very confused ehy you want to checkout source to src/main? > > Isn't it already there? > > btw, you have not explained about your usecase why you want to use > scm:checkout rather than direct svn checkout. With this, I would like > to perfer you back to maven docs. > > http://maven.apache.org/articles.html > > -D > > > On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > Okay I'll recheck my structure but how does the source code get from > > target/checkout to src/main ? > > > > -Original Message- > > From: Dan Tran [mailto:[EMAIL PROTECTED] > > Sent: March 11, 2007 1:51 AM > > To: Maven Users List > > Subject: Re: MAVEN 2.0 and SCM-SVN > > > > if you configure maven correctly then: > > > > 1. use svn to check out the source tree > > > > 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your > > eclipse workspace and projects > > > > 3. Use jboss-maven-plugin or maven cargo to deploy > > > > -D > > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > > > I think you are right. Here is the UC I develop on an windows box > > > and use eclipse/spring and JUnit to test locally. > > > Source stored in SVN on remote Linux box I want to use maven to > > > compile and test on a remote Linux box. To do this I want maven to > > > check out code on remote Linux box If tests all work then deploy > > > to a jBoss on same box > > > > > > All works except this checkout or in general the getting source > > > code into correct directory > > > > > > I am now looking at continuum as it looks like that is its role in > > > this process. > > > Of course not sure yet as I am still setting it up (conflicts on > > > port 8080 for the jBoss - nothing is easy - lol) > > > > > > Let me know your thoughts and thanks for this help > > > > > > Sincerely, > > >Phill > > > > > > > > > > > > > > > -Original Message- > > > From: Dan Tran [mailto:[EMAIL PROTECTED] > > > Sent: March 11, 2007 1:01 AM > > > To: Maven Users List > > > Subject: Re: MAVEN 2.0 and SCM-SVN > > > > > > there are JIRA filed against odd response. But they seem not > > > blocking issues > > > > > > I think you are trying to use maven scm in a odd way :-) > > > > > > What is your use case? why do you want to scm:update after > > scm:checkout?: > > > > > > -D > > > > > > > > > > > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > > > > > I removed the following section from the POM listed below > > > > > > > > > > > > > > > >validate > > > > > > > > > > > >scm:checkout > > > > > > > >user > > > >password > > > > > > > > > > > > > &
Re: MAVEN 2.0 and SCM-SVN
ah, what you want is a CI server, checkout Continuum, Cruisecontrol, hudson, etc. -D On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: I was planning on using the subversion hooks to trigger maven to checkout (refresh) its copy of src before building. I realize I can do this in a shell script but thought Maven would do it naturally, it does just to the wrong dir I recognize that it is standard for Maven to checkout to the target/checkout dir but I guess I am unclear why this dir and not under src? Would this not mean we have 2 copies of the source under this circumstance? I have not tried to set the checkout dir in the SCM config section would this suffice for me? Thanks for the link I own a few of those books and have been through most of the English articles Phill -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 11:53 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN I am very confused ehy you want to checkout source to src/main? Isn't it already there? btw, you have not explained about your usecase why you want to use scm:checkout rather than direct svn checkout. With this, I would like to perfer you back to maven docs. http://maven.apache.org/articles.html -D On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > Okay I'll recheck my structure but how does the source code get from > target/checkout to src/main ? > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 11, 2007 1:51 AM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > if you configure maven correctly then: > > 1. use svn to check out the source tree > > 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your > eclipse workspace and projects > > 3. Use jboss-maven-plugin or maven cargo to deploy > > -D > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > I think you are right. Here is the UC I develop on an windows box > > and use eclipse/spring and JUnit to test locally. > > Source stored in SVN on remote Linux box I want to use maven to > > compile and test on a remote Linux box. To do this I want maven to > > check out code on remote Linux box If tests all work then deploy to > > a jBoss on same box > > > > All works except this checkout or in general the getting source code > > into correct directory > > > > I am now looking at continuum as it looks like that is its role in > > this process. > > Of course not sure yet as I am still setting it up (conflicts on > > port 8080 for the jBoss - nothing is easy - lol) > > > > Let me know your thoughts and thanks for this help > > > > Sincerely, > >Phill > > > > > > > > > > -Original Message- > > From: Dan Tran [mailto:[EMAIL PROTECTED] > > Sent: March 11, 2007 1:01 AM > > To: Maven Users List > > Subject: Re: MAVEN 2.0 and SCM-SVN > > > > there are JIRA filed against odd response. But they seem not > > blocking issues > > > > I think you are trying to use maven scm in a odd way :-) > > > > What is your use case? why do you want to scm:update after > scm:checkout?: > > > > -D > > > > > > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > > > I removed the following section from the POM listed below > > > > > > > > > > > >validate > > > > > > > > >scm:checkout > > > > > >user > > >password > > > > > > > > > > > > > > > The SCM section now simply looks like this: > > > org.apache.maven.plugins > > > maven-scm-plugin > > > 1.0-beta-4 > > > > > > Keeping in mind this project is in a standard maven layout. > > > > > > When I issue a mvn scm:checkout > > > > > > [INFO] Scanning for projects... > > > [INFO] Searching repository for plugin with prefix: 'scm'. > > > [INFO] > > > > > > -- > > > -- > > > -- > > > -- [INFO] Building Maven BidSpec Server Archetype > > > [INFO]task-segment: [scm:checkout] (aggregator-style) > > > [INFO] > > > > > > -- > > >
RE: MAVEN 2.0 and SCM-SVN
I was planning on using the subversion hooks to trigger maven to checkout (refresh) its copy of src before building. I realize I can do this in a shell script but thought Maven would do it naturally, it does just to the wrong dir I recognize that it is standard for Maven to checkout to the target/checkout dir but I guess I am unclear why this dir and not under src? Would this not mean we have 2 copies of the source under this circumstance? I have not tried to set the checkout dir in the SCM config section would this suffice for me? Thanks for the link I own a few of those books and have been through most of the English articles Phill -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 11:53 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN I am very confused ehy you want to checkout source to src/main? Isn't it already there? btw, you have not explained about your usecase why you want to use scm:checkout rather than direct svn checkout. With this, I would like to perfer you back to maven docs. http://maven.apache.org/articles.html -D On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > Okay I'll recheck my structure but how does the source code get from > target/checkout to src/main ? > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 11, 2007 1:51 AM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > if you configure maven correctly then: > > 1. use svn to check out the source tree > > 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your > eclipse workspace and projects > > 3. Use jboss-maven-plugin or maven cargo to deploy > > -D > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > I think you are right. Here is the UC I develop on an windows box > > and use eclipse/spring and JUnit to test locally. > > Source stored in SVN on remote Linux box I want to use maven to > > compile and test on a remote Linux box. To do this I want maven to > > check out code on remote Linux box If tests all work then deploy to > > a jBoss on same box > > > > All works except this checkout or in general the getting source code > > into correct directory > > > > I am now looking at continuum as it looks like that is its role in > > this process. > > Of course not sure yet as I am still setting it up (conflicts on > > port 8080 for the jBoss - nothing is easy - lol) > > > > Let me know your thoughts and thanks for this help > > > > Sincerely, > >Phill > > > > > > > > > > -Original Message- > > From: Dan Tran [mailto:[EMAIL PROTECTED] > > Sent: March 11, 2007 1:01 AM > > To: Maven Users List > > Subject: Re: MAVEN 2.0 and SCM-SVN > > > > there are JIRA filed against odd response. But they seem not > > blocking issues > > > > I think you are trying to use maven scm in a odd way :-) > > > > What is your use case? why do you want to scm:update after > scm:checkout?: > > > > -D > > > > > > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > > > I removed the following section from the POM listed below > > > > > > > > > > > >validate > > > > > > > > >scm:checkout > > > > > >user > > >password > > > > > > > > > > > > > > > The SCM section now simply looks like this: > > > org.apache.maven.plugins > > > maven-scm-plugin > > > 1.0-beta-4 > > > > > > Keeping in mind this project is in a standard maven layout. > > > > > > When I issue a mvn scm:checkout > > > > > > [INFO] Scanning for projects... > > > [INFO] Searching repository for plugin with prefix: 'scm'. > > > [INFO] > > > > > > -- > > > -- > > > -- > > > -- [INFO] Building Maven BidSpec Server Archetype > > > [INFO]task-segment: [scm:checkout] (aggregator-style) > > > [INFO] > > > > > > -- > > > -- > > > -- > > >
Re: MAVEN 2.0 and SCM-SVN
I am very confused ehy you want to checkout source to src/main? Isn't it already there? btw, you have not explained about your usecase why you want to use scm:checkout rather than direct svn checkout. With this, I would like to perfer you back to maven docs. http://maven.apache.org/articles.html -D On 3/11/07, Phill Moran <[EMAIL PROTECTED]> wrote: Okay I'll recheck my structure but how does the source code get from target/checkout to src/main ? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 1:51 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN if you configure maven correctly then: 1. use svn to check out the source tree 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your eclipse workspace and projects 3. Use jboss-maven-plugin or maven cargo to deploy -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I think you are right. Here is the UC > I develop on an windows box and use eclipse/spring and JUnit to test > locally. > Source stored in SVN on remote Linux box I want to use maven to > compile and test on a remote Linux box. To do this I want maven to > check out code on remote Linux box If tests all work then deploy to a > jBoss on same box > > All works except this checkout or in general the getting source code > into correct directory > > I am now looking at continuum as it looks like that is its role in > this process. > Of course not sure yet as I am still setting it up (conflicts on port > 8080 for the jBoss - nothing is easy - lol) > > Let me know your thoughts and thanks for this help > > Sincerely, >Phill > > > > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 11, 2007 1:01 AM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > there are JIRA filed against odd response. But they seem not blocking > issues > > I think you are trying to use maven scm in a odd way :-) > > What is your use case? why do you want to scm:update after scm:checkout?: > > -D > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > I removed the following section from the POM listed below > > > > > > > >validate > > > > > >scm:checkout > > > >user > >password > > > > > > > > > > The SCM section now simply looks like this: > > org.apache.maven.plugins > > maven-scm-plugin > > 1.0-beta-4 > > > > Keeping in mind this project is in a standard maven layout. > > > > When I issue a mvn scm:checkout > > > > [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'scm'. > > [INFO] > > > > > > -- > > -- [INFO] Building Maven BidSpec Server Archetype > > [INFO]task-segment: [scm:checkout] (aggregator-style) > > [INFO] > > > > > > -- > > -- > > [INFO] [scm:checkout] > > [INFO] Removing /BidSpec/applications/emall/target/checkout > > [INFO] Executing: svn --username user --non-interactive checkout > > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > > Working directory: /BidSpec/applications/emall/target > > [INFO] Unknown file status: ' '. > > [INFO] > > > > -- > > -- > > [INFO] BUILD SUCCESSFUL > > [INFO] > > > > -- > > -- > > [INFO] Total time: 19 seconds > > [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: > > 4M/9M [INFO] > > > > -- > > -- I get that odd "Unknown file status: ' '." line not sure if this > > is significant > > > > Issueing a mvn scm:update esults in > > [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'scm'. > > [INFO] > > > > > > -- > > -- [INFO] Building Maven BidSpec Server Archetype > > [INFO]task-segment: [scm:update] (aggregator-style) > &g
RE: MAVEN 2.0 and SCM-SVN
Okay I'll recheck my structure but how does the source code get from target/checkout to src/main ? -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 1:51 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN if you configure maven correctly then: 1. use svn to check out the source tree 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your eclipse workspace and projects 3. Use jboss-maven-plugin or maven cargo to deploy -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I think you are right. Here is the UC > I develop on an windows box and use eclipse/spring and JUnit to test > locally. > Source stored in SVN on remote Linux box I want to use maven to > compile and test on a remote Linux box. To do this I want maven to > check out code on remote Linux box If tests all work then deploy to a > jBoss on same box > > All works except this checkout or in general the getting source code > into correct directory > > I am now looking at continuum as it looks like that is its role in > this process. > Of course not sure yet as I am still setting it up (conflicts on port > 8080 for the jBoss - nothing is easy - lol) > > Let me know your thoughts and thanks for this help > > Sincerely, >Phill > > > > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 11, 2007 1:01 AM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > there are JIRA filed against odd response. But they seem not blocking > issues > > I think you are trying to use maven scm in a odd way :-) > > What is your use case? why do you want to scm:update after scm:checkout?: > > -D > > > > > On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > > > I removed the following section from the POM listed below > > > > > > > >validate > > > > > >scm:checkout > > > >user > >password > > > > > > > > > > The SCM section now simply looks like this: > > org.apache.maven.plugins > > maven-scm-plugin > > 1.0-beta-4 > > > > Keeping in mind this project is in a standard maven layout. > > > > When I issue a mvn scm:checkout > > > > [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'scm'. > > [INFO] > > > > > > -- > > -- [INFO] Building Maven BidSpec Server Archetype > > [INFO]task-segment: [scm:checkout] (aggregator-style) > > [INFO] > > > > > > -- > > -- > > [INFO] [scm:checkout] > > [INFO] Removing /BidSpec/applications/emall/target/checkout > > [INFO] Executing: svn --username user --non-interactive checkout > > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > > Working directory: /BidSpec/applications/emall/target > > [INFO] Unknown file status: ' '. > > [INFO] > > > > -- > > -- > > [INFO] BUILD SUCCESSFUL > > [INFO] > > > > -- > > -- > > [INFO] Total time: 19 seconds > > [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: > > 4M/9M [INFO] > > > > -- > > -- I get that odd "Unknown file status: ' '." line not sure if this > > is significant > > > > Issueing a mvn scm:update esults in > > [INFO] Scanning for projects... > > [INFO] Searching repository for plugin with prefix: 'scm'. > > [INFO] > > > > > > -- > > -- [INFO] Building Maven BidSpec Server Archetype > > [INFO]task-segment: [scm:update] (aggregator-style) > > [INFO] > > > > > > -- > > -- > > [INFO] [scm:update] > > [INFO] Executing: svn --username user --non-interactive update > > [INFO] Working directory: /BidSpec/applications/emall [INFO] Unknown > > file > > status: 'S'
Re: MAVEN 2.0 and SCM-SVN
if you configure maven correctly then: 1. use svn to check out the source tree 2. use eplipse:add-maven-repo adn eclipse:eclipse to setup your eclipse workspace and projects 3. Use jboss-maven-plugin or maven cargo to deploy -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: I think you are right. Here is the UC I develop on an windows box and use eclipse/spring and JUnit to test locally. Source stored in SVN on remote Linux box I want to use maven to compile and test on a remote Linux box. To do this I want maven to check out code on remote Linux box If tests all work then deploy to a jBoss on same box All works except this checkout or in general the getting source code into correct directory I am now looking at continuum as it looks like that is its role in this process. Of course not sure yet as I am still setting it up (conflicts on port 8080 for the jBoss - nothing is easy - lol) Let me know your thoughts and thanks for this help Sincerely, Phill -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 1:01 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN there are JIRA filed against odd response. But they seem not blocking issues I think you are trying to use maven scm in a odd way :-) What is your use case? why do you want to scm:update after scm:checkout?: -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I removed the following section from the POM listed below > > > >validate > > >scm:checkout > >user >password > > > > > The SCM section now simply looks like this: > org.apache.maven.plugins > maven-scm-plugin > 1.0-beta-4 > > Keeping in mind this project is in a standard maven layout. > > When I issue a mvn scm:checkout > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:checkout] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:checkout] > [INFO] Removing /BidSpec/applications/emall/target/checkout > [INFO] Executing: svn --username user --non-interactive checkout > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > Working directory: /BidSpec/applications/emall/target > [INFO] Unknown file status: ' '. > [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 19 seconds > [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: > 4M/9M [INFO] > -- > -- I get that odd "Unknown file status: ' '." line not sure if this is > significant > > Issueing a mvn scm:update esults in > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:update] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:update] > [INFO] Executing: svn --username user --non-interactive update [INFO] > Working directory: /BidSpec/applications/emall [INFO] Unknown file > status: 'S' in line Skipped '.'. > [INFO] Storing revision in 'scm.revision' project property. > [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 14 seconds > [INFO] Finished at: Sat Mar 10 23:14:33 EST 2007 [INFO] Final Memory: > 4M/9M [INFO] > -- > -- > > Another odd file status response > > The code is checked out but issuing a mvn install after reports no > sources to compile. So my guess is I have not configured or told mvn > to move the source to the src dir > > I am still preplexed. > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 10, 2007 12:45 PM &g
RE: MAVEN 2.0 and SCM-SVN
I think you are right. Here is the UC I develop on an windows box and use eclipse/spring and JUnit to test locally. Source stored in SVN on remote Linux box I want to use maven to compile and test on a remote Linux box. To do this I want maven to check out code on remote Linux box If tests all work then deploy to a jBoss on same box All works except this checkout or in general the getting source code into correct directory I am now looking at continuum as it looks like that is its role in this process. Of course not sure yet as I am still setting it up (conflicts on port 8080 for the jBoss - nothing is easy - lol) Let me know your thoughts and thanks for this help Sincerely, Phill -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 11, 2007 1:01 AM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN there are JIRA filed against odd response. But they seem not blocking issues I think you are trying to use maven scm in a odd way :-) What is your use case? why do you want to scm:update after scm:checkout?: -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I removed the following section from the POM listed below > > > >validate > > >scm:checkout > >user >password > > > > > The SCM section now simply looks like this: > org.apache.maven.plugins > maven-scm-plugin > 1.0-beta-4 > > Keeping in mind this project is in a standard maven layout. > > When I issue a mvn scm:checkout > > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:checkout] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:checkout] > [INFO] Removing /BidSpec/applications/emall/target/checkout > [INFO] Executing: svn --username user --non-interactive checkout > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > Working directory: /BidSpec/applications/emall/target > [INFO] Unknown file status: ' '. > [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 19 seconds > [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: > 4M/9M [INFO] > -- > -- I get that odd "Unknown file status: ' '." line not sure if this is > significant > > Issueing a mvn scm:update esults in > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:update] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:update] > [INFO] Executing: svn --username user --non-interactive update [INFO] > Working directory: /BidSpec/applications/emall [INFO] Unknown file > status: 'S' in line Skipped '.'. > [INFO] Storing revision in 'scm.revision' project property. > [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 14 seconds > [INFO] Finished at: Sat Mar 10 23:14:33 EST 2007 [INFO] Final Memory: > 4M/9M [INFO] > -- > -- > > Another odd file status response > > The code is checked out but issuing a mvn install after reports no > sources to compile. So my guess is I have not configured or told mvn > to move the source to the src dir > > I am still preplexed. > > -Original Message- > From: Dan Tran [mailto:[EMAIL PROTECTED] > Sent: March 10, 2007 12:45 PM > To: Maven Users List > Subject: Re: MAVEN 2.0 and SCM-SVN > > why do you need to do scm:checkout at validate phase? is n't source > checkedout by scm:bootstrap already validated? > > > > take it out and try again > > -D > > > On 3/9/07, Phi
Re: MAVEN 2.0 and SCM-SVN
there are JIRA filed against odd response. But they seem not blocking issues I think you are trying to use maven scm in a odd way :-) What is your use case? why do you want to scm:update after scm:checkout?: -D On 3/10/07, Phill Moran <[EMAIL PROTECTED]> wrote: I removed the following section from the POM listed below validate scm:checkout user password The SCM section now simply looks like this: org.apache.maven.plugins maven-scm-plugin 1.0-beta-4 Keeping in mind this project is in a standard maven layout. When I issue a mvn scm:checkout [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven BidSpec Server Archetype [INFO]task-segment: [scm:checkout] (aggregator-style) [INFO] [INFO] [scm:checkout] [INFO] Removing /BidSpec/applications/emall/target/checkout [INFO] Executing: svn --username user --non-interactive checkout https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] Working directory: /BidSpec/applications/emall/target [INFO] Unknown file status: ' '. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: 4M/9M [INFO] I get that odd "Unknown file status: ' '." line not sure if this is significant Issueing a mvn scm:update esults in [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven BidSpec Server Archetype [INFO]task-segment: [scm:update] (aggregator-style) [INFO] [INFO] [scm:update] [INFO] Executing: svn --username user --non-interactive update [INFO] Working directory: /BidSpec/applications/emall [INFO] Unknown file status: 'S' in line Skipped '.'. [INFO] Storing revision in 'scm.revision' project property. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 14 seconds [INFO] Finished at: Sat Mar 10 23:14:33 EST 2007 [INFO] Final Memory: 4M/9M [INFO] Another odd file status response The code is checked out but issuing a mvn install after reports no sources to compile. So my guess is I have not configured or told mvn to move the source to the src dir I am still preplexed. -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 10, 2007 12:45 PM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN why do you need to do scm:checkout at validate phase? is n't source checkedout by scm:bootstrap already validated? take it out and try again -D On 3/9/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I am clearly missing something. > I get an error on mvn scm:bootstrap (although the code is there) > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:bootstrap] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:bootstrap] > [INFO] Removing /BidSpec/applications/emall/target/checkout > [INFO] Executing: svn --username pmoran --non-interactive checkout > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > Working directory: /BidSpec/applications/emall/target > [INFO] Unknown file status: ' '. > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > -- > -- > [INFO] Can't run goal null > Embedded error: Error while executing process. > java.io.IOException: mvn: not found > [INFO] > -- > -- [INFO] For more information, run Maven
RE: MAVEN 2.0 and SCM-SVN
I removed the following section from the POM listed below validate scm:checkout user password The SCM section now simply looks like this: org.apache.maven.plugins maven-scm-plugin 1.0-beta-4 Keeping in mind this project is in a standard maven layout. When I issue a mvn scm:checkout [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven BidSpec Server Archetype [INFO]task-segment: [scm:checkout] (aggregator-style) [INFO] [INFO] [scm:checkout] [INFO] Removing /BidSpec/applications/emall/target/checkout [INFO] Executing: svn --username user --non-interactive checkout https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] Working directory: /BidSpec/applications/emall/target [INFO] Unknown file status: ' '. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 19 seconds [INFO] Finished at: Sat Mar 10 23:12:57 EST 2007 [INFO] Final Memory: 4M/9M [INFO] I get that odd "Unknown file status: ' '." line not sure if this is significant Issueing a mvn scm:update esults in [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'scm'. [INFO] [INFO] Building Maven BidSpec Server Archetype [INFO]task-segment: [scm:update] (aggregator-style) [INFO] [INFO] [scm:update] [INFO] Executing: svn --username user --non-interactive update [INFO] Working directory: /BidSpec/applications/emall [INFO] Unknown file status: 'S' in line Skipped '.'. [INFO] Storing revision in 'scm.revision' project property. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 14 seconds [INFO] Finished at: Sat Mar 10 23:14:33 EST 2007 [INFO] Final Memory: 4M/9M [INFO] Another odd file status response The code is checked out but issuing a mvn install after reports no sources to compile. So my guess is I have not configured or told mvn to move the source to the src dir I am still preplexed. -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: March 10, 2007 12:45 PM To: Maven Users List Subject: Re: MAVEN 2.0 and SCM-SVN why do you need to do scm:checkout at validate phase? is n't source checkedout by scm:bootstrap already validated? take it out and try again -D On 3/9/07, Phill Moran <[EMAIL PROTECTED]> wrote: > > I am clearly missing something. > I get an error on mvn scm:bootstrap (although the code is there) > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > -- > -- [INFO] Building Maven BidSpec Server Archetype > [INFO]task-segment: [scm:bootstrap] (aggregator-style) > [INFO] > > -- > -- > [INFO] [scm:bootstrap] > [INFO] Removing /BidSpec/applications/emall/target/checkout > [INFO] Executing: svn --username pmoran --non-interactive checkout > https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout [INFO] > Working directory: /BidSpec/applications/emall/target > [INFO] Unknown file status: ' '. > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > -- > -- > [INFO] Can't run goal null > Embedded error: Error while executing process. > java.io.IOException: mvn: not found > [INFO] > -- > -- [INFO] For more information, run Maven with the -e switch [INFO] > -- > -- > [INFO] Total time: 19 seconds > [INFO] Finished at: Sat Mar 10 01:17:17 EST 2007 [INFO] Final Memory: > 4M/9M [INFO] > --
Re: MAVEN 2.0 and SCM-SVN
would be much appreciated Message to Dan Tran - Not useless that was a late night tired comment no offense intended ;) Phill _____ FromMax Bowsher <[EMAIL PROTECTED]> Subject Re: MAVEN 2.0 and SCM-SVN DateFri, 09 Mar 2007 09:59:37 GMT The thing you're missing is that the SCM code is usually used to do a checkout in order to create a *temporary* working copy in order to build a release from an SCM tag. It's not at all clear what you are using it for, that you would find it helpful to have it checking out under src. Max. _ From: Phill Moran [mailto:[EMAIL PROTECTED] Sent: March 8, 2007 9:21 PM To: 'users@maven.apache.org' Subject: MAVEN 2.0 and SCM-SVN This could be a dumb questions but why does maven SCM default to checkout to /target/checkout? I would expect it to go to a dir under src/java. It also seems that the SCM plug-in does not allow this to be overridden. I have tried setting and the others to no avail. I am using the standard MAVEN dir structure. Unless I am missing something fundamental this issue makes the plug-in a little useless
RE: MAVEN 2.0 and SCM-SVN
I am clearly missing something.
I get an error on mvn scm:bootstrap (although the code is there)
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'scm'.
[INFO]
[INFO] Building Maven BidSpec Server Archetype
[INFO]task-segment: [scm:bootstrap] (aggregator-style)
[INFO]
[INFO] [scm:bootstrap]
[INFO] Removing /BidSpec/applications/emall/target/checkout
[INFO] Executing: svn --username pmoran --non-interactive checkout
https://ubiquitous001:1180/svn/branches/1.2/bidspec checkout
[INFO] Working directory: /BidSpec/applications/emall/target
[INFO] Unknown file status: ' '.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Can't run goal null
Embedded error: Error while executing process.
java.io.IOException: mvn: not found
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 19 seconds
[INFO] Finished at: Sat Mar 10 01:17:17 EST 2007
[INFO] Final Memory: 4M/9M
[INFO]
I execute the following commands on a POM representing a project with standard
directory structure (IOW no <*directory> entries)
mvn clean -
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven BidSpec Server Archetype
[INFO]task-segment: [clean]
[INFO]
[INFO] [clean:clean]
[INFO] Deleting directory /BidSpec/applications/emall/target
[INFO] Deleting directory /BidSpec/applications/emall/target/classes
[INFO] Deleting directory /BidSpec/applications/emall/target/test-classes
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 9 seconds
[INFO] Finished at: Sat Mar 10 01:16:24 EST 2007
[INFO] Final Memory: 3M/6M
When I execute mvn install I get
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven BidSpec Server Archetype
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 8 source files to /BidSpec/applications/emall/target/test-classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
but as mentioned the source and test code is in the target/checkout directory
Here is my POM
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
ca.BidSpec
emall
Maven BidSpec Server Archetype
1.2.0
Blah blah blah
http://www.my-company.ca
2001
jar
scm:svn:https://[EMAIL PROTECTED]/svn/branches/1.2/my-company
scm:svn:https://[EMAIL PROTECTED]/svn/branches/1.2/my-company
https://ubiquitous001:/svn/branches/1.2/my-company
HEAD
Eventum
https://ubiquitous001/index.php
${artifactId}-${version}
install
$(baseDir)/src/test/resources
log4j.xml
org.codehaus.mojo
openjpa-maven-plugin
process-classes
enhance
addDefaultConstructor
false
enforcePropertyRestrictions
true
org.apache.maven.plugins
maven-compiler-plugin
2.0
1.5
1.5
org.apache.maven.plugins
maven-scm-plugin
1.0-beta-4
validate
scm:checkout
user
password
org.apache.maven.plugins
maven-javadoc-plugin
org.apache.maven.plugins
maven-project-info-reports-plugin
org.apache.maven.plugins
maven-jxr-plugin
org.apache.maven.plugins
maven-surefire-report-plugin
website
file:///my-company/applications/emall/www/
...
Any help/suggestions would be much appreciated
Message to Dan Tran - Not useless that was a late night tired comment no offense
intended ;)
Phill
_____
FromMax Bowsher <[EMAIL PROTECTED]>
Subject Re: MAVEN 2.0 and
Re: MAVEN 2.0 and SCM-SVN
Phill Moran wrote: > This could be a dumb questions but why does maven SCM default to checkout to > /target/checkout? I would expect it to go to a dir under src/java. It also > seems > that the SCM plug-in does not allow this to be overridden. I have tried > setting > and the others to no avail. I am using the standard MAVEN > dir > structure. > Unless I am missing something fundamental this issue makes the plug-in a > little > useless The thing you're missing is that the SCM code is usually used to do a checkout in order to create a *temporary* working copy in order to build a release from an SCM tag. It's not at all clear what you are using it for, that you would find it helpful to have it checking out under src. Max. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: MAVEN 2.0 and SCM-SVN
By convention, any thing generated by the build execution should be placed
under ${project.build.directory) ( ie target)
scm:checkout is not the exception either.
A good use case of this, maven release:perform which checkouts a know tag
into target/checkout and performs the build from there.
After that user can freely remove target dir ( ie mvn clean )
But there are cases you will want override the checkoutDirectory. May be
this is what you want, rather than calling it useless :)
-D
On 3/8/07, Phill Moran <[EMAIL PROTECTED]> wrote:
This could be a dumb questions but why does maven SCM default to checkout
to
/target/checkout? I would expect it to go to a dir under src/java. It also
seems
that the SCM plug-in does not allow this to be overridden. I have tried
setting
and the others to no avail. I am using the standard
MAVEN dir
structure.
Unless I am missing something fundamental this issue makes the plug-in a
little
useless
