Just make your changes and run the build. All cross-references will be
updated to match the new version during the build. This is how we
produce patch releases.
One problem we still haven't figured out, and this isn't specific to
m2e, is how to manage patch releases produced by different teams in
parallel. Say, for example, if your team provides a 1.5.0 patch release
and my team does the same. Most likely our two patch releases will be
incompatible in some ways. We need to communicate this to the user
somehow and ideally block updates between patch released provided by
different teams, but I don't know how to do this yet.
Btw, you know EPL requires you to provide changes somewhere we can
access, right? ;-)
--
Regards,
Igor
On 2014-10-22, 9:08, Lucas Persson wrote:
Hi Igor
yeah, I am trying to patch one of the plugins and I think I need to use
the exact same version and version qualifier as the original plugin.
Since there is a lot of cross referencing between plugins using version
I though it was best to sue the exact same version.
But I suppose I can just patch the original jar too with the new class.
/Lucas
22 okt 2014 kl. 15:05 skrev Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>>:
If you build from the tag, the contents of the build should be identical
to the release, minus version qualifier.
Do you mind explaining what you are trying to achieve?
From my experience, I never needed to recreate a release, I always
needed to produce a patched version of a release. This is why
I never setup "perfect" reproducible build for m2e (or any other project
for that matter).
--
Regards,
Igor
On 2014-10-22, 9:00, Lucas Persson wrote:
Hi
I am trying to build the m2e plugins.
I just cloned the repo and checked out the 1.5.0 release tag.
But when I build the version seems to still be 1.5.0-SNAPSHOT instead of
1.5.0.20140606-0033
How shall I do to re-crate the release build?
Thanks
Lucas
--
Oracle <http://www.oracle.com <http://www.oracle.com/>>
Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 <tel:+4684773644> | Mobile: +46730946656
<tel:+46730946656>
Oracle Communications Platform
ORACLE Sweden | Söder Mälarstrand 29, 6 tr | 118 25 Stockholm
Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA,reg.no
<http://reg.no/>
<http://reg.no <http://reg.no/>>. 556254-6746
Green Oracle <http://www.oracle.com/commitment>Oracle is committed to
developing practices and products that help protect the environment
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
--
Oracle <http://www.oracle.com>
Lucas Persson | Principal Member of Technical Staff
Phone: +4684773644 <tel:+4684773644> | Mobile: +46730946656
<tel:+46730946656>
Oracle Communications Platform
ORACLE Sweden | Söder Mälarstrand 29, 6 tr | 118 25 Stockholm
Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no
<http://reg.no>. 556254-6746
Green Oracle <http://www.oracle.com/commitment> Oracle is committed to
developing practices and products that help protect the environment
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev
