I tried to reproduce the problem, but was unable to.  I tried with both
maven 3.0.4 and maven 3.0.5.

My builds did not try to push stuff back to github, nor did I try to run the
deploy phase, which I would not have permission to do, so it is a slightly
different test.  Also while I did include "skipTests" I think that didn't
take effect and it ran the tests.

  git clone https://github.com/Jasig/cas.git
  /opt/apache-maven-3.0.4/bin/mvn release:prepare -DpushChanges=false
-DlocalCheckout=true -Dgoals=install -Darguments="-DskipTests=true"
  /opt/apache-maven-3.0.4/bin/mvn release:perform -DpushChanges=false
-DlocalCheckout=true -Dgoals=install -DskipTests -Darguments="-DskipTests"

That said, there is something familiar sounding about this problem from the
past.  But of course I can't find any info on it now... 

If there is some other test I could run to help reproduce the problem,
please let me know.

david


> -----Original Message-----
> From: Misagh Moayyed [mailto:[email protected]]
> Sent: Friday, July 05, 2013 4:33 PM
> To: [email protected]
> Subject: RE: [cas-dev] Status of 4.0.0-RC1 Release
> 
> I ran into the same problem before. What I would do is, navigate to the
> target/checkout directory, which is the place the plugin attempts to
checkout
> the code from the upstream branch. Run "mvn install" once, to have it
> produce dependencies. Then you'd be able to actually perform the release.
> 
> Documented some of the gotchas here:
> https://wiki.jasig.org/display/CAS/Release+Process
> 
> > -----Original Message-----
> > From: Marvin S. Addison [mailto:[email protected]]
> > Sent: Friday, July 05, 2013 8:32 AM
> > To: [email protected]
> > Subject: [cas-dev] Status of 4.0.0-RC1 Release
> >
> > Misagh and I have been fighting with cutting the RC1 release for the
> better
> > part of two weeks. I'm trying to jump in and do it myself, albeit from
> > a different machine, and running into problems. I can get to the mvn
> > release:perform step but the build fails due to the following root
> > cause:
> >
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
> project
> > cas-server: failed to get report for
> > org.apache.maven.plugins:maven-javadoc-plugin: Failed to execute goal
> > on project cas-server-support-generic: Could not resolve dependencies
> > for project org.jasig.cas:cas-server-support-generic:jar:4.0.0-RC1:
> > Could
> not
> > find artifact org.jasig.cas:cas-server-core:jar:4.0.0-RC1 in
> jasig-repository
> > (http://developer.ja-sig.org/maven2)
> >
> > It appears that maven is trying to resolve dependencies from the Jasig
> Maven
> > repository, which is insane -- of course the dependencies are not there.
> I
> > tried blowing away my local Maven repo, which sometimes helps with
> > these kinds of weird errors, but the problem persists.
> >
> > Suggestions? I'm at a loss and I sincerely don't have the energy to
> fight
> > with build systems.
> >
> > M
> >
> > --
> > You are currently subscribed to [email protected] as:
> > [email protected] To unsubscribe, change settings or access
> > archives,
> see
> > http://www.ja-sig.org/wiki/display/JSG/cas-dev
> 
> --
> You are currently subscribed to [email protected] as:
> [email protected] To unsubscribe, change settings or access archives,
> see http://www.ja-sig.org/wiki/display/JSG/cas-dev

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to