AW: AW: Making plugins a dependency
I tried this on Win2K, maven RC1.
If this does not work on linux, please see the repository:copy-artifact goal
for how it works...
Oliver
-Ursprüngliche Nachricht-
Von: Alex Vollmer [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 23. Januar 2004 21:42
An: Maven Users List
Betreff: Re: AW: Making plugins a dependency
What platform have you tried this on? I found that the way the 'SSH'
command is executed on Linux in RC1 is broken. Has anyone else had this
experience?
--Alex V.
On Thu, 2004-01-22 at 23:50, Oliver Nölle wrote:
Could you please be a bit more detailed with an example?
See the message I posted before, it's a goal that uses
repository:copy-artifact
Oliver
P.S.
Here is what I wrote:
I wrote the following goal to accomplish what I would have expected a
plugin:deploy goal to do:
goal name=plugindeploy
description=deploys a plugin to the central repository
prereqs=jar
ant:property name=artifact
value=${maven.build.dir}/${maven.final.name}.jar/
ant:property name=groupId value=${pom.groupId}/
ant:property name=type value=plugin/
attainGoal name=repository:copy-artifact/
/goal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Alex Vollmer
[EMAIL PROTECTED]
Software Engineer
Tenzing Communications, Inc.
705 Fifth Avenue South, Suite 700
Seattle, WA 98104 USA
T: +1 206.607.2869
Bring your laptop and try inflight email on your next United,
Continental or Cathay Pacific flight. All you need is your laptop, user
ID, password, and email server URL. Tenzing Communications, Inc.
provides inflight email systems that help airborne travelers stay in
touch.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
AW: Making plugins a dependency
I was also surprised to see plugin:deploy having quite a different
semtantics than jar:deploy and dist:deploy.
I wrote the following goal to accomplish what I would have expected a
plugin:deploy goal to do:
goal name=plugindeploy
description=deploys a plugin to the central repository
prereqs=jar
ant:property name=artifact
value=${maven.build.dir}/${maven.final.name}.jar/
ant:property name=groupId value=${pom.groupId}/
ant:property name=type value=plugin/
attainGoal name=repository:copy-artifact/
/goal
Maybe this helps...
Oliver
-Ursprungliche Nachricht-
Von: Mark R. Diggory [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 22. Januar 2004 22:59
An: Maven Users List
Betreff: Re: Making plugins a dependency
But, more specifically, for project external to maven, isn't this just
the same process as getting your artifacts published?
http://maven.apache.org/repository-upload.html
goals corresponding to this
dist:deploy
jar:deploy
...
but plugin:deploy ... doesn't exacty do the same thing, now does it?
-Mark
Mark R. Diggory wrote:
http://maven.apache.org/reference/developers/releasing-plugins.html
Alex Vollmer wrote:
The 'plugin:install' goal installs the JAR in the local repository, I
want a goal that installs the JAR in the remote repository.
--Alex V.
On Thu, 2004-01-22 at 12:58, Incze Lajos wrote:
On Thu, Jan 22, 2004 at 11:48:46AM -0800, Alex Vollmer wrote:
What Maven goal will allow me to deploy my plugin to our
repository the
same way I would deploy any other kind of artifact? Basically the
normal
'jar:deploy' puts the JAR file in the 'jars' sub-directory and I
want it
to go into the 'plugins' sub-directory.
Thanks in advance.
--Alex V.
plugin:install
incze
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Alex Vollmer
[EMAIL PROTECTED]
Software Engineer
Tenzing Communications, Inc.
705 Fifth Avenue South, Suite 700
Seattle, WA 98104 USA
T: +1 206.607.2869
Bring your laptop and try inflight email on your next United,
Continental or Cathay Pacific flight. All you need is your laptop, user
ID, password, and email server URL. Tenzing Communications, Inc.
provides inflight email systems that help airborne travelers stay in
touch.
--
Mark Diggory
Software Developer
Harvard MIT Data Center
http://www.hmdc.harvard.edu
-
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: Making plugins a dependency
What platform have you tried this on? I found that the way the 'SSH'
command is executed on Linux in RC1 is broken. Has anyone else had this
experience?
--Alex V.
On Thu, 2004-01-22 at 23:50, Oliver Nölle wrote:
Could you please be a bit more detailed with an example?
See the message I posted before, it's a goal that uses
repository:copy-artifact
Oliver
P.S.
Here is what I wrote:
I wrote the following goal to accomplish what I would have expected a
plugin:deploy goal to do:
goal name=plugindeploy
description=deploys a plugin to the central repository
prereqs=jar
ant:property name=artifact
value=${maven.build.dir}/${maven.final.name}.jar/
ant:property name=groupId value=${pom.groupId}/
ant:property name=type value=plugin/
attainGoal name=repository:copy-artifact/
/goal
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Alex Vollmer
[EMAIL PROTECTED]
Software Engineer
Tenzing Communications, Inc.
705 Fifth Avenue South, Suite 700
Seattle, WA 98104 USA
T: +1 206.607.2869
Bring your laptop and try inflight email on your next United,
Continental or Cathay Pacific flight. All you need is your laptop, user
ID, password, and email server URL. Tenzing Communications, Inc.
provides inflight email systems that help airborne travelers stay in
touch.
