Skip to main content

Cvs commit mailing list

15 replies [Last post]
Anonymous

Hi all :-)

Is there a mailing list for commits to cvs? It would really be useful to
keep track of the ongoing development...

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
...
> I'm not religiously devoted to any one build methodology. In this
> other thread
> (http://www.javadesktop.org/forums/thread.jspa?threadID=6656&tstart=0)
> I detailed (about halfway through the thread) the kinds of
> deliverables that we wanted to build, and the general project
> structure.

Ok.

>>Listen, here is my proposal:
>>
>> 0 - move in your package space all the files that are still
>> referenced from the jndc package (to make it indipendent)
>
> Sorry, what do you mean by "still referenced"?

I thought I saw some reference to the 0.5 jndc jar. I'll check.

>>1 - Retain Ant ans a build tool
>>2 - Add the project to the Gump
>>http://gump.apache.org/ build system
>
>
> We are currently using CruiseControl for continuous integration. Gump
> does the same thing, right? Is there any reason to favor Gump over
> CruiseControl? From what I've seen CC is pretty widely used, even by
> some Apache projects, I think. Could be wrong.

There is nothing preventing us from using both.

Gump has some diffferences:

1 - It builds the project with the latest build of *everything*.
Basically it takes all projects from CVS and builds them in order.
It's also doing test runs with GNU Classpath, so it should be a
good test for all

2 - It's free and easy, I just have to add the project descriptor
to it and it will build jndc, without having to install it here,
as Apache already does multiple daily runs with it (only one sends
mail nags though)

>> 3 - Make it dead simple to load stuff in a Netbeans and Eclipse
>> (the netbeans instructions now there need to be to be more
>> visible)
>
> Amen to that. I'd like to have predefined netbeans and eclipse
> project files, if possible. At the very least, it would be important
> to have a special walkthrough for setting up the project in each of
> these IDEs.
>
>>4 - Use plain html for documentation
>>5 - remove all dependencies that are not strictly
>>necessary
>>6 - refactor the packages to separate the swingx,
>>binding and jndc stuff
>
> One of the things that was really attractive about Maven was the
statCVS plugin, as well as some of the other "report" plugins that would
generate HTML for us. Do you know how to accomplish this with ant?

Yes. Maven uses the Ant tasks in fact to do it!

> It might also be possible to ship ant build scripts which build the
> various projects, but retain the website generating Maven code in
> house, but I think I'd rather it were all in CVS.
>
>>Oh, and I'm willing to help, of course. :-)
>
>
> Naturally! Let me see about cvs access to the incubator. I think
> access requires a JCA which I don't know if you've read about or faxed
> in yet. Essentially, Sun requires that anybody who contributes code to
> the project needs to sign a Joint Copyright Assignment. The idea is that
> code in JDNC may one day make its way back into Swing and in order for
> that to happen Sun needs to have the ability to change the license of
> the source code. Hence, the JCA. Its a real pain, but it makes sense.

Apache does it too. I'm ok with it, as it is a *joint* agreement. IOW I
share the rights but do not loose the rights on what I write exclusively.

I just have been granted karma. I'll start committing some stuff in my
package space.

> In the mean time, let me know how you would go about managing the
> build process for the various deliverables, and also generate some of
> the webpage stuff that Maven is currently doing.

Ok, hang on.

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Nicola Ken Barozzi

Nicola Ken Barozzi wrote:
...
>> In the mean time, let me know how you would go about managing the
>> build process for the various deliverables, and also generate some of
>> the webpage stuff that Maven is currently doing.

Ok, I've done some work today :-)

I've taken all your packages and refactored them in two package sets
(for now): org.jdesktop.swingx and org.jdesktop.jdnc. They will need
further changes and comments, but it's a start.

Then I've separated them in two projects, and I'm able to run them both
in eclipse and in netbeans 4.

While I was at it, I did a couple of changes to the classes themselves,
removing the asserts that were preventing a 1.4 JDK compilation, adding
a simpler demo for swingx only (very rough), added some more classes and
tweaked the TitledPanel and the StatusBar appearance.

I took a look at the java.net docs, and I found out that it's possible
to have a site without the normal sourcecast adornments, or to add items
to the sourcecast menu.

I tend to think that our best bet ATM is to do without any form of site
generation ATM, as it makes it easier for us to generate the site...
wait, it does not need to be generated :-)

I'm working now on the build enhancements.

What reports would you like to see?

Here is what I'm workin' on:

-statCVS
-jdepend
-CVS changelog
-checkstyle
-javadoc
-unit tests

I would like to commit this stuff tomorrow in the jndc-incubator repo,
but it would break the current conventions, as I would have to make
these folders:

jndc-incubator/nicolaken/swingx
jndc-incubator/nicolaken/jndc

Would it be ok?

Another point is about the separation between JX stuff and JN stuff.
I don't understand clearly how it can be done, as currently I was able
to cleanly separate only the JN* classes and the Form stuff.

The data, binding, action, etc stuff is still in SwingX... where to draw
the line?

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08
Points: 0

Wow!

> Ok, I've done some work today :-)
>
> I've taken all your packages and refactored them in
> two package sets
> (for now): org.jdesktop.swingx and org.jdesktop.jdnc.
> They will need
> further changes and comments, but it's a start.

Cool. Where did the xml stuff end up? It needs to be in its own package set as well.

>
> Then I've separated them in two projects, and I'm
> able to run them both
> in eclipse and in netbeans 4.
>
> While I was at it, I did a couple of changes to the
> classes themselves,
> removing the asserts that were preventing a 1.4 JDK
> compilation, adding
> a simpler demo for swingx only (very rough), added
> some more classes and
> tweaked the TitledPanel and the StatusBar appearance.
>
> I took a look at the java.net docs, and I found out
> that it's possible
> to have a site without the normal sourcecast
> adornments, or to add items
> to the sourcecast menu.
>
> I tend to think that our best bet ATM is to do
> without any form of site
> generation ATM, as it makes it easier for us to
> generate the site...
> wait, it does not need to be generated :-)
>
> I'm working now on the build enhancements.
>
> What reports would you like to see?
>
> Here is what I'm workin' on:
>
> -statCVS
> -jdepend
> -CVS changelog
> -checkstyle
> -javadoc
> -unit tests

That's a pretty good list to start with. Probably all we'll need.

>
> I would like to commit this stuff tomorrow in the
> jndc-incubator repo,
> but it would break the current conventions, as I
> would have to make
> these folders:
>
> jndc-incubator/nicolaken/swingx
> jndc-incubator/nicolaken/jndc
>
> Would it be ok?

I don't have any objections.

>
> Another point is about the separation between JX
> stuff and JN stuff.
> I don't understand clearly how it can be done, as
> currently I was able
> to cleanly separate only the JN* classes and the Form
> stuff.
>
> The data, binding, action, etc stuff is still in
> SwingX... where to draw
> the line?

That's a good question. For right now lets leave that stuff all in the swingx code. As long as the package structure is clear, we'll be alright. It should be easy to remove the data binding portion out into its own project if necessary later on.

Thanks for all your efforts, its very much appreciated!

Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
...
> Where did the xml stuff end up?
> It needs to be in its own package set as well.

There seem to be some things missing from your "branch", which I used as
a base, I'll see what needs to be added still.

...
>>-statCVS
>>-jdepend
>>-CVS changelog
>>-checkstyle
>>-javadoc
>>-unit tests
>
> That's a pretty good list to start with. Probably all we'll need.

Workin' on it...

>>I would like to commit this stuff tomorrow in the
>>jndc-incubator repo,
>>but it would break the current conventions, as I
>>would have to make
>>these folders:
>>
>> jndc-incubator/nicolaken/swingx
>> jndc-incubator/nicolaken/jndc
>>
>>Would it be ok?
>
> I don't have any objections.

Just a note: I named the dir "reorg", as IMHO it's not "my" extensions
but the general reorg work dir.

Note to all: don't hesitate to dive your hands in there and work on it,
unlimited permission to all granted beforehand :-)

...
> Thanks for all your efforts, its very much appreciated!

You don't know how much *I* appreciate your efforts and those of this
group. It's years I've been waiting to participate in a serious Swing
project, and the warm welcome and support I've received till now are
very promising :-)

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

Kleopatra

Hi Nicola,

>
> There seem to be some things missing from your "branch", which I used as
> a base, I'll see what needs to be added still.
>

just wondering - what exactly are you moving around? (did not read this
thread from the start because I'm not that interested in re-organization
and I'm lazy, I have to admit )

Specifically, do you have some guard that guarantees to synch current
commits to the core jdnc with the reorg'd? I did commit a couple of
refactored test classes this afternoon which do not show up in the
reorg. Hmmm ... or is it unrelated to the core?

Thanks,
Jeanette

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08
Points: 0

Let me jump in real quick

> > There seem to be some things missing from your
> "branch", which I used as
> > a base, I'll see what needs to be added still.
> >
>
> just wondering - what exactly are you moving around?
> (did not read this
> thread from the start because I'm not that interested
> in re-organization
> and I'm lazy, I have to admit )

I think the idea was to get a basic system established in the incubator, and then to move the build system over to core after its debugged since Nicola has commit access to the incubator, but not to core.

So its not a big deal that the markup stuff isn't in the incubator, although it would be nice for being able to debug the build system. Really, a CVS branch would be nice...

Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
...
> So its not a big deal that the markup stuff isn't in the incubator,
> although it would be nice for being able to debug the build system.

I'll put all in, and when it seems ok, then we can do the resynching.

> Really, a CVS branch would be nice...

From my experience, in cases where community involvment is important,
branches actually make it harder to gain interest, as once has to do a
new checkout... this is already in the "normal" checkout.

In any case, I will have to experiment some more on the refactoring, as
while using it I learn more and more...

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08
Points: 0

Hey,

> Is there a mailing list for commits to cvs? It would
> really be useful to
> keep track of the ongoing development...

There sure is! For whatever reason (to supress spamming?) the mailing lists are only accessible for people registered with the project. In particular, if you put in a reguest to be a project observer, then you can register on the mailing list.

Also, in the hopefully not too distant future the website will be updated to include changelogs and various CVS reports.

Cheers,
Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
...
> Also, in the hopefully not too distant future the website will be
> updated to include changelogs and various CVS reports.

I can help. How can we set up a cronjob to publish it daily? (I'm not
accustomed to java.net)

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08
Points: 0

Hey Nicola,

> I can help. How can we set up a cronjob to publish it
> daily? (I'm not
> accustomed to java.net)

Me neither :). This is really a two part problem -- first, getting the build scripts setup, and second to get the website generated.

I'm using Maven for both problems (if you have ANY maven insight, I could use it!). However, we are restricted on what we can do for the java.net website. Whereas Jakarta lets each sub-project do their own thing, and provides the jakarta-site2 template (or whatever its called), java.net only lets you play around with the content portion of the homepage. The navigation bar is off-limits.

The homepage is stored/retrieved from CVS, as I assume also are the binary deliverables, but I don't know that yet for sure.

So, what I'm trying to do is to get the builds automated first, and then to get the html generation working. I'm doing this on my local workstation (and deploying the test website on my machine), and then I was going to upload the finished product once it was all ironed out.

However, if you'd like to help me with the build process, I'd love to share! What I can do is upload the build scripts into the incubator (so we don't clutter up the main CVS repository), and then move the finished setup into the normal JDNC CVS later.

Richard

Nicola Ken Barozzi

jdnc-interest@javadesktop.org wrote:
> Hey Nicola,
>
>
>>I can help. How can we set up a cronjob to publish it
>>daily? (I'm not
>>accustomed to java.net)
>
>

> Me neither :). This is really a two part problem -- first, getting
> the build scripts setup, and second to get the website generated.
>
> I'm using Maven for both problems (if you have ANY maven insight, I
> could use it!).

Bad luck, I'm on another camp ;-)

I have contribted to Ant (import and xmlproperty tasks) and am a Forrest
PMC member... I'm not particularly fond of Maven...

> However, we are restricted on what we can do for the
> java.net website. Whereas Jakarta lets each sub-project do their own
> thing, and provides the jakarta-site2 template (or whatever its called),
> java.net only lets you play around with the content portion of the
> homepage. The navigation bar is off-limits.

IMHO a project like this should have a very low barrier to entry.

I would not use Maven, as it's still somewhat a moving target and not as
widely used and known as Ant, especially in the IDEs. BTW, the same
applies for Forrest.

> The homepage is stored/retrieved from CVS, as I assume also are the
> binary deliverables, but I don't know that yet for sure.
>
> So, what I'm trying to do is to get the builds automated first, and
> then to get the html generation working. I'm doing this on my local
> workstation (and deploying the test website on my machine), and then I
> was going to upload the finished product once it was all ironed out.

> However, if you'd like to help me with the build process, I'd love to
> share! What I can do is upload the build scripts into the incubator (so
> we don't clutter up the main CVS repository), and then move the finished
> setup into the normal JDNC CVS later.

This would be great :-)

Listen, here is my proposal:

0 - move in your package space all the files that are still referenced
from the jndc package (to make it indipendent)
1 - Retain Ant ans a build tool
2 - Add the project to the Gump http://gump.apache.org/ build system
3 - Make it dead simple to load stuff in a Netbeans and Eclipse
(the netbeans instructions now there need to be more visible)
4 - Use plain html for documentation
5 - remove all dependencies that are not strictly necessary
6 - refactor the packages to separate the swingx, binding and jndc stuff

Oh, and I'm willing to help, of course. :-)

--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: jdnc-unsubscribe@jdnc.dev.java.net
For additional commands, e-mail: jdnc-help@jdnc.dev.java.net

rbair
Offline
Joined: 2003-07-08
Points: 0

Hi,

> >
> > I'm using Maven for both problems (if you have ANY
> maven insight, I
> > could use it!).
>
> Bad luck, I'm on another camp ;-)
>
> I have contribted to Ant (import and xmlproperty
> tasks) and am a Forrest
> PMC member... I'm not particularly fond of Maven...

> I would not use Maven, as it's still somewhat a
> moving target and not as
> widely used and known as Ant, especially in the IDEs.
> BTW, the same
> applies for Forrest.

> > However, if you'd like to help me with the build
> process, I'd love to
> > share! What I can do is upload the build scripts
> into the incubator (so
> > we don't clutter up the main CVS repository), and
> then move the finished
> > setup into the normal JDNC CVS later.
>
> This would be great :-)

I'm not religiously devoted to any one build methodology. In this other thread (http://www.javadesktop.org/forums/thread.jspa?threadID=6656&tstart=0) I detailed (about halfway through the thread) the kinds of deliverables that we wanted to build, and the general project structure. I don't think that Maven could possibly do what we wanted it to out of the box -- I was going to end up scripting a plugin in order to do all of the builds and whatnot.

> Listen, here is my proposal:
>
> 0 - move in your package space all the files that are
> still referenced
> from the jndc package (to make it indipendent)

Sorry, what do you mean by "still referenced"?

> 1 - Retain Ant ans a build tool
> 2 - Add the project to the Gump
> http://gump.apache.org/ build system

We are currently using CruiseControl for continuous integration. Gump does the same thing, right? Is there any reason to favor Gump over CruiseControl? From what I've seen CC is pretty widely used, even by some Apache projects, I think. Could be wrong.

> 3 - Make it dead simple to load stuff in a Netbeans
> and Eclipse
> (the netbeans instructions now there need to be
> to be more visible)

Amen to that. I'd like to have predefined netbeans and eclipse project files, if possible. At the very least, it would be important to have a special walkthrough for setting up the project in each of these IDEs.

> 4 - Use plain html for documentation
> 5 - remove all dependencies that are not strictly
> necessary
> 6 - refactor the packages to separate the swingx,
> binding and jndc stuff

One of the things that was really attractive about Maven was the statCVS plugin, as well as some of the other "report" plugins that would generate HTML for us. Do you know how to accomplish this with ant? It might also be possible to ship ant build scripts which build the various projects, but retain the website generating Maven code in house, but I think I'd rather it were all in CVS.

> Oh, and I'm willing to help, of course. :-)

Naturally! Let me see about cvs access to the incubator. I think access requires a JCA which I don't know if you've read about or faxed in yet. Essentially, Sun requires that anybody who contributes code to the project needs to sign a Joint Copyright Assignment. The idea is that code in JDNC may one day make its way back into Swing and in order for that to happen Sun needs to have the ability to change the license of the source code. Hence, the JCA. Its a real pain, but it makes sense.

In the mean time, let me know how you would go about managing the build process for the various deliverables, and also generate some of the webpage stuff that Maven is currently doing.

Thanks!
Richard

dhall
Offline
Joined: 2006-02-17
Points: 0

Richard:

It's reasonably simple to execute a script on every CVS checkin: a couple of employers ago, I had one that echoed every commit log entry to a news group. It was a fairly short perl script -- if you want, I'll try and find it and send you a copy

Dave Hall
http://jga.sf.net/
http://jroller.com/page/dhall/

rbair
Offline
Joined: 2003-07-08
Points: 0

Dave,

Where does the script need to be installed? I assume on the server hosting cvs. Or does the script listen for mail from CVS indicating a checkin has occurred? I don't think we'd be able to install anything on the server itself since its hosted by CollabNet, and not us directly.

Richard

dhall
Offline
Joined: 2006-02-17
Points: 0

> Dave,
>
> Where does the script need to be installed? I assume
> on the server hosting cvs. Or does the script listen
> for mail from CVS indicating a checkin has occurred?
> I don't think we'd be able to install anything on the
> server itself since its hosted by CollabNet, and not
> us directly.
>
> Richard

The script itself does go on the server, so if you don't have enough access, it wouldn't work.

You make an entry in CVSROOT/loginfo that passes the commit information (user, commit time, log entry) through an arbitrary command line. I had control over the server so I did what I wanted in a script that was external. It's possible to include perl scripts on the command line via the -e flag, but you really want to keep them short (mine is only a dozen or so lines, but longer than I'd want on the command line).

If you can find a way to submit the information via command line, hooking into the loginfo is an option

Dave Hall
http://jga.sf.net/
http://jroller.com/page/dhall/