Skip to main content

Incubator

10 replies [Last post]
bcbeck
Offline
Joined: 2003-06-16

We've talked in several threads about setting up an incubator sub project (see http://www.javadesktop.org/forums/thread.jspa?forumID=53&threadID=3483&m...
for example)

Just wanted to let everyone know what was happening on this front. We've got an incubator sub project created and will hopefully be making it visible next week. While we expect the incubator to be pretty free form, we are also writing up some simple guidelines that should help everyone be more productive. We also are hoping to provide a little bit of infrastructure so that its really quick and easy to start new things in the incubator and folks don't have to reinvent stuff like ant scripts over and over.

Hope to have all this put together sometime next week so stay tuned.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
dhall
Offline
Joined: 2006-02-17

Mark:

I just caught this message today. My logins have been messed up ever since Sun's great unification of all of the various developer sites at JavaOne last year (or was it the year before?). I'm dhall as far as the forums are concerned but david_hall at most of the other java.net logins.

Dave

bcbeck
Offline
Joined: 2003-06-16

As promised, we have just put up the Incubator project. Have a look at the project page at:

https://jdnc-incubator.dev.java.net/

We intend to automatically make all the Observers of the JDNC project also Observers of the Incubator project. This hasn't happened yet but I hope to have that straightened out early next week. We will also be automatically giving Developer status to anyone who has signed a JCA. Look for that to be done by Tuesday (Monday is a holiday for us in the U.S.)

Any questions, let us know.

rbair
Offline
Joined: 2003-07-08

Brian,

Thanks for getting the incubator set up, that's good news! Has anybody considered getting forums up for that project as well, or do people prefer to keep all of the posts here?

Thanks,
Richard

Mark Davidson

On 09/03/2004 05:10 PM, jdnc-interest@javadesktop.org wrote:
> Brian,
>
> Thanks for getting the incubator set up, that's good news! Has
> anybody considered getting forums up for that project as well, or do
> people prefer to keep all of the posts here?

I think we should keep the conversation about incubation projects within
within this forum/mailing list just to keep things simple.

I've tried to add all the JCA signers in this list as developers to the
jdnc-incubator:

https://jdnc.dev.java.net/jca-signers.html

However, David Hall's id, dhall, is not a valid id within dev.java.net -
this is probably a javadesktop forums id. I found dhalle, and
dhall_sumant. If David can give me his java.net id then I'll add you as
a developer to the incubator.

--Mark

---------------------------------------------------------------------
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

Hey Mark,

Where should we put resources in the incubator? Was the thought to put a resources directory near top-level (like lib), or deep in the source tree?

Richard

Mark Davidson

Hi Richard,

I see you spent your long weekend contributing to the jdnc-incubator. ;-)

On 09/07/2004 10:27 AM, jdnc-interest@javadesktop.org wrote:
> Hey Mark,
>
> Where should we put resources in the incubator? Was the thought to
> put a resources directory near top-level (like lib), or deep in the
> source tree?

From the README.txt, I tried to outline a bit of a policy about this.

"lib/${java.net.id} - Libraries for use by individual developers.

Any resources like text files, test data, graphics or icons should be
placed in a sub-directory or the developers' package called "resources".
All files in the resources directory will be copied to thier respective
classpaths as part of the build process."

For your purposes, if you have external jars then place them in lib/rbair.

If you want to include test data or images then I would recomment them
to be placed in "resources".

Do you have any other requirements beyond this?

Thanks,

--Mark

---------------------------------------------------------------------
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

>I see you spent your long weekend contributing to the jdnc-incubator. ;)

...and watching plenty of college football ;)

To make sure I've got this right, resources should be in org.jdesktop.jdnc.incubator.rbair.resources, right?

>Do you have any other requirements beyond this?

Not that I know of, but I'll keep ya posted :)

Message was edited by: rbair

Mark Davidson

On 09/07/2004 11:31 AM, jdnc-interest@javadesktop.org wrote:
> To make sure I've got this right, resources should be in
> org.jdesktop.jdnc.incubator.rbair.resources, right?

Correct.

They will be copied to the build/classes directory as part of the build
process and you can reference them within your classes by using:

URL url = MyClass.class.getResource("resources/myIcon.png");

--Mark

---------------------------------------------------------------------
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

Hey Mark,

Gilles and I have run into a little snag in the incubator, and I was wondering what your opinion was on this:

" > Validator, WebStartContext, Converter, Converters and
> ConverterException and everything in the event
> package are pure copies. If removing them will make
> your job easier, then go ahead. It just means that in
> order for someone to run the incubator code they will
> also need the jdnc code to fill in the blanks.
>
> The other approach is a full branch of JDNC.
>
> Which do you prefer?
>
>
> Message was edited by: rbair

I think an incubator is mostly designed to add 'new things ' into the code base. In our case, you made changes to a large extent. When making large changes to an existing codebase (involving at least 10 classes), the best way would be to work directly on the jdnc project but in a dedicated branch like 'EXP-RBAIR-GPHILIPP' and with commit access in this branch only. It may not be acceptable politically for the JDNC team to setup such an access.

Thus, the best thing we can do to minimize work when we want to integrate changes in one way or the other (towards jdnc, or toward jdnc-incubator) is to replicate the whole thing. We could also keep the original JDNC package hierarchy (again to avoid unnecessary package renaming steps) and use a directory for each incubator submission :

jdnc-incubator/rbair/src/demo/org/jdesktop/swing/data/TestDataModel.java
jdnc-incubator/rbair/src/java/org/jdesktop/swing/data/DataModel.java
jdnc-incubator/rbair/src/test/...
jdnc-incubator/davidson1/src/java...

See ? No rbair or davidson in packages...

Gilles"

Richard

Mark Davidson

Hi Richard,

On 09/07/2004 06:12 PM, jdnc-interest@javadesktop.org wrote:
> Hey Mark,
>
> Gilles and I have run into a little snag in the incubator, and I was
> wondering what your opinion was on this:
>
> " > Validator, WebStartContext, Converter, Converters and
>
>> ConverterException and everything in the event package are pure
>> copies. If removing them will make your job easier, then go ahead.
>> It just means that in order for someone to run the incubator code
>> they will also need the jdnc code to fill in the blanks.
>>
>> The other approach is a full branch of JDNC.
>>
>> Which do you prefer?

Er, neither? ;-)

Perhaps we should check in the weekly promoted swingx.jar in the
JDNC-INCU_ROOT/lib dir. The compile and run task will pick these up.
This is preferable than maintaining copies of the JDNC source base
within two repositories.

Unfortunately, this will not allow changes to the JDNC swingx code
within the incubator. If issues arise using the swingx.jar classes
within the context of the incubator then bugs should be filed in JDNC.

> I think an incubator is mostly designed to add 'new things ' into the
> code base. In our case, you made changes to a large extent. When
> making large changes to an existing codebase (involving at least 10
> classes), the best way would be to work directly on the jdnc project
> but in a dedicated branch like 'EXP-RBAIR-GPHILIPP' and with commit
> access in this branch only. It may not be acceptable politically for
> the JDNC team to setup such an access.

Sorry if I may have broken you.

Obviously, if the changes are to the JDNC core classes then they should
be committed to the main JDNC source base. However, we would like to
review the fixes first.

> Thus, the best thing we can do to minimize work when we want to
> integrate changes in one way or the other (towards jdnc, or toward
> jdnc-incubator) is to replicate the whole thing. We could also keep
> the original JDNC package hierarchy (again to avoid unnecessary
> package renaming steps) and use a directory for each incubator
> submission :
>
> jdnc-incubator/rbair/src/demo/org/jdesktop/swing/data/TestDataModel.java
> jdnc-incubator/rbair/src/java/org/jdesktop/swing/data/DataModel.java
> jdnc-incubator/rbair/src/test/...
> jdnc-incubator/davidson1/src/java...
>
> See ? No rbair or davidson in packages...

Like you said, the incubator is used to add new things and was not
intended as a repository for checking in bug fixes. The best solution
would be to review your changes and then give you developer access so
you can check them in yourself.

We're still getting up to speed on this open source process. ;-)

--Mark

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