ble in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
> Issue Type: Bug
> Components: wtk
>Affects Versions: 2.0.1
sted it and TextPane now works again well.
I think that this issue can be now set as resolved.
Now I can upgrade my project on Pivot 2.0.1 using this fix - this was the last
blocking issue for me ;-)
Lukas
> TextPane is unusable in 2.0.1
y it out.
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
> Issue Type: Bug
&
expert on this (and
not only :-) ) ...
Bye,
Sandro
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
>
when caret is at the beginning or
at the end of line (paragraph).
Lukas
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
&g
d others) asap.
Thank you for now.
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project:
d others) asap.
Thank you for now.
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
> Is
nd others) asap.
Thank you for now.
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
it as an attachment.
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
> Issue Type: Bug
>
)
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
> Issue Type: Bug
> Components: wtk
>
works in 2.0 well but in 2.0.1 not
> TextPane is unusable in 2.0.1 release
> -
>
> Key: PIVOT-835
> URL: https://issues.apache.org/jira/browse/PIVOT-835
> Project: Pivot
>
[
https://issues.apache.org/jira/browse/PIVOT-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sandro Martini updated PIVOT-835:
-
Fix Version/s: 2.0.2
> TextPane is unusable in 2.0.1 rele
TextPane is unusable in 2.0.1 release
-
Key: PIVOT-835
URL: https://issues.apache.org/jira/browse/PIVOT-835
Project: Pivot
Issue Type: Bug
Components: wtk
Affects Versions: 2.0.1
---
From: Lukáš Macháček [mailto:cg...@coolmail.cz]
Sent: Monday, January 16, 2012 8:17 AM
To: dev@pivot.apache.org
Subject: 2.0.1 release and threads
Hi all,
I am now testing coming 2.0.1 release of Pivot libraries with my desktop
application developed during previous year on Pivot 2.0 and am fa
Roger:
yes, total agreement here :-)
the way I override is not to silence the problem,
but to permit few more legitimate threads
along with those already used by pivot;
Andrei
Original Message
Subject: Re: 2.0.1 release and threads
From: Roger L. Whitcomb
To: Andrei
...@gmail.com]
Sent: Monday, January 16, 2012 12:41 PM
To: Roger L. Whitcomb
Cc: dev@pivot.apache.org; u...@pivot.apache.org
Subject: Re: 2.0.1 release and threads
Roger:
yes, good point;
and in my case I have legitimate scenario
when I have to provide alternative checker, since I am running
Roger:
yes, good point;
and in my case I have legitimate scenario
when I have to provide alternative checker, since I am running inside
osgi launcher,
which is not covered by the default pivot checker implementation;
Andrei.
Original Message
Subject: Re: 2.0.1 release and
L. Whitcomb; u...@pivot.apache.org
Subject: Re: 2.0.1 release and threads
Lukas:
you can provide a temporary work around
by providing an alternative implementation to thread checker used by assert
org.apache.pivot.wtk.Container.assertEventDispatchThread
Andrei
Original Message
Lukas:
you can provide a temporary work around
by providing an alternative implementation to thread checker used by assert
org.apache.pivot.wtk.Container.assertEventDispatchThread
Andrei
Original Message
Subject: Re: 2.0.1 release and threads
From: Roger L. Whitcomb
To: dev
rom: Lukáš Macháček [mailto:cg...@coolmail.cz]
Sent: Monday, January 16, 2012 8:17 AM
To: dev@pivot.apache.org
Subject: 2.0.1 release and threads
Hi all,
I am now testing coming 2.0.1 release of Pivot libraries with my desktop
application developed during previous year on Pivot 2.0 and am
Hi all,
I am now testing coming 2.0.1 release of Pivot libraries with my desktop
application developed during previous year on Pivot 2.0 and am facing
one great problem with threads :-(
Every task which loads data at background and worked in 2.0 well now
throws exception like this
Hi Roger,
ok, don't worry, I was not sure if someone was waiting some fix from me (I
have some I'm working on but I need some more time ... so they will go in
2.0.2 or 2.1, let's see).
Bye
--
View this message in context:
http://apache-pivot-developers.417237.n3.nabble.com/freeze-for-2-0-1-rel
I have one more tiny change to TerraFileBrowserSheetSkin I would like to
make, but otherwise I'm fine with a freeze and re-tag.
~Roger Whitcomb
On 9/27/11 5:19 AM, Sandro Martini wrote:
Hi all,
some news on code freeze for the 2.0.1 release ?
Someone has objections (and a re-tag neede
Ok, thanks.
Tomorrow I hope to finish to reconfigure builds on jenkins.
I'll keep you updated.
Bye
Il giorno 25/ago/2011 19:58, "DreamTangerine"
ha scritto:
Chris, this is a great news !!
Tomorrow I'll try and move outside trunk the new folder (and maybe even
test, reports and logs if possible).
I keep you updated.
Thank you for now.
Bye
Il giorno 24/ago/2011 23:31, "Chris Bartlett" ha
scritto:
> Sandro,
>
> It looks like you can tell Jenkins to ch
Sandro,
It looks like you can tell Jenkins to check out multiple SVN paths
(from the same repository) into the build workspace.
https://builds.apache.org/job/Pivot-trunk/configure --> Source Code
Management --> 'Add more locations...'
So you should be able to place any files that are required fo
The problem is caused not by your patch, but in the presence of the new
folder containing jars for jenkins.
Now in the dist task (in the ant build) even the new folder is copied
inside. Should be enough to have it in exclude list (maybe renaming it with
a underscore char at the beginning, and excl
On mié, 2011-08-24 at 17:31 +0200, Sandro Martini wrote:
> Ok, thanks for the hint, it has been useful :-) .
>
> Committed under trunk a new folder ci-builds-on-jenkins containing all
> junit and maven-ant-task jars and related licenses.
> Make all changes to build.properties and build.xml propose
llow know if it a jenkins building or not.
But I agree that maybe is better to wait 2.0.1 release (or not commit
the changes, only copy then in jenkins build).
Ok, thanks for the hint, it has been useful :-) .
Committed under trunk a new folder ci-builds-on-jenkins containing all
junit and maven-ant-task jars and related licenses.
Make all changes to build.properties and build.xml proposed by
dreamtangerine and all works good (there is only a small probl
Here is an example of a build that uses JUnit
https://builds.apache.org/job/Lucene-Solr-tests-only-trunk-java7/304/
On 24 August 2011 17:40, Chris Bartlett wrote:
>> So I'll continue to search for info, and ask even to apache legals, to
>> see if it's a problem already solved (I think it is).
>
>
>> So I'll continue to search for info, and ask even to apache legals, to
>> see if it's a problem already solved (I think it is).
>
> I would think about emailing builds@ before legal@ :)
>
> It must have been asked before, so is probably in their mailing list
> archive or a FAQ somewhere. I will
> So I'll continue to search for info, and ask even to apache legals, to
> see if it's a problem already solved (I think it is).
I would think about emailing builds@ before legal@ :)
It must have been asked before, so is probably in their mailing list
archive or a FAQ somewhere. I will try to ha
dependencies) then it is fine.
>
> I just want to make sure that changes to the build files now won't
> cause any problems for the 2.0.1 release, or for anyone checking out
> the SVN tree and attempting to build.
Yes, I agree, so in the meantime I will not commit anything relate
I just want to make sure that changes to the build files now won't
cause any problems for the 2.0.1 release, or for anyone checking out
the SVN tree and attempting to build.
> For example, I'm searching how to let jenkins find the junit jar and
> other jdk jars required by us, but
Hi Chris, thanks for the help :-) ...
>It looks like it should be easy to set up committers from Pivot or any other
>Apache project as Jenkins build admins.
Our PMC Chair (Todd) has to ask to infra to enable a user, but it has
to be an Apache Committer at least (from whet I know), because Jenkins
Firstly, many thanks to DreamTangerine for making the initial effort
to get us going. :)
On 24 August 2011 15:36, Sandro Martini wrote:
> just created the Pivot-trunk Job on Jenkins here: https://builds.apache.org/
Thanks for jumping into this, Sandro. I was waiting to get an email
about an acc
Hi all,
just created the Pivot-trunk Job on Jenkins here: https://builds.apache.org/
Enabled the sent to dev for builds failed (but I don't know if it's
already enabled).
Of course first build has NOT been successful, because I have to
adjust some things in our build and commit changes in trunk,
f
Good.
If you (Sandro or Chris) have any problem I'll try to help.
The key is the build in Apache server from a checkout if you can build
Pivot in Apache server, the configuration of Jenkins is easy.
Maybe some problems come from libraries dependencies and maybe we have
to upload some jar (for e
Done. I'll also create the 2.0.1 tag today in preparation for a release vote.
-T
On Mon, Aug 22, 2011 at 10:07 AM, Chris Bartlett wrote:
> This says that Todd will have to run the script to create accounts as
> he is the PMC Chair.
> http://wiki.apache.org/general/Hudson#How_do_I_get_an_account
This says that Todd will have to run the script to create accounts as
he is the PMC Chair.
http://wiki.apache.org/general/Hudson#How_do_I_get_an_account
(I don't have permission either)
Todd - could you please add Sandro and myself as Jenkins (Hudson)
admins at your earliest convenience? (smarti
Hi Chris,
these two mailing lists should be enough.
I just tried to run shell commands to add myself to the related group
(as explained here: http://wiki.apache.org/general/Hudson ) but I
don't have enough privileges at the moment, so I'm opening an INFRA
issue .. let's see what happen.
If you can
I am subscribed to the Apache Builds & Infrastructure lists
bui...@apache.org
infrastruct...@apache.org
Is there a special one just for Jenkins? If there is, then I can
subscribe, or you can try to do for me if you want to.
On 22 August 2011 17:38, Sandro Martini wrote:
> Hi all,
> just see th
Hi all,
just see that this is the related ticket:
https://issues.apache.org/jira/browse/PIVOT-791
today I'll subscribe myself to the Jenkins Apache list (only for Apache PMC
members), and try to look at it.
Chris, I can subscribe even you (two is better than one :-) ) ... ok ?
Or do you prefer to
Thanks for looking in to this. I am not 100% sure how to proceed.
Perhaps the first step should be to create a JIRA ticket for the use
of Jenkins for regular builds & testing, and attach the relevant files
& any notes on configuration or setup. We can then review and test in
local Jenkins instal
On jue, 2011-06-23 at 00:26 +0200, Sandro Martini wrote:
> If someone of us is able to activate Pivot on the Continuous Build
> Apache service, it would be great, snapshots are useful.
>
> Bye,
> Sandro
>
Hello
I was playing with a local server of Jenkins (old Hundson) and Pivot's
job to learn
Hi Greg,
>done.
thank you very much.
As you can see now in JIRA all is good (no tickets) for the 2.0.1 release
:-) .
Bye
--
View this message in context:
http://apache-pivot-developers.417237.n3.nabble.com/Propose-2-0-1-release-tp3229452p3235480.html
Sent from the Apache Pivot - Develop
Done
On Aug 6, 2011, at 5:14 AM, Sandro Martini wrote:
> Greg, can you add to me and other PMC members full grants on Pivot JIRA ?
> Otherwise we aren'r able for example to open a new release needed now to
> move 2.0.1 tickets to 2.0.2, and useful for the future too).
> Currently only you and Tod
Hi Noel,
no problem, it's a pleasure for me, some times even more than
writing/debugging code :-) ...
Bye
--
View this message in context:
http://apache-pivot-developers.417237.n3.nabble.com/Propose-2-0-1-release-tp3229452p3235111.html
Sent from the Apache Pivot - Developers mailing list archiv
Thanks for doing admin work Sandro.
Sandro Martini wrote:
> Hi all,
> sorry for all JIRA mail of today, but I created the 2.0.2 release, resolved
> some issues already fixed in code and do some cleanup.
>
> Now 2.0.1 has no more tickets assigned (only one currently, but as soon as I
> get an answe
Hi all,
sorry for all JIRA mail of today, but I created the 2.0.2 release, resolved
some issues already fixed in code and do some cleanup.
Now 2.0.1 has no more tickets assigned (only one currently, but as soon as I
get an answer I think it will be moved to 2.0.2 or resolved).
We can start to gen
Hi,
I think 2.0.1 should be good ... or 2.1 now and 2.5 later ?
I'd prefer 2.0.1 but for me no problem.
Bye
Il giorno 06/ago/2011 04:08, "Chris Bartlett" ha
scritto:
> Is the 2.0.1 version number still appropriate, or is it worth considering
2.1?
>
>
https://issues.apache.org/jira/secure/ReleaseNo
Greg, can you add to me and other PMC members full grants on Pivot JIRA ?
Otherwise we aren'r able for example to open a new release needed now to
move 2.0.1 tickets to 2.0.2, and useful for the future too).
Currently only you and Todd should have ...
Il giorno 06/ago/2011 04:08, "Chris Bartlett"
Is the 2.0.1 version number still appropriate, or is it worth considering 2.1?
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310863&version=12315951
On 6 August 2011 01:12, Roger L. Whitcomb wrote:
> I'd like to propose we release 2.0.1 ASAP. I know there are a few
> thing
Yes, I know you can re-tag. I'm just trying to save you the step. :-)
I don't see any advantage in maintaining multiple tags for a given release.
On Aug 5, 2011, at 3:51 PM, Sandro Martini wrote:
> We could even re-tag (delete the old tag snd re-create) if/when needed. Or
> tag as 2.0.1-test an
We could even re-tag (delete the old tag snd re-create) if/when needed. Or
tag as 2.0.1-test and then rename if final, because (as in past) in case of
problems we'd have to test everything the same.
Just as idea ...
Il giorno 05/ago/2011 21:44, "Greg Brown" ha
scritto:
>> Someone of us has some f
> Someone of us has some file to commit before tagging ?
> I haven't ...
You may have missed this in my earlier message, but I'd recommend waiting until
testing is finished before tagging. Otherwise you'll need to re-tag.
gt;
> -Original Message-
> From: Sandro Martini [mailto:sandro.mart...@gmail.com]
> Sent: Friday, August 05, 2011 12:21 PM
> To: dev@pivot.apache.org
> Subject: Re: Propose 2.0.1 release
>
> Thinking on it I think that we could start next week the proposal for
> the
> 2.0.
..@gmail.com]
> Sent: Friday, August 05, 2011 12:21 PM
> To: dev@pivot.apache.org
> Subject: Re: Propose 2.0.1 release
>
> Thinking on it I think that we could start next week the proposal for
> the
> 2.0.1 , but please don't create a branch in svn, maybe create a tag
>
Yes, releases are generally tagged. But I'd hold off on creating the tag until
the QA part is done.
On Aug 5, 2011, at 3:21 PM, Sandro Martini wrote:
> Thinking on it I think that we could start next week the proposal for the
> 2.0.1 , but please don't create a branch in svn, maybe create a tag
0 Arguello Street | Suite 200 | Redwood City | CA | 94063 |
USA +1 650-587-5596 | fax: +1 650-587-5550
-Original Message-
From: Sandro Martini [mailto:sandro.mart...@gmail.com]
Sent: Friday, August 05, 2011 12:21 PM
To: dev@pivot.apache.org
Subject: Re: Propose 2.0.1 release
Thinking on
Thinking on it I think that we could start next week the proposal for the
2.0.1 , but please don't create a branch in svn, maybe create a tag instead,
so in the meantime we can continue to work on 2.0.x ... do you like this ?
What others think ?
Bye
Il giorno 05/ago/2011 20:12, "Roger L. Whitcomb"
I'd like to propose we release 2.0.1 ASAP. I know there are a few
things Sandro still has on his plate, but I'm thinking they are not
crucial to have in 2.0.1 necessarily.
Can I get help testing to make sure everything is stable? I've been
testing with our app for literally months now, trac
Hi all,
just fixed the execution of tests in our ant task:
add all projects under the test ant task (even if most of them
currently have the test folder empty), and changes the filter for
JUnit test files to **/*Test.java
so now we only have to remember that all our JUnite tests (that have
to be
Hi Andrei,
> how about one 2.0.x release every 3 months, like java, firefox & chrome do?
> :-)
Yes, why not ?
But maybe we could not have things to fix :-) ... and after this I go to sleep.
And maybe the 2.1 final near the end of the 2011 ...
Bye
how about one 2.0.x release every 3 months, like java, firefox & chrome
do? :-)
Original Message
Subject: Re: 2.0.1 release
From: Sandro Martini
To: dev@pivot.apache.org
Date: Wed 22 Jun 2011 05:26:01 PM CDT
> Sorry, a last thing of the "release often" theme
Sorry, a last thing of the "release often" theme:
I don't think it's a good idea to "release often", usually it gives
the idea that there are many things to fix ... but I agree that we
have to speedup our releases (many of as already know we are a small
team, and time is limited for all us ...).
I
Hi Roger,
just gave an answer (I hope :-) ) in the other mail sent from Chris
... tell me if there is something to verify.
Bye
Hi Chris,
from what I remember, the tests subproject contains only Test
Applications (no JUnit tests), so it's Ok to exclude it from the test
task of build.xml .
But I remember that some months ago the filter for JUnit test sources
was something like "**/Test.java" , without the "*" before the
ext
(moved from 'Re: 2.0.1 release')
Roger,
I just had a very quick look at the build.xml file, and it looks like the
'test' ant target only tests the
'core' and 'web' Eclipse projects/subdirectories of trunk.
However, this seems to be OK, as th
City | CA | 94063 |
USA +1 650-587-5596 | fax: +1 650-587-5550
-Original Message-
From: Chris Bartlett [mailto:cbartlet...@gmail.com]
Sent: Wednesday, June 22, 2011 12:29 PM
To: dev@pivot.apache.org
Subject: Re: 2.0.1 release
BeanAdapterTestObject is not a JUnit test, but its name m
t;
> -Original Message-
> From: Chris Bartlett [mailto:cbartlet...@gmail.com]
> Sent: Wednesday, June 22, 2011 11:29 AM
> To: dev@pivot.apache.org
> Subject: Re: 2.0.1 release
>
> Yep, 6 months is way too long, but with only a few committers whose time
> is
> limited, it
org
Subject: Re: 2.0.1 release
Yep, 6 months is way too long, but with only a few committers whose time
is
limited, it has just ended up that way.
Hopefully Piotr's road map question and Greg's friendly push will be
enough
to kick start the 2.0.1 process..
On 23 June 2011 01:20, Edvin
on why not.
>>>
>>> On Jun 22, 2011, at 12:42 PM, Andrei Pozolotin wrote:
>>>
>>> what is involved in "get the ball rolling"?
>>>>
>>>> can you start releasing 2.0.x versions once a month?
>>>>
>>>> Original Mess
take responsibility for it, I don't see any reason why not.
On Jun 22, 2011, at 12:42 PM, Andrei Pozolotin wrote:
what is involved in "get the ball rolling"?
can you start releasing 2.0.x versions once a month?
Original Message ----
Subject: 2.0.1 release
From: Greg
art releasing 2.0.x versions once a month?
> >
> > Original Message
> > Subject: 2.0.1 release
> > From: Greg Brown
> > To: Pivot Dev
> > Date: Wed 22 Jun 2011 10:16:40 AM CDT
> >> Hi all,
> >>
> >> I think the 2.0.1 r
age ----
> Subject: 2.0.1 release
> From: Greg Brown
> To: Pivot Dev
> Date: Wed 22 Jun 2011 10:16:40 AM CDT
>> Hi all,
>>
>> I think the 2.0.1 release is long overdue. Open-source projects without
>> frequent releases seem dead and lose users.
>>
what is involved in "get the ball rolling"?
can you start releasing 2.0.x versions once a month?
Original Message
Subject: 2.0.1 release
From: Greg Brown
To: Pivot Dev
Date: Wed 22 Jun 2011 10:16:40 AM CDT
> Hi all,
>
> I think the 2.0.1 release is long o
Hi all,
I think the 2.0.1 release is long overdue. Open-source projects without
frequent releases seem dead and lose users.
I unfortunately cannot drive the process, but I can help validate the release
if someone is willing to get the ball rolling. Are there any volunteers?
Greg
79 matches
Mail list logo
