You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Tarnopolsky, Alexander" <Al...@aspentech.com.INVALID> on 2023/05/14 10:39:00 UTC

Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Dear xalan contributors,

Our legacy code depends on xalan 2.7.2 and since the update on Maven Central our builds fail:


Anting /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build

/users/gdadmin/2022hf/project/toolworks/JDK/jdk-17.0.1/linux/bin/java \

    -Dant.home=/users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7 -classpath \

    /users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7/lib/ant-launcher.jar \

    org.apache.tools.ant.launch.Launcher

Buildfile: /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml

[resolver:resolve] Downloading https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml

[resolver:resolve] Downloaded https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml (646 B \

    at 0.6 KB/sec)

[resolver:resolve] Downloading https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml

[resolver:resolve] Downloaded https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml (435 B at \

    2.0 KB/sec)

[resolver:resolve] Downloading https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml

[resolver:resolve] Downloaded https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml (689 B at \

    4.4 KB/sec)

[resolver:resolve] Downloading https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml

[resolver:resolve] Downloaded https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml (317 B at 2.1 KB/sec)

[resolver:resolve] Downloading \

    https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml

[resolver:resolve] Downloaded \

    https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml (934 B at 5.0 KB/sec)

[resolver:resolve] Downloading https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml

[resolver:resolve] Downloaded https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml \

    (619 B at 4.0 KB/sec)



BUILD FAILED



/users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml:27: The following error occurred while \

    executing this line:

/users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/include.xml:14: Could not collect dependencies: \

    Failed to collect dependencies at xalan:xalan:jar:[2.7.2]

Total time: 6 seconds






The previous version of maven-metadata.xml contained declaration of several versions, including 2.7.2.

Now with the release of 2.7.3, olny the 2.7.3 appear in the https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml

Also, the depencency on serializer and xerces is no longer listed in https://repo1.maven.org/maven2/xalan/xalan/2.7.3/xalan-2.7.3.pom



Are those changes intentional?

Is there a way for us to keep using xalan 2.7.2 in our release branches?


Thanks,
Alexander Tarnopolsky
GSS_Team Lead, Dev Ops  |  Aspen Technology, Inc.
work: +972 99709624  |  www.aspentech.com<http://www.aspentech.com>

[cid:image001.png@01D9825A.00430500]

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
Joseph> Just a reminder:

Thank you for the reminder, however, it looks like you have responded to
the wrong thread.
The issue Alexander is facing right now does not involve Maven.
The issue involves Apache Ivy which fails to resolve Xalan 2.7.2 dependency.

External contributors are in a position to "submit a pull request" to fix
that.
You just can't fix that with a pull request.

From what I can tell, repository.apache.org data is corrupted, so it is
repository.apache.org that ships invalid metadata, and Central just
replicates it:
https://repository.apache.org/service/local/repositories/releases/content/xalan/xalan/maven-metadata.xml

I've filed a ticket to INFRA so they could trigger metadata rebuild:
https://issues.apache.org/jira/browse/INFRA-24595

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Joseph Kesselman <ke...@alum.mit.edu>.
Just a reminder: You do not need to be a committee to contribute to the Xalan project. As I've just demonstrated, you can work on a fork rather than a branch, then submit a pull request against that fork for the committers/approvers to evaluate.

So if Maven build is your top priority, _you_ can implement it and propose it. You can even invite folks to collaborate on it.

Or you can pay someone to do this.

Open source in action. If you need it now, make it happen. Otherwise you wait for someone else to be interested enough make it happen.


The Xalan _project_ is a big one, but it's build is relatively straightforward compared to some I've worked on. The biggest problem I see in moving to Mavin would be resolving jarfile dependencies; some of them won't be in Maven and the problem recurses.


As noted, making the project's Mavin _release_ cleaner is a separable question, and that's the one that seems to be the biggest ask here. It's probably worth making that its own issue and prioritizing it higher.  See earlier comments about how to actually make it happen.


For what it's worth,  I can probably be bribed to shift my own priorities and invest more hours. Though I admit that I'd have to bootstrap more Mavin to address these specific issues  properly; I have maintained Mavin builds but haven't written a nontrivial one de novo. And as I say, some of those jarfiles are themselves not in Mavin; there's at least one whose origin we're not completely sure of and a direct replacement may not exist.




--
   /_  Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
   /   https://www.amazon.com/dp/B09WJ3H657/

() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
________________________________
From: Vladimir Sitnikov <si...@gmail.com>
Sent: Sunday, May 14, 2023 10:48:54 AM
To: dev@xalan.apache.org <de...@xalan.apache.org>
Subject: Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml


https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml

Stanimir> Currently

I see that 2.7.2 is not listed there, and I think it is an issue.

Vladimir
--
Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml

Stanimir> Currently

I see that 2.7.2 is not listed there, and I think it is an issue.

Vladimir
-- 
Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Stanimir Stamenkov <s7...@netscape.net.INVALID>.
Sun, 14 May 2023 17:12:11 +0300, /Vladimir Sitnikov/:

> Gary> It sounds like your build does not set a version for xalan:xalan
> 
> Gary, the build failure ends with "Failed to collect dependencies at 
> xalan:xalan:jar:[2.7.2]",
> so it looks like they do look for a specific 2.7.2 version.

https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml

Currently:

     <metadata>
       <groupId>xalan</groupId>
       <artifactId>xalan</artifactId>
       <versioning>
         <latest>2.7.3</latest>
         <release>2.7.3</release>
         <versions>
           <version>2.7.3</version>
         </versions>
         <lastUpdated>20230504133529</lastUpdated>
       </versioning>
     </metadata>

-- 
Stanimir

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
> I've filed https://issues.apache.org/jira/browse/INFRA-24600 to get
assistance on the ways out.

Update: infra team updated maven-metadata.xml at Central, so it is valid
now.

See https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml

Alexander, Dominique,
Could you please check if the issue of "Failed to collect dependencies at
xalan:xalan:jar:[2.7.2]" is resolved now?

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
I've filed https://issues.apache.org/jira/browse/INFRA-24600 to get
assistance on the ways out.

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
Ok, I see the root cause.

Both xalan 2.7.1 and 2.7.2 were directly uploaded to Central, and those
versions never existed on repository.apache.org.
Then, in
https://issues.apache.org/jira/browse/INFRA-24533?focusedCommentId=17717955&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17717955
the team finally created a profile so xalan could be published to
repository.apache.org.

That caused metadata with a single 2.7.3 version which got replicated to
Central.

So I would ask Infra and Sonatype folks to collaborate on the best way
fixing this.
We could grab files from Central and publish them to repository.apache.org.
That sounds like the most promising idea, however, I don't now if it will
disrupt the synchronization from repository.apache.org to Central.

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
I got the file, and the test case there is the following (minimal pom
below):

    <dependency>
      <groupId>xalan</groupId>
      <artifactId>xalan</artifactId>
      <version>[2.7.2]</version>
    </dependency>

It causes Maven resolution to fail (see log below) when running something
like "mvn dependency:tree".
Frankly speaking, it is a bit strange to see version declaration like
[2.7.2] (why not just 2.7.2 without version ranges?)
However, it is a valid version declaration, so it might appear in practice.

The workaround is to use <version>2.7.2</version>, however, it won't
protect the project from accidentally using 2.7.3.
An alternative option is to just use 2.7.3, and add dependency on
xalan:serializer:2.7.3 side by side with xalan:xalan:2.7.3.
Both workarounds should fix the issue for the particular users, however, it
sounds devastating :(

I would say Maven could do better when resolving a range that is known to
have a single version only.
Maven could skip a query to maven-metadata.xml in that case.
However, we really need to update maven-metadata.xml somehow.

I will ask Sonatype to update maven-metadata.xml at Central, and then we
need to ask INFRA to restore old Xalan jars at repository.apache.org

The worst thing is that xalan 2.7.2 is no longer present at
repository.apache.org:
https://repository.apache.org/service/local/repositories/releases/content/xalan/xalan/2.7.2/xalan-2.7.2.pom
We basically lost a release artifact.

That might explain the reason maven-metadata.xml at repository.apache.org
misses 2.7.2 version (and the previous ones),
and it probably got synchronized to Central which caused the resolution
issue.

[INFO] Building Xalan-Issue-Reproducer 1.0.0
[INFO] --------------------------------[ jar
]---------------------------------
Downloading from central:
https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml
Downloaded from central:
https://repo.maven.apache.org/maven2/xalan/xalan/maven-metadata.xml (317 B
at 381 B/s)
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time:  1.096 s
[INFO] Finished at: 2023-05-16T18:09:39+03:00
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal on project xalan-issue-reproducer: Could not
resolve dependencies for project
com.example:xalan-issue-reproducer:jar:1.0.0: Failed to collect
dependencies at xalan:xalan:jar:[2.7.2,2.7.2]: No versions available for
xalan:xalan:jar:[2.7.2,2.7.2] within specified range -> [Help 1]


<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>com.example</groupId>
    <artifactId>xalan-issue-reproducer</artifactId>
    <version>1.0.0</version>
    <name>Xalan-Issue-Reproducer</name>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
  </properties>

  <dependencies>
    <dependency>
      <groupId>xalan</groupId>
      <artifactId>xalan</artifactId>
      <version>[2.7.2]</version>
    </dependency>
  </dependencies>
</project>

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Joseph Kesselman <ke...@alum.mit.edu>.
The usual solution when a file is too large for email is to put the file on a web storage service and send a download link to it. I've used Google Drive for the purpose, but anything that would let you generate a link that others could download from would do the job.

--
   /_  Joe Kesselman (he/him/his)
-/ _) My Alexa skill for New Music/New Sounds fans:
   /   https://www.amazon.com/dp/B09WJ3H657/

() Plaintext Ribbon Campaign
/\ Stamp out HTML mail!
________________________________
From: Ledit, Dominique <Do...@aspentech.com.INVALID>
Sent: Tuesday, May 16, 2023 5:05:33 AM
To: Vladimir Sitnikov <si...@gmail.com>; dev@xalan.apache.org <de...@xalan.apache.org>
Cc: DL SSE build mgr <EP...@aspentech.com>; de Donato, Laury <La...@aspentech.com>
Subject: RE: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml


Hi



I tried to send you a mail with a tar zipped file attached but it was rejected because of the size of the file.

How can I proceed to provide you with this file?

Thanks

Dominique Ledit
GSS_Dev Ops Specialist, Sr  |  AspenTech Europe, SA/NV
work: +33 559727914  |  www.aspentech.com<http://www.aspentech.com>



AspenTech Europe SA NV 1-7 Cours Valmy, 92800 Puteaux
Siège social de la société: 1-7 Cours Valmy, 92800 Puteaux
avec bureau à l’étranger: Aspen Technology, Inc., Siège social 20 Crosby Drive, Bedford, MA01730, USA, avec numéro d’enregistrement 2859683





From: Vladimir Sitnikov <si...@gmail.com>
Sent: Sunday, May 14, 2023 4:12 PM
To: dev@xalan.apache.org
Cc: DL SSE build mgr <EP...@aspentech.com>; de Donato, Laury <La...@aspentech.com>
Subject: Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml



Gary> It sounds like your build does not set a version for xalan:xalan



Gary, the build failure ends with "Failed to collect dependencies at xalan:xalan:jar:[2.7.2]",

so it looks like they do look for a specific 2.7.2 version.



It might be indeed a bit strange that the resolver checks xalan/xalan/maven-metadata.xml,

however, nothing says "maven-metadata.xml can be stale": https://maven.apache.org/repositories/metadata.html [maven.apache.org]<https://urldefense.com/v3/__https:/maven.apache.org/repositories/metadata.html__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s57nKyPLg$>



At the same time, it looks like Apache Ivy uses maven-metadata.xml by default (see useMavenMetadata):

https://ant.apache.org/ivy/history/2.5.0/resolver/ibiblio.html [ant.apache.org]<https://urldefense.com/v3/__https:/ant.apache.org/ivy/history/2.5.0/resolver/ibiblio.html__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s5XmQmPv8$>



Alexander>Also, the depencency on serializer and xerces is no longer listed



Alexander, It is a known issue: https://issues.apache.org/jira/browse/XALANJ-2649 [issues.apache.org]<https://urldefense.com/v3/__https:/issues.apache.org/jira/browse/XALANJ-2649__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s5BbJVfQI$>



Alexander>Is there a way for us to keep using xalan 2.7.2 in our release branches?



As a workaround, you might try adding useMavenMetadata="false" to your Ivy configs (I've no clue if it really helps or not).

However, it would help if you could share a small reproducer (e.g. Ant+Ivy file that fails to resolve Xalan 2.7.2)



Vladimir

RE: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by "Ledit, Dominique" <Do...@aspentech.com.INVALID>.
Hi

I tried to send you a mail with a tar zipped file attached but it was rejected because of the size of the file.
How can I proceed to provide you with this file?
Thanks

Dominique Ledit
GSS_Dev Ops Specialist, Sr  |  AspenTech Europe, SA/NV
work: +33 559727914  |  www.aspentech.com<http://www.aspentech.com>



AspenTech Europe SA NV 1-7 Cours Valmy, 92800 Puteaux
Siège social de la société: 1-7 Cours Valmy, 92800 Puteaux
avec bureau à l’étranger: Aspen Technology, Inc., Siège social 20 Crosby Drive, Bedford, MA01730, USA, avec numéro d’enregistrement 2859683


From: Vladimir Sitnikov <si...@gmail.com>
Sent: Sunday, May 14, 2023 4:12 PM
To: dev@xalan.apache.org
Cc: DL SSE build mgr <EP...@aspentech.com>; de Donato, Laury <La...@aspentech.com>
Subject: Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Gary> It sounds like your build does not set a version for xalan:xalan

Gary, the build failure ends with "Failed to collect dependencies at xalan:xalan:jar:[2.7.2]",
so it looks like they do look for a specific 2.7.2 version.

It might be indeed a bit strange that the resolver checks xalan/xalan/maven-metadata.xml,
however, nothing says "maven-metadata.xml can be stale": https://maven.apache.org/repositories/metadata.html [maven.apache.org]<https://urldefense.com/v3/__https:/maven.apache.org/repositories/metadata.html__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s57nKyPLg$>

At the same time, it looks like Apache Ivy uses maven-metadata.xml by default (see useMavenMetadata):
https://ant.apache.org/ivy/history/2.5.0/resolver/ibiblio.html [ant.apache.org]<https://urldefense.com/v3/__https:/ant.apache.org/ivy/history/2.5.0/resolver/ibiblio.html__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s5XmQmPv8$>

Alexander>Also, the depencency on serializer and xerces is no longer listed

Alexander, It is a known issue: https://issues.apache.org/jira/browse/XALANJ-2649 [issues.apache.org]<https://urldefense.com/v3/__https:/issues.apache.org/jira/browse/XALANJ-2649__;!!ApAMwfxt6g!-0kN-BDY0N3DyF6JBpBltkjGm3u5oV52gfTRxXp5sM7HgmUg2yDhCEI34YYYNGKZKvbhC_i5-GzwCv3qCzPUS9s5BbJVfQI$>

Alexander>Is there a way for us to keep using xalan 2.7.2 in our release branches?

As a workaround, you might try adding useMavenMetadata="false" to your Ivy configs (I've no clue if it really helps or not).
However, it would help if you could share a small reproducer (e.g. Ant+Ivy file that fails to resolve Xalan 2.7.2)

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Vladimir Sitnikov <si...@gmail.com>.
Gary> It sounds like your build does not set a version for xalan:xalan

Gary, the build failure ends with "Failed to collect dependencies at
xalan:xalan:jar:[2.7.2]",
so it looks like they do look for a specific 2.7.2 version.

It might be indeed a bit strange that the resolver checks
xalan/xalan/maven-metadata.xml,
however, nothing says "maven-metadata.xml can be stale":
https://maven.apache.org/repositories/metadata.html

At the same time, it looks like Apache Ivy uses maven-metadata.xml by
default (see useMavenMetadata):
https://ant.apache.org/ivy/history/2.5.0/resolver/ibiblio.html

Alexander>Also, the depencency on serializer and xerces is no longer listed

Alexander, It is a known issue:
https://issues.apache.org/jira/browse/XALANJ-2649

Alexander>Is there a way for us to keep using xalan 2.7.2 in our release
branches?

As a workaround, you might try adding useMavenMetadata="false" to your Ivy
configs (I've no clue if it really helps or not).
However, it would help if you could share a small reproducer (e.g. Ant+Ivy
file that fails to resolve Xalan 2.7.2)

Vladimir

Re: Update of xalan 2.7.3 at Maven Central repository wiped metadata for previous versions from maven-metadata.xml

Posted by Gary Gregory <ga...@gmail.com>.
Hello Alexander,

It sounds like your build does not set a version for xalan:xalan, in which
case your build system might be choosing for you to use whatever is the
latest version.

Gary

On Sun, May 14, 2023, 08:38 Tarnopolsky, Alexander
<Al...@aspentech.com.invalid> wrote:

> Dear xalan contributors,
>
>
>
> Our legacy code depends on xalan 2.7.2 and since the update on Maven
> Central our builds fail:
>
>
>
> Anting /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build
>
> /users/gdadmin/2022hf/project/toolworks/JDK/jdk-17.0.1/linux/bin/java \
>
>
> -Dant.home=/users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7
> -classpath \
>
>
> /users/gdadmin/2022hf/project/toolworks/ANT/apache-ant-1.10.7/lib/ant-launcher.jar
> \
>
>     org.apache.tools.ant.launch.Launcher
>
> Buildfile:
> /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml
>
> [resolver:resolve] Downloading
> https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml
>
> [resolver:resolve] Downloaded
> https://repo1.maven.org/maven2/commons-lang/commons-lang/maven-metadata.xml
> (646 B \
>
>     at 0.6 KB/sec)
>
> [resolver:resolve] Downloading
> https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml
>
> [resolver:resolve] Downloaded
> https://repo1.maven.org/maven2/com/toedter/jcalendar/maven-metadata.xml
> (435 B at \
>
>     2.0 KB/sec)
>
> [resolver:resolve] Downloading
> https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml
>
> [resolver:resolve] Downloaded
> https://repo1.maven.org/maven2/com/miglayout/miglayout/maven-metadata.xml
> (689 B at \
>
>     4.4 KB/sec)
>
> [resolver:resolve] Downloading
> https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml
>
> [resolver:resolve] Downloaded
> https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml (317 B at
> 2.1 KB/sec)
>
> [resolver:resolve] Downloading \
>
>
> https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml
>
> [resolver:resolve] Downloaded \
>
>
> https://repo1.maven.org/maven2/commons-collections/commons-collections/maven-metadata.xml
> (934 B at 5.0 KB/sec)
>
> [resolver:resolve] Downloading
> https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml
>
> [resolver:resolve] Downloaded
> https://repo1.maven.org/maven2/commons-digester/commons-digester/maven-metadata.xml
> \
>
>     (619 B at 4.0 KB/sec)
>
>
>
> BUILD FAILED
>
>
>
> /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/build.xml:27:
> The following error occurred while \
>
>     executing this line:
>
> /users/gdadmin/2022hf/project/src/library/Drilling/Interop/build/include.xml:14:
> Could not collect dependencies: \
>
>     Failed to collect dependencies at xalan:xalan:jar:[2.7.2]
>
> Total time: 6 seconds
>
>
>
>
>
>
>
> The previous version of maven-metadata.xml contained declaration of
> several versions, including 2.7.2.
>
> Now with the release of 2.7.3, olny the 2.7.3 appear in the
> https://repo1.maven.org/maven2/xalan/xalan/maven-metadata.xml
>
> Also, the depencency on serializer and xerces is no longer listed in
> https://repo1.maven.org/maven2/xalan/xalan/2.7.3/xalan-2.7.3.pom
>
>
>
> Are those changes intentional?
>
> Is there a way for us to keep using xalan 2.7.2 in our release branches?
>
> Thanks,
> Alexander Tarnopolsky
> GSS_Team Lead, Dev Ops  |  Aspen Technology, Inc.
> work: +972 99709624  |  www.aspentech.com
>
>
>
>
>