2008/7/2 Sahoo <[EMAIL PROTECTED]>:
> Stuart McCulloch wrote:
>
>> 2008/7/2 Sahoo <[EMAIL PROTECTED]>:
>>
>>
>>
>>> I am seeing build failures, because maven is downloading files with
>>> .bundle
>>> extension as opposed to .jar as shown below:
>>> Downloading
>>>
>>> http://download.java.net/maven/glassfish/org/glassfish/admin/admin-cli/10.0-SNAPSHOT/admin-cli-10.0-SNAPSHOT.bundle
>>>
>>> It is true the above artifact was produced by a plugin which uses custom
>>> packaging type called "bundle." But, why should that matter? Let me know
>>> if
>>> you want any further info. I need some help immediately.
>>>
>>>
>>>
>>
>> this is possibly related to http://jira.codehaus.org/browse/MNG-1682
>>
>>
> Yes, it looks like that. I looked at the Felix bug
> (https://issues.apache.org/jira/browse/FELIX-198) and it does have an
> interesting note that says this bug appears when atleast three custom
> packaging types are involved, which appear to be true in my case as
> well. I use maven-bundle-plugin and two other home grown plugins.
>
>> I think you'll need to provide the Maven debug output somewhere (mvn -X
>> ...)
>>
>>
> Please see the attachment.
>
>> and perhaps also the <dependency> details of the artifact being downloaded
>> ie. does the <dependency> have <type>bundle</type>, or no <type> ?
>>
>>
> Unfortunately, the dependencies are not published in any public repo
> yet, otherwise I would have been able to provide the URL. How do I check
> this detail? I looked at admin-cli-10.0-SNAPSHOT.pom in my local
> repository and I do see it has <packaging>bundle</packaging>.
>
I was thinking more about the pom that is pulling down this
dependency - for example do you use something like this:
<dependency>
<groupId>foo</groupId>
<artifactId>bar</artifactId>
<version>1.0</version>
<type>bundle</type>
</dependency>
or:
<dependency>
<groupId>foo</groupId>
<artifactId>bar</artifactId>
<version>1.0</version>
</dependency>
in whichever pom defines this dependency?
> the Maven version and platform are always useful when reporting any issue
>>
>> there have been issues with this in the past on various multi-module
>> projects
>> where Maven tried to install the artifact using the packaging name rather
>> than
>> the extension set in the component descriptor (we currently workaround
>> this
>> issue in the plugin) but this is the first time I've seen it wrt
>> downloading
>>
>>
> My env. is like this:
>
> Maven version: 2.0.7
> Java version: 1.5.0_13-rev
> OS name: "sunos" version: "5.11" arch: "x86"
>
>
> Thanks a lot for your help. I really appreciate it.
>
> Best regards,
> Sahoo
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
--
Cheers, Stuart
