This was the release plugin problem I discussed with Fabrizio. The
current (NOT SNAPSHOT) version of the plugin does not update the
cross module references during release:prepare. We have to do this
manually after a release.
If not yet done. I will update.
Philipp
On Nov 21, 2006, at 11:50 AM, Chris Miner wrote:
Am Montag, 20. November 2006 14:58 schrieb Grégory Joseph:
Hmm, sorry I'm confused now - I thought all submodules would depend
on the version declared in the main pom. So that means you'd have to
change the versions in each pom, which I can't really do right now. I
know this has been discussed on this list before, so you might dig
more insight in the archives.
Couldn't find an apparent reference to this on either of the
magnolia lists.
Nothing clearly related to substitution of jars either. Probably
creating a
build profile and entering it in the main pom.xml is the right
solution.
Should be able to change dependencies with that.
I ended up changing the version values in the main pom.xml for each
of the
magnolia related dependencies so they match the values declared in
each of
the subproject poms. For example:
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-dms</artifactId>
- <version>3.0-rc5-SNAPSHOT</version>
+ <version>1.2-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>info.magnolia</groupId>
<artifactId>magnolia-module-cache</artifactId>
- <version>3.0</version>
+ <version>3.0.1-SNAPSHOT</version>
</dependency>
This resulted in project references instead of local repo jar
references when
I rebuilt the eclipse files. Works for me. =)
g
On Nov 20, 2006, at 14:30 , Grégory Joseph wrote:
Hi Chris,
The only thing you'd need to change would be the main pom's
dependencies - but I'll be committing this now, since we're having
a couple of fixes to do on the trunk :)
Cheers
g
On Nov 20, 2006, at 13:05 , Chris Miner wrote:
Hi All,
When I regenerate my eclipse files lately, I get a magnolia
project that
doesn't know about the other magnolia projects in my workspace.
Looking at
the output from maven I receive informative messages such as:
[INFO] Artifact info.magnolia:magnolia-module-admininterface:jar:
3.0 already
available as a reactor project, but with different version.
Expected: 3.0,
found: 3.0.1-SNAPSHOT
Which make sense, since the version mentioned in the admin
interface pom is
3.0.1-SNAPSHOT, but the version required in the magnolia pom is
indeed 3.0.
So the existing admin interface project in my workspace is ignored.
Being as I know next to nothing about maven, the solution seems to
be to
change all the subproject poms to reference version 3.0.1 or
change them all
to produce a version 3.0. I am betting that neither of these
approaches is
correct.
What is the correct way to work around this in a development
environment? Is
there something I should configure in my maven settings file?
Chris
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
