We need to decide what to do about the wagon dependency before we can
release it. Currently the plugin depends on wagon 1.0-rc1-SNAPSHOT. I
don't follow wagon development so I don't know how far off an rc1
release is.
It would be nice if the repositoryId parameter could pick up the
username a
All sounds good. Shall we prepare a release? I can write up some doco
but it's probably good to get a quick alpha release out.
On 23 Jun 07, at 8:36 AM 23 Jun 07, Dennis Lundberg wrote:
Jason van Zyl wrote:
On 9 Jun 07, at 5:56 AM 9 Jun 07, Dennis Lundberg wrote:
Sure. I think I've found out
Jason van Zyl wrote:
On 9 Jun 07, at 5:56 AM 9 Jun 07, Dennis Lundberg wrote:
Sure. I think I've found out why the process stopped after the files
had been unzipped on the server. It turns out that we are using
OS-dependent file separators in the rename script. Here's what that
script looks
On 9 Jun 07, at 5:56 AM 9 Jun 07, Dennis Lundberg wrote:
Sure. I think I've found out why the process stopped after the
files had been unzipped on the server. It turns out that we are
using OS-dependent file separators in the rename script. Here's
what that script looks like for the maven-
Sure. I think I've found out why the process stopped after the files had
been unzipped on the server. It turns out that we are using OS-dependent
file separators in the rename script. Here's what that script looks like
for the maven-one-plugin release that I tried earlier:
mv org\apache\maven\
You want to work through some of these issues as I'm going to stage
2.0.7 today and there's a couple things I need to fix up.
On 4 Jun 07, at 1:22 PM 4 Jun 07, Dennis Lundberg wrote:
Hi
I've tried to get the maven-stage-plugin working. Currently the -
DrepositoryId parameter is not working,
Hi
I've tried to get the maven-stage-plugin working. Currently the
-DrepositoryId parameter is not working, which is not a fault of the
plugin itself. That problem seems to stem from WagonManager in
maven-artifact-manager or beyond. Anyway I couldn't find the root of the
problem.
Now I need