Hi Steve, I'm wondering if this is something specific to Eclipse? Or maybe your installation of Eclipse is trying to use an older version of Java? I also noticed that one person in that StackOverflow question you linked to mentioned an Eclipse specific setting change: https://stackoverflow.com/a/70150897
I admit, I don't use Eclipse myself, so I'm not sure what to recommend here. But, I can verify that this error doesn't occur when building DSpace 7 via Maven on commandline, and it also doesn't occur in other IDEs. I'm using IntelliJ IDEA Community Edition (which is free) and I'm not seeing those errors. So, this implies to me that it might not be an issue in our codebase (though I could be wrong, if someone else manages to find some way to fix this, I'm open to it). Or, maybe there are some other folks on this list who've tried using DSpace 7 + Eclipse and can provide some hints/tips on doing so. Tim On Monday, January 10, 2022 at 9:18:34 PM UTC-6 [email protected] wrote: > Similar to previous question, was surprised to see conflicts related to > Java modules and dependencies when building (in Eclipse). Error is -- "The > package javax.xml.transform is accessible from more than one module: > <unnamed>, java.xml" > > The underlying issue is most easily described here > <https://stackoverflow.com/questions/55571046/eclipse-is-confused-by-imports-accessible-from-more-than-one-module> > > e.g. import javax.xml.transform.Transformer; (in OpenSearchController) > > Is there a solution or known workaround to this? > > Thanks, > > Steve > > -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-community/488be401-3730-495a-8a85-5c5ea868d2dbn%40googlegroups.com.
