-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=
- -Durl=file:/
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:
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.)
-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 snaps
-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.or
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 <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Kenney,
>
> > I remember a bug like this, but it was fixed long ago. Perhaps you're
> > u
-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)
iD8DBQFEIsVuQvObkgCcDe0RAkx3A
-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.18004
You'll need to add the Maven SNAPSHOT repository to your pom. This is
such a common topic on the User list...
Maven Snapshots
http://snapshots.maven.codehaus.org/maven2/
true
false
Maven Snapshots
http://snapshots.
-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
v
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 <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Wayne,
>
> > You'll need to add the Maven SNAPSHO
11 matches
Mail list logo