[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
AW: AW: [jwt-dev] Stable Galileo M4 build of JWT this afternoon?
|
Hi Mickael,
great, thanks. I tried the stable-update-site and it works fine.
Some things we should change for the next version (already mentioned
elsewhere):
- the category on the update-site is somehow "Uncategorized" and should be
"Java Workflow Tooling" (and maybe others below, see other emails)
- it now says when opening an old file that this is no longer version 0.5.0
but 0.6.0S20081219-1024. Maybe we should change that to 0.6.0 only? Might be
confusing for other people maybe, and between different stable builds we
probably don't change the metamodel
- our plugin still defines some shortcuts which make problems in textual
editors to use "{", "[", "]" and "}". This will probably be recognized soon
by the other projects, so this needs to be changed for the next milestone
build I guess.
Otherwise it works perfectly fine as far as I can see!
Best regards,
Florian
-----Ursprüngliche Nachricht-----
Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Mickael Istria
Gesendet: 19 December 2008 16:32
An: Java Workflow Toolbox
Betreff: Re: AW: [jwt-dev] Stable Galileo M4 build of JWT this afternoon?
Hi all,
I tagged the plugins included in the build with name GALILEO_M4_20081219.
As you have thought of, Florian, the build process is not able to tag CVS
modules since it uses an anonymous connection.
Concerning the categories, I currently don't have any preference on this
topic, but I think that future JWT features will help us to find the best
organisation. Thus, I think we should delay this question to next months,
although I'm pretty sure that your suggestions are already the good ones ;)
The build successfully ended, our first Galileo milestone will be available
within a few minutes on
http://download.eclipse.org/technology/jwt/stable-update-site/ !
Regards,
Mickael
Florian Lautenbacher a écrit :
> Hi Mickael,
>
> thanks a lot! I updated also the JWT Download-page [1] to present the
> different update-sites there. I agree with Chris that we should
> probably provide different categories in the future. The first
> differentiation is probably between the existing components (WE, WAM,
> Desktop, Transformations), the second might then be for different
> feature-packs (views, aspects, etc.).
>
> I agree with Marc that it would be nice to have a tag of the source
> for each milestone build, but probably this need to be done manually
> and can't be automated in the build process, can it?
>
> Best regards,
>
> Florian
>
> [1]
> http://wiki.eclipse.org/JWT_Downloads#Installing_using_the_Update_site
>
> -----Ursprüngliche Nachricht-----
> Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx]
> Im Auftrag von Christian Saad
> Gesendet: 19 December 2008 15:03
> An: 'Java Workflow Toolbox'
> Betreff: AW: [jwt-dev] Stable Galileo M4 build of JWT this afternoon?
>
> Hi Mickael,
>
> great work on the automatic build process!! I've tried the update site
> and it seems to work fine.
>
> I think it would be a good idea to create the feature for the update
> site with the current versions (which, as far as I know, should be
> fairly stable).
>
> Since there will be probably many new plugins in the JWT project in
> the future, we could maybe separate them on the update site to
> different categories, e.g. base, views, transformations and so on. What do
you think?
>
> Regards,
> Chris
>
>
>> -----Ursprüngliche Nachricht-----
>> Von: jwt-dev-bounces@xxxxxxxxxxx [mailto:jwt-dev-bounces@xxxxxxxxxxx]
>> Im Auftrag von Mickael Istria
>> Gesendet: Freitag, 19. Dezember 2008 14:55
>> An: Java Workflow Toolbox
>> Betreff: [jwt-dev] Stable Galileo M4 build of JWT this afternoon?
>>
>> Hi all,
>>
>> Since JWT build is now operational, I suggest that we should have a
>> stable build of JWT before the end of the day, so that everyone can
>> go on holiday without any stress.
>>
>> I suggest that we simply build the current JWT feature (with we,
>> action-doc, view-uml, transfo-base & transfo-xpdl) from HEAD, without
>> adding other plugins. This way, the Galileo M4+3 build will confirm
>> us that the "minimal" JWT feature is OK in the Galileo release train.
>> Once this build is validated, we will integrate everything we want
>> (and we're allowed to integrate) into the JWT feature and into the
>> Galileo release train.
>>
>> If everybody is OK with that, I'll start this build at 4:00 pm
>> (France/Germay hour).
>>
>> Regards,
>> Mickael
>> _______________________________________________
>> jwt-dev mailing list
>> jwt-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>>
>
>
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>
> _______________________________________________
> jwt-dev mailing list
> jwt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jwt-dev
>
_______________________________________________
jwt-dev mailing list
jwt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jwt-dev
