I agree with what you are saying. Luckily there is an answer: setup
your own internal repository. There are a few options here, I'm sure
someone else on the list can provide you with more details as I'm a
maven newb. These references might help:
http://maven.apache.org/guides/introduction/introdu
Worked perfectly! (Except that I'm on windows so c:\Document and
Settings\username\.ssh)
I think something is broken with Wagon -- shouldn't it create that
directory and file, the same way that the command line version of ssh
does?
Thanks again!
On 7/26/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
On 7/25/06, Max Cooper <[EMAIL PROTECTED]> wrote:
Some production environments have similar issues. For example, some
webapps are deployed expanded. And the new version is simply dumped in
over the old version. Requesting to have files deleted during a
deployment in these schemes is overhead, an
Note you can change the names of jars/wars
within an ear so that the module URI in the application.xml does not
need to change with every version increment.
How? Do tell! =)
As Chris mentioned, the best way is to add a copy step after the fact
which renames the file to your legacy format and up
Ironic. I was just getting ready to ask a similar question. Although
I'm fine with the versioning that occurs in the repository, I need the
ability for the jar name to not contain this version string in it when
I create a release or deploy the project to the integration server
for testing.
In my
