Results 1 to 17 of 17
  1. #1
    dazz is offline Member
    Join Date
    Apr 2017
    Posts
    27
    Rep Power
    0

    Default How to fix PluginincompatibleException ???

    Hi

    I am trying to build a project from Maven Central in Netbeans. In theory that should be simple but it isn't for me. I seem to be stuck in version hell and I can't find my way out.

    The saga of trying to do this is detailed here

    The specific question I have is here. Cross posting like this may break etiquette but this forum is probably a better place to get answers and I should have posted here in the first place.

    Any help would be much appreciated.
    Last edited by dazz; 07-05-2017 at 01:00 AM.

  2. #2
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    Have you tried downgrading?
    That would be my first step.

    It is quite possible something in that plugin would be broken by some change in Maven made post 3.1.1.

    After all, the project you are trying to build worked with that version of the plugin and, presumably, that version of Maven.
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  3. #3
    benji2505 is offline Senior Member
    Join Date
    Sep 2014
    Location
    MA, USA
    Posts
    388
    Rep Power
    4

    Default Re: How to fix PluginincompatibleException ???

    quick question: is XBee-API a plugin or a dependency you want to add?
    Last edited by benji2505; 07-05-2017 at 03:43 PM.

  4. #4
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    Does Maven handle it's own dependencies, though?
    That is, if a plugin only works with an older Maven does Maven downgrade itself?
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  5. #5
    benji2505 is offline Senior Member
    Join Date
    Sep 2014
    Location
    MA, USA
    Posts
    388
    Rep Power
    4

    Default Re: How to fix PluginincompatibleException ???

    Quote Originally Posted by Tolls View Post
    Does Maven handle it's own dependencies, though?
    That is, if a plugin only works with an older Maven does Maven downgrade itself?
    Yes, good call. I confused plugin with dependencies. That brings me to the question whether XBee-API is really a Maven plugin.

  6. #6
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    It's not XBee, it's the git-commit-id-plugin that the XBee POM uses for something or other.
    That seems to be tagged with a (specific?) Maven version?
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  7. #7
    benji2505 is offline Senior Member
    Join Date
    Sep 2014
    Location
    MA, USA
    Posts
    388
    Rep Power
    4

    Default Re: How to fix PluginincompatibleException ???

    The version of XBee-Api the OP is using is outdated, OP is using 0.9.x and the most recent version is 1.2.x.

    I quickly glanced over the POM file and I could not find that plugin/dependency anymore.

    Not sure whether that helps, though. Maybe OP wants to build on a basis of the old version. I would then start in the git-commit-id-plugin pom file.

  8. #8
    dazz is offline Member
    Join Date
    Apr 2017
    Posts
    27
    Rep Power
    0

    Default Re: How to fix PluginincompatibleException ???

    Hi
    Thank you for all of your replies.

    If I need to downgrade Maven to run XBee-API, that would be bad engineering because it is highly likely that I would hit problems with other dependencies/plugins that were written for later versions of Maven. I don't want to go there.
    Part of the problem here seems to be the "new" requirement by Maven for version numbers to be specified in the POM. There may be large numbers of older POMs in Maven Central that don't have version numbers in them. I believe that users should have the reasonable expectation that software downloaded from any repository should at least build. If it won't, then it should come with a warning. It should be possible for code within Maven Central to identify crippled POMs.

    XBee-API is a set of classes that I want to use in my project.

    It appears that Maven has no obvious method of handling version problems apart from spitting out error messages. The problem here does not seem to be a direct Maven one. It looks like an aged POM with dependencies that no longer builds with the latest version of Maven. That in itself is a problem because it means there might be a lot of POMs in Maven Central that are no longer usable.

    The XBee Java library is written by Digi and although it is newer but it is far less capable.

    As far as I can tell, building from Maven Central doesn't give me the ability to access/change the source code. If that is the case, then my plan is to revert to the earlier version of XBee-API from Github and modify it to run with I2C. I have successfully downloaded and compiled this older version.

    As a Java noobie, I like Java but I am finding that the stuff related to its use like Maven are a nightmare. So far I have spent most of my time trying to sort out issues like that above instead of writing code. When it works its great, but when it doesn't, it is very time consuming to find the solution. In this case, I have hit a dead end. Very frustrating.

  9. #9
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    But that's the same with anything, though.
    You're trying to build an out of date API, using a plugin that seems to require an earlier version of Maven.
    That is always going to require a degree of jumping through hoops, whatever language or framework you use if it is in any way open.
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  10. #10
    dazz is offline Member
    Join Date
    Apr 2017
    Posts
    27
    Rep Power
    0

    Default Re: How to fix PluginincompatibleException ???

    Hi
    The difference is that the older version of XBee-API builds and the new one doesn't. I can't fix the problem with the new one so I'll use the old one which has the advantage that it comes with the source code. If I was just importing the XBee-API and writing my own code, it would be OK to revert to an older Maven, but that is not the case. Reverting to an old Maven ver is most likely to cause me grief further down track.

    This isn't the first problem I have had with Maven after only a few weeks of exposure. I haven't experienced this problem with Ubuntu or Perl repositories after years of use, which is not to say they are perfect.

  11. #11
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    But do you often have to build old APIs with either of those other repos?

    You are currently attempting to use an API that hasn't even made it to v1 ... if there are issues then I would argue that that is a start point.
    The API is already built, so your issue is (presumably) that you want to change it and build it yourself.
    This almost always hits issues with how the dev decides to set up their own environment.
    I don't see why that is a surprise.

    Of course, those issues are exacerbated by being a noob at the whole thing.
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  12. #12
    dazz is offline Member
    Join Date
    Apr 2017
    Posts
    27
    Rep Power
    0

    Default Re: How to fix PluginincompatibleException ???

    Hi
    Being a Java noob has been an exacerbating experience. Perhaps over 35 years programming in a range of other languages has tainted my expectations.

    A sub 1 version that I can build and customise the source code has to be better than a plus 1 version that won't build or can't be modified. I need to fork the code because this will be running on a Raspberry Pi and communicating via I2C. I plan to link into the Pi4J project which I expect will run under the latest version of Maven, and maybe not an older version. That should allow me to strip out a lot of the current XBee-API dependencies.

  13. #13
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    OK, but this is really not a normal use-case.

    As I said, you are forking someone else's project. Rapp seems to be content with whatever restrictions the XBee-API POM is enforcing on him.
    Have you tried to contact him? Maybe there's a reason for it all.

    And it looks like he's up to 0.9.3 now, though the git hub still talks about 0.9.2.
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  14. #14
    dazz is offline Member
    Join Date
    Apr 2017
    Posts
    27
    Rep Power
    0

    Default Re: How to fix PluginincompatibleException ???

    Hi
    One of the fundamental benefits of open source is the ability to take someone else s work and build on it (pun intended). That's is why open source has advanced so much. My case is a perfectly normal case in the open source world.

    Only today have I found a way to contact the author, and only after I posted problems I am having with his POM.

    Part of the issue here is that I had expectations that Maven should be a service that I use without the need to know how it works. I use CPAN and apt-get without any knowledge of how they work. Specifically they sort out dependency issues for me. I never expected to be hand cutting xml POM files and nor do I want to. That is so last century. I shouldn't even need to know what Maven is. The IDE (Netbeans) should protect me from all that.

    At this point I am feeling a high level of frustration. I should be writing Java code, not spending days trying to sort out configuration issues.

  15. #15
    benji2505 is offline Senior Member
    Join Date
    Sep 2014
    Location
    MA, USA
    Posts
    388
    Rep Power
    4

    Default Re: How to fix PluginincompatibleException ???

    Quote Originally Posted by dazz View Post
    ....Maven should be a service that I use without the need to know how it works. I use CPAN and apt-get without any knowledge of how they work. Specifically they sort out dependency issues for me. ...
    Maven does handle compatability of dependencies and its versions for you, but the issue was with plugins. The plugin that caused the problem was a one person development and whether it is maintained is questionable, particularly because maintenancee seems to be taken over by a different entity now.

    Maven is a complete build-tool rather than a service and you have to know some basics in order to get the result you're looking for.
    Last edited by benji2505; 07-07-2017 at 03:20 AM.

  16. #16
    Tolls is offline Moderator
    Join Date
    Apr 2009
    Posts
    13,541
    Rep Power
    25

    Default Re: How to fix PluginincompatibleException ???

    Quote Originally Posted by dazz View Post
    Hi
    One of the fundamental benefits of open source is the ability to take someone else s work and build on it (pun intended). That's is why open source has advanced so much. My case is a perfectly normal case in the open source world.
    I do know how it works, however it is also dependent on either the author writing in a way that a random user understands, or the user understanding whatever tools and techniques the author has chosen to use. Open source is not magic, and is not immune to issues like this.

    Quote Originally Posted by dazz View Post
    Only today have I found a way to contact the author, and only after I posted problems I am having with his POM.
    The git hub page has an issue tracker, and the author seems to be pretty quick (as in on-the-day quick) at replying. And there is the Google group, also linked to on the github page (which I see is where you posted). That's all pretty standard for git hub.

    Quote Originally Posted by dazz View Post
    At this point I am feeling a high level of frustration. I should be writing Java code, not spending days trying to sort out configuration issues.
    You're using a language that, from your Google group post, you have only been using for a few weeks, including a build tool (and it is a build tool, with all that that implies), and you are surprised that there are issues? As Rapp says, the POM is not just about building the API as it also covers publishing it. Which I did wonder, with some of those plugins in the list, but I'm not anything close to a Maven expert.
    Please do not ask for code as refusal often offends.

    ** This space for rent **

  17. #17
    jim829 is online now Senior Member
    Join Date
    Jan 2013
    Location
    Northern Virginia, United States
    Posts
    6,192
    Rep Power
    12

    Default Re: How to fix PluginincompatibleException ???

    Quote Originally Posted by dazz View Post
    One of the fundamental benefits of open source is the ability to take someone else s work and build on it (pun intended). That's is why open source has advanced so much.
    Actually, open source simply means (with some minor exceptions) that it is non-proprietary. It encourages open collaboration to improve or modify it but that does not imply that doing so is easy. The JDK/JRE are also open source. But most seasoned programmers with years of experience in writing code (even compilers) would find it difficult to add a new feature to the compiler or run-time.

    Regards,
    Jim
    The JavaTM Tutorials | SSCCE | Java Naming Conventions
    Poor planning on your part does not constitute an emergency on my part

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •