Ok, it is still referencing subversion. You need to add in your pom:
<scm>
<connection>scm:git:git://github.com/jenkinsci/${project.artifactId}-plugin.git</connection>
<developerConnection>scm:git:[email protected]:jenkinsci/${project.artifactId}-plugin.git</developerConnection>
<url>https://github.com/jenkinsci/${project.artifactId}-plugin</url>
</scm>Ulli Am 27.09.2013 um 11:06 schrieb Vivekanand S V <[email protected]>: > I've tried it and that step was done and it went till finishing running the > tests. After that while committing the pom I get this error > > [INFO] Checking in modified POMs... > [INFO] Executing: /bin/sh -c cd > /Users/vivekanand/NetBeansProjects/copy-to-slave-plugin && svn > --non-interactive commit --file > /var/folders/b2/cqp5lgd174d18cfqc122_sfnc9kyrp/T/maven-scm-1086457309.commit > --targets > /var/folders/b2/cqp5lgd174d18cfqc122_sfnc9kyrp/T/maven-scm-1986766400390318545-targets > [INFO] Working directory: > /Users/vivekanand/NetBeansProjects/copy-to-slave-plugin > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 51.151s > [INFO] Finished at: Fri Sep 27 14:09:16 GMT+05:30 2013 > [INFO] Final Memory: 11M/81M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare > (default-cli) on project copy-to-slave: Unable to commit files > [ERROR] Provider message: > [ERROR] The svn command failed. > [ERROR] Command output: > [ERROR] svn: '/Users/vivekanand/NetBeansProjects/copy-to-slave-plugin' is not > a working copy > [ERROR] -> [Help 1] > > After checking the effective pom, i saw that the scm part points to some svn > repo, the code is hosted in git. I don't understand how it is happening in > the background, but shall I change the <scm> </scm> part to point to github > in the pom as explained here ? What after effects does changing the scm part > will have here ? > > > > On Fri, Sep 27, 2013 at 2:05 PM, Vivekanand S V <[email protected]> > wrote: > I found a discussion which says we need to do this. I'm going to try it now, > is it the right way or just a workaround till a fix gets ready ? > > > On Fri, Sep 27, 2013 at 1:52 PM, Vivekanand S V <[email protected]> > wrote: > I added repo details in maven settings.xml and ran the mvn release command > and I got this :) > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare > (default-cli) on project copy-to-slave: Execution default-cli of goal > org.apache.maven.plugins:maven-release-plugin:2.0-beta-9:prepare failed: > Failed to build parent project for > org.jenkins-ci.plugins:copy-to-slave:hpi:1.4.1-SNAPSHOT: Some problems were > encountered while processing the POMs: > [ERROR] [WARNING] 'build.plugins.plugin.version' for > com.cloudbees:maven-license-plugin is missing. @ line 191, column 15 > [ERROR] [ERROR] Unresolveable build extension: Plugin > org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could > not be resolved: Could not find artifact > org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central > (http://repo.maven.apache.org/maven2) @: 2 problems were encountered while > building the effective model for org.jenkins-ci.plugins:plugin:1.424 > [ERROR] [WARNING] 'build.plugins.plugin.version' for > com.cloudbees:maven-license-plugin is missing. @ line 191, column 15 > [ERROR] [ERROR] Unresolveable build extension: Plugin > org.jenkins-ci.tools:maven-hpi-plugin:1.74 or one of its dependencies could > not be resolved: Could not find artifact > org.jenkins-ci.tools:maven-hpi-plugin:jar:1.74 in central > (http://repo.maven.apache.org/maven2) @ > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > > Btw, the maven version I am using to executing this command is "Apache Maven > 3.0.5". From the error it looks like looking into maven2, should I be using > maven version 2.x ? > > > On Fri, Sep 27, 2013 at 1:14 PM, Ullrich Hafner <[email protected]> > wrote: > You need to revert the version back to -SNAPSHOT. Maven will automatically > fill in the correct version. > > I'm not sure if the SCM section is derived from our parent Pom. Maven will > create a new TAG during the release. So that section needs to be present. You > can run mvn help:effective-pom to see the final Pom. > > Did you specify our maven repository in you settings.xml? And you password > and user? > > The best thing is to try the release and post any errors:-) > > Ulli > > > Am Freitag, 27. September 2013 schrieb Vivekanand S V : > > Need a small help in releasing the new version. I pushed the final commit by > changing the version number for this release. From this wiki I saw that I > have to execute mvn release:prepare release:perform command with user > details. Is it all I've to do ? From the previous releases of previous owner > I saw he adding/removing scm repositories in his pom during a release. > > I am new to this(both jenkins and maven) can someone please tell me what I > should be doing ? Just executing the maven command will be enough ? Should I > make any changes to my m2/settings.xml or pom like adding plugin repo details > ? > > > Thanks, > Vivek. > > > > On Wed, Sep 25, 2013 at 7:35 PM, Ulli Hafner <[email protected]> wrote: > Ups, yes of course now :-) > > Am 25.09.2013 um 16:02 schrieb Vivekanand S V <[email protected]>: > >> Thanks, I assume that was a "noW" in your reply :) >> >> >> On Wed, Sep 25, 2013 at 7:31 PM, Ulli Hafner <[email protected]> >> wrote: >> You should not have full access. >> >> Welcome aboard! >> >> Ulli >> >> Am 25.09.2013 um 15:48 schrieb Vivekanand S V <[email protected]>: >> >>> Sorry, I missed my details. >>> >>> GitHub id - svvivek (https://github.com/svvivek) >>> >>> >>> On Wed, Sep 25, 2013 at 7:16 PM, Vivekanand S V <[email protected]> >>> wrote: >>> Hi, >>> >>> >>> I've sent a pull request for this plugin, I've mailed the author recently >>> and he said he is not maintaining this plugin any more. So can I take >>> ownership of this plugin ? >>> >>> >>> Thanks, >>> Vivekanand. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Jenkins Developers" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected]. >>> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out.
signature.asc
Description: Message signed with OpenPGP using GPGMail
