On 04/03/2011, at 3:17 AM, Russel Winder wrote:
> On Thu, 2011-03-03 at 11:02 +1000, Luke Daley wrote:
> [ . . . ]
>>
>> If deploying to Codehaus, I suggest you move away from the deprecated
>> webdav mechanism and start using the Nexus instance. This relieves the
>> directory creation problem.
>
> This appears to be a completely separate repository compared to the one
> access by WebDav and given that there is no
>
> https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/gant
> https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/gpars
> https://nexus.codehaus.org/content/repositories/snapshots/org/codehaus/jsr166-mirror
>
> then these projects are going to find it hard to use this route. Is it
> a question of registering somewhere?
Yes, it's a completely separate mechanism. At some point the mechanism you are
using will have to be completely removed as the Maven Central dudes are
planning to remove the rsync upload mechanism which means that it will be Nexus
or nothing.
You have to open an issue under the Codehaus Jira “Haus Chores” project and
request that your project be Nexus enabled. It's a bit of a pain to setup, but
it will have to be done sometime. Now that I have this setup releases are easy
and pain free.
I had to fork the existing PGP plugin though to get it to work with javadoc and
source jars. I had an issue where having the javadoc and source jars in the
default archives configuration caused the source jar to be on the classpath,
which caused havoc with Groovy AST transforms. So I moved these two artefacts
two a separate configuration which fixed the classpath issue but broke the PGP
plugin, so I hacked a fork and checked out into buildSrc. You'll want to do the
same to avoid any funny business.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
