[ImageJ-devel] Help! - Maven/Eclipse problem with fiji.sc dependencies

[Tobias Pietzsch]

Hi Johannes,

thanks a lot for those pointers! I think I found it!
I traced it down to pom-fiji. It still has this section https://github.com/fiji/fiji/blob/master/pom.xml#L165-180
                <profile>
                        <id>eclipse</id>
                        <activation>
                                <property>
                                        <name>m2e.version</name>
                                </property>
                        </activation>
                        <dependencies>
                                <dependency>
                                        <groupId>net.java.sezpoz</groupId>
                                        <artifactId>sezpoz</artifactId>
                                        <version>${sezpoz.version}</version>
                                </dependency>
                        </dependencies>
                </profile>
which pulls in sezpoz with the undefined version.
I'm still working to put my setup back together into a working state, but that seems to be the cause of it.

Btw, can you recommend a good way to trace through the pom dependency tree?
I used a combination of Eclipse's "Effective pom", grep-ing in ~/.m2/repository, and pure luck… Are there better tools?

best regards,
Tobias


On Jan 17, 2014, at 2:39 PM, Johannes Schindelin <Johannes.Schindelin at gmx.de> wrote:

> Hi Tobias,
> 
> On Fri, 17 Jan 2014, Tobias Pietzsch wrote:
> 
>> ArtifactDescriptorException: Failed to read artifact descriptor for
>> net.java.sezpoz:sezpoz:jar:${sezpoz.version}:
>> ArtifactResolutionException: Failure to transfer
>> net.java.sezpoz:sezpoz:pom:${sezpoz.version} from
>> http://maven.imagej.net/content/repositories/releases was cached in the
>> local repository, resolution will not be reattempted until the update
>> interval of imagej.releases has elapsed or updates are forced.
> 
> We do not use Sezpoz anymore. I can only imagine that m2e (i.e. Eclipse's
> Maven support) cached the need for it somewhere, or that one of your
> other dependencies does. The pom-scijava does not define the
> sezpoz.version anymore.
> 
> A workaround would be to define sezpoz.version to 1.9-imagej, a proper
> solution would be to find out what is causing that dependency to be drawn
> in and update it accordingly.
> 
>> The weird thing is that from the command line everything works.
> 
> Command-line Maven is quite a bit more correct in its interpretation of
> the project configuration than m2e (or for that matter, than MiniMaven).
> 
> Ciao,
> Johannes

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20140117/ed8699b8/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20140117/ed8699b8/attachment.pgp>