Skip to main content

Netbeans project files for the framework

5 replies [Last post]
Anonymous

Hi all,

I found useful to have netbeans project for our ME Framework. It allows run and
debug framework just in one click directly from IDE! Very useful during
development. Attached project files can be used as is without any modifications
(thanks Dmitri Trounine for the hint how to provide link to JT Harness).
They should be placed under nbproject directory in the root directory of the
framework. Just one requirement: local.properties file must be present in the
build directory.

I propose to include nbproject directory to our repository. What do you think?

Thanks,
Alexander
[project.xml]
[ide-file-targets.xml]
---------------------------------------------------------------------
To unsubscribe, e-mail: meframework-unsubscribe@cqme.dev.java.net
For additional commands, e-mail: meframework-help@cqme.dev.java.net

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Vladimir Sizikov

Hi Alexander, Dmitri,

Excellent idea! I didn't know that we can get away without any manual
configuration for external libs, like JavaTests harness.

Please post the changes into your private branch in the subversion
repository, and I'll review them.

Which NB versions do you target? The current one is 5.5, so we'd
better make sure that 5.5 works fine with the proposed files.

Also, NB 6.0, which is currently in the works, offerns A LOT of great
editing goodies and finally reaches Eclipse levels. So it would be
great if the project files are applicable to NB 6.0 M7, the latest
one (that's what I currently use). :)

Just to be clear, our project still must be IDE-independent, and it
should be always possible to build it from the command line, without
any IDE.

But by providing the integration with Netbeans we'll make life of some
new ME Framework users much easier, which is a good thing.

These changes are for FW 1.2 (trunk), not for dot-dot release FW 1.1.2.

Thanks,
--Vladimir

On Wed, Mar 07, 2007 at 01:27:24PM +0300, Alexander Alexeev wrote:
> Hi all,
>
> I found useful to have netbeans project for our ME Framework. It allows run
> and
> debug framework just in one click directly from IDE! Very useful during
> development. Attached project files can be used as is without any
> modifications
> (thanks Dmitri Trounine for the hint how to provide link to JT Harness).
> They should be placed under nbproject directory in the root directory of the
> framework. Just one requirement: local.properties file must be present in
> the
> build directory.
>
> I propose to include nbproject directory to our repository. What do you
> think?
>
> Thanks,
> Alexander

>
>

>
> org.netbeans.modules.ant.freeform
>
>
>

> ME Framework
>
>
build/build.xml >
build/local.properties >
build/build.properties >
>
>
>
> java
> src/share/classes
>

>

>
>
>

> dist
>
>
>

> clean
>
>
>

> dist-docs
>
>
>

> clean
> dist
>
>
>

> run-nb
>
>
>

> debug-nb
>
>
>
>
>
>
> src/share/classes
>

>
> ${ant.script}
>

>

>
>
>
>
>
>
>
>

>

>
>
>
>
>
src/share/classes > ${FCS_JCTTOOLS}/lib/javatest.jar
> 1.5
>

>

>
>

>
>

>
>
>

>
>
>
>
>
>
>
>
>

>

>
>
>
>
>
>
>
>
>

>
>
>
>
>
>
>

>

> >

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

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

Alexander Alexeev

Hi Vladimir,

the changes in my private branch now. You can review them by following link:
http://fisheye4.cenqua.com/changelog/cqme/?cs=431

The project targeted to 5.5 release. The applicability for the 6.0 version
should be checked. I will do.

Thanks,
Alexander

Vladimir Sizikov wrote:
> Hi Alexander, Dmitri,
>
> Excellent idea! I didn't know that we can get away without any manual
> configuration for external libs, like JavaTests harness.
>
> Please post the changes into your private branch in the subversion
> repository, and I'll review them.
>
> Which NB versions do you target? The current one is 5.5, so we'd
> better make sure that 5.5 works fine with the proposed files.
>
> Also, NB 6.0, which is currently in the works, offerns A LOT of great
> editing goodies and finally reaches Eclipse levels. So it would be
> great if the project files are applicable to NB 6.0 M7, the latest
> one (that's what I currently use). :)
>
> Just to be clear, our project still must be IDE-independent, and it
> should be always possible to build it from the command line, without
> any IDE.
>
> But by providing the integration with Netbeans we'll make life of some
> new ME Framework users much easier, which is a good thing.
>
> These changes are for FW 1.2 (trunk), not for dot-dot release FW 1.1.2.
>
> Thanks,
> --Vladimir
>
> On Wed, Mar 07, 2007 at 01:27:24PM +0300, Alexander Alexeev wrote:
>> Hi all,
>>
>> I found useful to have netbeans project for our ME Framework. It allows run
>> and
>> debug framework just in one click directly from IDE! Very useful during
>> development. Attached project files can be used as is without any
>> modifications
>> (thanks Dmitri Trounine for the hint how to provide link to JT Harness).
>> They should be placed under nbproject directory in the root directory of the
>> framework. Just one requirement: local.properties file must be present in
>> the
>> build directory.
>>
>> I propose to include nbproject directory to our repository. What do you
>> think?
>>
>> Thanks,
>> Alexander
>

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

Vladimir Sizikov

Alexander,

Here are my comments:

1. We probably should also add the unit tests to the project tree:
"unitTests/classes". Currently, only "src/share/classes" are
visible.

2. "unit-tests" ant targed should be bound to NB's test IDE action
(Alt-F6), or maybe some other Netbeans magic so that we could run
unit tests from within the IDE. I guess this can be posponed for
the further updates.

3. I couldn't start the debugging for some reason, I got the following:
debug-nb:
ERROR: transport error 202: connect failed: Connection timed out
ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
initialized [../../../src/share/back/debugInit.c:690]

4. I'd suggest to make targets "run-nb" and "debug-nb" depend on
"dist-framework", not "dist". That way we'll save some time by
avoiding the zip file creation, which is not really needed here.

Thanks,
--Vladimir

On Wed, Mar 07, 2007 at 02:03:59PM +0300, Alexander Alexeev wrote:
> Hi Vladimir,
>
> the changes in my private branch now. You can review them by following link:
> http://fisheye4.cenqua.com/changelog/cqme/?cs=431
>
> The project targeted to 5.5 release. The applicability for the 6.0 version
> should be checked. I will do.
>
> Thanks,
> Alexander
>
> Vladimir Sizikov wrote:
> >Hi Alexander, Dmitri,
> >
> >Excellent idea! I didn't know that we can get away without any manual
> >configuration for external libs, like JavaTests harness.
> >
> >Please post the changes into your private branch in the subversion
> >repository, and I'll review them.
> >
> >Which NB versions do you target? The current one is 5.5, so we'd
> >better make sure that 5.5 works fine with the proposed files.
> >
> >Also, NB 6.0, which is currently in the works, offerns A LOT of great
> >editing goodies and finally reaches Eclipse levels. So it would be
> >great if the project files are applicable to NB 6.0 M7, the latest
> >one (that's what I currently use). :)
> >
> >Just to be clear, our project still must be IDE-independent, and it
> >should be always possible to build it from the command line, without
> >any IDE.
> >
> >But by providing the integration with Netbeans we'll make life of some
> >new ME Framework users much easier, which is a good thing.
> >
> >These changes are for FW 1.2 (trunk), not for dot-dot release FW 1.1.2.
> >
> >Thanks,
> > --Vladimir
> >
> >On Wed, Mar 07, 2007 at 01:27:24PM +0300, Alexander Alexeev wrote:
> >>Hi all,
> >>
> >>I found useful to have netbeans project for our ME Framework. It allows
> >>run and
> >>debug framework just in one click directly from IDE! Very useful during
> >>development. Attached project files can be used as is without any
> >>modifications
> >>(thanks Dmitri Trounine for the hint how to provide link to JT Harness).
> >>They should be placed under nbproject directory in the root directory of
> >>the
> >>framework. Just one requirement: local.properties file must be present in
> >>the
> >>build directory.
> >>
> >>I propose to include nbproject directory to our repository. What do you
> >>think?
> >>
> >>Thanks,
> >>Alexander
> >

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

Alexander Alexeev

Vladimir,

I've fixed 1), 2) and 4) issues. You can see the changes here:
http://fisheye4.cenqua.com/changelog/cqme/?cs=432

I can't event start debugger on current 6.0 version. Every time then I press
Debug button it prompt me to create debug target and nothing happens then.
Did you try on 5.5 version? If you succeeded on 5.5 I propose to postpone this
issue till more stable Netbeans version.

Thanks,
Alexander

Vladimir Sizikov wrote:
> Alexander,
>
> Here are my comments:
>
> 1. We probably should also add the unit tests to the project tree:
> "unitTests/classes". Currently, only "src/share/classes" are
> visible.
>
> 2. "unit-tests" ant targed should be bound to NB's test IDE action
> (Alt-F6), or maybe some other Netbeans magic so that we could run
> unit tests from within the IDE. I guess this can be posponed for
> the further updates.
>
> 3. I couldn't start the debugging for some reason, I got the following:
> debug-nb:
> ERROR: transport error 202: connect failed: Connection timed out
> ERROR: JDWP Transport dt_socket failed to initialize,
> TRANSPORT_INIT(510)
> JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
> initialized [../../../src/share/back/debugInit.c:690]
>
> 4. I'd suggest to make targets "run-nb" and "debug-nb" depend on
> "dist-framework", not "dist". That way we'll save some time by
> avoiding the zip file creation, which is not really needed here.
>
> Thanks,
> --Vladimir
>
> On Wed, Mar 07, 2007 at 02:03:59PM +0300, Alexander Alexeev wrote:
>> Hi Vladimir,
>>
>> the changes in my private branch now. You can review them by following link:
>> http://fisheye4.cenqua.com/changelog/cqme/?cs=431
>>
>> The project targeted to 5.5 release. The applicability for the 6.0 version
>> should be checked. I will do.
>>
>> Thanks,
>> Alexander
>>
>> Vladimir Sizikov wrote:
>>> Hi Alexander, Dmitri,
>>>
>>> Excellent idea! I didn't know that we can get away without any manual
>>> configuration for external libs, like JavaTests harness.
>>>
>>> Please post the changes into your private branch in the subversion
>>> repository, and I'll review them.
>>>
>>> Which NB versions do you target? The current one is 5.5, so we'd
>>> better make sure that 5.5 works fine with the proposed files.
>>>
>>> Also, NB 6.0, which is currently in the works, offerns A LOT of great
>>> editing goodies and finally reaches Eclipse levels. So it would be
>>> great if the project files are applicable to NB 6.0 M7, the latest
>>> one (that's what I currently use). :)
>>>
>>> Just to be clear, our project still must be IDE-independent, and it
>>> should be always possible to build it from the command line, without
>>> any IDE.
>>>
>>> But by providing the integration with Netbeans we'll make life of some
>>> new ME Framework users much easier, which is a good thing.
>>>
>>> These changes are for FW 1.2 (trunk), not for dot-dot release FW 1.1.2.
>>>
>>> Thanks,
>>> --Vladimir
>>>
>>> On Wed, Mar 07, 2007 at 01:27:24PM +0300, Alexander Alexeev wrote:
>>>> Hi all,
>>>>
>>>> I found useful to have netbeans project for our ME Framework. It allows
>>>> run and
>>>> debug framework just in one click directly from IDE! Very useful during
>>>> development. Attached project files can be used as is without any
>>>> modifications
>>>> (thanks Dmitri Trounine for the hint how to provide link to JT Harness).
>>>> They should be placed under nbproject directory in the root directory of
>>>> the
>>>> framework. Just one requirement: local.properties file must be present in
>>>> the
>>>> build directory.
>>>>
>>>> I propose to include nbproject directory to our repository. What do you
>>>> think?
>>>>
>>>> Thanks,
>>>> Alexander
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: meframework-unsubscribe@cqme.dev.java.net
> For additional commands, e-mail: meframework-help@cqme.dev.java.net
>

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

Vladimir Sizikov

Alexander,

Thanks for the quick fixes, everything is OK with NB 5.5, so please
commit. I will investigate NB 6.0 later, with more stable version, as
you suggested.

Thanks,
--Vladimir

On Wed, Mar 07, 2007 at 03:14:09PM +0300, Alexander Alexeev wrote:
> Vladimir,
>
> I've fixed 1), 2) and 4) issues. You can see the changes here:
> http://fisheye4.cenqua.com/changelog/cqme/?cs=432
>
> I can't event start debugger on current 6.0 version. Every time then I press
> Debug button it prompt me to create debug target and nothing happens then.
> Did you try on 5.5 version? If you succeeded on 5.5 I propose to postpone
> this
> issue till more stable Netbeans version.
>
> Thanks,
> Alexander
>
> Vladimir Sizikov wrote:
> >Alexander,
> >
> >Here are my comments:
> >
> >1. We probably should also add the unit tests to the project tree:
> > "unitTests/classes". Currently, only "src/share/classes" are
> > visible.
> >
> >2. "unit-tests" ant targed should be bound to NB's test IDE action
> > (Alt-F6), or maybe some other Netbeans magic so that we could run
> > unit tests from within the IDE. I guess this can be posponed for
> > the further updates.
> >
> >3. I couldn't start the debugging for some reason, I got the following:
> >debug-nb:
> >ERROR: transport error 202: connect failed: Connection timed out
> >ERROR: JDWP Transport dt_socket failed to initialize,
> >TRANSPORT_INIT(510)
> >JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports
> >initialized [../../../src/share/back/debugInit.c:690]
> >
> >4. I'd suggest to make targets "run-nb" and "debug-nb" depend on
> > "dist-framework", not "dist". That way we'll save some time by
> > avoiding the zip file creation, which is not really needed here.
> >
> >Thanks,
> > --Vladimir
> >
> >On Wed, Mar 07, 2007 at 02:03:59PM +0300, Alexander Alexeev wrote:
> >>Hi Vladimir,
> >>
> >>the changes in my private branch now. You can review them by following
> >>link:
> >>http://fisheye4.cenqua.com/changelog/cqme/?cs=431
> >>
> >>The project targeted to 5.5 release. The applicability for the 6.0 version
> >>should be checked. I will do.
> >>
> >>Thanks,
> >>Alexander
> >>
> >>Vladimir Sizikov wrote:
> >>>Hi Alexander, Dmitri,
> >>>
> >>>Excellent idea! I didn't know that we can get away without any manual
> >>>configuration for external libs, like JavaTests harness.
> >>>
> >>>Please post the changes into your private branch in the subversion
> >>>repository, and I'll review them.
> >>>
> >>>Which NB versions do you target? The current one is 5.5, so we'd
> >>>better make sure that 5.5 works fine with the proposed files.
> >>>
> >>>Also, NB 6.0, which is currently in the works, offerns A LOT of great
> >>>editing goodies and finally reaches Eclipse levels. So it would be
> >>>great if the project files are applicable to NB 6.0 M7, the latest
> >>>one (that's what I currently use). :)
> >>>
> >>>Just to be clear, our project still must be IDE-independent, and it
> >>>should be always possible to build it from the command line, without
> >>>any IDE.
> >>>
> >>>But by providing the integration with Netbeans we'll make life of some
> >>>new ME Framework users much easier, which is a good thing.
> >>>
> >>>These changes are for FW 1.2 (trunk), not for dot-dot release FW 1.1.2.
> >>>
> >>>Thanks,
> >>> --Vladimir
> >>>
> >>>On Wed, Mar 07, 2007 at 01:27:24PM +0300, Alexander Alexeev wrote:
> >>>>Hi all,
> >>>>
> >>>>I found useful to have netbeans project for our ME Framework. It allows
> >>>>run and
> >>>>debug framework just in one click directly from IDE! Very useful during
> >>>>development. Attached project files can be used as is without any
> >>>>modifications
> >>>>(thanks Dmitri Trounine for the hint how to provide link to JT Harness).
> >>>>They should be placed under nbproject directory in the root directory
> >>>>of the
> >>>>framework. Just one requirement: local.properties file must be present
> >>>>in the
> >>>>build directory.
> >>>>
> >>>>I propose to include nbproject directory to our repository. What do you
> >>>>think?
> >>>>
> >>>>Thanks,
> >>>>Alexander
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: meframework-unsubscribe@cqme.dev.java.net
> >For additional commands, e-mail: meframework-help@cqme.dev.java.net
> >
>

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