Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maven project addition #8

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

oehm-smith
Copy link

I've added a Maven project so that:

  1. Other IDEs can be used to develop jstock
  2. One is able to easily compile and produce artefacts from the command-line.
  3. The use of Maven as a dependency management tool removes the need to store dependencies within the repository (ie. the libs/ directory). Storing in the libs/ directory becomes an issue when multiple versions of those libs are used since each one becomes version controlled. If this fork is pulled into JStock I recommend that all the dependencies should all be done in this Maven way.

The dependencies such as blobsallad should also be setup as Maven projects so they can be:

  1. Submitted to a global maven repository to be used as external dependencies. That is, developers of JStock only see a maven coordinate for blobsallad (etc) and these get pulled down from somewhere like https://repo.maven.com.
  2. To facilitate local development of blobsallad (etc), they can be installed to the local repository and the jstock under development will pull in this version.

This fork works in all aspects except for some peripheral ones as mentioned in the README.md (discussed as TODOs). The README.md files contains usage instructions.

Please feel free to add any comments or requests for modifications here. I feel this is a valuable addition to the fantastic jstock project and would like to see it adopted.

… other IDEs can be used to develop the project. The README has been populated with instructions for Netbeans, Maven command line or importing and running from Eclipse.
@yccheok
Copy link
Owner

yccheok commented Mar 11, 2014

Thank you for your effort of attempting to provide alternative development environment for JStock.

However, we prefer to stick with NetBeans with reason : All our UI code, is auto-generated by NetBeans mostly. Using other IDEs, will break such auto-generated code mechanism. For instance, NetBeans will place

// <editor-fold defaultstate="collapsed" desc="Generated Code">  
// </editor-fold> 

Within the generated code block. This prohibits developers from modified the auto-generated code. If I were promoting other development environment, this introduces chance for breaking NetBeans auto-generated code mechanism.

What I will be very appreciated, is 1 page introduction, on how to check-out, compile and run JStock using NetBeans

Something looks similar to an out-dated 1 page introduction : http://sourceforge.net/apps/mediawiki/jstock/index.php?title=Hacking#How_To_Check_Out_JStock_Source_Code_to_Compile_and_Run.3F

Thanks. Please let me know if I misunderstand your intention.

@oehm-smith
Copy link
Author

Hi Yan Cheng (sorry for my ignorance - do I call you this?),

I can do the Netbeans doco as requested.

Yes, Netbeans has Matisse for GUI design. I understand. Do you think
that since the GUI component of jStock is just one part of many that
mandating that Netbeans must be used is somewhat limiting? The dev
documentation could state that GUI work can only be done through
Netbeans. Netbeans can open Maven projects as if they are native.

What do you think?

The idea i've had for a while (before coming across JStock) was to have
the business logic of something like JStock run as a service separate to
the client UI. RESTful web services can be used to expose the services
and UIs can be built from these. Multiple clients would then become
possible - Web clients (Spring, JSF, JSP if you wish, Javascript /
HTML); GUI applications (Swing, JavaFx, SWT); Smart phones. I haven't
looked but I expect your Android App is completely stand-alone with code
duplicated.

If the clients are split off from the server product then the Swing
client can be a Netbeans project. Similarly any SWT client can be an
Eclipse project. Everything else would be IDE agnostic.

What do you think about the client/server architecture idea? And as a
lead up to that, adopting my Maven patch? I'll update the doco with
your requested changes and include a part saying "to modify the GUI the
project must be opened in Netbeans"?

Cheers,

Brooke

On 12/03/14 1:12 AM, Yan Cheng CHEOK wrote:

Thank you for your effort of attempting to provide alternative
development environment for JStock.

However, we prefer to stick with NetBeans with reason : All our UI
code, is auto-generated by NetBeans mostly. Using other IDEs, will
break such auto-generated code mechanism. For instance, NetBeans will
place

|//
//
|

Within the generated code block. This prohibits developers from
modified the auto-generated code. If I were promoting other
development environment, this introduces chance for breaking NetBeans
auto-generated code mechanism.

** What I will be very appreciated, is 1 page introduction, on how to
check-out, compile and run JStock using NetBeans **

Thanks. Please let me know if I misunderstand your intention.


Reply to this email directly or view it on GitHub
#8 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants