AW: [JBoss-dev] RE: AW: Patches to jboss.net
Addendum: 4.5 you have to first utter a jboss-all/testsuite/build because there are some basic testcase classes which do the server deployment for us. Maybe these were the unresolved symbols you were seeing. I added that hint to the jboss.net/docs/Readme ... Martin and Marius, any help in getting the installation and build as user-friendly as possible would be appreciated. If you want to rewrite/add things to the Readme in better and more intelligible English than mine (which is not too hard), please go ahead. I really want this web service thingy to work for you and the rest of the world ... CGJ -Ursprüngliche Nachricht- Von: Peter Braswell [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. April 2002 00:39 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net All, I'm not sure if this is the *approved* way of doing things, but here's the sequence that seems to work for me: 1. Do a CVS update, rebuild jboss from jboss-all\build\build.sh or build.bat depending on your poison. 2. Goto jboss.net and build. Make sure .sar file makes it into the jboss deploy directory. This is a manual process for me. If this is a fresh get from CVS, sometimes the required .jars/config files don't make it to the right jboss directory in which case you have to do it manually. I can provide details here if this is what you are having problems with. 3. Start jboss, make sure jboss-net.sar deploys okay. 4. Goto jboss.net\testsuite and do a build tests-standard-unit 5. Watch in utter amazement the miracle to which you are witness to. Okay, maybe not that dramatic, but you get the idea... :-) All and all I know how frustrating this can be (BELEIVE ME!). Christoph and I will be working on docs/process/hints to make the whole thing easier... promise!! hope this helps, peter On Tue, 9 Apr 2002 15:24:44 -0700 [EMAIL PROTECTED] wrote: Hi Marius, I used ./build.sh -Dmodules=jboss.net/testsuite modules-tests which seems to just run the JBoss.net testsuite. This worked this morning but when I reapply my testsuite patch (capitalisation error removing the emption address book impl class, obviously hasn't made it into cvs yet), I still get a whole bunch of cannot resolve symbols when building the testsuites. I will try to find out what's causing this tomorrow morning. Cheers, Martin Original Message From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RE: AW: Patches to jboss.net Date: Tue, 09 Apr 2002 14:36:13 +0200 Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain on anything, but I can't see any .ear or wsr-files generated. Is this right? I though it would create hello.wsr. Martin Maisey wrote: Hi Christoph Thanks for having such a deep look into jboss.net and fixing these open issues. No problem + it wasn't a particularly deep look! Some of them were cause by my stupidity (the techtrader-lib copy operation, I did not commit, simply forgot it), Thought it was probably something like that - I've done the same thing myself many times... some of them are those frequent changes in the jboss-core which I cannot immediately adopt because of restricted time ... We really should have a separation of core and modules such as Peter Braswell suggested ... If you need a 'second pair of hands' to try to keep on top of this type of thing and test updates, I'm happy to do it as I would like to get a better knowledge of JBoss and web services and have (a small amount of ;-)) spare time. I noticed that some of the project web page seems a bit out of date - only one of the build commands worked for me and the command to start the test suite needs tweaking. What's the process to update it? I could also take a look at the failing JMX endpoint unit test if it would help, although this is likely to take a bit longer as I will probably have to wrap my head around much more of Axis and JBoss JMX ;-) Cheers, Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development Peter Braswell Utopian Software [EMAIL PROTECTED] 757.560.8867 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] RE: AW: Patches to jboss.net
This means that the testsuite does not find the jboss.net classes, could you please check That the class-path at the javac/ task points to jboss-all/jboss.net/output/lib/jboss-net.sar and that that file Exists. CGJ -Ursprüngliche Nachricht- Von: Marius [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. April 2002 10:24 An: Peter Braswell Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net Peter Braswell wrote: All, I'm not sure if this is the *approved* way of doing things, but here's the sequence that seems to work for me: 1. Do a CVS update, rebuild jboss from jboss-all\build\build.sh or build.bat depending on your poison. 2. Goto jboss.net and build. Make sure .sar file makes it into the jboss deploy directory. This is a manual process for me. If this is a fresh get from CVS, sometimes the required .jars/config files don't make it to the right jboss directory in which case you have to do it manually. I can provide details here if this is what you are having problems with. 3. Start jboss, make sure jboss-net.sar deploys okay. 4. Goto jboss.net\testsuite and do a build tests-standard-unit Do you use windows? This step gived me many syntax-errors, for example: [javac] /home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/src/main/org/jboss/t est/net/jmx/JmxUnitTestCase.java:72: cannot resolve symbol [javac] symbol : class RemoteAdaptor [javac] location: class org.jboss.test.net.jmx.JmxUnitTestCase [javac] RemoteAdaptor handler=createRemoteAdaptor(new URL(JMX_END_POINT)); [javac] ^ [javac] 36 errors 5. Watch in utter amazement the miracle to which you are witness to. Okay, maybe not that dramatic, but you get the idea... :-) All and all I know how frustrating this can be (BELEIVE ME!). Christoph and I will be working on docs/process/hints to make the whole thing easier... promise!! hope this helps, peter On Tue, 9 Apr 2002 15:24:44 -0700 [EMAIL PROTECTED] wrote: Hi Marius, I used ./build.sh -Dmodules=jboss.net/testsuite modules-tests which seems to just run the JBoss.net testsuite. This worked this morning but when I reapply my testsuite patch (capitalisation error removing the emption address book impl class, obviously hasn't made it into cvs yet), I still get a whole bunch of cannot resolve symbols when building the testsuites. I will try to find out what's causing this tomorrow morning. Cheers, Martin Original Message From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [JBoss-dev] RE: AW: Patches to jboss.net Date: Tue, 09 Apr 2002 14:36:13 +0200 Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain on anything, but I can't see any .ear or wsr-files generated. Is this right? I though it would create hello.wsr. Martin Maisey wrote: Hi Christoph Thanks for having such a deep look into jboss.net and fixing these open issues. No problem + it wasn't a particularly deep look! Some of them were cause by my stupidity (the techtrader-lib copy operation, I did not commit, simply forgot it), Thought it was probably something like that - I've done the same thing myself many times... some of them are those frequent changes in the jboss-core which I cannot immediately adopt because of restricted time ... We really should have a separation of core and modules such as Peter Braswell suggested ... If you need a 'second pair of hands' to try to keep on top of this type of thing and test updates, I'm happy to do it as I would like to get a better knowledge of JBoss and web services and have (a small amount of ;-)) spare time. I noticed that some of the project web page seems a bit out of date - only one of the build commands worked for me and the command to start the test suite needs tweaking. What's the process to update it? I could also take a look at the failing JMX endpoint unit test if it would help, although this is likely to take a bit longer as I will probably have to wrap my head around much more of Axis and JBoss JMX ;-) Cheers, Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development Peter Braswell Utopian Software [EMAIL PROTECTED] 757.560.8867 ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] RE: AW: Patches to jboss.net
Jung , Dr. Christoph wrote:
This means that the testsuite does not find the jboss.net classes, could you
please check
That the class-path at the javac/ task points to
jboss-all/jboss.net/output/lib/jboss-net.sar and that that file
Exists.
Thanks. This leaves just one error, that I think Martins patch fixes.
Can you commit this?
CGJ
-Ursprüngliche Nachricht-
Von: Marius [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 10. April 2002 10:24
An: Peter Braswell
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net
Peter Braswell wrote:
All,
I'm not sure if this is the *approved* way of doing things, but here's
the sequence that seems to work for me:
1. Do a CVS update, rebuild jboss from jboss-all\build\build.sh or
build.bat depending on your poison.
2. Goto jboss.net and build. Make sure .sar file makes it into the
jboss deploy directory. This is a manual process for me. If this is
a fresh get from CVS, sometimes the required .jars/config files
don't make it to the right jboss directory in which case you have to
do it manually. I can provide details here if this is what you are
having problems with.
3. Start jboss, make sure jboss-net.sar deploys okay.
4. Goto jboss.net\testsuite and do a build tests-standard-unit
Do you use windows? This step gived me many syntax-errors, for example:
[javac]
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/src/main/org/jboss/t
est/net/jmx/JmxUnitTestCase.java:72:
cannot resolve symbol
[javac] symbol : class RemoteAdaptor
[javac] location: class org.jboss.test.net.jmx.JmxUnitTestCase
[javac] RemoteAdaptor handler=createRemoteAdaptor(new
URL(JMX_END_POINT));
[javac] ^
[javac] 36 errors
5. Watch in utter amazement the miracle to which you are witness to.
Okay, maybe not that dramatic, but you get the idea... :-)
All and all I know how frustrating this can be (BELEIVE ME!).
Christoph and I will be working on docs/process/hints to make the
whole thing easier... promise!!
hope this helps,
peter
On Tue, 9 Apr 2002 15:24:44 -0700 [EMAIL PROTECTED] wrote:
Hi Marius,
I used ./build.sh -Dmodules=jboss.net/testsuite modules-tests
which seems to just run the JBoss.net testsuite. This worked this
morning but when I reapply my testsuite patch (capitalisation error
removing the emption address book impl class, obviously hasn't made
it into cvs yet), I still get a whole bunch of cannot resolve
symbols when building the testsuites.
I will try to find out what's causing this tomorrow morning.
Cheers,
Martin
Original Message
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] RE: AW: Patches to jboss.net
Date: Tue, 09 Apr 2002 14:36:13 +0200
Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't
complain
on
anything, but I can't see any .ear or wsr-files generated. Is this
right? I though it would create hello.wsr.
Martin Maisey wrote:
Hi Christoph
Thanks for having such a deep look into jboss.net and fixing
these
open issues.
No problem + it wasn't a particularly deep look!
Some of them were cause by my stupidity (the techtrader-lib
copy operation, I did not commit, simply forgot it),
Thought it was probably something like that - I've done the same
thing myself many times...
some of them are those frequent changes in the jboss-core
which
I
cannot immediately adopt because of restricted time ... We
really
should have a separation of core and modules such as Peter
Braswell suggested ...
If you need a 'second pair of hands' to try to keep on top of
this type of thing and test updates, I'm happy to do it as I
would like
to
get a better knowledge of JBoss and web services and have (a
small amount of ;-)) spare time. I noticed that some of the
project web page seems a bit out of date - only one of the build
commands
worked
for me and the command to start the test suite needs tweaking.
What's
the process to update it?
I could also take a look at the failing JMX endpoint unit test
if
it
would help, although this is likely to take a bit longer as I
will probably have to wrap my head around much more of Axis and
JBoss
JMX
;-)
Cheers,
Martin
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
Peter Braswell
Utopian Software
[EMAIL PROTECTED]
757.560.8867
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss
RE: AW: [JBoss-dev] RE: AW: Patches to jboss.net
Christoph, 4.5 you have to first utter a jboss-all/testsuite/build because there are some basic testcase classes which do the server deployment for us. Maybe these were the unresolved symbols you were seeing. I added that hint to the jboss.net/docs/Readme ... Yes, this was the reason! I don't know if it's possible to get the dependency explicitly into the build file so that this doesn't catch other users - I will continue to look at this... Martin and Marius, any help in getting the installation and build as user-friendly as possible would be appreciated. If you want to rewrite/add things to the Readme in better and more intelligible English than mine (which is not too hard), please go ahead. I'm very happy to help out. Would it make sense for me to get myself set up as a JBoss committer if I'm going to continue to submit quite a few small patches? Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: AW: [JBoss-dev] RE: AW: Patches to jboss.net
Thanks for the (quite constructive and positive) feedback. I guess that other characters would just go like doesn´t work. baah! Let the dudes alone. That´s the spirit. That is satisfying ... I guess that as long as you contribute small patches and such or take issues from the bug list, it is common (jboss) use to have the Jboss people (in this case Peter and me) operate as filters. Once you went through that a while (and I guess that in our case this while would not be too long as we are seeking volunteers desperately ;-) and you decide to overtake one of the pending tasks, we will get you an rw through the jboss administrators. Please continue and get a part of the community. CGJ -Ursprüngliche Nachricht- Von: Martin Maisey [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 10. April 2002 11:37 An: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: RE: AW: [JBoss-dev] RE: AW: Patches to jboss.net Christoph, 4.5 you have to first utter a jboss-all/testsuite/build because there are some basic testcase classes which do the server deployment for us. Maybe these were the unresolved symbols you were seeing. I added that hint to the jboss.net/docs/Readme ... Yes, this was the reason! I don't know if it's possible to get the dependency explicitly into the build file so that this doesn't catch other users - I will continue to look at this... Martin and Marius, any help in getting the installation and build as user-friendly as possible would be appreciated. If you want to rewrite/add things to the Readme in better and more intelligible English than mine (which is not too hard), please go ahead. I'm very happy to help out. Would it make sense for me to get myself set up as a JBoss committer if I'm going to continue to submit quite a few small patches? Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] RE: AW: Patches to jboss.net
Look into jboss-all/jboss.net/output/lib ... From there, the testsuite deploys them directly to the server Without interfering with the autodeployer! Best, CGJ -Ursprüngliche Nachricht- Von: Marius [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 14:36 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain on anything, but I can't see any .ear or wsr-files generated. Is this right? I though it would create hello.wsr. Martin Maisey wrote: Hi Christoph Thanks for having such a deep look into jboss.net and fixing these open issues. No problem + it wasn't a particularly deep look! Some of them were cause by my stupidity (the techtrader-lib copy operation, I did not commit, simply forgot it), Thought it was probably something like that - I've done the same thing myself many times... some of them are those frequent changes in the jboss-core which I cannot immediately adopt because of restricted time ... We really should have a separation of core and modules such as Peter Braswell suggested ... If you need a 'second pair of hands' to try to keep on top of this type of thing and test updates, I'm happy to do it as I would like to get a better knowledge of JBoss and web services and have (a small amount of ;-)) spare time. I noticed that some of the project web page seems a bit out of date - only one of the build commands worked for me and the command to start the test suite needs tweaking. What's the process to update it? I could also take a look at the failing JMX endpoint unit test if it would help, although this is likely to take a bit longer as I will probably have to wrap my head around much more of Axis and JBoss JMX ;-) Cheers, Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
AW: [JBoss-dev] RE: AW: Patches to jboss.net
excuse me, its jboss-all/jboss.net/testsuite/output/lib ... -Ursprüngliche Nachricht- Von: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 14:40 An: 'Marius' Cc: '[EMAIL PROTECTED]' Betreff: AW: [JBoss-dev] RE: AW: Patches to jboss.net Look into jboss-all/jboss.net/output/lib ... From there, the testsuite deploys them directly to the server Without interfering with the autodeployer! Best, CGJ -Ursprüngliche Nachricht- Von: Marius [mailto:[EMAIL PROTECTED]] Gesendet: Dienstag, 9. April 2002 14:36 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain on anything, but I can't see any .ear or wsr-files generated. Is this right? I though it would create hello.wsr. Martin Maisey wrote: Hi Christoph Thanks for having such a deep look into jboss.net and fixing these open issues. No problem + it wasn't a particularly deep look! Some of them were cause by my stupidity (the techtrader-lib copy operation, I did not commit, simply forgot it), Thought it was probably something like that - I've done the same thing myself many times... some of them are those frequent changes in the jboss-core which I cannot immediately adopt because of restricted time ... We really should have a separation of core and modules such as Peter Braswell suggested ... If you need a 'second pair of hands' to try to keep on top of this type of thing and test updates, I'm happy to do it as I would like to get a better knowledge of JBoss and web services and have (a small amount of ;-)) spare time. I noticed that some of the project web page seems a bit out of date - only one of the build commands worked for me and the command to start the test suite needs tweaking. What's the process to update it? I could also take a look at the failing JMX endpoint unit test if it would help, although this is likely to take a bit longer as I will probably have to wrap my head around much more of Axis and JBoss JMX ;-) Cheers, Martin ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development ___ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: AW: [JBoss-dev] RE: AW: Patches to jboss.net
How do you build to get that files?
This doesn't work:
=
marius@boostcom:~/tmp/jbosscvs/jboss-all/jboss.net/testsuite sh
./build.sh
Searching for build.xml ...
Buildfile:
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/build.xml
BUILD FAILED
Error reading project file
Total time: 0 seconds
===
Do you use the .bat file?
Tried to copy the build.sh from iiop. Then it parses the buildscript,
but fails to compile:
sh ./build.sh
Searching for build.xml ...
Buildfile:
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/build.xml
_buildmagic:init:
_buildmagic:init:buildlog:
configure:
_configure-tools:
_configure-libraries:
_configure-modules:
_configure-tasks:
init:
compile-classes:
[mkdir] Created dir:
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/output/gen-src
[mkdir] Created dir:
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/output/classes
[javac] Compiling 37 source files to
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/output/classes
[javac]
/home/marius/tmp/jbosscvs/jboss-all/jboss.net/testsuite/output/gen-src/samples/addr/AddressBookSOAPBindingImpl.java:10:
duplicate class: samples.addr.AddressBookSOAPBindingImpl
[javac] public class AddressBookSOAPBindingImpl implements
samples.addr.AddressBook {
[javac]^
[javac] 1 error
BUILD FAILED
Thanks
Marius
Jung , Dr. Christoph wrote:
excuse me, its jboss-all/jboss.net/testsuite/output/lib ...
-Ursprüngliche Nachricht-
Von: Jung , Dr. Christoph [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 9. April 2002 14:40
An: 'Marius'
Cc: '[EMAIL PROTECTED]'
Betreff: AW: [JBoss-dev] RE: AW: Patches to jboss.net
Look into jboss-all/jboss.net/output/lib ... From there, the testsuite
deploys them directly to the server Without interfering with the
autodeployer!
Best,
CGJ
-Ursprüngliche Nachricht-
Von: Marius [mailto:[EMAIL PROTECTED]]
Gesendet: Dienstag, 9. April 2002 14:36
An: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]
Betreff: Re: [JBoss-dev] RE: AW: Patches to jboss.net
Tried ./build.sh testsuite -Dmodules=jboss.net. It doesn't complain on
anything, but I can't see any .ear or wsr-files generated. Is this right? I
though it would create hello.wsr.
Martin Maisey wrote:
Hi Christoph
Thanks for having such a deep look into jboss.net and fixing these
open issues.
No problem + it wasn't a particularly deep look!
Some of them were cause by my stupidity (the techtrader-lib copy
operation, I did not commit, simply forgot it),
Thought it was probably something like that - I've done the same thing
myself many times...
some of them are those frequent changes in the jboss-core which I
cannot immediately adopt because of restricted time ... We really
should have a separation of core and modules such as Peter Braswell
suggested ...
If you need a 'second pair of hands' to try to keep on top of this
type of thing and test updates, I'm happy to do it as I would like to
get a better knowledge of JBoss and web services and have (a small
amount of ;-)) spare time. I noticed that some of the project web page
seems a bit out of date - only one of the build commands worked for me
and the command to start the test suite needs tweaking. What's the
process to update it?
I could also take a look at the failing JMX endpoint unit test if it
would help, although this is likely to take a bit longer as I will
probably have to wrap my head around much more of Axis and JBoss JMX
;-)
Cheers,
Martin
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
___
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
