You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mi...@amsterdam.politie.nl on 2007/01/26 09:26:35 UTC
How to deploy maven plugin jar to inhouse repository
Hi all,
Does anyone know how to deploy a maven plugin jar to an inhouse
repository (no proxy)? I tried deploy:deploy-file like this:
mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins
-DartifactId=maven-ejb-plugin -Dversion=2.1-SNAPSHOT
-Dpackaging=maven-plugin
-Durl=file://R:\maven\repositories\isc-external-snapshots
-Dfile=d:\maven-ejb-plugin-2.1-SNAPSHOT.jar
Unfortunately the result does not look the same as other entries in the
repository. For instance the file .metadata-maven2-snapshot-apache and
the timestamped version of the snapshot are missing.
Let me explain my situation:
1) At work we have no internet connection, we use stand-alone PC's for
that.
2) So our internal maven repository (we use archiva) is not able to
proxy.
3) I build the maven-ejb-plugin myself at home (with proper internet
connection)
4) Did a mvn install
5) Tried it at home and it works.
6) I took the resulting jar to work and used mvn deploy:deployf-file to
get it in the internal repository.
7) Using it gives me the following result
..
[INFO] [compiler:compile]
Compiling 110 source files to
d:\Workspaces\projects\xpolejb\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] No sources to compile
[INFO] [surefire:test]
[INFO] Tests are skipped.
-----------------------------------------------------
this realm =
app0.child-container[org.apache.maven.plugins:maven-ejb-plugin]
urls[0] =
file:/d:/Dev/Tools/maven/maven-2.0.4/../Repository/org/apache/maven/pl
ugins/maven-ejb-plugin/2.1-SNAPSHOT/maven-ejb-plugin-2.1-SNAPSHOT.jar
Number of imports: 0
this realm = plexus.core.maven
urls[0] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/commons-cli-1.0.jar
urls[1] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/doxia-sink-api-1.0-alpha-7.ja
r
urls[2] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/jsch-0.1.24.jar
urls[3] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-artifact-2.0.4.jar
urls[4] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-artifact-manager-2.0.4.
jar
urls[5] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-core-2.0.4.jar
urls[6] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-error-diagnostics-2.0.4
jar
urls[7] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-model-2.0.4.jar
urls[8] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-monitor-2.0.4.jar
urls[9] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-api-2.0.4.jar
urls[10] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-descriptor-2.0.
4.jar
urls[11] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-parameter-docum
enter-2.0.4.jar
urls[12] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-registry-2.0.4.
jar
urls[13] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-profile-2.0.4.jar
urls[14] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-project-2.0.4.jar
urls[15] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-reporting-api-2.0.4.ja
r
urls[16] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-repository-metadata-2.
0.4.jar
urls[17] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-settings-2.0.4.jar
urls[18] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/plexus-interactivity-api-1.0
-alpha-4.jar
urls[19] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-file-1.0-alpha-7.jar
urls[20] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-http-lightweight-1.0-a
lpha-6.jar
urls[21] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-provider-api-1.0-alpha
-6.jar
urls[22] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-ssh-1.0-alpha-7.jar
urls[23] =
file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-ssh-external-1.0-alpha
-6.jar
Number of imports: 0
this realm = plexus.core
urls[0] =
file:/d:/Dev/Tools/maven/maven-2.0.4/core/plexus-container-default-1.0
-alpha-9.jar
urls[1] = file:/d:/Dev/Tools/maven/maven-2.0.4/core/plexus-utils-1.1.jar
Number of imports: 0
-----------------------------------------------------
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal
'org.apache.maven.plu
gins:maven-ejb-plugin:2.1-SNAPSHOT:ejb': Unable to find the mojo
'org.apache.mav
en.plugins:maven-ejb-plugin:2.1-SNAPSHOT:ejb' in the plugin
'org.apache.maven.pl
ugins:maven-ejb-plugin'
org/codehaus/plexus/archiver/jar/ManifestException
..
I probably did something wrong, but I have no clue what.
Hope someone can provide me with some clues how to resolve this.
Regards,
Minto van der Sluis
DISCLAIMER
De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken aan andere personen dan de geadresseerde. Indien u deze e-mail abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af voor en/of in verband met alle gevolgen en/of schade van een onjuiste of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het gebruik van Internet e-mail brengt zekere risico's met zich. Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium door de Politie Amsterdam-Amstelland van de hand gewezen.
Re: How to deploy maven plugin jar to inhouse repository
Posted by Nick Stolwijk <ni...@planet.nl>.
If you change the distributionManagement in the pom file of the plugin
you want to deploy to point to your own repository, you can do a "mvn
deploy" to deploy it to there.
Hth,
Nick Stolwijk
Minto.van.der.Sluis@amsterdam.politie.nl wrote:
> Hi all,
>
> Does anyone know how to deploy a maven plugin jar to an inhouse
> repository (no proxy)? I tried deploy:deploy-file like this:
>
> mvn deploy:deploy-file -DgroupId=org.apache.maven.plugins
> -DartifactId=maven-ejb-plugin -Dversion=2.1-SNAPSHOT
> -Dpackaging=maven-plugin
> -Durl=file://R:\maven\repositories\isc-external-snapshots
> -Dfile=d:\maven-ejb-plugin-2.1-SNAPSHOT.jar
>
> Unfortunately the result does not look the same as other entries in the
> repository. For instance the file .metadata-maven2-snapshot-apache and
> the timestamped version of the snapshot are missing.
>
> Let me explain my situation:
> 1) At work we have no internet connection, we use stand-alone PC's for
> that.
> 2) So our internal maven repository (we use archiva) is not able to
> proxy.
> 3) I build the maven-ejb-plugin myself at home (with proper internet
> connection)
> 4) Did a mvn install
> 5) Tried it at home and it works.
> 6) I took the resulting jar to work and used mvn deploy:deployf-file to
> get it in the internal repository.
> 7) Using it gives me the following result
>
> ..
> [INFO] [compiler:compile]
> Compiling 110 source files to
> d:\Workspaces\projects\xpolejb\target\classes
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] No sources to compile
> [INFO] [surefire:test]
> [INFO] Tests are skipped.
> -----------------------------------------------------
> this realm =
> app0.child-container[org.apache.maven.plugins:maven-ejb-plugin]
> urls[0] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/../Repository/org/apache/maven/pl
> ugins/maven-ejb-plugin/2.1-SNAPSHOT/maven-ejb-plugin-2.1-SNAPSHOT.jar
> Number of imports: 0
>
>
> this realm = plexus.core.maven
> urls[0] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/commons-cli-1.0.jar
> urls[1] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/doxia-sink-api-1.0-alpha-7.ja
> r
> urls[2] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/jsch-0.1.24.jar
> urls[3] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-artifact-2.0.4.jar
> urls[4] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-artifact-manager-2.0.4.
> jar
> urls[5] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-core-2.0.4.jar
> urls[6] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-error-diagnostics-2.0.4
> jar
> urls[7] = file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-model-2.0.4.jar
> urls[8] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-monitor-2.0.4.jar
> urls[9] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-api-2.0.4.jar
> urls[10] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-descriptor-2.0.
> 4.jar
> urls[11] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-parameter-docum
> enter-2.0.4.jar
> urls[12] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-plugin-registry-2.0.4.
> jar
> urls[13] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-profile-2.0.4.jar
> urls[14] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-project-2.0.4.jar
> urls[15] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-reporting-api-2.0.4.ja
> r
> urls[16] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-repository-metadata-2.
> 0.4.jar
> urls[17] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/maven-settings-2.0.4.jar
> urls[18] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/plexus-interactivity-api-1.0
> -alpha-4.jar
> urls[19] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-file-1.0-alpha-7.jar
> urls[20] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-http-lightweight-1.0-a
> lpha-6.jar
> urls[21] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-provider-api-1.0-alpha
> -6.jar
> urls[22] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-ssh-1.0-alpha-7.jar
> urls[23] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/lib/wagon-ssh-external-1.0-alpha
> -6.jar
> Number of imports: 0
>
>
> this realm = plexus.core
> urls[0] =
> file:/d:/Dev/Tools/maven/maven-2.0.4/core/plexus-container-default-1.0
> -alpha-9.jar
> urls[1] = file:/d:/Dev/Tools/maven/maven-2.0.4/core/plexus-utils-1.1.jar
> Number of imports: 0
> -----------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Internal error in the plugin manager executing goal
> 'org.apache.maven.plu
> gins:maven-ejb-plugin:2.1-SNAPSHOT:ejb': Unable to find the mojo
> 'org.apache.mav
> en.plugins:maven-ejb-plugin:2.1-SNAPSHOT:ejb' in the plugin
> 'org.apache.maven.pl
> ugins:maven-ejb-plugin'
> org/codehaus/plexus/archiver/jar/ManifestException
> ..
>
> I probably did something wrong, but I have no clue what.
>
> Hope someone can provide me with some clues how to resolve this.
>
> Regards,
>
> Minto van der Sluis
>
>
>
> DISCLAIMER
> De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken aan andere personen dan de geadresseerde. Indien u deze e-mail abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender op de hoogte, waarbij u bij deze gevraagd wordt het originele bericht te vernietigen. Politie Amsterdam-Amstelland is niet verantwoordelijk voor de inhoud van deze e-mail en wijst iedere aansprakelijkheid af voor en/of in verband met alle gevolgen en/of schade van een onjuiste of onvolledige verzending ervan. Tenzij uitdrukkelijk het tegendeel blijkt, kunnen aan dit bericht geen rechten worden ontleend. Het gebruik van Internet e-mail brengt zekere risico's met zich. Daarom wordt iedere aansprakelijkheid voor het gebruik van dit medium door de Politie Amsterdam-Amstelland van de hand gewezen.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org