> > 1) Are you using the right version of maven? Sometimes an upgrade > > solves strange problems. Does cas use maven 2.x or 3.x? > > Don't think there's an official standard; it's simply whatever the core devs > use, which is 3.x. I'm using 3.0.4, so no issue there.
[DO]
I would definitely try moving to 3.0.5. I have this in a parent pom of
mine:
<!-- 3.0.4 fails with artifactory when there are problems with the
pom file for a dependency -->
<prerequisites>
<maven>3.0.5</maven>
</prerequisites>
No guarantees, but I did have really weird dependency resolution problems
with 3.0.4. I remember banging my head against the wall for a while until
I found it was some weird combination of 3.0.4 with some plugins or plugin
versions. I don't remember the details now.
>
> > 2) Are you passing in the "-s" flag to get a specfic settings.xml file?
>
> Nope. I've done the release process several times now using the following
> instructions without incident:
>
> https://wiki.jasig.org/display/CAS/Release+Process
>
> This time it's proving to be a major pain point for multiple folks.
[DO] Hmmm... I would double check, then, you default settings.xml.
Unlikely, because, as you say, others are having problems.
I'll see if I can try to reproduce your problem. I've spent more time on
maven junk that I care to admit. When it is working, it works nicely...
>
> 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
smime.p7s
Description: S/MIME cryptographic signature
