[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] Tycho versus the maven-release-plugin
|
Hm, I haven't thought about it, looks like API Tools needs to be extended :)
On Tue, Jul 5, 2011 at 12:09 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:
> API Tools is just part of the story. Things like resources and pom.xml
> contents (think compiler configuration or source file encoding, for
> example), should also be taken into account when deciding if version
> change is necessary.
>
> --
> Regards,
> Igor
>
> On 11-07-05 1:54 AM, Danail Nachev wrote:
>>
>> API Tools can help you manage your versions based on the changes in the
>> module, but it doesn't support tycho, so changes are applied only in the
>> manifest. Have a look and see whether it can help you.
>>
>> On 4 Jul 2011 18:06, "Igor Fedorenko" <igor@xxxxxxxxxxxxxx
>> <mailto:igor@xxxxxxxxxxxxxx>> wrote:
>> > I think it is a good idea to support smart(er) version management, but
>> I
>> > am not aware of any software that can automate this for you.
>> >
>> > --
>> > Regards,
>> > Igor
>> >
>> > On 11-07-04 6:55 PM, motes motes wrote:
>> >> Thanks this works fine with my application!
>> >>
>> >> But how do I manage/release projects with many sub modules (around
>> >> 15-20 bundles)?
>> >>
>> >> Using the approach described at the link will just generate the same
>> >> version for the parent and all sub projects (which maybe is a good way
>> >> to create the first release). As a result sub projects that have not
>> >> been modified now appears as if they have changed - will also be
>> >> downloaded when a user updates the application.
>> >>
>> >> Is it possible to get a more fine grained control of the release
>> >> process for projects with many sub projects? I know this a more
>> >> general question and relates to basic knowledge of versioning software
>> >> but maybe you can point me to some directions/give hints to good
>> >> practices?
>> >>
>> >>
>> >>
>> >>
>> >> On Fri, Jul 1, 2011 at 2:19 PM, Igor Fedorenko<igor@xxxxxxxxxxxxxx
>> <mailto:igor@xxxxxxxxxxxxxx>> wrote:
>> >>> See how we use it to release m2e, for example
>> >>>
>> >>>
>>
>> https://docs.sonatype.org/display/M2ECLIPSE/Staging+and+releasing+new+M2Eclipse+release
>> >>>
>> >>> --
>> >>> Regards,
>> >>> Igor
>> >>>
>> >>> On 11-07-01 2:56 PM, motes motes wrote:
>> >>>>
>> >>>> Could you give an example on how to run tycho-versions-plugin to
>> >>>> update pom versions? I have looked at:
>> >>>>
>> >>>> https://issues.sonatype.org/browse/TYCHO-214
>> >>>>
>> >>>> but it does not show how the plugin is used/called.
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Mon, May 30, 2011 at 3:08 PM, Igor
>> Fedorenko<igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>
>> >>>> wrote:
>> >>>>>
>> >>>>> We use tycho-versions-plugin to set versions in pom.xml and eclipse
>> >>>>> metadata files en masse. The rest is manual.
>> >>>>>
>> >>>>> Beware that in OSGi and p2, version "1.2.3" is considered *older*
>> than
>> >>>>> 1.2.3.<qualifier>. If you just strip .<qualifier> suffix for
>> release
>> >>>>> version, OSGi and p2 will prefer the last snapshot over the
>> release. You
>> >>>>> can either use even/odd convention for release and snapshots
>> >>>>> (1.2.3-SNAPSHOT gets released as 1.2.4, for example) or use
>> >>>>> fully-qualified release versions both in pom.xml and eclispe/osgi
>> >>>>> metadata.
>> >>>>>
>> >>>>> --
>> >>>>> Regards,
>> >>>>> Igor
>> >>>>>
>> >>>>> On 11-05-29 05:37 AM, motes motes wrote:
>> >>>>>>
>> >>>>>> We also need to do a "real" release soon. I think we basically
>> just
>> >>>>>> create a tag in svn and then we can always generate p2 sites
>> from the
>> >>>>>> content of the tags corresponding to released p2 sites.
>> >>>>>>
>> >>>>>> But how do you tycho guys perform a release in the first place? I
>> am
>> >>>>>> familiar with performing pure maven releases and was thinking
>> >>>>>> something like this:
>> >>>>>>
>> >>>>>> 1) Remove .qualifier from all versions in manifest files. svn
>> commit
>> >>>>>> 2) Remove .SNAPSHOT from all pom files. svn commit
>> >>>>>> 3) Create svn tag
>> >>>>>> 4) Increment all version (both in pom and manifest files) and add
>> >>>>>> .qualifer/.SNAPSHOT version suffix.
>> >>>>>>
>> >>>>>> If any of the above steps can be performed automatically I you
>> be happy
>> >>>>>> to
>> >>>>>> know!
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Fri, May 27, 2011 at 8:01 PM, Benson
>> Margulies<bimargulies@xxxxxxxxx <mailto:bimargulies@xxxxxxxxx>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>> Oh! What are you all doing? Are you just always publishing
>> sites from
>> >>>>>>> snapshot builds with qualifiers? I just assumed that I had to
>> make a
>> >>>>>>> 'real release version'.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> On Fri, May 27, 2011 at 1:32 PM, Igor
>> Fedorenko<igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>
>> >>>>>>> wrote:
>> >>>>>>>>
>> >>>>>>>> Yes -- it won't work.
>> >>>>>>>>
>> >>>>>>>> There is some discussion in TYCHO-214 [1], and I remember
>> there were
>> >>>>>>>> patches for release-plugin somewhere, but I've never tried them
>> >>>>>>>> myself.
>> >>>>>>>>
>> >>>>>>>> [1] https://issues.sonatype.org/browse/TYCHO-214
>> >>>>>>>>
>> >>>>>>>> --
>> >>>>>>>> Regards,
>> >>>>>>>> Igor
>> >>>>>>>>
>> >>>>>>>> On 11-05-27 01:00 PM, Benson Margulies wrote:
>> >>>>>>>>>
>> >>>>>>>>> Is there anything I need to know about running the release
>> plugin on
>> >>>>>>>>> a
>> >>>>>>>>> set of tycho projects?
>> >>>>>>>>> _______________________________________________
>> >>>>>>>>> tycho-user mailing list
>> >>>>>>>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>>>>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>>>>>>
>> >>>>>>>> _______________________________________________
>> >>>>>>>> tycho-user mailing list
>> >>>>>>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>>>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>>>>>>
>> >>>>>>> _______________________________________________
>> >>>>>>> tycho-user mailing list
>> >>>>>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> tycho-user mailing list
>> >>>>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>>>
>> >>>>> _______________________________________________
>> >>>>> tycho-user mailing list
>> >>>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>>>
>> >>>> _______________________________________________
>> >>>> tycho-user mailing list
>> >>>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>
>> >>> _______________________________________________
>> >>> tycho-user mailing list
>> >>> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> >>>
>> >> _______________________________________________
>> >> tycho-user mailing list
>> >> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> >> https://dev.eclipse.org/mailman/listinfo/tycho-user
>> > _______________________________________________
>> > tycho-user mailing list
>> > tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
>> > https://dev.eclipse.org/mailman/listinfo/tycho-user
>>
>>
>> _______________________________________________
>> tycho-user mailing list
>> tycho-user@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/tycho-user
>
