I do use maven-dependency-plugin to unpack one resource. I have a flex
module and a blaze one, I have another module that just has the XML config
files needed by blaze.
I wouldn't expect this to be an issue because there are not Java sources
involved with this.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-dependency-plugin</artifactId>
<version>2.1</version>
<executions>
<execution>
<id>unpack-config</id>
<goals>
<goal>unpack-dependencies</goal>
</goals>
<phase>generate-resources</phase>
<configuration>
<outputDirectory>${project.build.directory}/generated-resources</outputDirectory>
<includeGroupIds>${project.groupId}</includeGroupIds>
<excludeTransitive>true</excludeTransitive>
<excludeTypes>pom,jar</excludeTypes>
<includeArtifactIds>cdf-blaze-svcs-config</includeArtifactIds>
</configuration>
</execution>
</executions>
</plugin>
-Dave
On Thu, Apr 16, 2009 at 10:52 AM, Stephen Connolly <
[email protected]> wrote:
> by any chance are you using
>
> dependency:copy
>
> or
>
> dependency:unpack
>
> anywhere in your build?
>
> If you are that could well be the source of your issues.
>
> It sounds like one of the plugins you are using is not searching the
> reactor
> for dependencies.
>
> -Stephen
>
> 2009/4/16 David Hoffer <[email protected]>
>
> > Then there is a big bug here because I have a multi-module project with a
> > few modules, the dependent one was built first (as seen in the build log)
> > but yet when the depending module was built it did NOT use the dependent
> > build rather it went to the repo and downloaded the previously deployed
> > artifact snapshot.
> >
> > -Dave
> >
> > On Thu, Apr 16, 2009 at 10:24 AM, Todd Thiessen <[email protected]>
> > wrote:
> >
> > > FYI. Here is one reference,
> > >
> > > http://maven.apache.org/pom.html#Aggregation
> > >
> > > ---
> > > Todd Thiessen
> > >
> > >
> > > > -----Original Message-----
> > > > From: David Hoffer [mailto:[email protected]]
> > > > Sent: Thursday, April 16, 2009 11:46 AM
> > > > To: Maven Users List
> > > > Subject: Re: Multi-module build is not building with current
> > > > module source code
> > > >
> > > > Then I'm understanding the order of the reactor wrong. I
> > > > assumed its top to bottom, that is...just before internal is
> > > > built...public is built; and just before security-public is
> > > > built...internal is built.
> > > >
> > > > Can you clarify the order?
> > > >
> > > > -Dave
> > > >
> > > > On Thu, Apr 16, 2009 at 9:39 AM, Nick Stolwijk
> > > > <[email protected]>wrote:
> > > >
> > > > > Maven always takes the artifacts out of the local
> > > > repository. However,
> > > > > this is not a problem, because the reactor knows in which order to
> > > > > built the projects. Just before your internal project is
> > > > built, maven
> > > > > has installed the most recent version of security-public in
> > > > the local
> > > > > repository.
> > > > >
> > > > > Maybe I don't understand your problem. If that is the case,
> > > > please clarify.
> > > > >
> > > > > Hth,
> > > > >
> > > > > Nick Stolwijk
> > > > > ~Java Developer~
> > > > >
> > > > > Iprofs BV.
> > > > > Claus Sluterweg 125
> > > > > 2012 WS Haarlem
> > > > > www.iprofs.nl
> > > > >
> > > > >
> > > > >
> > > > > On Thu, Apr 16, 2009 at 5:26 PM, Dmitry Skavish
> > > > <[email protected]> wrote:
> > > > > > I am having the same problem and would like to know that
> > > > as well. Thanks!
> > > > > >
> > > > > > On Thu, Apr 16, 2009 at 10:19 AM, David Hoffer
> > > > <[email protected]>
> > > > > wrote:
> > > > > >
> > > > > >> I have a multi-module build where some modules are dependent on
> > > > > >> other modules. What is happening is that the dependent
> > > > module is
> > > > > >> getting its dependency from the local/corporate maven
> > > > repo instead
> > > > > >> of the source
> > > > > code
> > > > > >> that was just built. How do I specify that modules always build
> > > > > >> using current source not prior built snapshot jars?
> > > > > >>
> > > > > >> Here is an example of the problem (it is really simple)
> > > > > >>
> > > > > >> Parent pom:
> > > > > >> <version>0.1-SNAPSHOT</version>
> > > > > >> <modules>
> > > > > >> <module>public</module>
> > > > > >> <module>internal</module>
> > > > > >> <module>security-public</module> </modules>
> > > > > >>
> > > > > >> public pom:
> > > > > >> <version>0.1-SNAPSHOT</version>
> > > > > >>
> > > > > >> internal pom:
> > > > > >> <dependencies>
> > > > > >> <dependency>
> > > > > >> <groupId>${project.groupId}</groupId>
> > > > > >> <artifactId>public</artifactId>
> > > > > >> <version>0.1-SNAPSHOT</version>
> > > > > >> </dependency>
> > > > > >> </dependencies>
> > > > > >>
> > > > > >> security-public:
> > > > > >> <dependency>
> > > > > >> <groupId>${project.groupId}</groupId>
> > > > > >> <artifactId>public</artifactId>
> > > > > >> <version>0.1-SNAPSHOT</version> </dependency>
> > > > > >>
> > > > > >> So what is happening is that instead of internal &
> > > > security-public
> > > > > >> building using the just built public (note it is first so it was
> > > > > >> built first)
> > > > > they
> > > > > >> go
> > > > > >> out and download the last deployed snapshot and build using that
> > > > > instead.
> > > > > >>
> > > > > >> Nothing in the pom dependency syntax really says which
> > > > to use but I
> > > > > assumed
> > > > > >> that because maven 'knows' these are all in the reactor it would
> > > > > >> use
> > > > > module
> > > > > >> source. However this doesn't seem to work, what do I
> > > > need to do to
> > > > > >> fix this?
> > > > > >>
> > > > > >> BTW, the goals being run are 'clean deploy site-deploy'
> > > > > >>
> > > > > >> -Dave
> > > > > >>
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Dmitry Skavish
> > > > > >
> > > > >
> > > > >
> > > > ---------------------------------------------------------------------
> > > > > 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]
> > >
> > >
> >
>
