You're right Antonio, but as we modified code the public solr artifacts
don't work for us. Let me explain the sequence i want to implement in the
build process.
*Step one*: pom calls the ant-target that generates the artifacts
<execution>
<id>build.xml dist target</id>
<phase>process-sources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<tasks>
<ant antfile="build.xml">
<property name="build.compiler"
value="extJavac"/>
<target name="dist" />
</ant>
</tasks>
</configuration>
</execution>
Step two: maven compiles de webapp including in the classpath some of the
previous' phase generated jar's.
(my question)
Step three: Package the war file with the compiled webapp code, static
resources and some of the libraries generated in phase 1.
Step four: Install the resultant artifact into local repository
2010/1/28 Antonio Petrelli <[email protected]>
> 2010/1/28 Licinio Fernández Maurelo <[email protected]>:
> > As we are changing part of the code we just want to integrate the
> > solr-webapp into our projects. As i said, don't want to mavenize the
> whole
> > project.
>
> Wait a Minute, I see that Solr packages are already available at the
> main repository, with the exception of the War itself...
> IMHO you need to put only the correct dependencies. Or does the
> build.xml do strange things in the final package?
>
> Antonio
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Lici
~Java Developer~
