It is a new plugin. I am using maven 2.2.1 to develop the plugin, with jdk 1.6. and Eclipse Indigo with embbeded Maven 3.0. When I try to compile from command line I get this errors:
/mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/myPlugin/ PomXmlManager.java:[20,19] package hudson.maven does not exist [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[21,19] package hudson.maven does not exist [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[20,19] package hudson.maven does not exist [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[21,19] package hudson.maven does not exist [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[70,2] cannot find symbol [ERROR] symbol : class MavenModuleSetBuild [ERROR] location: class myPlugin.PomXmlManager [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[70,32] cannot find symbol [ERROR] symbol : class MavenModuleSetBuild [ERROR] location: class myPlugin.PomXmlManager [ERROR] /mnt/home/usuario/Documents/profilemixer-plugin/src/main/java/ myPlugin/PomXmlManager.java:[225,10] cannot find symbol [ERROR] symbol : class AbstractMavenProject [ERROR] location: class myPlugin.PomXmlManager.DescriptorImpl The errors indicates that maven (from commandline) can not find some classes, like hudson.maven.MavenModuleSetBuild. But when I compile from Eclipse all it's ok. I've tried to compile from command line with maven 3.0, but with no luck. Also I've tried deleting the folder repository of maven (.m2). The plugin HelloWorldPlugin works fine, but if I add the class hudson.maven.MavenModuleSetBuild, it gives me the same error as my plugin: hudson.maven does not exist. Any idea? On 1 mar, 18:13, Kohsuke Kawaguchi <[email protected]> wrote: > What is this plugin, and what's the error you get? > > On 03/01/2012 02:27 AM, Coutemeier wrote: > > > > > > > > > > > Sorry, but it doesn't works for my plugin. > > > My plugin is based on 1.436. > > > My settings.xml is: > > > <pluginGroups> > > <pluginGroup>org.jenkins-ci.tools</pluginGroup> > > </pluginGroups> > > <mirrors> > > <mirror> > > <id>repo.jenkins-ci.org</id> > > <url>http://repo.jenkins-ci.org/public/</url> > > <mirrorOf>m.g.o-public</mirrorOf> > > </mirror> > > </mirrors> > > <profiles> > > <!-- Give access to Jenkins plugins --> > > <profile> > > <id>jenkins</id> > > <activation> > > <activeByDefault>true</activeByDefault> <!-- > > change this to false, > > if you don't like to have it on per default --> > > </activation> > > <repositories> > > <repository> > > <id>maven.jenkins-ci.org</id> > > > > <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url> > > </repository> > > </repositories> > > <pluginRepositories> > > <pluginRepository> > > <id>maven.jenkins-ci.org</id> > > > > <url>http://maven.jenkins-ci.org/content/groups/artifacts/</url> > > </pluginRepository> > > </pluginRepositories> > > </profile> > > </profiles> > > > And my pom.xml has the repositories: > > > <repositories> > > <repository> > > <id>m.g.o-public</id> > > > > <url>http://maven.glassfish.org/content/groups/public/</url> > > </repository> > > <repository> > > <id>repo.jenkins-ci.org</id> > > <url>http://repo.jenkins-ci.org/public/</url> > > </repository> > > </repositories> > > > <pluginRepositories> > > <pluginRepository> > > <id>m.g.o-public</id> > > > > <url>http://maven.glassfish.org/content/groups/public/</url> > > </pluginRepository> > > <pluginRepository> > > <id>repo.jenkins-ci.org</id> > > <url>http://repo.jenkins-ci.org/public/</url> > > </pluginRepository> > > </pluginRepositories> > > > Is anything wrong with my configuration? > > > On 1 mar, 04:11, Kohsuke Kawaguchi<[email protected]> wrote: > >> We've been usinghttp://maven.glassfish.org/forresolving all the > >> artifacts for building core and plugins. But it has been down for the > >> past two days and we have no ETA. > > >> So I propose we switch tohttp://repo.jenkins-ci.org/public. > > >> This issue was raised several times in the past that we rely on a 3rd > >> party repository we have on control over. It was simply an inertia from > >> earlier days when I was in the Glassfish team (and even had the physical > >> access to the system!), and the migration never really came high enough > >> in the priority list, until this outage. > > >> http://repo.jenkins-ci.org/isa hosted Artifactory, operated by JFrog. > >> They kindly let us use their service for free (thanks JFrog!) It was > >> started several weeks ago after a discussion in the project meeting, and > >> the original motivation was to migrate from > >> self-managedhttp://maven.jenkins-ci.org/ > > >> That migration work is still in the proof-of-concept phase, and more on > >> that in the upcoming project meeting, but in the mean time, we can and > >> we should fast-track maven.glassfish.org migration since it has a bigger > >> impact on our development. > > >> The core and super POM have already been modified to use this new > >> repository, and it works well. The plugin parent POM will have this new > >> location starting 1.453, but if you depend on earlier parent POMs, you > >> can specify the following fragment in your plugin POM to make this > >> resolve: > > >> <repositories> > >> <repository> > >> <id>repo.jenkins-ci.org</id> > >> <url>http://repo.jenkins-ci.org/public/</url> > >> </repository> > >> </repositories> > > >> <pluginRepositories> > >> <pluginRepository> > >> <id>repo.jenkins-ci.org</id> > >> <url>http://repo.jenkins-ci.org/public/</url> > >> </pluginRepository> > >> </pluginRepositories> > > >> Also, adding the following fragment to your ~/.m2/settings.xml will make > >> your Maven use the new repository whenever m.g.o-public is referenced. > > >> <settings> > >> <mirrors> > >> <mirror> > >> <id>repo.jenkins-ci.org</id> > >> <url>http://repo.jenkins-ci.org/public/</url> > >> <mirrorOf>m.g.o-public</mirrorOf> > >> </mirror> > > >> This time, we are using the *.jenkins-ci.org URL. Even if JFrog goes > >> belly up tomorrow, we just need to make a few DNS/redirect adjustments > >> to be able to keep this new URL working. So this should be the last time > >> we need to make this kind of migration. > > >> -- > >> Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/ > >> Try Nectar, our professional version of Jenkins > > -- > Kohsuke Kawaguchi | CloudBees, Inc. |http://cloudbees.com/ > Try Nectar, our professional version of Jenkins
