You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Tony Wu <wu...@gmail.com> on 2009/12/21 14:43:27 UTC
[General]offer Harmony 6 Select build with M1
Hi, all
We are testing 6M1 on windows and linux. I was wondering how about
delivering the Harmony Select build along with our M1 build. There is
no extra testing required, I'm writing a script to simply package
following modules as Harmony Select core:
ANNOTATION ARCHIVE AUTH
BEANS CONCURRENT CRYPTO
JNDI INSTRUMENT LANG-MANAGEMENT
LOGGING LUNI MATH
NIO NIO_CHAR PACK200
PREFS REGEX SECURITY
SQL TEXT XML
X-NET
and left following out for selection:
ACCESSIBILITY APPLET AWT
IMAGEIO ORB PRINT
RMI SOUND SWING
X_MGT
--
Tony Wu
China Software Development Lab, IBM
Re: [General]offer Harmony 6 Select build with M1
Posted by Tony Wu <wu...@gmail.com>.
On Mon, Dec 21, 2009 at 11:54 PM, Mark Hindess
<ma...@googlemail.com> wrote:
>
> In message <21...@mail.gmail.com>,
> Tony Wu writes:
>>
>> ya, I'm hereby requesting for committing the script for packaging a
>> Harmony Select build ;-)
>
> I was hoping you weren't going to ask. :-(
>
> -1
lol. have fallen right into your trap.
>
> It is interesting but it isn't needed for 6.0M1 and I think it would be
> a distraction. The code stream has already been frozen for a long time
> so I don't think we need more distractions from getting 6.0M1 out and
> unfreezing the 6.0 code base.
well. as I mentioned there is no extra testing required. I don't think
it will bring some distraction to others. Everybody should focus on M1
testing and If the regular M1 build is well tested, I just need to
package some modules to be a smaller jre and put it onto web page for
downloading and playing.
>
> Anyway, why would it not go into trunk first and be merged to the Java 6
> branch like most other improvements?
I agree with you on the point we should add improvements to trunk
first if applicable. But I think, on the one hand the script should be
independent, it will not break any other existing features and would
be much easy to be merged to trunk, on the other, next milestone for
trunk should be 3 months later. why we have to wait for another 3
months to make a Select build available for people to play? I think
it's a shame that we have been doing without it, despite that Harmony
has such a good modularity basis.
>
> -Mark.
>
>> On Mon, Dec 21, 2009 at 10:13 PM, Mark Hindess
>> <ma...@googlemail.com> wrote:
>> >
>> > In message <21...@mail.gmail.com>,
>> > Tony Wu writes:
>> >>
>> >> Hi, all
>> >> We are testing 6M1 on windows and linux. I was wondering how about
>> >> delivering the Harmony Select build along with our M1 build. There is
>> >> no extra testing required, I'm writing a script to simply package
>> >> following modules as Harmony Select core:
>> >> =A0ANNOTATION =A0 =A0 =A0 =A0 ARCHIVE =A0 =A0 =A0 =A0 =A0 =A0 AUTH
>> >> =A0BEANS =A0 =A0 =A0 =A0 =A0 =A0 =A0CONCURRENT =A0 =A0 =A0 =A0 =A0CRYPTO
>> >> =A0JNDI =A0 =A0 =A0 =A0 =A0 =A0 =A0 INSTRUMENT =A0 =A0 =A0 =A0 =A0LANG-M=
>> ANAGEMENT
>> >> =A0LOGGING =A0 =A0 =A0 =A0 =A0 =A0LUNI =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0MA=
>> TH
>> >> =A0NIO =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0NIO_CHAR =A0 =A0 =A0 =A0 =A0 =A0PA=
>> CK200
>> >> =A0PREFS =A0 =A0 =A0 =A0 =A0 =A0 =A0REGEX =A0 =A0 =A0 =A0 =A0 =A0 =A0 SE=
>> CURITY
>> >> =A0SQL =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0TEXT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
>> =A0XML
>> >> =A0X-NET
>> >>
>> >> and left following out for selection:
>> >> =A0ACCESSIBILITY =A0 =A0 =A0APPLET =A0 =A0 =A0 =A0 =A0 =A0 =A0AWT
>> >> =A0IMAGEIO =A0 =A0 =A0 =A0 =A0 =A0ORB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PR=
>> INT
>> >> =A0RMI =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0SOUND =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
>> SWING
>> >> =A0X_MGT
>> >
>> > While I like the idea of a select build, I think having an "official"[0]
>> > select build would require that your script be integrated into the
>> > official source release.
>> >
>> > Are you planning to request commit permission to integrate your script?
>> > If not, then I think it should wait until this can be done post M1.
>> >
>> > Regards,
>> > =A0Mark.
>> >
>> > [0] if any binary artifacts are "official"
>> >
>> >
>> >
>>
>>
>>
>> --=20
>> Tony Wu
>> China Software Development Lab, IBM
>>
>
>
>
--
Tony Wu
China Software Development Lab, IBM
Re: [General]offer Harmony 6 Select build with M1
Posted by Mark Hindess <ma...@googlemail.com>.
In message <21...@mail.gmail.com>,
Tony Wu writes:
>
> ya, I'm hereby requesting for committing the script for packaging a
> Harmony Select build ;-)
I was hoping you weren't going to ask. :-(
-1
It is interesting but it isn't needed for 6.0M1 and I think it would be
a distraction. The code stream has already been frozen for a long time
so I don't think we need more distractions from getting 6.0M1 out and
unfreezing the 6.0 code base.
Anyway, why would it not go into trunk first and be merged to the Java 6
branch like most other improvements?
-Mark.
> On Mon, Dec 21, 2009 at 10:13 PM, Mark Hindess
> <ma...@googlemail.com> wrote:
> >
> > In message <21...@mail.gmail.com>,
> > Tony Wu writes:
> >>
> >> Hi, all
> >> We are testing 6M1 on windows and linux. I was wondering how about
> >> delivering the Harmony Select build along with our M1 build. There is
> >> no extra testing required, I'm writing a script to simply package
> >> following modules as Harmony Select core:
> >> =A0ANNOTATION =A0 =A0 =A0 =A0 ARCHIVE =A0 =A0 =A0 =A0 =A0 =A0 AUTH
> >> =A0BEANS =A0 =A0 =A0 =A0 =A0 =A0 =A0CONCURRENT =A0 =A0 =A0 =A0 =A0CRYPTO
> >> =A0JNDI =A0 =A0 =A0 =A0 =A0 =A0 =A0 INSTRUMENT =A0 =A0 =A0 =A0 =A0LANG-M=
> ANAGEMENT
> >> =A0LOGGING =A0 =A0 =A0 =A0 =A0 =A0LUNI =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0MA=
> TH
> >> =A0NIO =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0NIO_CHAR =A0 =A0 =A0 =A0 =A0 =A0PA=
> CK200
> >> =A0PREFS =A0 =A0 =A0 =A0 =A0 =A0 =A0REGEX =A0 =A0 =A0 =A0 =A0 =A0 =A0 SE=
> CURITY
> >> =A0SQL =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0TEXT =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
> =A0XML
> >> =A0X-NET
> >>
> >> and left following out for selection:
> >> =A0ACCESSIBILITY =A0 =A0 =A0APPLET =A0 =A0 =A0 =A0 =A0 =A0 =A0AWT
> >> =A0IMAGEIO =A0 =A0 =A0 =A0 =A0 =A0ORB =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PR=
> INT
> >> =A0RMI =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0SOUND =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
> SWING
> >> =A0X_MGT
> >
> > While I like the idea of a select build, I think having an "official"[0]
> > select build would require that your script be integrated into the
> > official source release.
> >
> > Are you planning to request commit permission to integrate your script?
> > If not, then I think it should wait until this can be done post M1.
> >
> > Regards,
> > =A0Mark.
> >
> > [0] if any binary artifacts are "official"
> >
> >
> >
>
>
>
> --=20
> Tony Wu
> China Software Development Lab, IBM
>
Re: [General]offer Harmony 6 Select build with M1
Posted by Tony Wu <wu...@gmail.com>.
ya, I'm hereby requesting for committing the script for packaging a
Harmony Select build ;-)
On Mon, Dec 21, 2009 at 10:13 PM, Mark Hindess
<ma...@googlemail.com> wrote:
>
> In message <21...@mail.gmail.com>,
> Tony Wu writes:
>>
>> Hi, all
>> We are testing 6M1 on windows and linux. I was wondering how about
>> delivering the Harmony Select build along with our M1 build. There is
>> no extra testing required, I'm writing a script to simply package
>> following modules as Harmony Select core:
>> ANNOTATION ARCHIVE AUTH
>> BEANS CONCURRENT CRYPTO
>> JNDI INSTRUMENT LANG-MANAGEMENT
>> LOGGING LUNI MATH
>> NIO NIO_CHAR PACK200
>> PREFS REGEX SECURITY
>> SQL TEXT XML
>> X-NET
>>
>> and left following out for selection:
>> ACCESSIBILITY APPLET AWT
>> IMAGEIO ORB PRINT
>> RMI SOUND SWING
>> X_MGT
>
> While I like the idea of a select build, I think having an "official"[0]
> select build would require that your script be integrated into the
> official source release.
>
> Are you planning to request commit permission to integrate your script?
> If not, then I think it should wait until this can be done post M1.
>
> Regards,
> Mark.
>
> [0] if any binary artifacts are "official"
>
>
>
--
Tony Wu
China Software Development Lab, IBM
Re: [General]offer Harmony 6 Select build with M1
Posted by Mark Hindess <ma...@googlemail.com>.
In message <21...@mail.gmail.com>,
Tony Wu writes:
>
> Hi, all
> We are testing 6M1 on windows and linux. I was wondering how about
> delivering the Harmony Select build along with our M1 build. There is
> no extra testing required, I'm writing a script to simply package
> following modules as Harmony Select core:
> ANNOTATION ARCHIVE AUTH
> BEANS CONCURRENT CRYPTO
> JNDI INSTRUMENT LANG-MANAGEMENT
> LOGGING LUNI MATH
> NIO NIO_CHAR PACK200
> PREFS REGEX SECURITY
> SQL TEXT XML
> X-NET
>
> and left following out for selection:
> ACCESSIBILITY APPLET AWT
> IMAGEIO ORB PRINT
> RMI SOUND SWING
> X_MGT
While I like the idea of a select build, I think having an "official"[0]
select build would require that your script be integrated into the
official source release.
Are you planning to request commit permission to integrate your script?
If not, then I think it should wait until this can be done post M1.
Regards,
Mark.
[0] if any binary artifacts are "official"