Project

Profile

Help

Actions
Send by e-mail Copy link

Support #1897

closed

Saxon-HE binary jar not properly compressed (only under maven)

Added by Stéphane Landelle about 11 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Low
Assignee:
O'Neil Delpratt
Category:
Build and release
Sprint/Milestone:
-
Start date:
2013-09-11
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:

Description

Hi,

Saxon-HE jar is currently about 10Mo.

It doesn't seem to be properly compressed, like any other regular jar.

For example, if I just decompress and re-compress it with any regular zip client, or even jar command, it falls to about 4Mo.

This is causing a lot of bandwith and storage space on our CI system.

Regards,

Stéphane Landelle

Actions
Copy link
 #1

Updated by Michael Kay about 11 years ago

  • Category set to Build and release
  • Status changed from New to In Progress

Thanks for reporting it. The decision not to compress the JAR file was a deliberate one made many years ago in response to advice that this would improve start-up/loading time, which for typical Saxon use cases is more important than the speed of downloading the software from the network. We will review the decision to see whether this trade-off is still correct, or whether the reasoning is now different. Perhaps the fact that many people now download repeatedly using Maven makes a difference.

Actions
Copy link
 #2

Updated by Stéphane Landelle about 11 years ago

OK, get it.

If you don't want to make a choice, a solution would be to deploy both

uncompressed an compressed versions, having the compressed one use a

classifier:

http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html

2013/9/11 Saxonica Developer Community

Actions
Copy link
 #3

Updated by O'Neil Delpratt about 11 years ago

Hi,

I am looking into folowing through with your suggestion in comment #2. Do I need to add something in the POM file or is it as simple as creating an additional jar file with a name like Saxon-HE-9.5.1.2-dev.jar (i.e. compressed version)?

Actions
Copy link
 #4

Updated by Stéphane Landelle about 11 years ago

I see 2 solutions:

  • either deploy two jars of the same (groupId, artifactId) with different

classifiers (sources and javadoc are actually classifiers). In this case,

they share the same pom.

  • or deploy two jars with different artifactId. In this case, they have

different poms.

As you wish.

2013/9/12 Saxonica Developer Community

Actions
Copy link
 #5

Updated by Stéphane Landelle about 11 years ago

How do you build your maven files? Manually or really from maven? Maybe I

can help.

2013/9/12 Saxonica Developer Community

Actions
Copy link
 #6

Updated by O'Neil Delpratt about 11 years ago

We use an ant build script to create the jar files required for maven. The files are then uploaded and released at https://oss.sonatype.org

There is a manual step when generating keys for the files.

Actions
Copy link
 #7

Updated by Stéphane Landelle about 11 years ago

Then I guess the classifier is the easiest solution for you: either modify

your ant build so it generates a second compressed jar, or unzip/re-zip

manually, and just upload with a classifier along the other binaries.

2013/9/12 Saxonica Developer Community

Actions
Copy link
 #8

Updated by O'Neil Delpratt about 11 years ago

  • Assignee set to O'Neil Delpratt
  • Found in version set to 9.5

Ok we will add this compressed jar with the classifier in the next maintenance release of Saxon on maven.

Thanks.

Actions
Copy link
 #9

Updated by Stéphane Landelle about 11 years ago

Great, thanks a lot!

2013/9/13 Saxonica Developer Community

Actions
Copy link
 #10

Updated by Stéphane Landelle about 11 years ago

We're in the process of releasing on maven central.

Do you have any idea about the date of the next release, please?

Actions
Copy link
 #11

Updated by Michael Kay about 11 years ago

We're not planning an imminent maintenance release as there are no critical fixes waiting to go out. It might be a month or so - more or less depending what issues crop up.

Actions
Copy link
 #12

Updated by Stéphane Landelle about 11 years ago

Hi,

I see that you've released Saxon-HE 9.5.1-3. Will you be able to deploy on maven central, both uncompressed and compressed?

Regards,

Stéphane

Actions
Copy link
 #13

Updated by O'Neil Delpratt about 11 years ago

  • Tracker changed from Bug to Support
  • Subject changed from Saxon-HE binary jar not properly compressed to Saxon-HE binary jar not properly compressed (only under maven)
  • Status changed from In Progress to Resolved

The Saxon 9.5.1.3 maven artifact has now been released. As requested I have included a more compressed jar to the release. So now we have the following Saxon jars in the maven repository:

  • Saxon-HE-9.5.1-3.jar

  • Saxon-HE-9.5.1-3-compressed.jar

Actions
Copy link
 #14

Updated by Stéphane Landelle about 11 years ago

Great!

I see the artifacts in Sonatype, waiting for central sync.

Thanks a lot for your help and this great library!

Actions
Copy link
 #15

Updated by O'Neil Delpratt over 10 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100

Closing this support issue as it was fixed in Saxon 9.5.1.3

Please register to edit this issue

Actions
Send by e-mail Copy link

Also available in: Atom PDF