If that is indeed the case, can I just use the lifecycle plugin to ignore that execution during a workspace build?
Jason King Software Engineer Open Roads Consulting, Inc. (757) 546-3401 | [email protected] -----Original Message----- From: Igor Fedorenko [mailto:[email protected]] Sent: Tuesday, August 19, 2014 6:02 PM To: Jason W. King; 'Maven Integration for Eclipse users mailing list' Subject: Re: [m2e-users] Dependency Plugin - Artifact has not been packaged yet. Looks like you are forcing execution of dependency:copy during workspace build. This is not supported. -- Regards, Igor On 2014-08-19, 17:00, Jason W. King wrote: > I get this when the project is imported into eclipse. If I "Update > Project..." the error remains as a Maven Problem under the Markers tab. I > have no problem executing a "clean install" from within Eclipse or on the > command line and achieving the desired outcome. > > Jason King > Software Engineer > Open Roads Consulting, Inc. > (757) 546-3401 | [email protected] > > -----Original Message----- > From: Igor Fedorenko [mailto:[email protected]] > Sent: Tuesday, August 19, 2014 4:56 PM > To: Maven Integration for Eclipse users mailing list; Jason W. King; > [email protected] > Subject: Re: [m2e-users] Dependency Plugin - Artifact has not been packaged > yet. > > What do you do to get this message, run as maven build? What goals do you > specify? > > On August 19, 2014 4:35:34 PM EDT, "Jason W. King" > <[email protected]> wrote: >> In Eclipse Luna, the m2e plugin is complaining about my use of the >> dependency plugin. >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-dependency-plugin</artifactId> >> <version>2.8</version> >> <executions> >> <execution> >> <goals> >> <goal>copy</goal> >> </goals> >> <configuration> >> <artifactItems> >> <artifactItem> >> <groupId>com.orci.VATVD.db</groupId> >> >> <artifactId>database</artifactId> >> <outputDirectory>${project.build.directory}/VATVD-DGListener-${project.version}</outputDirectory> >> <destFileName>VATVD-Database-${project.version}.jar</destFileName> >> </artifactItem> >> </artifactItems> >> </configuration> >> </execution> >> </executions> >> </plugin> >> >> The full message I'm getting is as follows: >> >> "Artifact has not been packaged yet. When used on reactor artifact, >> copy should be executed after packaging: see MDEP-187. >> (org.apache.maven.plugins:maven-dependency-plugin:2.8:copy:default:process-sources)" >> >> This seems to be a problem with the resolution in the plugin and not >> with my POM. Any suggestions on getting around this? >> >> >> This email communication (including any attachments) may contain >> confidential and/or privileged material intended solely for the >> individual or entity to which it is addressed. >> If you are not the intended recipient, please delete this email >> immediately. >> >> >> --------------------------------------------------------------------- >> -- >> - >> >> _______________________________________________ >> m2e-users mailing list >> [email protected] >> To change your delivery options, retrieve your password, or >>unsubscribe from this list, visit >>https://dev.eclipse.org/mailman/listinfo/m2e-users > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > This email communication (including any attachments) may contain confidential > and/or privileged material intended solely for the individual or entity to > which it is addressed. > If you are not the intended recipient, please delete this email immediately. > This email communication (including any attachments) may contain confidential and/or privileged material intended solely for the individual or entity to which it is addressed. If you are not the intended recipient, please delete this email immediately. _______________________________________________ m2e-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
