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 <dominique.le...@aspentech.com.INVALID> Sent: Tuesday, May 16, 2023 5:05:33 AM To: Vladimir Sitnikov <sitnikov.vladi...@gmail.com>; dev@xalan.apache.org <dev@xalan.apache.org> Cc: DL SSE build mgr <epsbuild...@aspentech.com>; de Donato, Laury <laury.dedon...@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 <sitnikov.vladi...@gmail.com> Sent: Sunday, May 14, 2023 4:12 PM To: dev@xalan.apache.org Cc: DL SSE build mgr <epsbuild...@aspentech.com>; de Donato, Laury <laury.dedon...@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
