----- Original Message -----
From: "Mikolaj Izdebski" <mizdebsk(a)redhat.com>
To: "java-devel" <java-devel(a)lists.fedoraproject.org>, "Aleksandar
Kurtakov" <akurtako(a)redhat.com>
Sent: Friday, February 22, 2013 9:50:23 AM
Subject: Re: Installing effective Maven POM files
Are there any other problems with installing effective POMs? If yes
then I would be happy to discuss them and work on possible solutions.
Aleksandar, do you still have problems with installing effective
POMs?
I don't mind installing effective poms as long as normal poms are installed too and
there is easy way to make use of them instead of the effective poms (e.g
mvn-rpmbuild/mvn-local keeps using them). See why further in the email.
If yes then do you mind explaining them in more detail? Examples are
more then welcome. That's needed so that we can understand each other
and work on resolving the issue. I think that I have provided enough
details from my side and explained everything (if not then I will be
happy to do so, just ask).
OK, the simplest case that would not work for us if we can't make use of the normal
poms.
1. eclipse-cbi-plugin calls eclipse to run various tasks implemented in eclipse
2. the bundle set needed to run eclipse is defined in eclipse-parent
3. eclipse platform changes and adds additional bundle
4. eclipse-parent is updated to add new dependency
5. eclipse-cbi-plugin can't be rebuild as it requires to run eclipse which needs
additional bundle which is in the parent but not in eclipse-cbi-plugin package. I know
that cyclic dependencies are bad but these is the norm in Java land and this is not the
only cycle.
6. if in this case we can call mvn-rpmbuild which relies on normal poms - no problems as
parent is correct.
Note that patching eclipse-parent pom to add xmvn configuration is not ideal solution as
it would mean that xmvn would need to be resolvable in case one runs pure mvn or during
development one would need to switch between upstream/fedora eclipse-parent pom (e.g. one
runs mvn-local and gets a failure, run pure mvn to test whether it's smth in fedora
that caused the problem and things fail because xmvn is not resolved). As much as this
might sound imaginery to some people this is common case if you both work upstream and
keep care of the integration in Fedora. Any such modification introduces churns which are
very easy to overlook and either push to upstream xmvn specifics or push to Fedora without
xmvn configs so break other things later.
Keep mvn-local/mvn-rpmbuild to use normal poms and I would have no objections.
Alexander Kurtakov
Red Hat Eclipse team
--
Mikolaj Izdebski