Upgrading on Mac/Linux was painless as usual - and everything here
seems to run fine with 2.3.2 - but Windows continues to be a pain in
the rear...

You can't lein upgrade so I updated the version string in lein.bat and
tried lein self-install:

C:\Users\Sean>lein self-install
Downloading Leiningen now...
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\gow/etc/wgetrc
--2013-08-20 22:01:41--
https://cloud.github.com/downloads/technomancy/leiningen/leiningen-2.3.2-standalone.jar
Resolving cloud.github.com... 54.240.188.252, 54.230.71.6, 54.230.70.21, ...
Connecting to cloud.github.com|54.240.188.252|:443... connected.
WARNING: cannot verify cloud.github.com's certificate, issued by
`/C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert High Assurance
CA-3':
  Self-signed certificate encountered.
WARNING: certificate common name `*.cloudfront.net' doesn't match
requested host name `cloud.github.com'.
HTTP request sent, awaiting response... 403 Forbidden
2013-08-20 22:01:41 ERROR 403: Forbidden.

Failed to download
https://cloud.github.com/downloads/technomancy/leiningen/leiningen-2.3.2-standalone.jar

You can't download that file via a browser either:

This XML file does not appear to have any style information associated
with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>BBF8809DA1520371</RequestId>
<HostId>
Laq6Bi6lZlah+zalsro6LbnHl2hKt0fDsZO1Tvu6spiEjq8CghIMHLDSwk7XTm+k
</HostId>
</Error>

I have HTTP_CLIENT set to wget --no-check-certificate -O as a global
environment variable.

Is this just a problem upgrading from 2.1.3 that is - finally - going
to be a thing of the past from now on, or is there still work to do?

Sean


On Tue, Aug 20, 2013 at 3:11 PM, Phil Hagelberg <p...@hagelb.org> wrote:
>
> Hello everybody.
>
> I'm happy to announce the release of Leiningen 2.3.2, a minor bugfix
> release over 2.3.1. Changes include the following:
>
> * Write `.nrepl-port` file for better tool interoperability. (Phil Hagelberg)
> * Support targeted upgrades in `lein.bat`. (Shantanu Kumar)
> * Warn when projects rely on implicit AOT of `:main`. (Phil Hagelberg)
> * Fix a bug where implicit AOT of `:main` was disabled. (Phil Hagelberg)
> * Disable profile isolation by default. Will be back in 3.x. (Phil Hagelberg)
>
> The biggest change here the disabling of profile isolation (a new by
> default due to incompatibilities with certain projects that hard-code
> paths. Profile isolation was a new feature in 2.3.0 described in the FAQ:
>
>> Leiningen supports isolating different profiles by their target
>> directory. Simply specify `:target-path "target/%s"` in order to have
>> each profile set use a different directory for generated files. Then you
>> can put your `:aot` settings in the `:uberjar` profiles, and the .class
>> files created from the AOT process will not affect normal development
>> use. You can specify the profile-isolated `:target-path` in your `:user`
>> profile if you want it applied across all the projects you work on.
>
> I still recommend using profile isolation since it helps avoid a number
> of subtle gotchas around stale AOT files and user-level dependencies
> being visible with downstream consumers, but you now have to opt-in to
> this feature by setting :target-path as described above.
>
> We've also fixed a bug where setting :main without setting :aot would no
> longer implicitly compile the :main namespace. It's still recommended to
> be explicit about what :aot you need, (in the :uberjar profile if
> applicable) but the old behaviour has been restored.
>
> You'll also want to add a .gitignore entry for the new .nrepl-port file
> which we're using for improved cross-tool compatibility; discussion of
> that feature is here: https://github.com/technomancy/leiningen/issues/1296
>
> Thanks!
>
> -Phil



-- 
Sean A Corfield -- (904) 302-SEAN
An Architect's View -- http://corfield.org/
World Singles, LLC. -- http://worldsingles.com/

"Perfection is the enemy of the good."
-- Gustave Flaubert, French realist novelist (1821-1880)

-- 
-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to