The Eclipse and Site plugins are both still marked as beta. They are very close to a release.
After that, no beta plugins will be released into the main repository, so you won't have to worry about the automated update aspect. Additionally, you can lock your projects to particular versions of plugins if you desire. Regards, Brett On 11/5/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote: > Meant to say: > > "Would be nice to hear from the Maven team on this topic" > > On 11/4/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote: > > > > Would be nice to hea > > > > On 11/4/05, Thomas Van de Velde <[EMAIL PROTECTED]> wrote: > > > > > > Agreed. I think care should be taken with plugins that get automatically > > > updated as this has already created many unpleasant surprises. I think by > > > default only "stable" versions should be distributed as part of the Maven > > > core. Something like xxx-2.0-beta-2 doesn't belong in a production > > > environment. I suggest that by default only stable release are > > > automatically > > > downloaded and make updating to "bleeding-edge" plugins an option. > > > > > > I would never accept the risks that come from automatically downloading > > > beta versions to hunderds of developer workstations. > > > > > > Thomas > > > > > > On 11/4/05, Anuerin Diaz < [EMAIL PROTECTED]> wrote: > > > > > > > > ok, then something must be wrong on my side because i had to declare > > > > the M2_REPO classpath variable to point to my local repository to get > > > > rid of the errors. here is my eclipse classpath file > > > > > > > > <?xml version=" 1.0" encoding="UTF-8"?> > > > > <classpath> > > > > <classpathentry kind="src" path="src/main/java"/> > > > > <classpathentry output="target/test-classes" kind="src" > > > > path="src/test/java"/> > > > > <classpathentry sourcepath="JRE_SRC" kind="var" path="JRE_LIB"/> > > > > <classpathentry kind="var" > > > > path="M2_REPO/com/merlin/tools/ABC-tools/1.0/ABC-tools-1.0.jar"/> > > > > <classpathentry kind="lib" > > > > path="C:/Work/Maintenance/ENV/tools/repository/org/apache/maven/maven-plugin-api/2.0/maven- > > > > plugin-api-2.0.jar"/> > > > > <classpathentry kind="output" path="target/classes"/> > > > > </classpath> > > > > > > > > where i set M2_REPO to point to > > > > "C:/Work/Maintenance/ENV/tools/repository". the weird thing is if i > > > > replace the same string in the kind="lib" element then i get an error. > > > > > > > > i too agree that m2 is being communicated as "production ready" but > > > > still thin on the supporting documentation side. i appreciate the bug > > > > squashing efforts done by the team but this is one of the things that > > > > is considered by management. > > > > > > > > ciao! > > > > > > > > On 11/4/05, Thomas Van de Velde < [EMAIL PROTECTED] > wrote: > > > > > Hi Anuerin, > > > > > > > > > > I think you are wrong :-) > > > > > > > > > > This is clearly a (btw, blocking) bug in the Eclipse plugin. I find > > > > it odd > > > > > that this isn't detected before this version was released, > > > > especially give > > > > > that M2 is communicated as "production ready". This along with the > > > > site > > > > > plugin that generates a nullpointer makes it clear to me that M2 is > > > > not > > > > > ready for large-scale use. > > > > > > > > > > I'd be happy to continue testing and post bugs. Hopefully this gets > > > > ironed > > > > > out quickly. > > > > > > > > > > Thomas > > > > > > > > > > On 11/3/05, Anuerin Diaz <[EMAIL PROTECTED] > wrote: > > > > > > > > > > > > hi, > > > > > > > > > > > > doesnt M2_REPO supposed to resolve to the user's local repository? > > > > > > > > > > if that is the case and assuming the local repository is > > > > > > "c:\repository" then the final path will be > > > > > > "c:\repository/C:/dev/Java/jdk1.5.0_04/jre/../lib/tools.jar" which > > > > i > > > > > > think is already invalid. > > > > > > > > > > > > i am a new maven user so i only encountered this yesterday when i > > > > > > tried using the eclipse:eclipse goal. i had to create the M2_REPO > > > > > > eclipse variable to let my plugin see the Mojo classes. > > > > > > > > > > > > thought there is a large possibility that i might be wrong. > > > > > > > > > > > > ciao! > > > > > > > > > > > > On 11/3/05, Thomas Van de Velde < [EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > > > > > > > When generating the Eclipse classpath, I am getting this: > > > > > > > > > > > > > > <classpathentry kind="var" > > > > > > > path="M2_REPO/C:/dev/Java/jdk1.5.0_04/jre/../lib/tools.jar"/ > > > > > > > > > > > > > > This used to work a couple of days ago and now all of a sudden I > > > > get > > > > > > this > > > > > > > error. > > > > > > > > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > "Programming, an artform that fights back" > > > > > > > > > > > > Anuerin G. Diaz > > > > > > Registered Linux User #246176 > > > > > > Friendly Linux Board @ http://mandrivausers.org/index.php > > > > > > http://capsule.ramfree17.org , when you absolutely have nothing > > > > else > > > > > > better to do > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > "Programming, an artform that fights back" > > > > > > > > Anuerin G. Diaz > > > > Registered Linux User #246176 > > > > Friendly Linux Board @ http://mandrivausers.org/index.php > > > > http://capsule.ramfree17.org , when you absolutely have nothing else > > > > better to do > > > > > > > > --------------------------------------------------------------------- > > > > 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]
