Re: [osgi-dev] Checking index project APP for rebuild
> On 6 Mar 2019, at 10:56, Paul F Fraser wrote: > > Hi Tim, > > On 6/03/2019 8:41 pm, Tim Ward wrote: >> Hi Paul, >> >> Firstly - this sounds like something for the Bndtools list rather than the >> OSGi developer list, in that your asking a question about the Bndtools M2E >> integration, rather than a question about OSGi enRoute. > Not sure I understand this point, I am working with all enRoute archetypes in > what I presume is a pure enRoute approach. The enRoute archetypes are designed to be IDE agnostic, and so can be used in lots of different ways. If you were seeing the same thing happening across Eclipse, IntelliJ, and the command line then this definitely indicates an issue somewhere in the templates or project structure. In your email, however, you give your environment as "Eclipse 2018-12, bndtools 4.3.0.DEV” and your stated problem is "it is spending a long time in "Checking index project APP for rebuild””. These are clear indications that you are using Bndtools to develop your application (which is fine) and that therefore it is possible that issues you encounter may not be because of enRoute, but because of Eclipse or Bndtools. In this case "Checking index project APP for rebuild” is an action being taken by Bndtools as part of the Eclipse Incremental build (that string occurs nowhere in OSGi enRoute). There is nothing that OSGi enRoute can do to stop this from happening, so it can only be fixed on the Bndtools side. It is also the case that other projects not using enRoute (but still using Maven) could trigger the same issue. >> That said, “a long time” isn’t hugely clear - are we talking seconds or >> minutes? Seconds is probably normal, minutes probably isn’t. If it is >> minutes then is this every time, or is it only when you force updates? If >> you’re forcing a dependency update this will make Maven look for your >> dependencies in remote repos again, which will definitely add time. > > Just running a "Maven Update Projects" on all modules, the progress messages > took over 1Hr to finish. This is definitely too long unless you’re on some sort of dial-up access. The Bndtools team is the right place to ask for help. > > Running Maven Install on all modules give a 100% BUILD SUCCESS but I m > getting a "Failed to execute goal on project " and it mentions in the message > that it could not resolve some of the artifacts. > > But even before I had this resolve message it was still taking minutes. > > In a previous discussion on this list you stated that you have never > experienced this type of problem, so all I can do is recheck all of my maven > work and try to isolate the problem. > > Paul > ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] Checking index project APP for rebuild
Hi Tim, On 6/03/2019 8:41 pm, Tim Ward wrote: Hi Paul, Firstly - this sounds like something for the Bndtools list rather than the OSGi developer list, in that your asking a question about the Bndtools M2E integration, rather than a question about OSGi enRoute. Not sure I understand this point, I am working with all enRoute archetypes in what I presume is a pure enRoute approach. That said, “a long time” isn’t hugely clear - are we talking seconds or minutes? Seconds is probably normal, minutes probably isn’t. If it is minutes then is this every time, or is it only when you force updates? If you’re forcing a dependency update this will make Maven look for your dependencies in remote repos again, which will definitely add time. Just running a "Maven Update Projects" on all modules, the progress messages took over 1Hr to finish. Running Maven Install on all modules give a 100% BUILD SUCCESS but I m getting a "Failed to execute goal on project " and it mentions in the message that it could not resolve some of the artifacts. But even before I had this resolve message it was still taking minutes. In a previous discussion on this list you stated that you have never experienced this type of problem, so all I can do is recheck all of my maven work and try to isolate the problem. Paul ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
Re: [osgi-dev] Checking index project APP for rebuild
Hi Paul, Firstly - this sounds like something for the Bndtools list rather than the OSGi developer list, in that your asking a question about the Bndtools M2E integration, rather than a question about OSGi enRoute. That said, “a long time” isn’t hugely clear - are we talking seconds or minutes? Seconds is probably normal, minutes probably isn’t. If it is minutes then is this every time, or is it only when you force updates? If you’re forcing a dependency update this will make Maven look for your dependencies in remote repos again, which will definitely add time. Another thing to be aware of is that a lot of build tasks in Eclipse don’t add a message, so if the successor/children to "Checking index project APP for rebuild” don’t add a message it may look like the check is taking a long time, even though what it’s actually doing is something else. If you’re after more detailed analysis, or actually looking for a fix then I can recommend raising this with the Bndtools list. Tim > On 6 Mar 2019, at 05:11, Paul F Fraser via osgi-dev > wrote: > > With about 30 modules in an enRoute project it is spending a long time in > "Checking index project APP for rebuild" > > APP is the name of the project application. > > Is this normal or have I missed a setting somewhere? > > Eclipse 2018-12, bndtools 4.3.0.DEV > > Paul Fraser > > ___ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev ___ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
