Jesse,
From maven side - I know you've gone through that, but just to
reiterate: we have a server security configuration which by default
includes either name/password or a private key file with a password for it.
We can probably enhance that to include realm name, or can use server id
for t
On 19-Jul-08, at 6:42 PM, Dennis Lundberg wrote:
No, I don't have Cygwin installed, and I'm seeing the same problem
that Benjamin is.
The problem is that the config.xml for maven-2.1.x-IT-support and
maven-2.1.x-ITs use this:
...
To be able to run such a job in Hudson,
No, I don't have Cygwin installed, and I'm seeing the same problem that
Benjamin is.
The problem is that the config.xml for maven-2.1.x-IT-support and
maven-2.1.x-ITs use this:
...
To be able to run such a job in Hudson, it requires the presence of a
"sh" executable,
+1 -- I tried it with the Deploy plugin build and spot checked for
signatures and license/notice files.
--
Wendy
On Fri, Jul 18, 2008 at 8:16 AM, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Important note: this release changes the groupId for the artifacts:
> http://maven.markmail.org/m
This is great as long as it does not become bureaucratic and onerous
for everyone to do a release.
How to prevent that is codify the process in the tooling. No one has
ever, and never will, follow a workflow that is defined in a document.
People are just people and most people themselves wo
I went and harvested the mojo-dev list for release vote comments, most
of the from Benjamin. Some are specific to plugins, but many are
general. Here's the list:
Inherit from the latest released parent to benefit from its improvements.
If the latest parent-SNAPSHOT has important fixes, copy t
