RE: [m1.1] jar/war deploy doesn't Deploy

2005-08-17 Thread Curtis, Harrison
Good Guess. The deployed jar and associated md5 and sha1 are in the
c:\temp\Mavenrepository\DBB_Deploy\plugins. It looks like the new
artifact doesn't add the folder separator between 'maven.repo.R1' and
'maven.repo.R1.directory' properties as it use to. I have several
folders under the Maven folder, so I missed it until I did the search.

maven.repo.list=R1
maven.repo.R1=file://c:\\temp\\Maven
maven.repo.R1.directory=repository

Bud Curtis
JDIMS Project
L-3 Communications
(719) 637-5633

-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, August 17, 2005 1:03 AM
To: Curtis, Harrison
Cc: Maven Users List
Subject: Re: [m1.1] jar/war deploy doesn't Deploy

Thanks. Can you do a search to find out where the actually did end up?
(it would be very strange for it to show progress and not save them).
With that info, please file a bug report and I'll try and repair it as
soon as possible.
- Brett
On 8/17/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> I'm using the 1.6 artifact plugin. I upgraded because the original
> artifact plugin couldn't write to the local repository the updated 
> jars.
> 
> Bud Curtis
> JDIMS Project
> L-3 Communications
> (719) 637-5633
> 
> 
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 15, 2005 7:07 PM
> To: Maven Users List
> Subject: Re: [m1.1] jar/war deploy doesn't Deploy
> 
> 
> You'll find them in c:\
> 
> The bug was fixed in the 1.6 release of the artifact plugin.
> 
> - Brett
> 
> On 8/16/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> > In Maven 1.1 when a jar:deploy is performed the jar files in the
> > local
> 
> > repository should be copied to the specified remotes. My
> > build.properties has the following entries to specify the remote:
> >
> > maven.repo.list=R1
> > maven.repo.R1=file://c:\\temp\\Maven
> > maven.repo.R1.directory=repository
> >
> > The following is an excerpt of the jar:deploy console log. The
> > plugin
> 
> > must understand the maven.repo.list set of properties.
> >
> > jar:jar:
> >
> > jar:deploy:
> > [echo] Deploying...
> > Will deploy to 1 repository(ies): R1
> > Deploying to repository: R1
> > Uploading to scnc_dbb_common/poms/DBUtil-1.2.pom:
> >  (3K)
> > Will deploy to 1 repository(ies): R1
> > Deploying to repository: R1
> > Uploading to scnc_dbb_common/jars/DBUtil-1.2.jar:
> >  (73K)
> > BUILD SUCCESSFUL
> > Total time : 10 seconds
> > Finished at : Monday, August 15, 2005 2:31:40 PM MDT
> >
> > -
> >
> > After the BUILD SUCCESSFUL, I looked in the
> > c:/temp/Maven/repository/scnc_dbb_common/jars folder for the jar 
> > archive, MD5, or Sha1 files, After the deploy they were not 
> > updated. It looks like the plugin is going through all the motions 
> > without effecting the result. This is also true with the 
> > war:deploy, so I suspect there is another problem perhaps with the 
> > artifact plugin.
> >
> > The deploy did work with the Maven 1.0.1 release.
> >
> > Bud Curtis
> > JDIMS Project
> > L-3 Communications
> > (719) 637-5633
> >
> > 
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

Bud Curtis
JDIMS Project
L-3 Communications
(719) 637-5633

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [m1.1] jar/war deploy doesn't Deploy

2005-08-17 Thread Brett Porter
Thanks. Can you do a search to find out where the actually did end up?
(it would be very strange for it to show progress and not save them).
With that info, please file a bug report and I'll try and repair it as
soon as possible.

- Brett

On 8/17/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> I'm using the 1.6 artifact plugin.  I upgraded because the original
> artifact plugin couldn't write to the local repository the updated jars.
> 
> Bud Curtis
> JDIMS Project
> L-3 Communications
> (719) 637-5633
> 
> 
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 15, 2005 7:07 PM
> To: Maven Users List
> Subject: Re: [m1.1] jar/war deploy doesn't Deploy
> 
> 
> You'll find them in c:\
> 
> The bug was fixed in the 1.6 release of the artifact plugin.
> 
> - Brett
> 
> On 8/16/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> > In Maven 1.1 when a jar:deploy is performed the jar files in the local
> 
> > repository should be copied to the specified remotes.  My
> > build.properties has the following entries to specify the remote:
> >
> > maven.repo.list=R1
> > maven.repo.R1=file://c:\\temp\\Maven
> > maven.repo.R1.directory=repository
> >
> > The following is an excerpt of the jar:deploy console log.  The plugin
> 
> > must understand the maven.repo.list set of properties.
> >
> > jar:jar:
> >
> > jar:deploy:
> > [echo] Deploying...
> > Will deploy to 1 repository(ies): R1
> > Deploying to repository: R1
> > Uploading to scnc_dbb_common/poms/DBUtil-1.2.pom:
> >  (3K)
> > Will deploy to 1 repository(ies): R1
> > Deploying to repository: R1
> > Uploading to scnc_dbb_common/jars/DBUtil-1.2.jar:
> >  (73K)
> > BUILD SUCCESSFUL
> > Total time   : 10 seconds
> > Finished at  : Monday, August 15, 2005 2:31:40 PM MDT
> >
> > -
> >
> > After the BUILD SUCCESSFUL, I looked in the
> > c:/temp/Maven/repository/scnc_dbb_common/jars folder for the jar
> > archive, MD5, or Sha1 files,  After the deploy they were not updated.
> > It looks like the plugin is going through all the motions without
> > effecting the result.  This is also true with the war:deploy, so I
> > suspect there is another problem perhaps with the artifact plugin.
> >
> > The deploy did work with the Maven 1.0.1 release.
> >
> > Bud Curtis
> > JDIMS Project
> > L-3 Communications
> > (719) 637-5633
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: [m1.1] jar/war deploy doesn't Deploy

2005-08-16 Thread Curtis, Harrison
I'm using the 1.6 artifact plugin.  I upgraded because the original
artifact plugin couldn't write to the local repository the updated jars.

Bud Curtis
JDIMS Project
L-3 Communications
(719) 637-5633


-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 15, 2005 7:07 PM
To: Maven Users List
Subject: Re: [m1.1] jar/war deploy doesn't Deploy


You'll find them in c:\

The bug was fixed in the 1.6 release of the artifact plugin.

- Brett

On 8/16/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> In Maven 1.1 when a jar:deploy is performed the jar files in the local

> repository should be copied to the specified remotes.  My 
> build.properties has the following entries to specify the remote:
> 
> maven.repo.list=R1
> maven.repo.R1=file://c:\\temp\\Maven
> maven.repo.R1.directory=repository
> 
> The following is an excerpt of the jar:deploy console log.  The plugin

> must understand the maven.repo.list set of properties.
> 
> jar:jar:
> 
> jar:deploy:
> [echo] Deploying...
> Will deploy to 1 repository(ies): R1
> Deploying to repository: R1
> Uploading to scnc_dbb_common/poms/DBUtil-1.2.pom:
>  (3K)
> Will deploy to 1 repository(ies): R1
> Deploying to repository: R1
> Uploading to scnc_dbb_common/jars/DBUtil-1.2.jar:
>  (73K)
> BUILD SUCCESSFUL
> Total time   : 10 seconds
> Finished at  : Monday, August 15, 2005 2:31:40 PM MDT
> 
> -
> 
> After the BUILD SUCCESSFUL, I looked in the 
> c:/temp/Maven/repository/scnc_dbb_common/jars folder for the jar 
> archive, MD5, or Sha1 files,  After the deploy they were not updated. 
> It looks like the plugin is going through all the motions without 
> effecting the result.  This is also true with the war:deploy, so I 
> suspect there is another problem perhaps with the artifact plugin.
> 
> The deploy did work with the Maven 1.0.1 release.
> 
> Bud Curtis
> JDIMS Project
> L-3 Communications
> (719) 637-5633
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [m1.1] jar/war deploy doesn't Deploy

2005-08-15 Thread Brett Porter
You'll find them in c:\

The bug was fixed in the 1.6 release of the artifact plugin.

- Brett

On 8/16/05, Curtis, Harrison <[EMAIL PROTECTED]> wrote:
> In Maven 1.1 when a jar:deploy is performed the jar files in the local
> repository should be copied to the specified remotes.  My
> build.properties has the following entries to specify the remote:
> 
> maven.repo.list=R1
> maven.repo.R1=file://c:\\temp\\Maven
> maven.repo.R1.directory=repository
> 
> The following is an excerpt of the jar:deploy console log.  The plugin
> must understand the maven.repo.list set of properties.
> 
> jar:jar:
> 
> jar:deploy:
> [echo] Deploying...
> Will deploy to 1 repository(ies): R1
> Deploying to repository: R1
> Uploading to scnc_dbb_common/poms/DBUtil-1.2.pom:
>  (3K)
> Will deploy to 1 repository(ies): R1
> Deploying to repository: R1
> Uploading to scnc_dbb_common/jars/DBUtil-1.2.jar:
>  (73K)
> BUILD SUCCESSFUL
> Total time   : 10 seconds
> Finished at  : Monday, August 15, 2005 2:31:40 PM MDT
> 
> -
> 
> After the BUILD SUCCESSFUL, I looked in the
> c:/temp/Maven/repository/scnc_dbb_common/jars folder for the jar
> archive, MD5, or Sha1 files,  After the deploy they were not updated.
> It looks like the plugin is going through all the motions without
> effecting the result.  This is also true with the war:deploy, so I
> suspect there is another problem perhaps with the artifact plugin.
> 
> The deploy did work with the Maven 1.0.1 release.
> 
> Bud Curtis
> JDIMS Project
> L-3 Communications
> (719) 637-5633
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[m1.1] jar/war deploy doesn't Deploy

2005-08-15 Thread Curtis, Harrison
In Maven 1.1 when a jar:deploy is performed the jar files in the local
repository should be copied to the specified remotes.  My
build.properties has the following entries to specify the remote:

maven.repo.list=R1
maven.repo.R1=file://c:\\temp\\Maven
maven.repo.R1.directory=repository

The following is an excerpt of the jar:deploy console log.  The plugin
must understand the maven.repo.list set of properties.

jar:jar:

jar:deploy:
[echo] Deploying...
Will deploy to 1 repository(ies): R1
Deploying to repository: R1
Uploading to scnc_dbb_common/poms/DBUtil-1.2.pom:
 (3K)
Will deploy to 1 repository(ies): R1
Deploying to repository: R1
Uploading to scnc_dbb_common/jars/DBUtil-1.2.jar:
 (73K)
BUILD SUCCESSFUL
Total time   : 10 seconds
Finished at  : Monday, August 15, 2005 2:31:40 PM MDT

-

After the BUILD SUCCESSFUL, I looked in the
c:/temp/Maven/repository/scnc_dbb_common/jars folder for the jar
archive, MD5, or Sha1 files,  After the deploy they were not updated.
It looks like the plugin is going through all the motions without
effecting the result.  This is also true with the war:deploy, so I
suspect there is another problem perhaps with the artifact plugin.

The deploy did work with the Maven 1.0.1 release.

Bud Curtis
JDIMS Project
L-3 Communications
(719) 637-5633

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]