Comments (19)
Hi Brian,
I'm very puzzled. The last person who had this kind of behavior solved it by renaming the JAR file, replacing the version which was 4 digits (x.y.z.t) to a 3 digit number (x.y.z).
I still do not understand as it was just in the file name (the internal version number was not changed) but we came to the conclusion that the version should always stay with 3 digits.
In your case, the version number is in 3 digits form so I haven't have a clue about what can happen.
What I can suggest is for you to try older version, just to know if you experience the same behavior with all of them, or only the last one.
Then I can try to find other ways to compile the JAR file, or try to change the Java version used to generate the JAR file, even if it should not have any impact ... but who knows ...
My apologies, I cannot provide a best answer, as I do not own a MAC to test and Apple do not allow to create a VM running MAC OS.
Best regards
Hervé
from specialization-plugin.
Thanks, Hervé. Yeah, I noticed some others had similar problems but I missed that a file rename had been a fix, but it sounds like you already covered for that condition. I had considered trying a previous version, I will give it a go. It's a fantastic plugin.
from specialization-plugin.
I'm trying to find a colleague that have got a MAC to conduct dome testing but until then, I won't be able to be really helpful I'm afraid.
Please let me know if you find anything that can give me a clue ...
from specialization-plugin.
It may be something local to my machine but I have no idea what. Rolling back to an oder version of the plugin didn't make any difference, and rolling the app back to 4.2 didn't seem to help, either. I suppose I will just have to live without this plugin for the time being.
from specialization-plugin.
Hey Brian,
But I never used one so I'm a bit lost ... could you please help me ?
How do you expand the Archi file to put the JAR file in the plugins folder ?
Once I know how to test my plugins on MAC, I'll be able to investigate ...
Thanks
Hervé
from specialization-plugin.
Usually I do it from the command line, but the other option is to right click over the executable and choose "Show Package Contents".
from specialization-plugin.
Thanks.
I reproduced your issue. When I try to change a label, it is not changed. This means that it does not come from your MAC but there is something that MAC does not like in my plugin.
I cannot guarantee that I will find why it doesn't work, but at least I can now do some testing.
I'll let you know ASAP.
Best regards
Hervé
from specialization-plugin.
Hi,
I still do not understand why the JAR file does not work, but I installed Eclipse on my MAC and generated a JAR file that works.
It will do the trick until I understand what happens.
Please tell me if it works for you.
Best regards
Hervé
from specialization-plugin.
The updated plugin is indeed working, thanks! So you think that there might be a build inconsistency between Eclipse on Windows and Eclipse on MacOS? All you did was rebuild on MacOS?
from specialization-plugin.
Yes, I installed Eclipse, the sources of Archi and the sources of my plugin and generated the JAR file from MAC.
The JAR size is the same but the content is not 100% identical so I need to understand whare are these differences and may be I'll be ableto generate a JAR file that works for both systems :-)
from specialization-plugin.
I close this issue as a workaround has been found. I hope I'll understand soon what happens.
from specialization-plugin.
Sorry but the ...1.0.10_for_mac.jar
does not seem to fix the issue for me, and when I check for update it keeps offering me to download it. (It originally complained that I had both but was still using 1.0.10
so I deleted the original from the plugin directory so only the 1.0.10_for_mac.jar
exists but still not rendering.
from specialization-plugin.
Unfortunately, It works for me anf for other people ... As MAC is a very specific system and as I do not know well this system, I won't be ableto help you more on this subject I'm afraid.
Regarding the update procedure, it is not aware that there is a specific MAC version ... so until this MAC stuff is not solved definitively, you won't be able to use it.
Best regards
Hervé
from specialization-plugin.
Hi Hervé,
Sorry to disturb again with that old thread but I have some kind of similar issue and this time not only with my Mac. Actually I've got 3 computers on my desk with 3 different OS (macOS, Windows and Linux Ubuntu).
On Windows it works pretty well (and it is really what I am looking for :-) but on both other OS it doesn't render at all. So I guess the issue is not macOS but more Unix like systems.
The shame for me is that I am supposed to do modelling only on the Linux platform.
Did you face already that issue on a Linux platform?
Best regards
Gilles
from specialization-plugin.
Hi Gilles,
I know my plugins can have strange behaviour on MacOS, but I regularly check them on Linux and never experienced any issue. I just tried on a Ubuntu machine and it works well.
_
Linux ubuntu16 4.15.0-29-generic #31~16.04.1-Ubuntu SMP Wed Jul 18 08:54:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Could you please provide me with more information about your issue on Ubuntu ?
Best regards
Hervé
from specialization-plugin.
Hi Hervé and thanks for your fast reply.
Here is
Linux version: 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Java version: Java(TM) SE Runtime Environment (build 1.8.0_77-b03)
Archi version: 4.3.1 build 201901281101
Specialization plugin: 1.0.10
I've just activated the Logger (after reload Archi) and while setting &a new Icon and new Label on a technology function I've got that message on the log:
2019-02-12 17:09:56 DEBUG 525:PreferencePage - Logger initialised.
2019-02-12 17:10:47 ERROR 1051:SpecializationPlugin - DiagramModelArchimateObject:"Technology Function" is not in a view not in a folder.
Which is a strange message since that element is clearly in a View and in the folder "Technology & Physical"
Hope it will helps you ;-)
Anyway, this plugin looks great otherwise
Bon courage
Gilles
from specialization-plugin.
I do not understand why you've got this error message ... So what I suggest is that you send me your phone number by mail and I'll call you tomorrow morning to conduct more tests.
Best regards
Hervé
from specialization-plugin.
I had to rename the plugin from org.archicontribs.specialization_v1.0.10.jar to org.archicontribs.specialization_1.0.10.jar (remove the "v" from the version sub-string) and that fixed the problem. I noticed this because when I build the plugin on my Eclipse Environment, the name of the created jar file was "org.archicontribs.specialization_1.0.10.jar" and it worked.
Then I downloaded again the plugin, renamed and installed and this time it worked!
from specialization-plugin.
Hi Alberto,
Are you on MacOS as well ?
Best regards
Hervé
from specialization-plugin.
Related Issues (20)
- v2.0.0: Feature proposal: Selectable default image positions and sizes HOT 2
- Wiki page doesn't work HOT 1
- v.2.0.0 Alpha 1 / Archi 4.5 Beta 1 error HOT 5
- Image folder settings in preferences not fully visibible HOT 12
- GDI objects are not released and reached the limit , archi freezes HOT 3
- 2.0.0.alpha doesn't work with Archi 4.5.1 HOT 10
- Setting specialization attributes using jArchi script HOT 6
- Use concept type for label HOT 2
- Preferences does not render as expected in 2.0.0.alpha2 HOT 7
- Error message when adding a (new or existing) application component to a view HOT 7
- Compatibility with report feature ? HOT 6
- The Archi's Preference Page of the Specialization Plugin is not complete with Archi 4.7.1 (on windows) HOT 2
- Version 1.x of plugin needs to be compiled against Archi 4.7.x to address API changes HOT 3
- Support for more element types HOT 6
- Drill-down Elements navigation on HTML-reports HOT 1
- Inconsistency in plugin installation HOT 6
- Deletion or replace of images from icon pallete HOT 1
- Ability to have the archimate icon along with a new icon HOT 3
- Doesn't work with Archi 4.8.1 HOT 3
- Error when create a new object HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from specialization-plugin.