Hi Steven,
On 06/07/11 14:17, Steven A Rowe wrote:
Eric,
On 7/6/2011 at 5:35 AM, Eric Charles wrote:
Diverging from the thread title and probably already discussed...
but why pom are not committed and maintained in SVN?
The POMs *are* committed to SVN, under dev-tools/maven/, as pom.xml.template files,
which have their<version> filled in when they are copied over to where they
can be used and renamed to pom.xml. The Maven configuration is a non-official build,
and maintaining the POMs outside of the main source tree is one way in which this
fact is conveyed to users.
Yes, I just saw this.
It's just that they are not committed on the standard place and they
need to be generated before to be used.
Even if 'mvn install' works fine, I still have issues importing the
modules hierarchy in eclipse due to e.g. the src/test-framework module.
Do you know about the eclipse configuration available via 'ant eclipse' ?
I've given a try to 'ant eclipse', and yes, it create one eclipse
project with may src folders (the lucene, contrib, modules, solr...).
Before coming to mailing list, I looked across the lucene website and
wiki for the information.
Now I see it's on
http://wiki.apache.org/solr/HowToContribute#Development_Environment_Tips
and in the SVN README.txt. Sorry for the noise.
I'm more used to work with m2eclipse that allows me to directly import
modules as different eclipse projects, having snapshots resolved from
maven repo. But that's just a developer habit and I'm fine working with
the generated eclipse project. Nevertheless, I would have preferred
having the final pom committed to be sure it imports fine in eclipse
(now, I'm stuck with the src/test-framework module).
Steve
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
