You need to specify the groupId in the parent. On Thu, Sep 30, 2010 at 11:15 AM, motes motes <[email protected]> wrote: > Hm in the submodule where I use felix: > > <plugin> > <groupId>org.apache.felix</groupId> > <artifactId>maven-bundle-plugin</artifactId> > <extensions>true</extensions> > <configuration> > <instructions> > ... > </instructions> > </configuration> > </plugin> > > > I still get the warning: > > [WARNING] Some problems were encountered while building the effective > model for com.model:bundle:2.0.2-SNAPSHOT > [WARNING] 'build.plugins.plugin.version' for > org.apache.felix:maven-bundle-plugin is missing. @ line 18, column 17 > > even though I in the parent specified: > > <pluginManagement> > <plugins> > ... > <plugin> > > <artifactId>maven-bundle-plugin</artifactId> > <version>2.1.0</version> > </plugin> > </plugins> > </pluginManagement> > > > Are the children not supposed to use the maven-plugin version > specified in the parent? > > > > > > > On Thu, Sep 30, 2010 at 4:46 PM, Michael Hess <[email protected]> wrote: >> motes motes <[email protected]> wrote on 30.09.2010 16:38:22: >> >>> From: motes motes <[email protected]> >>> To: [email protected] >>> Date: 30.09.2010 16:38 >>> Subject: Re: Bug in maven-bundle-plugin ?? >>> >>> I think I am slowly seeing you point :-) So the task of managing >>> maven-plugins is actually the same task as managing dependencies using >>> eg. the <dependencyManager > tag. >>> >>> Based on this (if I understand you correct) would a good approach be >>> to create a "super pom" where I specify all the versions og the >>> maven-plugins like: >>> >>> <pluginManagement> >>> <plugins> >>> <plugin> >>> <artifactId>maven-resources-plugin</artifactId> >>> <version>2.4.3</version> >>> </plugin> >>> <plugin> >>> <artifactId>maven-install-plugin</artifactId> >>> <version>2.3.1</version> >>> </plugin> >>> <plugin> >>> <artifactId>maven-compiler-plugin</artifactId> >>> <version>2.3.2</version> >>> </plugin> >>> ... >>> </plugins> >>> </pluginManagement> >>> >>> then everything should work and its still free for the children to >>> override the versions if necessary. >> >> Yes, that's how we did it back then. >> >>> Is this how conflicts are avoided >>> when using a large mix of maven-plugins? >> >> No, since you cannot really avoid the conflicts. If you use 2 artifacts, >> and both refer another artifact in different versions, you still have >> conflicts. What maven does (or used to do), is that it enforces a >> "shortest path first" policy. Given >> >> A --> B --> C (2.0) >> D --> E --> F --> C (3.0) >> >> Then you will get C (2.0) on your build path. >> >> It should be explained in more detail and with all the nitpicks somewhere >> in the maven wiki i think. >> >>> >>> On Thu, Sep 30, 2010 at 4:10 PM, Michael Hess <[email protected]> >> wrote: >>> >> Its not in my local maven repo since its not supposed to be there. >> For >>> > >>> > You cannot know that, as you simply don't have all the plugins under >> your >>> > control. You will for sure somehow be connected to an external >> repository. >>> > Whether you download directly, or via some proxy that mirrors an >> external >>> > repo into your cooperate network: You always will get changes from the >>> > outside from time to time. So I think it is perfectly possible, that >> some >>> > artifact/bundle has changed. >>> > >>> >> some reason another plugins specifies that it depends on : >>> > >>> > It's been a while since I last used maven, so I cannot be too specific >>> > here. >>> > But I know for sure, but I think that it was the dependecy plugin, >> that >>> > has >>> > this nice "tree" goal, where it presents a graph of the dependencies >> onto >>> > the >>> > console. You should probably run that, and then you will know where >> those >>> > dependencies are comming from. >>> > >>> >> maven-resources-plugin:2.5-SNAPSHOT >>> >> >>> >> which makes no sense to me at all. I have tried to add: >>> >> >>> >> <pluginManagement> >>> >> <plugins> >>> >> <plugin> >>> >> <artifactId>maven-resource-plugin</artifactId> >>> >> <version>2.4.3</version> >>> >> </plugin> >>> >> </plugins> >>> >> </pluginManagement> >>> >> >>> >> which is in nexus. And then I get: >>> >> >>> >> [ERROR] Plugin >>> > org.apache.maven.plugins:maven-install-plugin:2.4-SNAPSHOT >>> >> or one of its dependencies could not be resolved: The following >>> >> artifacts could not be resolved: org.apache. >>> >> maven.plugins:maven-install-plugin:jar:2.4-SNAPSHOT: Failure to find >>> >> org.apache.maven.plugins:maven-install-plugin:jar:2.4-SNAPSHOT in >>> >> http://repository:8081/nexus/content/groups/pub >>> >> lic was cached in the local repository. Resolution will not be >>> >> reattempted until the update interval of nexus has elapsed or updates >>> >> are forced. -> [Help 1] >>> >> [ERROR] >>> >> >>> >> I have then tried to add maven-install-plugin 2.3.1 (which is in >>> >> nexus) to the above manager and then I get : >>> >> >>> >> [ERROR] Failed to execute goal >>> >> org.apache.maven.plugins:maven-surefire-plugin:2.4.3-JBOSS:test >>> >> (default-test) on project birtGenerator-model: Error to resolving >>> >> surefire provider dep >>> >> endency: Missing: >>> >> ---------- >>> >> 1) org.apache.maven.surefire:surefire-junit4:jar:2.4.3-JBOSS >>> >> >>> >> Try downloading the file manually from the project website. >>> >> >>> >> Then, install it using the command: >>> >> mvn install:install-file -DgroupId=org.apache.maven.surefire >>> >> -DartifactId=surefire-junit4 -Dversion=2.4.3-JBOSS -Dpackaging=jar >>> >> -Dfile=/path/to/file >>> >> >>> >> Alternatively, if you host your own repository you can deploy the >> file >>> > there: >>> >> mvn deploy:deploy-file -DgroupId=org.apache.maven.surefire >>> >> -DartifactId=surefire-junit4 -Dversion=2.4.3-JBOSS -Dpackaging=jar >>> >> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[i >>> >> d] >>> >> >>> >> Path to dependency: >>> >> 1) dummy:dummy:jar:1.0 >>> >> 2) org.apache.maven.surefire:surefire-junit4:jar:2.4.3-JBOSS >>> >> >>> >> ---------- >>> >> 1 required artifact is missing. >>> >> >>> >> for artifact: >>> >> dummy:dummy:jar:1.0 >>> > >>> > This looks strange. Is dummy/dummy your own test bundle, or did >> something >>> > else go wrong here? >>> > >>> >> It seems that a whole bunch of artifacts has been wiped or could some >>> >> other setting of the felix plugin cause this? >>> > >>> > I don't think so. The felix plugin should not touch the local >> repository. >>> > And even if it did, you maven installation would simply download the >> jars >>> > again from (your) central repo. >>> > >>> >> >>> >> >>> >> On Thu, Sep 30, 2010 at 3:18 PM, Michael Hess >> <[email protected]> >>> > wrote: >>> >> >> but when I build it with maven3 : mvn clean install -U I get the >>> > error: >>> >> >> >>> >> >> [ERROR] Plugin >>> >> > org.apache.maven.plugins:maven-resources-plugin:2.5-SNAPSHOT >>> >> >> or one of its dependencies could not be resolved: The following >>> >> >> artifacts could not be resolved: org.apach >>> >> >> e.maven.plugins:maven-resources-plugin:jar:2.5-SNAPSHOT: Failure >> to >>> >> >> find >> org.apache.maven.plugins:maven-resources-plugin:jar:2.5-SNAPSHOT >>> >> >> in http://repository:8081/nexus/content/grou >>> >> >> ps/public was cached in the local repository. Resolution will not >> be >>> >> >> reattempted until the update interval of nexus has elapsed or >> updates >>> >> >> are forced. -> [Help 1] >>> >> >> [ERROR] >>> >> >> >>> >> >> This project has worked fine before. Any ideas why its all of the >>> > sudden >>> >> > broken? >>> >> > >>> >> > Seems like a maven problem to me. >>> >> > Did you check, that the mentioned missing artifact is in your local >>> > maven >>> >> > repository? >>> >> > If it's gone it might have happened, that the component got >> released >>> > and >>> >> > the SNAPSHOT versions were cleared out. >>> >> > >>> >> > bye, Michael >>> > >>> > >>> > The information included in this e-mail and any files transmitted with >> it is strictly >>> confidential and may be privileged or otherwise protected from >> disclosure. If you are not the >>> intended recipient, please notify the sender immediately by e-mail and >> delete this e-mail as well >>> as any attachment from your system. If you are not the intended >> recipient you are not authorized >>> to use and/or copy this message and/or attachment and/or disclose the >> contents to any other person. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >> >> >> The information included in this e-mail and any files transmitted with it is >> strictly confidential and may be privileged or otherwise protected from >> disclosure. If you are not the intended recipient, please notify the sender >> immediately by e-mail and delete this e-mail as well as any attachment from >> your system. If you are not the intended recipient you are not authorized to >> use and/or copy this message and/or attachment and/or disclose the contents >> to any other person. > > --------------------------------------------------------------------- > 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]
