Tycho build maven artifact (org.jboss.forge.roaster.roaster-api) #1007

antoniogarmendia · 2022-06-09T13:16:20Z

antoniogarmendia
Jun 9, 2022

Hi all,

I am trying to include this maven plugin: org.jboss.forge.roaster.roaster-api in my deployment, but I am getting this error:

[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:2.7.3:validate-classpath (default-validate-classpath) on project generate.java.code: Execution default-validate-classpath of goal org.eclipse.tycho:tycho-compiler-plugin:2.7.3:validate-classpath failed: org.osgi.framework.BundleException: Bundle generate.java.code cannot be resolved:generate.java.code [3]
[ERROR] Unresolved requirement: Require-Bundle: org.jboss.forge.roaster.roaster-api
[ERROR] -> Bundle-SymbolicName: org.jboss.forge.roaster.roaster-api; bundle-version="2.25.0.Final"; singleton:="true"
[ERROR] org.jboss.forge.roaster.roaster-api [1]
[ERROR] Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:2.7.3:validate-classpath (default-validate-classpath) on project generate.java.code: Execution default-validate-classpath of goal org.eclipse.tycho:tycho-compiler-plugin:2.7.3:validate-classpath failed: org.osgi.framework.BundleException: Bundle generate.java.code cannot be resolved:generate.java.code [3]
Unresolved requirement: Require-Bundle: org.jboss.forge.roaster.roaster-api
-> Bundle-SymbolicName: org.jboss.forge.roaster.roaster-api; bundle-version="2.25.0.Final"; singleton:="true"
org.jboss.forge.roaster.roaster-api [1]
Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.processor)"

Since I am using Apache Aries I do not know if I am missing something. I am working with Tycho 2.7.3.

I was able to implement a minimal example and the same error appear.

minimal.example.project.zip

This minimal example is pomless and has the following structure:

bundles: has only one plugin called generate.java.code
features: contains the project with the feature project
launch: run tycho. Basically, "clean verify -X"
releng: contains the target paltform, the tycho configuration and the update site project

In this example, I added the Apache Aries to the target platform, but I am not sure if this is necessary for compilation.

What I am missing? Any hints?

Thanks in advance.

Kind regards,
Antonio

Bananeweizen · 2022-06-10T09:08:57Z

Bananeweizen
Jun 10, 2022
Collaborator

You might try adding explicit POM requirements for the Aries bundles: https://stackoverflow.com/questions/43775025/after-jetty-update-to-9-4-x-missing-constraint-require-capability-osgi-extend.
I have only used Aries with the Serviceloader (for automatic JUnit 5 extension registration), that worked without explicit POM dependencies, however.

0 replies

antoniogarmendia · 2022-06-13T08:42:24Z

antoniogarmendia
Jun 13, 2022
Author

Hi Michael,

Thanks for your answer. Unfortunately, It seems that it does not work for me. I updated the minimal example and added those three dependencies but I got the same error.

minimal.example.projectv1.zip

Any other hints?

Thanks.

Kind regards,
Antonio

16 replies

antoniogarmendia Jun 21, 2022
Author

Hi Michael,

Sorry, I removed Xtend dependency (It is really not necessary:-/) and reduced the pom as much as I could, but the other dependencies are needed in order to roaster compiles correctly. It has 5 dependencies, but all of them are added in the target platform.

This is the updated minimal example:

minimal.example.project.zip

This minimal example is pomless and has the following structure:

bundles: has only one plugin called generate.java.code
features: contains the project with the feature project (minimal.example.feature)
launch called "minimal.example.project": run tycho. Basically, "clean verify -X"
releng: contains the target paltform (minimal.example.target\minimal.example.target.), the tycho configuration and the update site project.

Do you need more info? Do I need to reduce this even more? Please, do not hesitate to let me know.

Thanks!

Kind regards,
Antonio

mickaelistria Jun 21, 2022
Collaborator

I gave it a try. The unit is properly generated in the feature as one can see in features/minimal.example.feature/target/p2content.xml , but the unit is not included into the p2 repo. To force inclusion in the p2 repo, you can add <iu id="org.apache.aries.util.fragment"/> in the category.xml, just like you'd add a bundle.

laeubi Jun 21, 2022
Maintainer

Why not just include the fragment in the feature if its required?

antoniogarmendia Jun 22, 2022
Author

Hi all,

@mickaelistria Thanks for giving it a try. Indeed, I missed that on the category.xml (I just read [1]). However, It does not work for me when I install this plugin. I extended the previous minimal example with other units that I also need. In my runtime Eclipse I have the following start-level configuration:

aries.util->startlevel:1
aries.spifly.dynamic.bundle->startlevel:1
roaster-api->startlevel:2
roaster-jdt->startlevel:2

In the content.jar/content.xml I can see that the start levels are well defined. However, when I install these fragments I got the following error:

org.osgi.framework.BundleException: Could not resolve module: org.jboss.forge.roaster.roaster-jdt [1628]
  Unresolved requirement: Import-Package: com.ibm.cds; resolution:="optional"
  Unresolved requirement: Import-Package: com.ibm.oti.shared; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.core.filesystem; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.core.filesystem.provider; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.core.internal.runtime.auth; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.equinox.app; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.equinox.internal.app; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster._shade.org.eclipse.osgi.internal.resolver; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster.model; resolution:="optional"
  Unresolved requirement: Import-Package: org.jboss.forge.roaster.model.source; resolution:="optional"
  Unresolved requirement: Require-Bundle: org.jboss.forge.roaster.roaster-api

	at org.eclipse.osgi.container.Module.start(Module.java:463)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel$2.run(ModuleContainer.java:1847)
	at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor$1$1.execute(EquinoxContainerAdaptor.java:136)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1840)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1783)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1745)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1667)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:234)
	at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:345)

It seems that roaster-jdt cannot find the roaster-api, however, it is included in the list of plugins. Why does this happen? Should I add anything else? This is the minimal example updated:

minimal.example.project.zip

Thanks.

@laeubi Thanks for your answer. Not sure how to include the unit within feature. It is possible to do so? How?

Kind regards,
Antonio

[1] https://wiki.eclipse.org/Tycho/category.xml

antoniogarmendia Jun 30, 2022
Author

Hi all,

I am still interested in solving this issue. At this moment, the only solution that I found is to write a bash that changes the auto start file in configuration\org.eclipse.equinox.simpleconfigurator\bundles.info, but of course, I am still looking for a way to automate this in order to provide a user-friendly installation process. If I need to improve the minimal example, just let me know.

Thanks.

Kind regards,
Antonio

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Tycho build maven artifact (org.jboss.forge.roaster.roaster-api) #1007

{{title}}

Replies: 2 comments 16 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Tycho build maven artifact (org.jboss.forge.roaster.roaster-api) #1007

antoniogarmendia Jun 9, 2022

Replies: 2 comments · 16 replies

Bananeweizen Jun 10, 2022 Collaborator

antoniogarmendia Jun 13, 2022 Author

antoniogarmendia Jun 21, 2022 Author

mickaelistria Jun 21, 2022 Collaborator

laeubi Jun 21, 2022 Maintainer

antoniogarmendia Jun 22, 2022 Author

antoniogarmendia Jun 30, 2022 Author

antoniogarmendia
Jun 9, 2022

Replies: 2 comments 16 replies

Bananeweizen
Jun 10, 2022
Collaborator

antoniogarmendia
Jun 13, 2022
Author

antoniogarmendia Jun 21, 2022
Author

mickaelistria Jun 21, 2022
Collaborator

laeubi Jun 21, 2022
Maintainer

antoniogarmendia Jun 22, 2022
Author

antoniogarmendia Jun 30, 2022
Author