Jason, what is the status of the eclipse plugin release? Should I do the release from my machine? As soon as this release is out I will start fixing and refactoring tests so that they will work on any os...
fabrizio On 12/31/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 31 Dec 06, at 5:35 AM 31 Dec 06, Fabrizio Giustina wrote: > Hi Jason, > maybe the problem is not on the OS, I was just able to reproduce your > error on Windows: > [ERROR] Nonexistent component: > org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-eclipse- > plugin:2.3-SNAPSHOT:add-maven-repo > > this is exactly what happens when I try to install the plugin using > java 6.0! Using java 5 everything works as expected. Not sure if the > problem is in the testing framework or in maven itself at the end.... > Which jdk did you use on linux? If it was 6, could you try with a > different version? > I don't have Java 6.0 anywhere. I was using Java 5 when trying to release the Eclipse plugin. > A side note: while testing with java 6 I realized that the eclipse > plugin wasn't correctly writing the configuration for wtp projects > configured with a version 6 compiler: eclipse requires the version to > be "6.0" and not "6". Since it's a very minimal change and the problem > is pretty bad (pom with a "6" jdk target version result in unusable > projects in eclipse) I am going to commit this small fix: I hope it's > acceptable to keep the vote result valid after this change in svn, if > you think it's not I will call a vote again. > > fabrizio > > > On 12/28/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> >> On 27 Dec 06, at 10:56 PM 27 Dec 06, Barrie Treloar wrote: >> >> > On 12/28/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> >> Fabrizio, >> >> >> >> Slight delay but I'll have to release the Eclipse plugin from >> Window. >> >> The forked test that you're using won't pass on any system >> properties >> >> so I can't skip the tests. They all fail on OS/X and on Linux. I >> >> think that's a clear sign we have some problems with the testing. >> >> >> >> I will do this tomorrow, but not good at all I don't think that I >> >> have to resort to releasing on Windows. The tests are highly >> fragile >> >> if they only survive on Window. >> > >> > This isn't the only plugin that has platform brittleness. >> >> In this it is exacerbated by the testing framework. In a lot of cases >> by using things like Plexus Utils we avoid most of common problems. >> The second we start rolling new utilities we get bitten. This is why >> it is crucial that we align all the integration testing tools. >> >> Jason. >> >> > I'm hoping that once continuum is setup against the maven svn >> plugins >> > that you have multiple build machines building to catch these >> errors. >> > >> > >> --------------------------------------------------------------------- >> > 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] >> >> > > --------------------------------------------------------------------- > 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
