Sounds reasonable.

In the dependency tag you have to define the type by using the type tag.
Else Maven defaults to jar.

Wodzuu can check this by having a look in his local repository. He wil
probably find a file without an ejb classifier. (Which is nothing more than
blabla-ejb-1.0.0.jar, notice the bold text.)

When using a dependecymanagement section this already bit me a couple of
times.

Jeroen

On 19/04/07, Riegel, Holger <[EMAIL PROTECTED]> wrote:

My best guess is that the type of the artifact is missing.

So just change in your pom2.xml the dependency description by adding the
type:

<dependency>
  <groupId>com.sius.beans</groupId>
  <artifactId>ejb3</artifactId>
  <version>1.0-SNAPSHOT</version>
  <type>ejb</type>
</dependency>

Without the type Maven tries to resolve the dependency for a jar type
which is the default.
See
http://maven.apache.org/ref/current/maven-model/maven.html#class_dependency
.

I hope this helps...

/Holger

-----Original Message-----
From: Wodzuu [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 19, 2007 9:44 AM
To: users@maven.apache.org
Subject: RE: Maven does not find artifact in local repo



Hi!
Thanks for your reply.

Hmm... that's strange I can see them correctly. To be sure you can se then
correctly too i put them on my server under adress :
http://student.agh.edu.pl/~zientar/poms/ There you can find first and the
second one :) Maybe now you can help me :)

thanks.


Jörg Schaible wrote:
>
> Hi Maciej,
>
> well, your POM should contain XML tags ;-)
>
> ...
>
> Resend the message in a format please, that does not filter out the
> XML tags - otherwise noone can say something useful.
>
> - Jörg
>
> Wodzuu wrote on Thursday, April 19, 2007 8:42 AM:
>
>> Hi!
>>
>> I am a newbie in maven an i have one maybe silly question. I have
>> created one project with its pom.xml:
>>
>> <?xml version="1.0"?>
>>
>>     ejb
>>     com.sius.beans
>>     1.0-SNAPSHOT
>>
>>   4.0.0
>>   com.sius.beans
>>   ejb3
>>   ejb
>>   ejb :: ${artifactId}
>>   1.0-SNAPSHOT
>>   http://maven.apache.org
>>
>>
>>       junit
>>       junit
>>       3.8.1
>>       test
>>
>>
>>             org.jboss
>>             ejb3-persistence
>>             1.0-SNAPSHOT
>>             provided
>>
>>
>>             org.jboss
>>             jboss-ejb3x
>>             1.0-SNAPSHOT
>>             provided
>>
>>
>>
>>
>> I have executed commands:
>>
>> mvn package
>> mvn install
>>
>> Everything went right.
>>
>> Now I have another project that depends on previous one. (pom.xml):
>>
>> <?xml version="1.0"?>
>>
>>     ejb
>>     com.sius.beans
>>     1.0-SNAPSHOT
>>
>>   4.0.0
>>   com.sius.beans
>>   webapp
>>   war
>>   ejb :: ${artifactId}
>>   1.0-SNAPSHOT
>>
>>     webapp
>>
>>
>>
>>       junit
>>       junit
>>       3.8.1
>>       test
>>
>>
>>             org.jboss
>>             jboss-ejb3x
>>             1.0-SNAPSHOT
>>             provided
>>
>>
>>             com.sius.beans
>>             ejb3
>>             1.0-SNAPSHOT
>>
>>
>>
>>
>> i execute
>>
>> mvn package and i get the following error:
>>
>> [INFO] Failed to resolve artifact.
>>
>> GroupId: com.sius.beans
>> ArtifactId: ejb
>> Version: 1.0-SNAPSHOT
>>
>> Reason: Unable to download the artifact from any repository
>>
>>   com.sius.beans:ejb:pom:1.0-SNAPSHOT
>>
>> from the specified remote repositories:
>>   central (http://repo1.maven.org/maven2)
>>
>> Could someone help me in solving this problem ?
>> first project can be found in my local repo at
>> .m2\repository\com\sius\beans\ejb3\1.0-SNAPSHOT\ so I don't know what
>> to do.
>>
>> Thanks in advance.
>>
>> Maciej
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>

--
View this message in context:
http://www.nabble.com/Maven-does-not-find-artifact-in-local-repo-tf3605339s177.html#a10073396
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


Reply via email to