You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Chris Helck <Ch...@us.icap.com> on 2010/11/12 18:18:17 UTC
What is the right way to create a patch jar file?
I need to support patching: creating a jar file that has just those
classes modified since a base line. Is Maven the right tool to do this?
If so how? There is a patch plugin for Maven1, but nothing for Maven2.
Thanks,
C. Helck
**********************************************************************
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**********************************************************************
RE: What is the right way to create a patch jar file?
Posted by Chris Helck <Ch...@us.icap.com>.
Sorry, I was not clear. I don't mean patchng source code.
Suppose we create foo_1.2.3.jar and it is in production. A bug is found.
Normally we'd fix the bug, create a new release called foo_1.2.4.jar,
test it, and deploy it to production. But, my operations group would, in
certain circumstances, prefer a patch jar file containing just the
classes modified by the bug fix. The patch jar would be called
foo_1.2.3.p1.jar and would be much smaller then the 1.2.4 jar.
Operations would deploy it so that it goes in the front of the
application's classpaths.
I think that this patch stuff is a deployment issue and not a build
issue. I would like to leave Maven out of this entirely if I can, I
think what I would really like is a utility that takes two jar files and
creates a new jar file just containing those classes that are different.
I'm not sure if such a thing exists because class files have creation
timestamps embedded within them that are different for each build.
Hope it's clearer now.
-Chris Helck
-----Original Message-----
From: Wendy Smoak [mailto:wsmoak@gmail.com]
Sent: Friday, November 12, 2010 12:28 PM
To: Maven Users List
Subject: Re: What is the right way to create a patch jar file?
On Fri, Nov 12, 2010 at 12:18 PM, Chris Helck <Ch...@us.icap.com>
wrote:
> I need to support patching: creating a jar file that has just those
> classes modified since a base line. Is Maven the right tool to do
this?
> If so how? There is a patch plugin for Maven1, but nothing for Maven2.
There is this... https://maven.apache.org/plugins/maven-patch-plugin/
(not sure if that has the same functionality as the Maven 1 plugin
though.)
Is this your code? If so I'd branch just that module, say from the
2.5.6 release, make the change, and release version 2.5.6.1 of that jar.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
**********************************************************************
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**********************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: What is the right way to create a patch jar file?
Posted by Wendy Smoak <ws...@gmail.com>.
On Fri, Nov 12, 2010 at 12:18 PM, Chris Helck <Ch...@us.icap.com> wrote:
> I need to support patching: creating a jar file that has just those
> classes modified since a base line. Is Maven the right tool to do this?
> If so how? There is a patch plugin for Maven1, but nothing for Maven2.
There is this... https://maven.apache.org/plugins/maven-patch-plugin/
(not sure if that has the same functionality as the Maven 1 plugin
though.)
Is this your code? If so I'd branch just that module, say from the
2.5.6 release, make the change, and release version 2.5.6.1 of that
jar.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org