Problem with resolving Snapshot depenencies

[Christian Goos <Ch...@forum-informatik.ch>]

Sorry I posted this with the wrong subject

Hi 

I have a question regarding the snapshot conversion.
I defined snapshot dependencies as shown below but when I use
the convert-snapshots goal I get a message:"Can't retrieve snapshot version
file: null"
When I confirm the dialog to update the dependency the project.xml isn't
changed.

What is wrong with the dependency declaration or what do I have to do to get
the dependencies resolved?

Thank you
Christian


"/><dependency>
                        <groupId>common</groupId>
                        <artifactId>common</artifactId>
                        <version>SNAPSHOT</version>
                        <type>jar</type>
                        <properties>
                                <jnlp.jar>true</jnlp.jar>
                        </properties>
                </dependency>    [echo]
Can't retrieve snapshot version file: null
<dependency>
                        <groupId>common</groupId>
                        <artifactId>common</artifactId>
                        <version>SNAPSHOT</version>
                        <type>jar</type>
                        <properties>
                                <jnlp.jar>true</jnlp.jar>
                        </properties>
                </dependency>    [echo]
Do you want to update this dependency? [yes]

-----Original Message-----
From: Arik Kfir [mailto:arikkfir@bezeqint.net] 
Sent: Monday, October 06, 2003 2:37 PM
To: Maven Users List
Subject: POM extend feature - improvement suggestion

Hello,

Maven has a mechanism for project-inheritance via the <extend> tag. This is
a good practice enabling even further standardization and unity between
various project aspects, especially for organizations/corporations
generating more than a small number of projects.

However, I've seen in several Maven-powered projects that the project.xml
file extends other project.xml files by pointing to them in a
filesystem-dependant way. For example, one project.xml file would contain a
statement such as:

    <extend>../project.xml</extend>

This only holds ofcourse if I have the parent project in my local
filesystem. But that breaks the notion of every project standing on its own,
isn't it? or perhaps this wasn't the notion at all to begin with - am I
suppose to download the parent projects as well? (not a retorical question -
I'm really asking what's the standard practice)

I believe a better alternative would be to embed this behaviour through the
dependency mechanism, such that a project "depends" on another project (a
POM artifact perhaps?), but not to receive classpath elements, but rather to
receive its POM metadata. Something like:

    <groupId>commons</groupId>
    <id>util</id>
    <extend>
        <groupId>commons</groupId>
        <id>general</id>
    </extend>

Such that the 'commons' (some virtual 'commons' project) project exists by
itself, producing a single artifact which is an abstract POM model, and a
subproject named 'util' which is under the 'commons' group-id uses that
abstract POM model to extend from.

Ofcourse this could be simplified if needed to specifying a URL to the
abstract POM, or some other mechanism perhaps. But I think the idea is
clear.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org