You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by nicolas de loof <ni...@gmail.com> on 2007/05/03 12:45:08 UTC
question about POMs in (new) trunk
The POMs in the new trunk don't set versions for dependencies on other
arhiva modules. Maven has no issue with that when running mvn install.
I tried to do the same on my project and got error :
Validation Messages:
[0] 'dependencies.dependency.version' is missing for
com.capgemini.quickstart:quickstart-model
Reason: Failed to validate POM
I don't see any special version setting in archiva. Did I miss something ?
Nico.
Re: question about POMs in (new) trunk
Posted by nicolas de loof <ni...@gmail.com>.
Adding " <version>${project.version}</version> " on my modules dependencies
solves this.
What maven hack is used by archiva ???
2007/5/3, nicolas de loof <ni...@gmail.com>:
>
> The POMs in the new trunk don't set versions for dependencies on other
> arhiva modules. Maven has no issue with that when running mvn install.
>
> I tried to do the same on my project and got error :
> Validation Messages:
>
> [0] 'dependencies.dependency.version' is missing for
> com.capgemini.quickstart:quickstart-model
>
> Reason: Failed to validate POM
>
>
> I don't see any special version setting in archiva. Did I miss something ?
>
>
> Nico.
>
Re: question about POMs in (new) trunk
Posted by nicolas de loof <ni...@gmail.com>.
I've made some test on minimalist POM hierarchy and having multi-level
parents OR setting version using dependencyManagement doesn't break the
ability to setup eclipse without having the project installed in local
repository..
You can take a look at my poms here : http://ndeloof.free.fr/temp/poms.zip
test (pom)
|_ test-one (pom)
| |_ sub-test-one (jar)
|_test-two (pom)
|_ sub-test-two (jar) with dependency on sub-test-one
mvn eclipse:eclipse creates the expected .classpath in sub-test-two and
doesn't requires the jars in local repo neither tries to download them.
I don't understand why this fails with archiva-webapp
2007/5/3, nicolas de loof <ni...@gmail.com>:
>
> I allready use this for my corporate projects with not having this issue :
>
> as maven knows the projects are modules from the same parent POM, it
> resolves such modules dependencies as inter-project dependencies under
> eclipse and DOESN'T require the project to be installed in local repo.
>
> Some prior Eclipse plugin version had the issue to require the compile
> phase to be executed before generating the eclipse configuration, and this
> created troubles for many users taht fall in the same situation : checkout
> of an unstable project require to fix with vi... (vi is great but I also
> like eclipse)
>
> Maybe this issue relates to the two-level of parent POMs : archiva-webapp
> and it's dependencies do not share the same direct parent.
>
> 2007/5/3, Joakim Erdfelt < joakim@erdfelt.com>:
> >
> > That's expected.
> >
> > On a fresh checkout/update, the modules do not exist in the local (or
> > remote) repositories yet.
> >
> > When you run the eclipse:eclipse goal, it tries to resolve the
> > dependencies, it can't as there is no information present in the
> > repository system for those modules.
> >
> > Compile it first, then run eclipse:eclipse, then import it into
> > eclipse.
> >
> > - Joakim
> >
> >
> > nicolas de loof wrote:
> > > You're right, I missed it.
> > >
> > > This has a strange side effect : when I run mvn eclipse:eclipse from a
> > > fresh
> > > checkout, all inter-modules dependencies are unresolved :
> > >
> > > [INFO]
> > >
> > ------------------------------------------------------------------------
> > > [ERROR] BUILD ERROR
> > > [INFO]
> > >
> > ------------------------------------------------------------------------
> > > [INFO] Failed to resolve artifact.
> > >
> > > Missing:
> > > ----------
> > > 1)
> > >
> > org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
> > >
> > >
> > > Try downloading the file manually from the project website.
> > >
> > > Then, install it using the command:
> > > mvn install:install-file
> > > -DgroupId=
> > org.apache.maven.archiva-DartifactId=archiva-database-consumers
> > > \
> > > -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
> > > -Dfile=/path/to/file
> > >
> > > Path to dependency:
> > > 1)
> > > org.apache.maven.archiva:archiva-webapp:war:1.0-alpha-1-SNAPSHOT
> > > 2)
> > > org.apache.maven.archiva:archiva-scheduled:jar:1.0-alpha-1-SNAPSHOT
> > > 3)
> > >
> > org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
> > >
> > > ...
> > >
> > >
> > > I can't import all modules in Eclipse before mvn install is
> > successfull.
> > > This may create issues if the code in SVN has compilation failures due
> > to
> > > some unfortunate commit.
> > >
> > >
> > > 2007/5/3, Andrew Williams <andy@handyande.co.uk >:
> > >>
> > >> I have not looked, but am guessing there is a dependencyManagement
> > >> section in the parent pom.
> > >>
> > >> Andy
> > >>
> > >> On 3 May 2007, at 11:45, nicolas de loof wrote:
> > >>
> > >> > The POMs in the new trunk don't set versions for dependencies on
> > other
> > >> > arhiva modules. Maven has no issue with that when running mvn
> > install.
> > >> >
> > >> > I tried to do the same on my project and got error :
> > >> > Validation Messages:
> > >> >
> > >> > [0] 'dependencies.dependency.version' is missing for
> > >> > com.capgemini.quickstart:quickstart-model
> > >> >
> > >> > Reason: Failed to validate POM
> > >> >
> > >> >
> > >> > I don't see any special version setting in archiva. Did I miss
> > >> > something ?
> > >> >
> > >> > Nico.
> > >>
> > >>
> > >
> >
> >
>
Re: question about POMs in (new) trunk
Posted by nicolas de loof <ni...@gmail.com>.
I allready use this for my corporate projects with not having this issue :
as maven knows the projects are modules from the same parent POM, it
resolves such modules dependencies as inter-project dependencies under
eclipse and DOESN'T require the project to be installed in local repo.
Some prior Eclipse plugin version had the issue to require the compile phase
to be executed before generating the eclipse configuration, and this created
troubles for many users taht fall in the same situation : checkout of an
unstable project require to fix with vi... (vi is great but I also like
eclipse)
Maybe this issue relates to the two-level of parent POMs : archiva-webapp
and it's dependencies do not share the same direct parent.
2007/5/3, Joakim Erdfelt <jo...@erdfelt.com>:
>
> That's expected.
>
> On a fresh checkout/update, the modules do not exist in the local (or
> remote) repositories yet.
>
> When you run the eclipse:eclipse goal, it tries to resolve the
> dependencies, it can't as there is no information present in the
> repository system for those modules.
>
> Compile it first, then run eclipse:eclipse, then import it into eclipse.
>
> - Joakim
>
>
> nicolas de loof wrote:
> > You're right, I missed it.
> >
> > This has a strange side effect : when I run mvn eclipse:eclipse from a
> > fresh
> > checkout, all inter-modules dependencies are unresolved :
> >
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] BUILD ERROR
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Failed to resolve artifact.
> >
> > Missing:
> > ----------
> > 1)
> >
> org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
> >
> >
> > Try downloading the file manually from the project website.
> >
> > Then, install it using the command:
> > mvn install:install-file
> > -DgroupId=
> org.apache.maven.archiva-DartifactId=archiva-database-consumers
> > \
> > -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
> > -Dfile=/path/to/file
> >
> > Path to dependency:
> > 1)
> > org.apache.maven.archiva:archiva-webapp:war:1.0-alpha-1-SNAPSHOT
> > 2)
> > org.apache.maven.archiva:archiva-scheduled:jar:1.0-alpha-1-SNAPSHOT
> > 3)
> >
> org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
> >
> > ...
> >
> >
> > I can't import all modules in Eclipse before mvn install is successfull.
> > This may create issues if the code in SVN has compilation failures due
> to
> > some unfortunate commit.
> >
> >
> > 2007/5/3, Andrew Williams <an...@handyande.co.uk>:
> >>
> >> I have not looked, but am guessing there is a dependencyManagement
> >> section in the parent pom.
> >>
> >> Andy
> >>
> >> On 3 May 2007, at 11:45, nicolas de loof wrote:
> >>
> >> > The POMs in the new trunk don't set versions for dependencies on
> other
> >> > arhiva modules. Maven has no issue with that when running mvn
> install.
> >> >
> >> > I tried to do the same on my project and got error :
> >> > Validation Messages:
> >> >
> >> > [0] 'dependencies.dependency.version' is missing for
> >> > com.capgemini.quickstart:quickstart-model
> >> >
> >> > Reason: Failed to validate POM
> >> >
> >> >
> >> > I don't see any special version setting in archiva. Did I miss
> >> > something ?
> >> >
> >> > Nico.
> >>
> >>
> >
>
>
Re: question about POMs in (new) trunk
Posted by Joakim Erdfelt <jo...@erdfelt.com>.
That's expected.
On a fresh checkout/update, the modules do not exist in the local (or
remote) repositories yet.
When you run the eclipse:eclipse goal, it tries to resolve the
dependencies, it can't as there is no information present in the
repository system for those modules.
Compile it first, then run eclipse:eclipse, then import it into eclipse.
- Joakim
nicolas de loof wrote:
> You're right, I missed it.
>
> This has a strange side effect : when I run mvn eclipse:eclipse from a
> fresh
> checkout, all inter-modules dependencies are unresolved :
>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1)
> org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
>
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.maven.archiva-DartifactId=archiva-database-consumers
> \
> -Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Path to dependency:
> 1)
> org.apache.maven.archiva:archiva-webapp:war:1.0-alpha-1-SNAPSHOT
> 2)
> org.apache.maven.archiva:archiva-scheduled:jar:1.0-alpha-1-SNAPSHOT
> 3)
> org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
>
> ...
>
>
> I can't import all modules in Eclipse before mvn install is successfull.
> This may create issues if the code in SVN has compilation failures due to
> some unfortunate commit.
>
>
> 2007/5/3, Andrew Williams <an...@handyande.co.uk>:
>>
>> I have not looked, but am guessing there is a dependencyManagement
>> section in the parent pom.
>>
>> Andy
>>
>> On 3 May 2007, at 11:45, nicolas de loof wrote:
>>
>> > The POMs in the new trunk don't set versions for dependencies on other
>> > arhiva modules. Maven has no issue with that when running mvn install.
>> >
>> > I tried to do the same on my project and got error :
>> > Validation Messages:
>> >
>> > [0] 'dependencies.dependency.version' is missing for
>> > com.capgemini.quickstart:quickstart-model
>> >
>> > Reason: Failed to validate POM
>> >
>> >
>> > I don't see any special version setting in archiva. Did I miss
>> > something ?
>> >
>> > Nico.
>>
>>
>
Re: question about POMs in (new) trunk
Posted by nicolas de loof <ni...@gmail.com>.
You're right, I missed it.
This has a strange side effect : when I run mvn eclipse:eclipse from a fresh
checkout, all inter-modules dependencies are unresolved :
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1)
org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file
-DgroupId=org.apache.maven.archiva-DartifactId=archiva-database-consumers
\
-Dversion=1.0-alpha-1-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Path to dependency:
1) org.apache.maven.archiva:archiva-webapp:war:1.0-alpha-1-SNAPSHOT
2)
org.apache.maven.archiva:archiva-scheduled:jar:1.0-alpha-1-SNAPSHOT
3)
org.apache.maven.archiva:archiva-database-consumers:jar:1.0-alpha-1-SNAPSHOT
...
I can't import all modules in Eclipse before mvn install is successfull.
This may create issues if the code in SVN has compilation failures due to
some unfortunate commit.
2007/5/3, Andrew Williams <an...@handyande.co.uk>:
>
> I have not looked, but am guessing there is a dependencyManagement
> section in the parent pom.
>
> Andy
>
> On 3 May 2007, at 11:45, nicolas de loof wrote:
>
> > The POMs in the new trunk don't set versions for dependencies on other
> > arhiva modules. Maven has no issue with that when running mvn install.
> >
> > I tried to do the same on my project and got error :
> > Validation Messages:
> >
> > [0] 'dependencies.dependency.version' is missing for
> > com.capgemini.quickstart:quickstart-model
> >
> > Reason: Failed to validate POM
> >
> >
> > I don't see any special version setting in archiva. Did I miss
> > something ?
> >
> > Nico.
>
>
Re: question about POMs in (new) trunk
Posted by Andrew Williams <an...@handyande.co.uk>.
I have not looked, but am guessing there is a dependencyManagement
section in the parent pom.
Andy
On 3 May 2007, at 11:45, nicolas de loof wrote:
> The POMs in the new trunk don't set versions for dependencies on other
> arhiva modules. Maven has no issue with that when running mvn install.
>
> I tried to do the same on my project and got error :
> Validation Messages:
>
> [0] 'dependencies.dependency.version' is missing for
> com.capgemini.quickstart:quickstart-model
>
> Reason: Failed to validate POM
>
>
> I don't see any special version setting in archiva. Did I miss
> something ?
>
> Nico.