Date   

Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

JerryG
 

Thanks so much for the quick responses!  Great ideas here and I will be thinking more about them over the next few days.  Perhaps I will split into two pages, perhaps more, perhaps we need a -- 


"PanelPro Orientation / Getting Started Guide"

See this topic/message #3458.  Dave Sand raised this idea earlier in this thread (and I believe elsewhere) so I started a new topic on it a few days ago.

I will say that my goal for the page under review (which I will definitely rename to avoid the "save/store" issue) was somewhat more limited, as I said "This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index" - so I will try to stick with that goal rather than incorporating the entire Getting Started Guide into this one page.  As to Bob's point about what should and should not be shown to beginners vs experts, I somewhat agree - although there should be a way to easily make the transition from one to the other.  I'll work on that...

Jerry 

Jerry


Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

Dave Sand
 

Wouter,

Maybe the title should be something like "JMRI Data Management".

To me, save/store have different connotations.  Save implies a document, such as a roster entry, while store implies a complex data structure which includes the relationships between many discrete components, some of which may exist in real life.

Your action driven concept is a good goal.  The challenge is which actions and with what detail.  Here is a simplistic one:
  1. Start PanelPro
  2. Create the connection definition is necessary.
  3. Select a PanelPro tool.
  4. Load the data for the tool if it exists.
  5. Manipulate the tool.
  6. Store/save the data for the tool if it has changed.
  7. Quit PanelPro.

Item 3 is the tough one.  I could come up at least a dozen without much effort.

Another approach is goal based scenarios.  A popular one is running trains automatically.  Is this one scenario or 3+ based on the available approaches.

Dave Sand


----- Original message -----
From: whmvd <vandoornw@...>
Subject: Re: [jmri-developers] The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate
Date: Wednesday, May 27, 2020 4:40 PM

Hi Gerry,

I think this page will be worth its weight in gold in the long run. One small comment to start with: the term 'saving' is very contentious, so to have it in the main header is going to raise some eyebrows. I'd suggest to replace it, at that point at least, by 'Not losing'. Some saving really is saving and is called saving without confusion (roster). Other is called storing and users are supposed to glean from that that something magically different is meant. A major hurdle, and one that I'd like to see go, but that's not going to happen so it needs to be addressed, but most especially is must be avoided as the term for writing your data to disk.

A much bigger point is that a page like this, invaluable as it will prove to be, tells a one-sided story. It tells that story from the capabilituies of the program. Yes, that's needed. But it is *not* the logical jumping-in poin t for relatively new users. In fact, before they've gone three paragraphs in, you'll have lost them. What they need is a *task*  based description. Use cases, if you will. Explaining in use cases what data is touched, how to ensure it's not lost when closing JMRI, and where it ends up. That page will be at least as long, and should contain many cross-references to this new page, which I think is a very good starting point indeed. But: you need two pages. Tech driven as is the one you've made, action-driven which is the missing one.

Please do not take this as criticism. It's not.

Wouter

On Wed, 27 May 2020 at 22:00, JerryG via groups.io <jerryg2003=aol.com@groups.io> wrote:
I've created a page that includes all your comments (thank you!).  It turned out to be a lot more work than I thought it would, at least in part because of my relative unfamiliarity with the OperationsPro aspects of JMRI.  Also, because I found seven (7!) different things a user has to do to ensure that ALL their work is saved (and I think there are a couple more). Perhaps someone can figure out a script to do all these seven things with one button click that can be added to the PanelPro main window?

Please take a look, suggest additions, changes, deletions.  This page is NOT currently linked anywhere because I don't want to put anything out for general consumption with incorrect information and I need your help for that.


The finished version will have the same sidebar as the apps/index.shtml page.  The last column (check mark or blank) will also go away.  Right now, check mark means I'm confident in the information.  There are a fair number of blanks and question marks as yet.

This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index (all three of which need some updating).  All of these should make it easier for new (and old) users to take best advantage of all JMRI's features. And also reduce some of the user group posts for basic info (or at least make it easier to answer them.

Thanks for you help, Jerry





Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

Bob Jacobsen
 

Although experts need this info, and it’s good to have it available, I do not think that beginners should see it _at_ _all_. It shouldn’t be in any kind of step-by-step _introduction_.

We have a simple model that works for 90+% of users. We should just tell people how to _use_ the program without showing all the gears and mechanisms underlying that.

JmriUsers conversations around this have clearly become a cognitive burden due to too much detail. Many people are confused by details that should not be relevant to them.

Example: Person runs JMRI, finds extra panels. That’s _should_ _not_ result in a conversation about XML, file storage, or anything else. Instead the answer should be:

*) Say sorry this happened

*) Solve the problem: What you should do now if to delete the extras (click, pick “Delete”, ..) and then Store again once you have things the way you want them, so they’ll be restored the way you want by Load when you restart the program.

*) Then a bit of teaching: This can happen if you load your panels twice. Each load adds content to JMRI so two loads duplicates things. It’s best to set up JMRI to load your file at start, and that’s it.

No XML, no data structures, just simple “Start, Load, have fun, Store if you’ve made changes you want to keep, Quit, repeat”

Some people may want to become experts. Very few people _want_ to become experts when dealing with a problem, especially a panic-making problem. If the problem happens, get them through the problem, and then say “The simple approach will get you working. Now, if you want to do something more complicated, here are some references for how things work”.

Again, I think having this information available and accurate is great. Linking it from and to advanced pages is great.

I also think simple walkthroughs for new users would be good. But they should be _simple_, showing a reliable way of _working_, and not bring in things like storage formats that are not necessary.

Do you know where Microsoft Word saves its preferences? Do you care? (I understand JMRI isn’t a word processor; the point here is that even if it was, there are things you shouldn’t have to know). Would it help you get started if you had to read a paragraph about that during Word's introductory tutorial?

Bob

On May 27, 2020, at 2:40 PM, whmvd <vandoornw@gmail.com> wrote:

Hi Gerry,

I think this page will be worth its weight in gold in the long run. One small comment to start with: the term 'saving' is very contentious, so to have it in the main header is going to raise some eyebrows. I'd suggest to replace it, at that point at least, by 'Not losing'. Some saving really is saving and is called saving without confusion (roster). Other is called storing and users are supposed to glean from that that something magically different is meant. A major hurdle, and one that I'd like to see go, but that's not going to happen so it needs to be addressed, but most especially is must be avoided as the term for writing your data to disk.

A much bigger point is that a page like this, invaluable as it will prove to be, tells a one-sided story. It tells that story from the capabilituies of the program. Yes, that's needed. But it is *not* the logical jumping-in poin t for relatively new users. In fact, before they've gone three paragraphs in, you'll have lost them. What they need is a *task* based description. Use cases, if you will. Explaining in use cases what data is touched, how to ensure it's not lost when closing JMRI, and where it ends up. That page will be at least as long, and should contain many cross-references to this new page, which I think is a very good starting point indeed. But: you need two pages. Tech driven as is the one you've made, action-driven which is the missing one.

Please do not take this as criticism. It's not.

Wouter

On Wed, 27 May 2020 at 22:00, JerryG via groups.io <jerryg2003=aol.com@groups.io> wrote:
I've created a page that includes all your comments (thank you!). It turned out to be a lot more work than I thought it would, at least in part because of my relative unfamiliarity with the OperationsPro aspects of JMRI. Also, because I found seven (7!) different things a user has to do to ensure that ALL their work is saved (and I think there are a couple more). Perhaps someone can figure out a script to do all these seven things with one button click that can be added to the PanelPro main window?

Please take a look, suggest additions, changes, deletions. This page is NOT currently linked anywhere because I don't want to put anything out for general consumption with incorrect information and I need your help for that.

https://www.jmri.org/help/en/html/apps/SaveWhatHowWhereWhen.shtml

The finished version will have the same sidebar as the apps/index.shtml page. The last column (check mark or blank) will also go away. Right now, check mark means I'm confident in the information. There are a fair number of blanks and question marks as yet.

This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index (all three of which need some updating). All of these should make it easier for new (and old) users to take best advantage of all JMRI's features. And also reduce some of the user group posts for basic info (or at least make it easier to answer them.

Thanks for you help, Jerry
--
Bob Jacobsen
rgj1927@gmail.com


Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

whmvd
 

Hi Gerry,

I think this page will be worth its weight in gold in the long run. One small comment to start with: the term 'saving' is very contentious, so to have it in the main header is going to raise some eyebrows. I'd suggest to replace it, at that point at least, by 'Not losing'. Some saving really is saving and is called saving without confusion (roster). Other is called storing and users are supposed to glean from that that something magically different is meant. A major hurdle, and one that I'd like to see go, but that's not going to happen so it needs to be addressed, but most especially is must be avoided as the term for writing your data to disk.

A much bigger point is that a page like this, invaluable as it will prove to be, tells a one-sided story. It tells that story from the capabilituies of the program. Yes, that's needed. But it is *not* the logical jumping-in poin t for relatively new users. In fact, before they've gone three paragraphs in, you'll have lost them. What they need is a *task*  based description. Use cases, if you will. Explaining in use cases what data is touched, how to ensure it's not lost when closing JMRI, and where it ends up. That page will be at least as long, and should contain many cross-references to this new page, which I think is a very good starting point indeed. But: you need two pages. Tech driven as is the one you've made, action-driven which is the missing one.

Please do not take this as criticism. It's not.

Wouter


On Wed, 27 May 2020 at 22:00, JerryG via groups.io <jerryg2003=aol.com@groups.io> wrote:
I've created a page that includes all your comments (thank you!).  It turned out to be a lot more work than I thought it would, at least in part because of my relative unfamiliarity with the OperationsPro aspects of JMRI.  Also, because I found seven (7!) different things a user has to do to ensure that ALL their work is saved (and I think there are a couple more). Perhaps someone can figure out a script to do all these seven things with one button click that can be added to the PanelPro main window?

Please take a look, suggest additions, changes, deletions.  This page is NOT currently linked anywhere because I don't want to put anything out for general consumption with incorrect information and I need your help for that.

https://www.jmri.org/help/en/html/apps/SaveWhatHowWhereWhen.shtml

The finished version will have the same sidebar as the apps/index.shtml page.  The last column (check mark or blank) will also go away.  Right now, check mark means I'm confident in the information.  There are a fair number of blanks and question marks as yet.

This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index (all three of which need some updating).  All of these should make it easier for new (and old) users to take best advantage of all JMRI's features. And also reduce some of the user group posts for basic info (or at least make it easier to answer them.

Thanks for you help, Jerry


Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

Dan Boudreau
 

Backup panels are stored in a directory called “backupPanels”.  Whenever a user saves a panel using the same panel name, a backup is made with the date and time appended to the panel name.

 

OperationsPro saves the data in 6 files.  Here’s the info:

 

https://www.jmri.org/help/en/package/jmri/jmrit/operations/Operations.shtml#OperationFiles

 

The default is to automatically save the data for the user, see auto save:

 

https://www.jmri.org/help/en/package/jmri/jmrit/operations/Operations.shtml#Settings

 

The default setting also creates a backup each time the OperationsPro is launched, see auto backup using the link above.

 

Dan

 

 

From: JerryG via groups.io
Sent: Wednesday, May 27, 2020 5:00 PM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

 

I've created a page that includes all your comments (thank you!).  It turned out to be a lot more work than I thought it would, at least in part because of my relative unfamiliarity with the OperationsPro aspects of JMRI.  Also, because I found seven (7!) different things a user has to do to ensure that ALL their work is saved (and I think there are a couple more). Perhaps someone can figure out a script to do all these seven things with one button click that can be added to the PanelPro main window?

Please take a look, suggest additions, changes, deletions.  This page is NOT currently linked anywhere because I don't want to put anything out for general consumption with incorrect information and I need your help for that.

https://www.jmri.org/help/en/html/apps/SaveWhatHowWhereWhen.shtml

The finished version will have the same sidebar as the apps/index.shtml page.  The last column (check mark or blank) will also go away.  Right now, check mark means I'm confident in the information.  There are a fair number of blanks and question marks as yet.

This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index (all three of which need some updating).  All of these should make it easier for new (and old) users to take best advantage of all JMRI's features. And also reduce some of the user group posts for basic info (or at least make it easier to answer them.

Thanks for you help, Jerry

 


Re: The Definitive Users' Guide on How to Save Your Work in JMRI #WebHelpUpdate

JerryG
 

I've created a page that includes all your comments (thank you!).  It turned out to be a lot more work than I thought it would, at least in part because of my relative unfamiliarity with the OperationsPro aspects of JMRI.  Also, because I found seven (7!) different things a user has to do to ensure that ALL their work is saved (and I think there are a couple more). Perhaps someone can figure out a script to do all these seven things with one button click that can be added to the PanelPro main window?

Please take a look, suggest additions, changes, deletions.  This page is NOT currently linked anywhere because I don't want to put anything out for general consumption with incorrect information and I need your help for that.

https://www.jmri.org/help/en/html/apps/SaveWhatHowWhereWhen.shtml

The finished version will have the same sidebar as the apps/index.shtml page.  The last column (check mark or blank) will also go away.  Right now, check mark means I'm confident in the information.  There are a fair number of blanks and question marks as yet.

This page is also designed to fit in with other efforts, such as Dave Sand's idea of a Getting Started guide, Bob Jacobsen's page on profile file structure (which I linked to), and the JMRI glossary, TOC, and index (all three of which need some updating).  All of these should make it easier for new (and old) users to take best advantage of all JMRI's features. And also reduce some of the user group posts for basic info (or at least make it easier to answer them.

Thanks for you help, Jerry


After Maven conversion, slight problem with Restarting JMRI under Properties.

wombat_rrnut
 

All:

My configuration:
Windows 7, NetBeans 11.2 (after fresh install of it and JMRI source code).
I selected apps.PanelPro.PanelPro as the main class.

The problem:
After modifying some property(s) that puts up the dialog box "You must restart PanelPro"
and selecting "Restart", the IDE bombs off PanelPro (see below).

?Important? note:
This is a minor annoyance, as restarting JMRI works fine, and the modified configuration
is (more importantly) saved properly from the "Restart".  But I don't know if this points out a potential problem
with something yet in Maven, or a future problem that may bite us?  So I can't say how
important this is......

Text from "bombs off":

Command execution failed.
org.apache.commons.exec.ExecuteException Process exited with an error 100 (Exit value 100)
    at org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java404)
    at org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java166)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java764)
    at org.codehaus.mojo.exec.ExecMojo.executeCommandLine(ExecMojo.java711)
    at org.codehaus.mojo.exec.ExecMojo.execute(ExecMojo.java289)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java134)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java207)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java153)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java145)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java116)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java80)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java51)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java128)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java307)
    at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java193)
    at org.apache.maven.DefaultMaven.execute(DefaultMaven.java106)
    at org.apache.maven.cli.MavenCli.execute(MavenCli.java863)
    at org.apache.maven.cli.MavenCli.doMain(MavenCli.java288)
    at org.apache.maven.cli.MavenCli.main(MavenCli.java199)
    at java.basejdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at java.basejdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java62)
    at java.basejdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java43)
    at java.basejava.lang.reflect.Method.invoke(Method.java564)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java289)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java229)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java415)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java356)
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time 1204 min
Finished at 2020-05-25T175051-0500
Final Memory 19M70M
------------------------------------------------------------------------
Failed to execute goal org.codehaus.mojoexec-maven-plugin1.5.0exec (default-cli) on project jmri Command execution failed. Process exited with an error 100 (Exit value 100) - [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read the following articles
[Help 1] httpcwiki.apache.orgconfluencedisplayMAVENMojoExecutionException


Re: Problem with building 4.19.7 relating to Maven (I guess).

wombat_rrnut
 

Addendum to below:

It turns out that the first time you try to run JMRI, it will ask "Select
Main Class for Execution".
I needed PanelPro, so I selected Apps.PanelPro.PanelPro. You can use the
radio buttons for
"this time only" or "permanent". I'd suggest permanent.....
After a bunch more machinations of downloads and builds (took a little
time), it ran fine.
Subsequent runs no longer did the machinations, and ran fine. Was able to
get my
test "Config Profiles" to startup at least. Seems to work, but I haven't
done any runtime testing
of my Config Profile yet.......

Greg

-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of wombat_rrnut
Sent: Monday, May 25, 2020 10:31 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

All:

Updating to NetBeans 11.2, following the JMRI help page on NetBeans etc.,
doing the <LF> thing, downloading code etc., allowed the build to work first
time.

So though your suggestion on upgrading Ant would probably have been one way
to go, I decided to "catch up with the world" with 11.2, which probably
saved me a lot of headaches now and in the future.

Thank you.

Sincerely
Greg





-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of wombat_rrnut
Sent: Monday, May 25, 2020 8:38 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

Thanks for the suggestion. I think I'll first upgrade to NetBeans 11.2 like
you have.
then perform the rest.

Greg


-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of danielb987
Sent: Monday, May 25, 2020 8:33 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

Please try to update ant.

https://ant.apache.org/bindownload.cgi

I'm not sure how it is in NetBeans 8.2, but in NetBeans 11.2, you go to menu
item Tools / Options and select "Java" and "Ant". There you can see where
ant is located.

Daniel

2020-05-25 15:10 skrev wombat_rrnut:
I haven't had time sine 1/10/2020 to do anything to JMRI (I'm the CTC
guy).

Finally, I needed to update my source to the current set (4.19.7 i
believe)

So I did that. Builds no longer work. Ant->RealClean, Clean and
Build.
I've noticed (and searched fort this answer on this forum) that there
were in the past a LOT of problems with movement from Ant? to Maven?
builds

I looked at the web site for NetBeans new instructions per the
suggestions on this forum, and on my version of NetBeans, there is no
"Resolve Project Problems"
as illustrated. I'm running NetBeans 8.2 So first, do I need to
upgrade NetBeans to what version I assume?
I suspect if I can "Resolve Project Problems", that this problem will
go away?

Output from compile:

cd C:\Users\NetBeansJMRI\Documents\NetBeansProjects\JMRI;
"JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_181" cmd /c
"\"\"C:\\Program Files\\NetBeans 8.2\\java\\maven\\bin\\mvn.bat\"
-DskipTests=true -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
clean install\""
Scanning for projects...

Some problems were encountered while building the effective model for
org.jmri:jmri:jar:4.19.7-SNAPSHOT 'reporting.plugins.plugin.version'
for com.buschmais.jqassistant:jqassistant-maven-plugin is missing. @
line 1142, column 21

It is highly recommended to fix these problems because they threaten
the stability of your build.

For this reason, future Maven versions might no longer support
building such malformed projects.

----------------------------------------------------------------------
--
Building JMRI 4.19.7-SNAPSHOT
----------------------------------------------------------------------
--
Downloading:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plu
gin/2.6/javacc-maven-plugin-2.6.pom

----------------------------------------------------------------------
--
BUILD FAILURE
----------------------------------------------------------------------
--
Total time: 0.840s
Finished at: Mon May 25 08:07:46 CDT 2020 Final Memory: 6M/123M
----------------------------------------------------------------------
-- Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer
artifact org.codehaus.mojo:javacc-maven-plugin:pom:2.6 from/to central
(http://repo.maven.apache.org/maven2): Failed to transfer file:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.
6/javacc-maven-plugin-2.6.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e
switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please
read the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionExcep
tion



Links:
------
[1] https://jmri-developers.groups.io/g/jmri/message/3471
[2] https://groups.io/mt/74455912/1303822
[3] https://jmri-developers.groups.io/g/jmri/post
[4] https://jmri-developers.groups.io/g/jmri/editsub/1303822
[5]
https://jmri-developers.groups.io/g/jmri/leave/defanged


Re: Problem with building 4.19.7 relating to Maven (I guess).

wombat_rrnut
 

All:

Updating to NetBeans 11.2, following the
JMRI help page on NetBeans etc.,
doing the <LF> thing, downloading code etc.,
allowed the build to work first time.

So though your suggestion on upgrading Ant
would probably have been one way to go,
I decided to "catch up with the world" with
11.2, which probably saved me a lot of headaches now and in the future.

Thank you.

Sincerely
Greg

-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of wombat_rrnut
Sent: Monday, May 25, 2020 8:38 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

Thanks for the suggestion. I think I'll first upgrade to NetBeans 11.2 like
you have.
then perform the rest.

Greg


-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of danielb987
Sent: Monday, May 25, 2020 8:33 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

Please try to update ant.

https://ant.apache.org/bindownload.cgi

I'm not sure how it is in NetBeans 8.2, but in NetBeans 11.2, you go to menu
item Tools / Options and select "Java" and "Ant". There you can see where
ant is located.

Daniel

2020-05-25 15:10 skrev wombat_rrnut:
I haven't had time sine 1/10/2020 to do anything to JMRI (I'm the CTC
guy).

Finally, I needed to update my source to the current set (4.19.7 i
believe)

So I did that. Builds no longer work. Ant->RealClean, Clean and
Build.
I've noticed (and searched fort this answer on this forum) that there
were in the past a LOT of problems with movement from Ant? to Maven?
builds

I looked at the web site for NetBeans new instructions per the
suggestions on this forum, and on my version of NetBeans, there is no
"Resolve Project Problems"
as illustrated. I'm running NetBeans 8.2 So first, do I need to
upgrade NetBeans to what version I assume?
I suspect if I can "Resolve Project Problems", that this problem will
go away?

Output from compile:

cd C:\Users\NetBeansJMRI\Documents\NetBeansProjects\JMRI;
"JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_181" cmd /c
"\"\"C:\\Program Files\\NetBeans 8.2\\java\\maven\\bin\\mvn.bat\"
-DskipTests=true -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
clean install\""
Scanning for projects...

Some problems were encountered while building the effective model for
org.jmri:jmri:jar:4.19.7-SNAPSHOT 'reporting.plugins.plugin.version'
for com.buschmais.jqassistant:jqassistant-maven-plugin is missing. @
line 1142, column 21

It is highly recommended to fix these problems because they threaten
the stability of your build.

For this reason, future Maven versions might no longer support
building such malformed projects.

----------------------------------------------------------------------
--
Building JMRI 4.19.7-SNAPSHOT
----------------------------------------------------------------------
--
Downloading:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plu
gin/2.6/javacc-maven-plugin-2.6.pom

----------------------------------------------------------------------
--
BUILD FAILURE
----------------------------------------------------------------------
--
Total time: 0.840s
Finished at: Mon May 25 08:07:46 CDT 2020 Final Memory: 6M/123M
----------------------------------------------------------------------
-- Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer
artifact org.codehaus.mojo:javacc-maven-plugin:pom:2.6 from/to central
(http://repo.maven.apache.org/maven2): Failed to transfer file:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.
6/javacc-maven-plugin-2.6.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e
switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please
read the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionExcep
tion



Links:
------
[1] https://jmri-developers.groups.io/g/jmri/message/3471
[2] https://groups.io/mt/74455912/1303822
[3] https://jmri-developers.groups.io/g/jmri/post
[4] https://jmri-developers.groups.io/g/jmri/editsub/1303822
[5]
https://jmri-developers.groups.io/g/jmri/leave/defanged


Re: Problem with building 4.19.7 relating to Maven (I guess).

wombat_rrnut
 

Thanks for the suggestion. I think I'll first
upgrade to NetBeans 11.2 like you have.
then perform the rest.

Greg

-----Original Message-----
From: jmri@jmri-developers.groups.io [mailto:jmri@jmri-developers.groups.io]
On Behalf Of danielb987
Sent: Monday, May 25, 2020 8:33 AM
To: jmri@jmri-developers.groups.io
Subject: Re: [jmri-developers] Problem with building 4.19.7 relating to
Maven (I guess).

Please try to update ant.

https://ant.apache.org/bindownload.cgi

I'm not sure how it is in NetBeans 8.2, but in NetBeans 11.2, you go to menu
item Tools / Options and select "Java" and "Ant". There you can see where
ant is located.

Daniel

2020-05-25 15:10 skrev wombat_rrnut:
I haven't had time sine 1/10/2020 to do anything to JMRI (I'm the CTC
guy).

Finally, I needed to update my source to the current set (4.19.7 i
believe)

So I did that. Builds no longer work. Ant->RealClean, Clean and
Build.
I've noticed (and searched fort this answer on this forum) that there
were in the past a LOT of problems with movement from Ant? to Maven?
builds

I looked at the web site for NetBeans new instructions per the
suggestions on this forum, and on my version of NetBeans, there is no
"Resolve Project Problems"
as illustrated. I'm running NetBeans 8.2 So first, do I need to
upgrade NetBeans to what version I assume?
I suspect if I can "Resolve Project Problems", that this problem will
go away?

Output from compile:

cd C:\Users\NetBeansJMRI\Documents\NetBeansProjects\JMRI;
"JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_181" cmd /c
"\"\"C:\\Program Files\\NetBeans 8.2\\java\\maven\\bin\\mvn.bat\"
-DskipTests=true -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
clean install\""
Scanning for projects...

Some problems were encountered while building the effective model for
org.jmri:jmri:jar:4.19.7-SNAPSHOT 'reporting.plugins.plugin.version'
for com.buschmais.jqassistant:jqassistant-maven-plugin is missing. @
line 1142, column 21

It is highly recommended to fix these problems because they threaten
the stability of your build.

For this reason, future Maven versions might no longer support
building such malformed projects.

----------------------------------------------------------------------
--
Building JMRI 4.19.7-SNAPSHOT
----------------------------------------------------------------------
--
Downloading:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plu
gin/2.6/javacc-maven-plugin-2.6.pom

----------------------------------------------------------------------
--
BUILD FAILURE
----------------------------------------------------------------------
--
Total time: 0.840s
Finished at: Mon May 25 08:07:46 CDT 2020 Final Memory: 6M/123M
----------------------------------------------------------------------
-- Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer
artifact org.codehaus.mojo:javacc-maven-plugin:pom:2.6 from/to central
(http://repo.maven.apache.org/maven2): Failed to transfer file:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.
6/javacc-maven-plugin-2.6.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e
switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please
read the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionExcep
tion



Links:
------
[1] https://jmri-developers.groups.io/g/jmri/message/3471
[2] https://groups.io/mt/74455912/1303822
[3] https://jmri-developers.groups.io/g/jmri/post
[4] https://jmri-developers.groups.io/g/jmri/editsub/1303822
[5]
https://jmri-developers.groups.io/g/jmri/leave/defanged


Re: Problem with building 4.19.7 relating to Maven (I guess).

danielb987
 

Please try to update ant.

https://ant.apache.org/bindownload.cgi

I'm not sure how it is in NetBeans 8.2, but in NetBeans 11.2, you go to menu item Tools / Options and select "Java" and "Ant". There you can see where ant is located.

Daniel

2020-05-25 15:10 skrev wombat_rrnut:

I haven't had time sine 1/10/2020 to do anything to JMRI (I'm the CTC
guy).
Finally, I needed to update my source to the current set (4.19.7 i
believe)
So I did that. Builds no longer work. Ant->RealClean, Clean and
Build.
I've noticed (and searched fort this answer on this forum) that there
were
in the past a LOT of problems with movement from Ant? to Maven? builds
I looked at the web site for NetBeans new instructions per the
suggestions
on this forum, and on my version of NetBeans, there is no "Resolve
Project Problems"
as illustrated. I'm running NetBeans 8.2
So first, do I need to upgrade NetBeans to what version I assume?
I suspect if I can "Resolve Project Problems", that this problem will
go away?
Output from compile:
cd C:\Users\NetBeansJMRI\Documents\NetBeansProjects\JMRI;
"JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_181" cmd /c
"\"\"C:\\Program Files\\NetBeans 8.2\\java\\maven\\bin\\mvn.bat\"
-DskipTests=true -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans
8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8
clean install\""
Scanning for projects...
Some problems were encountered while building the effective model for
org.jmri:jmri:jar:4.19.7-SNAPSHOT
'reporting.plugins.plugin.version' for
com.buschmais.jqassistant:jqassistant-maven-plugin is missing. @ line
1142, column 21
It is highly recommended to fix these problems because they threaten
the stability of your build.
For this reason, future Maven versions might no longer support
building such malformed projects.
------------------------------------------------------------------------
Building JMRI 4.19.7-SNAPSHOT
------------------------------------------------------------------------
Downloading:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.6/javacc-maven-plugin-2.6.pom
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 0.840s
Finished at: Mon May 25 08:07:46 CDT 2020
Final Memory: 6M/123M
------------------------------------------------------------------------
Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its
dependencies could not be resolved: Failed to read artifact descriptor
for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer
artifact org.codehaus.mojo:javacc-maven-plugin:pom:2.6 from/to central
(http://repo.maven.apache.org/maven2): Failed to transfer file:
http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.6/javacc-maven-plugin-2.6.pom.
Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]
To see the full stack trace of the errors, re-run Maven with the -e
switch.
Re-run Maven using the -X switch to enable full debug logging.
For more information about the errors and possible solutions, please
read the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
Links:
------
[1] https://jmri-developers.groups.io/g/jmri/message/3471
[2] https://groups.io/mt/74455912/1303822
[3] https://jmri-developers.groups.io/g/jmri/post
[4] https://jmri-developers.groups.io/g/jmri/editsub/1303822
[5] https://jmri-developers.groups.io/g/jmri/leave/defanged


Problem with building 4.19.7 relating to Maven (I guess).

wombat_rrnut
 

I haven't had time sine 1/10/2020 to do anything to JMRI (I'm the CTC guy).

Finally, I needed to update my source to the current set (4.19.7 i believe)

So I did that.  Builds no longer work.  Ant->RealClean, Clean and Build.
I've noticed (and searched fort this answer on this forum) that there were
in the past a LOT of problems with movement from Ant? to Maven? builds

I looked at the web site for NetBeans new instructions per the suggestions
on this forum, and on my version of NetBeans, there is no "Resolve Project Problems"
as illustrated.  I'm running NetBeans 8.2
So first, do I need to upgrade NetBeans to what version I assume?
I suspect if I can "Resolve Project Problems", that this problem will go away?

Output from compile:

cd C:\Users\NetBeansJMRI\Documents\NetBeansProjects\JMRI; "JAVA_HOME=C:\\Program Files\\Java\\jdk1.8.0_181" cmd /c "\"\"C:\\Program Files\\NetBeans 8.2\\java\\maven\\bin\\mvn.bat\" -DskipTests=true -Dmaven.ext.class.path=\"C:\\Program Files\\NetBeans 8.2\\java\\maven-nblib\\netbeans-eventspy.jar\" -Dfile.encoding=UTF-8 clean install\""
Scanning for projects...

Some problems were encountered while building the effective model for org.jmri:jmri:jar:4.19.7-SNAPSHOT
'reporting.plugins.plugin.version' for com.buschmais.jqassistant:jqassistant-maven-plugin is missing. @ line 1142, column 21

It is highly recommended to fix these problems because they threaten the stability of your build.

For this reason, future Maven versions might no longer support building such malformed projects.

                                                                       
------------------------------------------------------------------------
Building JMRI 4.19.7-SNAPSHOT
------------------------------------------------------------------------
Downloading: http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.6/javacc-maven-plugin-2.6.pom

------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 0.840s
Finished at: Mon May 25 08:07:46 CDT 2020
Final Memory: 6M/123M
------------------------------------------------------------------------
Plugin org.codehaus.mojo:javacc-maven-plugin:2.6 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.codehaus.mojo:javacc-maven-plugin:jar:2.6: Could not transfer artifact org.codehaus.mojo:javacc-maven-plugin:pom:2.6 from/to central (http://repo.maven.apache.org/maven2): Failed to transfer file: http://repo.maven.apache.org/maven2/org/codehaus/mojo/javacc-maven-plugin/2.6/javacc-maven-plugin-2.6.pom. Return code is: 501 , ReasonPhrase:HTTPS Required. -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException


Re: club logo vs. JMRI trademarks…

Petr Šídlo
 

I use club logo.
When I start PanelPro logo is displayed OK.
When I start DecoderPro first and from menu PanelPro there is origin PanelPro Logo.

--
Petr Šídlo
Czech Republic
https://sites.google.com/site/sidloweb/


Short-term release sequence

Bob Jacobsen
 

This note is about the release sequence leading up to the next production release. I’ll (try to) write another note about beyond the next production release later today.

Our next production release is nominally named 4.20 and scheduled for before July 10th.

Our normal sequence is then a test release 4.19.7 around now that’s the last from the HEAD of master. I’d like to build this next weekend, ideally Saturday May 30.

After that, the criteria for including changes great stricter and stricter.

A) Bug fixes and _small_ changes will be included in a 4.19.8 test release around June 15
B) After that, only very specific fixes for identified regressions will be included; if there are any, additional test releases will be made as needed.

It’s important that merging the changes in (A) and (B) do not bring in other things. That’s quite trivial to do: When you start work on of those

git checkout v4.19.7
git checkout -b branchForMyFeature

so that you’re making changes based on 4.19.7, not on top of changes that took place after that. (Earlier, like v4.19.6 or master before v.4.19.7 is cut, is also fine) That’s all it takes.

But essentially every time, we get a contribution that’s not like this, because it comes from master later and pulls in other changes. What to do? Last time I came up with a branching scheme that would let people continue to work off master. It too required people to think about where they branched their work, and wasn’t really a success.

So this time, I propose:

i) Development will continue via master as usual so it doesn’t get too far behind
ii) Changes to be included in v4.20 will be merged iff they’re branched from v4.19.7 or before.
iii) Changes for 4.20 branched too late will have to be moved (via various git operations) to a from-v4.19.7 branch before being merged.

Thoughts?

Bob
--
Bob Jacobsen
rgj1927@gmail.com


Re: Format of try ... catch blocks

George Warner
 

This also started happening to me after I updated(¿) to NetB 11.3.
The checkboxes weren't checked but reformatting put catches on new lines.
I finally had to turn off "reformat on save" or otherwise I'd have to post edit externally (TGF BBEdit!) and restore all the catch block formatting.
So thanks for finding/fixing this! ;-)


Re: Format of try ... catch blocks

Dave Heap
 


Thanks Daniel.

Dave

On 24 May 2020, at 4:50 PM, Bob Jacobsen <rgj1927@...> wrote:

I really hope that we can find the cause of this catch-line reformatting and kill it. K&R formatting was good enough for K&R, and I’ve become really accustomed to reading it.


Re: Format of try ... catch blocks

Dave Heap
 

Bob,

On 24 May 2020, at 6:10 PM, Dave Heap <dgheap@...> wrote:


It’s in every standards doc I know of. I think perhaps somebody misinterpreted the page you referenced, which mentioned but doesn’t show catch blocks.  The next page ( https://docs.oracle.com/javase/tutorial/essential/exceptions/catch.html) does show them, and they’re in our old “Egyptian format”.

I copied and pasted into my email from what I was sure was that page. Weird.

I wasn't imagining it. It was the previous page:

Dave


Re: Format of try ... catch blocks

Dave Heap
 

Bob,

On 24 May 2020, at 4:50 PM, Bob Jacobsen <rgj1927@...> wrote:

I really hope that we can find the cause of this catch-line reformatting and kill it. K&R formatting was good enough for K&R, and I’ve become really accustomed to reading it.   

Agreed.


It’s in every standards doc I know of. I think perhaps somebody misinterpreted the page you referenced, which mentioned but doesn’t show catch blocks.  The next page ( https://docs.oracle.com/javase/tutorial/essential/exceptions/catch.html) does show them, and they’re in our old “Egyptian format”.

I copied and pasted into my email from what I was sure was that page. Weird.

Could you also check the project properties?  Right-click on the JMRI project, select Properties, then Formatting, then alignment, then the catch checkbox?

I'll look later.

Dave


Re: Format of try ... catch blocks

danielb987
 

Test PR #8578. I think that will solve it.

https://github.com/JMRI/JMRI/pull/8578

Daniel

2020-05-24 08:50 skrev Bob Jacobsen:

I really hope that we can find the cause of this catch-line
reformatting and kill it. K&R formatting was good enough for K&R, and
I’ve become really accustomed to reading it.
It’s in every standards doc I know of. I think perhaps somebody
misinterpreted the page you referenced, which mentioned but doesn’t
show catch blocks. The next page (
https://docs.oracle.com/javase/tutorial/essential/exceptions/catch.html)
does show them, and they’re in our old “Egyptian format”.
Could you also check the project properties? Right-click on the JMRI
project, select Properties, then Formatting, then alignment, then the
catch checkbox?
Bob

On May 23, 2020, at 10:57 PM, Dave Heap <dgheap@gmail.com> wrote:
All,
On 24 May 2020, at 3:37 PM, danielb987 <db123@bergqvist.se> wrote:

There you have a checkbox "catch". Is that checkbox checked?
No, it's not checked. Something seems to be overriding that setting.
I'm suspecting:
<https://github.com/JMRI/JMRI/pull/8544/commits/70262a42f5368cb74f510df25a143461a134d10d>
merged since yesterday (my time zone).
What policy do we want?
I'm also suspecting this for suddenly aligning descriptions of
@param in JavaDoc . I must say I like that one. Again, what policy
do we want?
I'll hold off on a PR I was about to create...
Dave
--
Bob Jacobsen
rgj1927@gmail.com
Links:
------
[1] https://jmri-developers.groups.io/g/jmri/message/3463
[2] https://groups.io/mt/74432823/1303822
[3] https://jmri-developers.groups.io/g/jmri/post
[4] https://jmri-developers.groups.io/g/jmri/editsub/1303822
[5] https://jmri-developers.groups.io/g/jmri/leave/defanged


Re: Format of try ... catch blocks

Bob Jacobsen
 

I really hope that we can find the cause of this catch-line reformatting and kill it. K&R formatting was good enough for K&R, and I’ve become really accustomed to reading it.   

It’s in every standards doc I know of. I think perhaps somebody misinterpreted the page you referenced, which mentioned but doesn’t show catch blocks.  The next page ( https://docs.oracle.com/javase/tutorial/essential/exceptions/catch.html) does show them, and they’re in our old “Egyptian format”.

Could you also check the project properties?  Right-click on the JMRI project, select Properties, then Formatting, then alignment, then the catch checkbox?


Bob


On May 23, 2020, at 10:57 PM, Dave Heap <dgheap@...> wrote:

All,
On 24 May 2020, at 3:37 PM, danielb987 <db123@...> wrote:

There you have a checkbox "catch". Is that checkbox checked?

No, it's not checked. Something seems to be overriding that setting.

I'm suspecting:
<https://github.com/JMRI/JMRI/pull/8544/commits/70262a42f5368cb74f510df25a143461a134d10d>
merged since yesterday (my time zone).

What policy do we want?

I'm also suspecting this for suddenly aligning descriptions of @param in JavaDoc . I must say I like that one. Again, what policy do we want?

I'll hold off on a PR I was about to create...

Dave

--
Bob Jacobsen
rgj1927@...



1661 - 1680 of 5136