You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Dieter Stüken <d....@conterra.de> on 2017/07/18 13:34:21 UTC

sis-referencing 0.8-jdk8-SNAPSHOT

Hmm...

I'm just trying to use 0.8-jdk8-SNAPSHOT. Unfortunately I got some error like:

The POM for org.apache.sis.core:sis-referencing:jar:0.8-jdk8-20170717.215031-446 is missing

I'm not an expert with maven, but if I have a look at:

https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/0.8-jdk8-SNAPSHOT

I notice it is named:

sis-referencing-0.8-jdk8-20170717.215030-446.jar<https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/0.8-jdk8-SNAPSHOT/sis-referencing-0.8-jdk8-20170717.215030-446.jar>

while maven-metadata.xml refers to ...215031-446.jar

Is there a "temporary" problem with the maven deployment?
Will see, if the problem vanishes with the next build tonight.

Dieter.

Dieter Stüken
Software Engineer
Natur, Umwelt, Ressourcen

con terra - Gesellschaft für Angewandte Informationstechnologie mbH
Martin-Luther-King-Weg 24
48155 Münster
Telefon +49 89 207 005 2267
D.Stueken@conterra.de<ma...@conterra.de>
www.conterra.de<https://www.conterra.de/>

Geschäftsführung: Karl Wiesmann, Uwe König
HRB 4149, Amtsgericht Münster
Ust. IDNr. DE 162264061


Re: sis-referencing 0.8-jdk8-SNAPSHOT

Posted by Martin Desruisseaux <ma...@geomatys.com>.
Hello Dieter

(Thanks Steve for letting know that it worked for you - at least for
this time)

Le 19/07/2017 à 10:26, Dieter Stüken a écrit :

> this time
> https://repository.apache.org/(…snip…)/sis-metadata/0.8-jdk8-SNAPSHOT/
> was hit:
>
Yes, I was fearing that something like that would happen.

> Seems to be a problem with the maven build system. How are those
> timestamps and the sequence number generated?
>
It is done by the standard Maven plugin; I do not know their internal.
Normally it is "maven-jar-plugin". In Apache SIS case, we use
"maven-bundle-plugin" instead, which is supposed to do the same thing
with some extra information for OSGi bundles.


> I have the current snapshot checked out. Is it some maven plugin? Can
> I reproduce and analyze such a deployment locally?
>
Yes. You can add the following lines somewhere in the root pom.xml file
(e.g. just before the closing </project> tag):

      <distributionManagement>
        <repository>
          <id>test</id>
          <url>file:///path/to/my/directory</url>
        </repository>
      </distributionManagement>

Then, execution of "mvn deploy" shoud write in the
"/path/to/my/directory". However I'm not sure it will reproduce the
issue, because I suspect that the bug is caused by the delay between the
different files written by Maven, and writing to a local repository
would be may too fast for allowing the bug to show.

I have limited internet connection now because I'm at FOSS4G-Europe, but
next week I should be more reactive. One thing that we may try is to
abandon (for now) the use of "maven-bundle-plugin" and use the more
usual "maven-jar-plugin" instead. We would loose OSGi support on JDK8
branch, but we could keep it on trunk. Anyway, with JDK9 modularisation,
I do not know if it is worth to keep OSGi for Apache SIS.

    Martin



RE: sis-referencing 0.8-jdk8-SNAPSHOT

Posted by Dieter Stüken <d....@conterra.de>.
Hi Martin,

this time  https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-metadata/0.8-jdk8-SNAPSHOT/ was hit:

sis-metadata-0.8-jdk8-20170718.214026-447.jar versus ...214027-447.jar

my workaround was to manually download the files into my local .m2/ repository and rename them.
It's a bit annoying but it works by now.

Seems to be a problem with the maven build system. 
How are those timestamps and the sequence number generated?
I have the current snapshot checked out. Is it some maven plugin? 
Can I reproduce and analyze such a deployment locally?

Dieter.

-----Original Message-----
From: Martin Desruisseaux [mailto:martin.desruisseaux@geomatys.com] 
Sent: Mittwoch, 19. Juli 2017 00:27
To: dev@sis.apache.org
Subject: Re: sis-referencing 0.8-jdk8-SNAPSHOT

Indeed, the maven-metadata.xml content mismatched the actual filenames again. I launched another build, and the maven-metadata.xml content
(0.8-jdk8-20170718.214118-447) now seems to matches the actual filenames. Would you have a chance to test?

However given that the matches or mismatches seem to happen randomly, I worry that even if it work this time, it may break after any future build. If it happen again, I will ask on the Maven mailing list if this is a known issue.

    Martin


Le 18/07/2017 à 15:34, Dieter Stüken a écrit :

> Hmm...
>
> I'm just trying to use 0.8-jdk8-SNAPSHOT. Unfortunately I got some error like:
>
> The POM for 
> org.apache.sis.core:sis-referencing:jar:0.8-jdk8-20170717.215031-446 
> is missing
>
> I'm not an expert with maven, but if I have a look at:
>
> https://repository.apache.org/content/groups/snapshots/org/apache/sis/
> core/sis-referencing/0.8-jdk8-SNAPSHOT
>
> I notice it is named:
>
> sis-referencing-0.8-jdk8-20170717.215030-446.jar<https://repository.ap
> ache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/
> 0.8-jdk8-SNAPSHOT/sis-referencing-0.8-jdk8-20170717.215030-446.jar>
>
> while maven-metadata.xml refers to ...215031-446.jar
>
> Is there a "temporary" problem with the maven deployment?
> Will see, if the problem vanishes with the next build tonight.
>
> Dieter.


RE: sis-referencing 0.8-jdk8-SNAPSHOT

Posted by HRUDA Steve <st...@hexagongeospatial.com>.
That solves my issue too. I'm now able to get the latest SNAPSHOT version of sis-referencing 0.8.

Regards,
Steve




Diese E-Mail wurde versandt im Auftrag des Unternehmens Intergraph Ges.m.b.H.
Vertretungsberechtigte Geschäftsführer: Maximilian Weber
Sitz der Gesellschaft: Margaretenstraße 70/I/1, 1050 Wien, Österreich, Tel. +43 (1) 9610567-0
Eingetragen beim Handelsgericht Wien, Firmenbuch-Nr.: FN 116859 b
Umsatzsteuer-Identifikationsnummer / VAT-ID: ATU15138401, Steuer-Nummer: 264/4807

This E-Mail has been sent on behalf of the company Intergraph Ges.m.b.H.
Authorised Managing Directors: Maximilian Weber
Registered office and Austrian headquarters: Margaretenstr. 70/I/1, 1050 Wien, Austria, Tel. +43 (1) 9610567-0
The company is recorded at the commercial court of Vienna under the company register number FN 116859 b
VAT-ID: ATU15138401, Austrian Tax ID: 264/4807

Diese E-Mail (mit zugehörigen Dateien) enthält möglicherweise Informationen, die vertraulich sind, dem Urheberrecht unterliegen oder ein Geschäftsgeheimnis darstellen. Falls Sie diese Nachricht irrtümlicherweise erhalten haben, benachrichtigen Sie uns bitte umgehend, indem Sie eine Antwort senden, und löschen Sie bitte diese E-Mail und Ihre Antwort darauf. Sämtliche aufgeführten Ansichten oder Meinungen sind ausschließlich diejenigen des Autors und entsprechen nicht notwendigerweise denen des Unternehmens Intergraph.

This E-Mail (and any attachments) may be confidential and protected by legal privilege. If you are not the intended recipient please notify us immediately by replying to the sender and delete this E-Mail and your reply from your system. All the views and opinions published here are solely based on the author's own opinion and should not be considered necessarily as reflecting the opinion of Intergraph.


-----Original Message-----
From: Martin Desruisseaux [mailto:martin.desruisseaux@geomatys.com]
Sent: Wednesday, July 19, 2017 12:27 AM
To: dev@sis.apache.org
Subject: Re: sis-referencing 0.8-jdk8-SNAPSHOT

Indeed, the maven-metadata.xml content mismatched the actual filenames again. I launched another build, and the maven-metadata.xml content
(0.8-jdk8-20170718.214118-447) now seems to matches the actual filenames. Would you have a chance to test?

However given that the matches or mismatches seem to happen randomly, I worry that even if it work this time, it may break after any future build. If it happen again, I will ask on the Maven mailing list if this is a known issue.

    Martin


Le 18/07/2017 à 15:34, Dieter Stüken a écrit :

> Hmm...
>
> I'm just trying to use 0.8-jdk8-SNAPSHOT. Unfortunately I got some error like:
>
> The POM for
> org.apache.sis.core:sis-referencing:jar:0.8-jdk8-20170717.215031-446
> is missing
>
> I'm not an expert with maven, but if I have a look at:
>
> https://repository.apache.org/content/groups/snapshots/org/apache/sis/
> core/sis-referencing/0.8-jdk8-SNAPSHOT
>
> I notice it is named:
>
> sis-referencing-0.8-jdk8-20170717.215030-446.jar<https://repository.ap
> ache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/
> 0.8-jdk8-SNAPSHOT/sis-referencing-0.8-jdk8-20170717.215030-446.jar>
>
> while maven-metadata.xml refers to ...215031-446.jar
>
> Is there a "temporary" problem with the maven deployment?
> Will see, if the problem vanishes with the next build tonight.
>
> Dieter.


Re: sis-referencing 0.8-jdk8-SNAPSHOT

Posted by Martin Desruisseaux <ma...@geomatys.com>.
Indeed, the maven-metadata.xml content mismatched the actual filenames
again. I launched another build, and the maven-metadata.xml content
(0.8-jdk8-20170718.214118-447) now seems to matches the actual
filenames. Would you have a chance to test?

However given that the matches or mismatches seem to happen randomly, I
worry that even if it work this time, it may break after any future
build. If it happen again, I will ask on the Maven mailing list if this
is a known issue.

    Martin


Le 18/07/2017 à 15:34, Dieter Stüken a écrit :

> Hmm...
>
> I'm just trying to use 0.8-jdk8-SNAPSHOT. Unfortunately I got some error like:
>
> The POM for org.apache.sis.core:sis-referencing:jar:0.8-jdk8-20170717.215031-446 is missing
>
> I'm not an expert with maven, but if I have a look at:
>
> https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/0.8-jdk8-SNAPSHOT
>
> I notice it is named:
>
> sis-referencing-0.8-jdk8-20170717.215030-446.jar<https://repository.apache.org/content/groups/snapshots/org/apache/sis/core/sis-referencing/0.8-jdk8-SNAPSHOT/sis-referencing-0.8-jdk8-20170717.215030-446.jar>
>
> while maven-metadata.xml refers to ...215031-446.jar
>
> Is there a "temporary" problem with the maven deployment?
> Will see, if the problem vanishes with the next build tonight.
>
> Dieter.