Thanks guys, will do this tonight.  Arrghh, mvn install, not deploy, I don't
how I got those confused!
-aps

On Feb 11, 2008 5:56 PM, Vincent Siveton <[EMAIL PROTECTED]> wrote:

> Hi,
>
> More comments inside...
>
> 2008/2/11, Dennis Lundberg <[EMAIL PROTECTED]>:
> > Alexander Sack wrote:
> > > Hey Vincent:
> > > No problem.  I would love to.  I have a really really stupid question.
> > >
> > > What I've done is:
> > >
> > > 1)  Checked out the 2.0.x trunk
> >
> > This is not necessary, you can use a regular Maven release.
> >
>
> Do a co from
> https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin
>
> Cheers,
>
> Vincent
>
> > > 2)  Built a new maven-javadoc-plugin
> > > 3)  Used mvn deploy:deploy-file to install it on my test machine
> >
> > To install your version of the plugin into your local repository, use
> > the command instead: mvn install
> >
> > > 4)  Change my project's pom file that uses javadoc to include
> <version>
> > > 2.4-SNAPSHOT</version>
> > > 5)  Execute mvn site
> > > 6)  Stair blankly at the screen as I get the can't fine 
> > > 2.4-SNAPSHOTmessage
> > >
> > > I've tried using the 2.0.8 stable as well as the bootstrapped
> > > 2.0.9-SNAPSHOTI built with no luck (I've even built offline (-o)).  It
> > > can't seem to find
> > > my new javadoc plugin jar file I deployed.   I noticed that
> > > deploy:deploy-file on 2.0.8 adds a date as part of the jar file (2.0.4did
> > > not do this).  Have snapshot deployment/handling changed?  What am I
> doing
> > > wrong?
> > >
> > > Here is my deploy line:
> > >
> > > mvn deploy:deploy-file
> > > -Dversion=2.4-SNAPSHOT-DartifactId=maven-javadoc-plugin -DgroupId=
> > > org.apache.maven.plugins -Dpackaging=jar -Dfile=/root/maven-
> > > javadoc-plugin-2.4-SNAPSHOT.jar -url=file:///root/.m2/repository
> > >
> > > Thanks!
> > >
> > > -aps
> > >
> > > On Feb 11, 2008 7:22 AM, Vincent Siveton <[EMAIL PROTECTED]>
> wrote:
> > >
> > >> Alexander,
> > >>
> > >> Please open an issue, and if you want propose a patch :)
> > >> I guess that the pattern used should also work with -J-version
> > >>
> > >> Vincent
> > >>
> > >> 2008/2/10, Alexander Sack <[EMAIL PROTECTED]>:
> > >>> Exactly.  The use of "-fullversion" is really for internal use as
> per
> > >>> Benjamin and typically the format is "java version <version>" or
> > >> something
> > >>> of that elk which is very easy to parse.  Again, I would rely on the
> > >>> javadocVersion tag as a backup.
> > >>> Thanks!
> > >>>
> > >>> -aps
> > >>>
> > >>> On Feb 10, 2008 3:22 PM, Benjamin Bentmann <
> [EMAIL PROTECTED]>
> > >>> wrote:
> > >>>
> > >>>>>> Is there any reason again why it can't use "-version?"
> > >>>>>>
> > >>>>> -version gives a lot of unuseful informations.
> > >>>> The unuseful information should not be a problem for the version
> > >> parsing.
> > >>>> On
> > >>>> the other hand, "-fullversion" is "for internal use only" according
> to
> > >> [0]
> > >>>> so it seems wise to switch to "-version" and rely on a
> > >> public/documentated
> > >>>> command line switch.
> > >>>>
> > >>>> Regards,
> > >>>>
> > >>>>
> > >>>> Benjamin Bentmann
> > >>>>
> > >>>>
> > >>>> [0] http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4127994
> > >>>>
> > >>>>
> > >>>
> > >>> --
> > >>> "What lies behind us and what lies in front of us is of little
> concern
> > >> to
> > >>> what lies within us." -Ralph Waldo Emerson
> > >>>
> > >
> > >
> > >
> >
> >
> > --
> > Dennis Lundberg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>



-- 
"What lies behind us and what lies in front of us is of little concern to
what lies within us." -Ralph Waldo Emerson

Reply via email to