When you do a 'mvn package' from thirdparty (it's part of the build), the old
component-info.xml files are generated and the jar files copied in the expected locations
in
thirdparty directory, driven by the information in the thirdparty.pom.xml. This is a
plugin
Paul wrote.
What you want to change?
Heiko Braun wrote:
When I look at the thirdparty/pom.xml and jbossas-component-matrix
it seems that all dependencies that once have been declared in
component-info.xml have disappeared from the maven build or have been
replaced by some (latest?) release.
* Is the migration from buildmagic to maven automated or done by hand?
* Who is responsible for that? The subcomponent developer?
* How do I change jbossas-component-matrix?
/Heiko
On Mon, 2008-04-21 at 12:47 +0300, Dimitris Andreadis wrote:
> No further changes to the AS build. The thirdparty directory is now
> backed by the maven
> repo and that seems to work well (minus the gripes). In order not to
> disrupt the builds we
> will leave the full mavenization of the AS build for later.
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development