What is the recommened way to bundle wikitext.core modules?

[parasharjoshi]

Hi,

The modules of wikitext.core are now set to eclipse-plugin i.e. <packaging>eclipse-plugin</packaging> e.g. for modules

• org.eclipse.mylyn.wikitext.confluence
• org.eclipse.mylyn.wikitext.textile

We tried changing the pom.xml to use packaging - <packaging>bundle</packaging> but this requires explicitly updating the pom to have dependencies update in pom.xml which i am sure is not the right way. Or is it?

We have been building the libs with
mvn clean verify -B -Dmaven.test.skip -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true -Ddash.fail=false

What is the recommended way to build these modules as bundles (like the 3.0.4XX releases) and not as eclipse-plugin?
Please advise.

Thank you.

[merks]

Can you explain why you want to do this? The build does work as is so there are no recommended changes...

[parasharjoshi]

Hi @merks,
Thank you for your response.
This is to be able to consume the bundles (jar and/or pom) of
org.eclipse.mylyn.wikitext.confluence & org.eclipse.mylyn.wikitext.textile in the application that render the textile or confluence markup text as html.

Since I noticed that the new package contents were slightly different for the jar of 3.0.48.202308291007 & the 4.6.0 jar.
Like the 3.0.4X has plugin properties and maven info in META-INF\ which is missing in 4.6.0.
Is it intentional or result of move to new packaging?

I was trying a bundled build to evaluate if that makes any difference as I was not sure how different are eclipse-plugin packaging and bundled.

Thank you.

P.S: Since the 4.X releases are not in maven repo, I was trying the build for the first time locally to consume them locally for evaluation and verification activities.

[parasharjoshi]

Please ignore the question. You are right.
The build does work as is and no changes are needed.

I was just mixing up a few things which resulted in build failures which lead me to go down the route of bundled updates asked above.
Cleaned up repo and local maven repo and the build worked as expected generating the required libraries.

mvn clean install -B -Dmaven.test.skip -Dmaven.test.failure.ignore=true -Dmaven.test.error.ignore=true -Ddash.fail=false
works and generated jars, pom and other artifacts as expected.