Re: deploying plugin jars

2004-06-22 Thread Eric Giguere
repository-deploy... that's it!
Thx a lot Brett
I know why I didn't see it before, I don't have the latest from the 
plugin:plugin.

thx again
Eric.
Brett Porter wrote:
Dan,
Not quite :)
maven plugin:install is used from a plugin source tree to build and
install a plugin into your maven installation.
maven plugin:download (with the artifact ID etc params you gave) is
used to get a plugin from a remote repository and install into your
maven installation
maven plugin:repository-deploy (like jar:deploy) builds a plugin and
puts it into your remote repository.
You probably want to do a plugin:repository-deploy on the plugin code,
then run plugin:download on all Maven installations.
- Brett
On Tue, 22 Jun 2004 12:39:56 +1000, Washusen, Dan
[EMAIL PROTECTED] wrote:
 

Put the downloaded jar file in your $MAVEN_HOME/plugins dir (not the
$HOME/.maven/plugins) and then call 'maven plugin:install' with the
appropriate properties.
So for example one of the sf.net maven-plugins could be installed, after
downloading, with:
maven -DgroupId=maven-plugins -DartifactId=maven-dbunit-plugin -Dversion=1.1
plugin:install
That's from memory but it should be right, hope that helps...
Cheers,
Dan
-Original Message-
From: Eric Giguere [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 22 June 2004 6:35 AM
To: Maven User List
Subject: deploying plugin jars
Hi
Got a small problem. I'm trying to deploy a custom plugin jar in our
internal remote repository.
I've tried using the jar:deploy command but I couldn't get the guy to
put my jar in the right place (maven/plugins/).
No matter how I play with directories (using the propeties), I never
could get the jar in the maven/plugins dir. So, the plugin:download goal
cannot be executed to retreive it.
Is there a way to do so without copying them by hand in the
maven/plugin dir of the repository ?
thx.
Eric.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
www.sensis.com.au
A leading Australian advertising, information
and directories business.
www.yellowpages.com.au
www.whitepages.com.au
www.citysearch.com.au
www.whereis.com.au
www.telstra.com.au
www.tradingpost.com.au
This email and any attachments are intended only for the use of the recipient and may 
be confidential and/or legally privileged.
Sensis Pty Ltd disclaims liability for any errors, omissions, viruses, loss and/or 
damage arising from using, opening or transmitting this email.
If you are not the intended recipient you must not use, interfere with, disclose, copy 
or retain this email and you should notify the sender immediately by return email or 
by contacting Sensis Pty Ltd by telephone on [+61 3 9201 4888]
   

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




AW: deploying plugin jars

2004-06-22 Thread Oliver Noelle
 maven plugin:repository-deploy (like jar:deploy) builds a plugin and
 puts it into your remote repository.

Brett, where is the goal plugin:repository-deploy documented? I can't 
find anything on the plugin's documentation 
(http://maven.apache.org/reference/plugins/plugin/goals.html), and using 
maven -g I just find an empty entry, and I just find it because now I 
know that this entry should exist!

I had exactly the same problem before and wrote my own goal to do the 
plugin:repository-deploy.

I don't think it's acceptable to find out these things via the mailing 
list! I think an existing goal which is not internal must be documented 
properly on the plugins page! You don't want to spend all your time on 
answering all these questions on the mailing list that could be answered 
by looking at the docs, do you? But if people don't find anything in the 
docs anyway, they won't even try in the future... I think you have to 
educate the users to lookup the docs before consulting the mailing list, 
but this assumes that the docs are kept in an appropriate quality and 
completeness.


Just my 2 cents, because right now I tend to use maven more and more 
without following the mailing list, and it just does not work, because 
there is too much info on the list which I would expect to find in the 
docs...

Oliver Noelle


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



Re: deploying plugin jars

2004-06-22 Thread Brett Porter
maven.repo.central
maven.repo.central.directory

(or specify distributionSite and distributionDirectory in your POM)

- Brett

On Tue, 22 Jun 2004 15:51:06 +0200, Jesper Linvald [EMAIL PROTECTED] wrote:
 
 Hi Brett,
 maven plugin:repository-deploy (like jar:deploy) builds a plugin and
 puts it into your remote repository.
 
 I tried this but the plugin (or rather the class Java13CommandLauncher i
 think)wants to upload to ibiblio.org which is not what I want...
 
 In my project.properties I have:
 maven.repo.remote
 maven.proxy.host
 maven.proxy.port
 maven.username
 
 Which should be what is needed...??
 
 Regards
 
 Jesper Linvald
 MAERSK DATA TRANSPORT
 Tel no.: +45 3911 1891
 e-mail: [EMAIL PROTECTED]
 
 Brett Porter [EMAIL PROTECTED]
 22-06-2004 05:34
 Please respond to
 Maven Users List [EMAIL PROTECTED]
 
 To
 Maven Users List [EMAIL PROTECTED]
 cc
 
 Subject
 Re: deploying plugin jars
 
 
 
 
 Dan,
 
 Not quite :)
 
 maven plugin:install is used from a plugin source tree to build and
 install a plugin into your maven installation.
 
 maven plugin:download (with the artifact ID etc params you gave) is
 used to get a plugin from a remote repository and install into your
 maven installation
 
 maven plugin:repository-deploy (like jar:deploy) builds a plugin and
 puts it into your remote repository.
 
 You probably want to do a plugin:repository-deploy on the plugin code,
 then run plugin:download on all Maven installations.
 
 - Brett
 
 On Tue, 22 Jun 2004 12:39:56 +1000, Washusen, Dan
 [EMAIL PROTECTED] wrote:
 
 
  Put the downloaded jar file in your $MAVEN_HOME/plugins dir (not the
  $HOME/.maven/plugins) and then call 'maven plugin:install' with the
  appropriate properties.
 
  So for example one of the sf.net maven-plugins could be installed, after
  downloading, with:
  maven -DgroupId=maven-plugins -DartifactId=maven-dbunit-plugin
 -Dversion=1.1
  plugin:install
 
  That's from memory but it should be right, hope that helps...
 
  Cheers,
  Dan
 
  -Original Message-
  From: Eric Giguere [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, 22 June 2004 6:35 AM
  To: Maven User List
  Subject: deploying plugin jars
 
  Hi
 
  Got a small problem. I'm trying to deploy a custom plugin jar in our
  internal remote repository.
  I've tried using the jar:deploy command but I couldn't get the guy to
  put my jar in the right place (maven/plugins/).
  No matter how I play with directories (using the propeties), I never
  could get the jar in the maven/plugins dir. So, the plugin:download goal
  cannot be executed to retreive it.
 
  Is there a way to do so without copying them by hand in the
  maven/plugin dir of the repository ?
 
  thx.
  Eric.
 
  -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
  www.sensis.com.au
 
  A leading Australian advertising, information
  and directories business.
 
  www.yellowpages.com.au
  www.whitepages.com.au
  www.citysearch.com.au
  www.whereis.com.au
  www.telstra.com.au
  www.tradingpost.com.au
 
  This email and any attachments are intended only for the use of the
 recipient and may be confidential and/or legally privileged.
  Sensis Pty Ltd disclaims liability for any errors, omissions, viruses,
 loss and/or damage arising from using, opening or transmitting this email.
  If you are not the intended recipient you must not use, interfere with,
 disclose, copy or retain this email and you should notify the sender
 immediately by return email or by contacting Sensis Pty Ltd by telephone
 on [+61 3 9201 4888]
 
 
 -
 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: AW: deploying plugin jars

2004-06-22 Thread Brett Porter
Documentation patches are welcome :)

I'll take the blame for this one - I hacked it in and didn't document
it. Raise it in JIRA and we'll make sure it gets done.

- Brett

On Tue, 22 Jun 2004 12:05:22 +0200, Oliver Noelle
[EMAIL PROTECTED] wrote:
 
  maven plugin:repository-deploy (like jar:deploy) builds a plugin and
  puts it into your remote repository.
 
 Brett, where is the goal plugin:repository-deploy documented? I can't
 find anything on the plugin's documentation
 (http://maven.apache.org/reference/plugins/plugin/goals.html), and using
 maven -g I just find an empty entry, and I just find it because now I
 know that this entry should exist!
 
 I had exactly the same problem before and wrote my own goal to do the
 plugin:repository-deploy.
 
 I don't think it's acceptable to find out these things via the mailing
 list! I think an existing goal which is not internal must be documented
 properly on the plugins page! You don't want to spend all your time on
 answering all these questions on the mailing list that could be answered
 by looking at the docs, do you? But if people don't find anything in the
 docs anyway, they won't even try in the future... I think you have to
 educate the users to lookup the docs before consulting the mailing list,
 but this assumes that the docs are kept in an appropriate quality and
 completeness.
 
 Just my 2 cents, because right now I tend to use maven more and more
 without following the mailing list, and it just does not work, because
 there is too much info on the list which I would expect to find in the
 docs...
 
 Oliver Noelle
 
 -
 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]



deploying plugin jars

2004-06-21 Thread Eric Giguere
Hi
Got a small problem. I'm trying to deploy a custom plugin jar in our 
internal remote repository.
I've tried using the jar:deploy command but I couldn't get the guy to 
put my jar in the right place (maven/plugins/).
No matter how I play with directories (using the propeties), I never 
could get the jar in the maven/plugins dir. So, the plugin:download goal 
cannot be executed to retreive it.

Is there a way to do so without copying them by hand in the 
maven/plugin dir of the repository ?

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


Re: deploying plugin jars

2004-06-21 Thread Erik Husby
Eric Giguere wrote:
Hi
Got a small problem. I'm trying to deploy a custom plugin jar in our 
internal remote repository.
I've tried using the jar:deploy command but I couldn't get the guy to 
put my jar in the right place (maven/plugins/).
No matter how I play with directories (using the propeties), I never 
could get the jar in the maven/plugins dir. So, the plugin:download 
goal cannot be executed to retreive it.

Is there a way to do so without copying them by hand in the 
maven/plugin dir of the repository ?

thx.
Eric.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yes, the correct way is to use the plugin plugin.  See 
http://maven.apache.org/reference/plugins/plugin/goals.html for details.

--
Erik Husby
Team Lead for Software Quality Automation
Broad Institute of MIT and Harvard 
Rm. 2192  320 Charles St
Cambridge, MA 02141-2023
mobile: 781.354.6669, office: 617.258.9227, [EMAIL PROTECTED]

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