You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Thorsten Heit <th...@xtramind.com> on 2006/03/22 19:20:22 UTC
[m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm trying to use the beta-4 snapshot of the maven-javadoc-plugin and
wanted to deploy it on my local proxy. The plugin is deployed via:
$ mvn compile jar:jar
(lots of messages)
$ cd target
$ mvn deploy:deploy-file -DrepositoryId=<my_proxy>
- -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml
- -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
(lots of messages)
The plugin jar gets copied to the proxy, and so far everything seems to
be fine. In another project, I added the following lines to my pom.xml:
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-javadoc-plugin</artifactId>
<version>2.0-beta-4-SNAPSHOT</version>
<configuration>
<tag>created</tag>
<maxmemory>256m</maxmemory>
</configuration>
</plugin>
...
</plugins>
</build>
Unfortunately the plugin cannot be downloaded from my proxy:
$ mvn clean
[INFO] Scanning for projects...
[INFO]
-
----------------------------------------------------------------------------
[INFO] Building base Repository
[INFO] task-segment: [clean]
[INFO]
-
----------------------------------------------------------------------------
Downloading:
http://maven_proxy:9999/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.jar
[INFO]
-
----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
-
----------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-javadoc-plugin
Version: 2.0-beta-4-20060322.180042-2
Reason: Unable to locate resource in repository
org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.0-beta-4-20060322.180042-2
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
bender (http://maven_proxy:9999/repository),
snapshots-codehaus-org (http://snapshots.maven.codehaus.org/maven2)
which is strange because I just deployed it. I looked into the proxy
directories and wondered that the files are named differently:
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
When I manually rename the -1.jar* files to -2.jar* the plugin is
downloadable, and "mvn clean" above will work...
Is there a reason for this behaviour? Is this a bug?
Regards
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFEIZVlQvObkgCcDe0RAjz7AJ9InFVTGyFAvwOSuy5W8BGujTkUHwCglbtO
9S4ieHuxassG1Cmg4sDUots=
=37Im
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Wayne Fay <wa...@gmail.com>.
Not sure but sounds reasonable. Give it a try. If it doesn't work,
then come back and complain about it, and ask for more help. ;-)
Wayne
On 3/30/06, Thorsten Heit <th...@xtramind.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Wayne,
>
> > You'll need to add the Maven SNAPSHOT repository to your pom. This is
> > such a common topic on the User list...
>
> Sorry, forgot to mention that I already have this...
>
> Unfortunately http://snapshots.maven.codehaus.org/maven2 only contains
> version 2.1-SNAPSHOT of the deploy plugin so it seems that I have to
> build the deploy plugin from source, right? If so, how can I tell Maven
> to use that self-compiled plugin? Is it enough to deploy it in my local
> repository via deploy:deploy-file?
>
>
> Regards
>
> Thorsten
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (MingW32)
>
> iD8DBQFELBeQQvObkgCcDe0RAh1yAKDmXbjEby2/X7bAvfadg9+LfuRg+QCgu0lL
> zz6/lDerfhPbYM/J9GNM4KA=
> =buNH
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Thorsten Heit <th...@xtramind.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Wayne,
> You'll need to add the Maven SNAPSHOT repository to your pom. This is
> such a common topic on the User list...
Sorry, forgot to mention that I already have this...
Unfortunately http://snapshots.maven.codehaus.org/maven2 only contains
version 2.1-SNAPSHOT of the deploy plugin so it seems that I have to
build the deploy plugin from source, right? If so, how can I tell Maven
to use that self-compiled plugin? Is it enough to deploy it in my local
repository via deploy:deploy-file?
Regards
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFELBeQQvObkgCcDe0RAh1yAKDmXbjEby2/X7bAvfadg9+LfuRg+QCgu0lL
zz6/lDerfhPbYM/J9GNM4KA=
=buNH
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Wayne Fay <wa...@gmail.com>.
You'll need to add the Maven SNAPSHOT repository to your pom. This is
such a common topic on the User list...
<repository>
<id>Maven Snapshots</id>
<url>http://snapshots.maven.codehaus.org/maven2/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</repository>
<pluginRepository>
<id>Maven Snapshots</id>
<url>http://snapshots.maven.codehaus.org/maven2/</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>false</enabled>
</releases>
</pluginRepository>
Wayne
On 3/30/06, Thorsten Heit <th...@xtramind.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> > which is strange because I just deployed it. I looked into the proxy
> > directories and wondered that the files are named differently:
> >
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
> > * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
> >
> > When I manually rename the -1.jar* files to -2.jar* the plugin is
> > downloadable, and "mvn clean" above will work...
>
> According to JIRA (http://jira.codehaus.org/browse/MDEPLOY-27) this
> should be fixed in version 2.3 of the maven-deploy-plugin (actually I'm
> using 2.2, according to mvn -X). Unfortunately this version isn't yet
> available.
>
> Can someone tell me what I have to do to use a newer snapshot version of
> that plugin?
>
>
> Regards
>
> Thorsten
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (MingW32)
>
> iD8DBQFEK/DIQvObkgCcDe0RAllaAJ4prHIS30C/lWmyVzOfomg4GQoJTQCg2qk8
> Omf8KDQvR6l8Bpj1imtFRNE=
> =3OI2
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Thorsten Heit <th...@xtramind.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
> which is strange because I just deployed it. I looked into the proxy
> directories and wondered that the files are named differently:
>
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
> * maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
>
> When I manually rename the -1.jar* files to -2.jar* the plugin is
> downloadable, and "mvn clean" above will work...
According to JIRA (http://jira.codehaus.org/browse/MDEPLOY-27) this
should be fixed in version 2.3 of the maven-deploy-plugin (actually I'm
using 2.2, according to mvn -X). Unfortunately this version isn't yet
available.
Can someone tell me what I have to do to use a newer snapshot version of
that plugin?
Regards
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFEK/DIQvObkgCcDe0RAllaAJ4prHIS30C/lWmyVzOfomg4GQoJTQCg2qk8
Omf8KDQvR6l8Bpj1imtFRNE=
=3OI2
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Thorsten Heit <th...@xtramind.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> Sure looks like a bug to me.
>
> Might want to file this log along with your pom.xml in Jira?
Done: http://jira.codehaus.org/browse/MDEPLOY-27
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFEIsVuQvObkgCcDe0RAkx3AKD3WXPUg/UZJ7ovtUmJr4FtcBCfOwCg/n1C
61KHZpIIOH8rLxoZgOd0l7A=
=ovPV
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Wayne Fay <wa...@gmail.com>.
Sure looks like a bug to me.
Might want to file this log along with your pom.xml in Jira?
Wayne
On 3/23/06, Thorsten Heit <th...@xtramind.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Kenney,
>
> > I remember a bug like this, but it was fixed long ago. Perhaps you're
> > using an old version of Maven 2? Maybe your proxy needs updating..
>
> Both are the newest versions (Maven 2.0.2; maven-proxy-standalone-0.2
> from maven-proxy.codehaus.org).
>
> > What version of maven2 are you using? What version of the deploy plugin is
> > used? (run mvn -X to find out.)
>
> It seems to me to be a bug of the plugin deployment:
>
> $ mvn -X deploy:deploy-file -DrepositoryId=bender -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
> + Error stacktraces are turned on.
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und Einstellungen\heit\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from: 'c:\Programme\Apache\maven-2.0.2\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'deploy'.
> [DEBUG] maven-deploy-plugin: resolved to version 2.2 from repository central
> [DEBUG] Retrieving parent-POM from the repository for project: null:maven-deploy-plugin:maven-plugin:2.2
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [deploy:deploy-file] (aggregator-style)
> [INFO] ----------------------------------------------------------------------------
> [DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0.1
> [DEBUG] org.apache.maven:maven-project:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0.1
> [DEBUG] org.apache.maven:maven-model:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-utils:jar:1.0.5
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0.1
> [DEBUG] org.apache.maven:maven-profile:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: null:plexus-container-default:jar:1.0-alpha-9
> [DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-containers:pom:1.0.3
> [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0.1
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0.1
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.1 (selected for runtime)
> [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0.1
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0.1
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.1 (removed - nearer found: 2.0)
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (removed - nearer found: 1.0-alpha-9)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (removed - nearer found: 2.0.1)
> [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (removed - nearer found: 2.0)
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
> [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.2:deploy-file' -->
> [DEBUG] (f) file = c:\devel\maven\plugins\maven-javadoc-plugin\target\maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
> [DEBUG] (s) localRepository = [local] -> file://C:\Dokumente und Einstellungen\heit\.m2\repository
> [DEBUG] (f) pomFile = c:\devel\maven\plugins\maven-javadoc-plugin\target\exported-pom.xml
> [DEBUG] (f) repositoryId = bender
> [DEBUG] (f) uniqueVersion = true
> [DEBUG] (f) url = file://H:/maven-proxy/target/repo-local
> [DEBUG] -- end configuration --
> [INFO] [deploy:deploy-file]
> [INFO] Retrieving previous build number from bender
> [DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
> [DEBUG] not adding permissions to wagon connection
> Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-1.jar
> 26K uploaded
> [INFO] Retrieving previous metadata from bender
> [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin' could not be found on repository: bender
> [INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
> [DEBUG] not adding permissions to wagon connection
> [INFO] Retrieving previous metadata from bender
> [DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
> [INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
> [DEBUG] not adding permissions to wagon connection
> [INFO] Retrieving previous build number from bender
> [DEBUG] not adding permissions to wagon connection
> Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-2.pom
> 10K uploaded
> [INFO] Retrieving previous metadata from bender
> [INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
> [DEBUG] not adding permissions to wagon connection
> [INFO] Retrieving previous metadata from bender
> [INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
> [DEBUG] not adding permissions to wagon connection
> [INFO] ----------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO] ----------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Mar 23 12:01:38 CET 2006
> [INFO] Final Memory: 2M/4M
> [INFO] ----------------------------------------------------------------------------
>
>
> As you can see in the debug output, when Maven uploads the metadata for the plugin,
> the POM file has a different build number than the uploaded Jar. It seems that the
> build number is increased during the Jar and POM file uploads...
>
>
> Is this a normal (correct) behaviour of the deployment plugin? Or is it simply a
> bug/feature? ;-)
>
>
> Regards
>
> Thorsten
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (MingW32)
>
> iD8DBQFEIoIHQvObkgCcDe0RAqH6AJ9GReUYHQozGGDQZkJ23zkyyuMmdgCfQMP7
> gkcSTaOTGampacBqhZbKrdM=
> =dJpk
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Thorsten Heit <th...@xtramind.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Kenney,
> I remember a bug like this, but it was fixed long ago. Perhaps you're
> using an old version of Maven 2? Maybe your proxy needs updating..
Both are the newest versions (Maven 2.0.2; maven-proxy-standalone-0.2
from maven-proxy.codehaus.org).
> What version of maven2 are you using? What version of the deploy plugin is
> used? (run mvn -X to find out.)
It seems to me to be a bug of the plugin deployment:
$ mvn -X deploy:deploy-file -DrepositoryId=bender -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente und Einstellungen\heit\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from: 'c:\Programme\Apache\maven-2.0.2\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'deploy'.
[DEBUG] maven-deploy-plugin: resolved to version 2.2 from repository central
[DEBUG] Retrieving parent-POM from the repository for project: null:maven-deploy-plugin:maven-plugin:2.2
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [deploy:deploy-file] (aggregator-style)
[INFO] ----------------------------------------------------------------------------
[DEBUG] org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:2.2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0.1
[DEBUG] org.apache.maven:maven-project:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0.1
[DEBUG] org.apache.maven:maven-model:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: null:plexus-utils:jar:1.0.5
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: null:maven-profile:jar:2.0.1
[DEBUG] org.apache.maven:maven-profile:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: null:plexus-container-default:jar:1.0-alpha-9
[DEBUG] Retrieving parent-POM from the repository for project: org.codehaus.plexus:plexus-containers:pom:1.0.3
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.5 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0.1
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0.1
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.1 (selected for runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0.1
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-plugin-api:jar:2.0.1
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.1 (removed - nearer found: 2.0)
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (removed - nearer found: 1.0-alpha-9)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (removed - nearer found: 2.0.1)
[DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.1 (removed - nearer found: 2.0)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (removed - nearer found: 1.0.5)
[DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.2:deploy-file' -->
[DEBUG] (f) file = c:\devel\maven\plugins\maven-javadoc-plugin\target\maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
[DEBUG] (s) localRepository = [local] -> file://C:\Dokumente und Einstellungen\heit\.m2\repository
[DEBUG] (f) pomFile = c:\devel\maven\plugins\maven-javadoc-plugin\target\exported-pom.xml
[DEBUG] (f) repositoryId = bender
[DEBUG] (f) uniqueVersion = true
[DEBUG] (f) url = file://H:/maven-proxy/target/repo-local
[DEBUG] -- end configuration --
[INFO] [deploy:deploy-file]
[INFO] Retrieving previous build number from bender
[DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
[DEBUG] not adding permissions to wagon connection
Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-1.jar
26K uploaded
[INFO] Retrieving previous metadata from bender
[DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin' could not be found on repository: bender
[INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
[DEBUG] not adding permissions to wagon connection
[INFO] Retrieving previous metadata from bender
[DEBUG] repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT' could not be found on repository: bender
[INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
[DEBUG] not adding permissions to wagon connection
[INFO] Retrieving previous build number from bender
[DEBUG] not adding permissions to wagon connection
Uploading: file://H:/maven-proxy/target/repo-local/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060323.110138-2.pom
10K uploaded
[INFO] Retrieving previous metadata from bender
[INFO] Uploading repository metadata for: 'artifact org.apache.maven.plugins:maven-javadoc-plugin'
[DEBUG] not adding permissions to wagon connection
[INFO] Retrieving previous metadata from bender
[INFO] Uploading repository metadata for: 'snapshot org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-4-SNAPSHOT'
[DEBUG] not adding permissions to wagon connection
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Mar 23 12:01:38 CET 2006
[INFO] Final Memory: 2M/4M
[INFO] ----------------------------------------------------------------------------
As you can see in the debug output, when Maven uploads the metadata for the plugin,
the POM file has a different build number than the uploaded Jar. It seems that the
build number is increased during the Jar and POM file uploads...
Is this a normal (correct) behaviour of the deployment plugin? Or is it simply a
bug/feature? ;-)
Regards
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFEIoIHQvObkgCcDe0RAqH6AJ9GReUYHQozGGDQZkJ23zkyyuMmdgCfQMP7
gkcSTaOTGampacBqhZbKrdM=
=dJpk
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of
maven-javadoc-plugin
Posted by Kenney Westerhof <ke...@apache.org>.
On Thu, 23 Mar 2006, Odea Ching wrote:
Hi Thorsten,
I remember a bug like this, but it was fixed long ago. Perhaps you're
using an old version of Maven 2? Maybe your proxy needs updating..
What version of maven2 are you using? What version of the deploy plugin is
used? (run mvn -X to find out.)
-- Kenney
> Hi Thorsten,
>
> mvn deploy automatically appends the timestamp when it deploys the jar
> file in the repository when it is a snapshot version.
> If you want to disable this, you would have to specify a version of the
> plugin instead of specifying it as a snapshot.
>
> Thanks,
> Odea
>
>
>
> Thorsten Heit wrote:
>
> >-----BEGIN PGP SIGNED MESSAGE-----
> >Hash: SHA1
> >
> >Hi,
> >
> >I'm trying to use the beta-4 snapshot of the maven-javadoc-plugin and
> >wanted to deploy it on my local proxy. The plugin is deployed via:
> >
> >$ mvn compile jar:jar
> >(lots of messages)
> >
> >$ cd target
> >$ mvn deploy:deploy-file -DrepositoryId=<my_proxy>
> >- -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml
> >- -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
> >(lots of messages)
> >
> >The plugin jar gets copied to the proxy, and so far everything seems to
> >be fine. In another project, I added the following lines to my pom.xml:
> >
> ><build>
> > <plugins>
> > <plugin>
> > <groupId>org.apache.maven.plugins</groupId>
> > <artifactId>maven-javadoc-plugin</artifactId>
> > <version>2.0-beta-4-SNAPSHOT</version>
> > <configuration>
> > <tag>created</tag>
> > <maxmemory>256m</maxmemory>
> > </configuration>
> > </plugin>
> > ...
> > </plugins>
> ></build>
> >
> >Unfortunately the plugin cannot be downloaded from my proxy:
> >
> >
> >$ mvn clean
> >[INFO] Scanning for projects...
> >[INFO]
> >-
> >----------------------------------------------------------------------------
> >[INFO] Building base Repository
> >[INFO] task-segment: [clean]
> >[INFO]
> >-
> >----------------------------------------------------------------------------
> >Downloading:
> >http://maven_proxy:9999/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.jar
> >[INFO]
> >-
> >----------------------------------------------------------------------------
> >[ERROR] BUILD ERROR
> >[INFO]
> >-
> >----------------------------------------------------------------------------
> >[INFO] Failed to resolve artifact.
> >
> >GroupId: org.apache.maven.plugins
> >ArtifactId: maven-javadoc-plugin
> >Version: 2.0-beta-4-20060322.180042-2
> >
> >Reason: Unable to locate resource in repository
> >
> >
> >org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.0-beta-4-20060322.180042-2
> >
> >from the specified remote repositories:
> > central (http://repo1.maven.org/maven2),
> > bender (http://maven_proxy:9999/repository),
> > snapshots-codehaus-org (http://snapshots.maven.codehaus.org/maven2)
> >
> >
> >which is strange because I just deployed it. I looked into the proxy
> >directories and wondered that the files are named differently:
> >
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
> >* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
> >
> >When I manually rename the -1.jar* files to -2.jar* the plugin is
> >downloadable, and "mvn clean" above will work...
> >
> >Is there a reason for this behaviour? Is this a bug?
> >
> >
> >Regards
> >
> >Thorsten
> >-----BEGIN PGP SIGNATURE-----
> >Version: GnuPG v1.4.2.2 (MingW32)
> >
> >iD8DBQFEIZVlQvObkgCcDe0RAjz7AJ9InFVTGyFAvwOSuy5W8BGujTkUHwCglbtO
> >9S4ieHuxassG1Cmg4sDUots=
> >=37Im
> >-----END PGP SIGNATURE-----
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Thorsten Heit <th...@xtramind.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
> mvn deploy automatically appends the timestamp when it deploys the jar
> file in the repository when it is a snapshot version.
> If you want to disable this, you would have to specify a version of the
> plugin instead of specifying it as a snapshot.
The problem isn't the timestamp, but obviously a build number that is
appended at the end, right before the file name extension...
Thorsten
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)
iD8DBQFEIn6RQvObkgCcDe0RAqAZAJwPnNQh15S8Sc+Xu5J8E5fM18ILXQCgysOa
paQJJ6Pd+tZ2bAXHtHRZHWY=
=/N9r
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Improper build number after deploying a snapshot of maven-javadoc-plugin
Posted by Odea Ching <oc...@exist.com>.
Hi Thorsten,
mvn deploy automatically appends the timestamp when it deploys the jar
file in the repository when it is a snapshot version.
If you want to disable this, you would have to specify a version of the
plugin instead of specifying it as a snapshot.
Thanks,
Odea
Thorsten Heit wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Hi,
>
>I'm trying to use the beta-4 snapshot of the maven-javadoc-plugin and
>wanted to deploy it on my local proxy. The plugin is deployed via:
>
>$ mvn compile jar:jar
>(lots of messages)
>
>$ cd target
>$ mvn deploy:deploy-file -DrepositoryId=<my_proxy>
>- -Durl=file://H:/maven-proxy/target/repo-local -DpomFile=exported-pom.xml
>- -Dfile=maven-javadoc-plugin-2.0-beta-4-SNAPSHOT.jar
>(lots of messages)
>
>The plugin jar gets copied to the proxy, and so far everything seems to
>be fine. In another project, I added the following lines to my pom.xml:
>
><build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-javadoc-plugin</artifactId>
> <version>2.0-beta-4-SNAPSHOT</version>
> <configuration>
> <tag>created</tag>
> <maxmemory>256m</maxmemory>
> </configuration>
> </plugin>
> ...
> </plugins>
></build>
>
>Unfortunately the plugin cannot be downloaded from my proxy:
>
>
>$ mvn clean
>[INFO] Scanning for projects...
>[INFO]
>-
>----------------------------------------------------------------------------
>[INFO] Building base Repository
>[INFO] task-segment: [clean]
>[INFO]
>-
>----------------------------------------------------------------------------
>Downloading:
>http://maven_proxy:9999/repository/org/apache/maven/plugins/maven-javadoc-plugin/2.0-beta-4-SNAPSHOT/maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.jar
>[INFO]
>-
>----------------------------------------------------------------------------
>[ERROR] BUILD ERROR
>[INFO]
>-
>----------------------------------------------------------------------------
>[INFO] Failed to resolve artifact.
>
>GroupId: org.apache.maven.plugins
>ArtifactId: maven-javadoc-plugin
>Version: 2.0-beta-4-20060322.180042-2
>
>Reason: Unable to locate resource in repository
>
>
>org.apache.maven.plugins:maven-javadoc-plugin:maven-plugin:2.0-beta-4-20060322.180042-2
>
>from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> bender (http://maven_proxy:9999/repository),
> snapshots-codehaus-org (http://snapshots.maven.codehaus.org/maven2)
>
>
>which is strange because I just deployed it. I looked into the proxy
>directories and wondered that the files are named differently:
>
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.md5
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-1.jar.sha1
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.md5
>* maven-javadoc-plugin-2.0-beta-4-20060322.180042-2.pom.sha1
>
>When I manually rename the -1.jar* files to -2.jar* the plugin is
>downloadable, and "mvn clean" above will work...
>
>Is there a reason for this behaviour? Is this a bug?
>
>
>Regards
>
>Thorsten
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v1.4.2.2 (MingW32)
>
>iD8DBQFEIZVlQvObkgCcDe0RAjz7AJ9InFVTGyFAvwOSuy5W8BGujTkUHwCglbtO
>9S4ieHuxassG1Cmg4sDUots=
>=37Im
>-----END PGP SIGNATURE-----
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org