Hello,
See comments bellow.
Asma
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Christian Damus
Envoyé : mercredi 11 mai 2016 21:18
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] New problem with Oomph developer setup
The nuclear option? It seemed to work for Asma. But, it removes a lot of goodness, such as Oomph’s download cache directory and the bundle pool. In fact, deleting that bundle
pool yanks out all of the plug-ins from your Oomph-managed Eclipse installations, so you’ll have to delete all of those, too, because they won’t work any more.
I can’t really see your secure storage and maven problems being caused by interference from other installations; Oomph and p2 keep this stuff pretty well isolated. But, I don’t
actually know what’s happening in your environment, so I can’t advise one way or the other. Sorry.
Yes. It was working for me, I even downloaded a new Eclipse Installer and started all from scratch ;). But I think there is no use to do so. It is a brutal procedure
J
I think we could just suppress the antrun in this lifecycle mappings preference file for now and remove the same from the POMs. That just leaves the three lifecycle errors in the feature
POMs that I mentioned earlier, which we can then review.
The nice thing about this is that by default, m2e doesn’t create this file in the preferences, so we can actually create it in the setup model and then the next time developers run the setup,
they will get this file. That is, assuming they didn’t already create it for themselves. That’s the tricky bit: we get one chance at creating this file; Oomph will not replace it if we make changes (users would have to delete it and then let Oomph re-create
it).
BTW, the m2e connectors that we know we need are currently installed in my Eclipse from here:
org.sonatype.tycho.repository - http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-tycho/0.8.0/N/LATEST/
So, we can just go with these for now in the setup model?
Done. I just pushed 72559 and added you as a reviewer. I put the features and these two repos under the "Core Development Tools"
P2 director. Is that the appropriate place?
I followed the link suggested by Christian and I ended up with a lifecycle-mapping-metadata.xml that contains <pluginExecution> balises, with different filters and goals <pluginExecutionFilter>
<goals><goal>validate-version</goal>…with ignore actions. <action><ignore /> </action></pluginExecution>.
I did not modify the setup file, that’s why my lifecycle-mapping-metadata.xml contains filter execution for all different goals validate-version, build-qualifier, validate-id,
complie, run…and not just the antrum run goal as I can notice in the lifecycle-mapping-metadata.xml created when testing the latest setup file version.
However, it could be also interesting to mege Ernesto patch that generates code automatically for xtuml different models to endup with 0 errors ;)
Asma
|
