ok - where do Jira's for updating the common Apache Parent go? The pom in question is missing an "<issueManagement>" element... ;-)
-Marshall Schor On 5/17/2010 3:00 PM, Brian Fox wrote: > When that was written the jar goal didn't fork iirc. > > On Mon, May 17, 2010 at 2:37 PM, Marshall Schor <[email protected]> wrote: > >> When doing an "apache-release" , the common Apache Parent version 7 invokes: >> >> <plugin> >> <groupId>org.apache.maven.plugins</groupId> >> <artifactId>maven-source-plugin</artifactId> >> <executions> >> <execution> >> <id>attach-sources</id> >> <goals> >> <goal>jar</goal> <!-- ========== ITEM OF INTEREST --> >> </goals> >> </execution> >> </executions> >> </plugin> >> >> This causes re-running of the lifecycle up to the package goal, which is >> inefficient, I think. >> >> Is there a reason the goal "jar-no-fork" isn't used instead? >> >> -Marshall Schor >> >> --------------------------------------------------------------------- >> 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]
