You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 5, 2019. It is now read-only.
We checked the released versions of jaxb and this bugfix can be found starting from the
release 2.3.1-b180717.0505, but this release has never made it to Maven Central or Maven Repo.
We tried to get 2.4.x running, but we get a lot of dependency issues and compaitiblity problems there, therefore the most simple solution would be, if someone could create another 2.3.x release and make it official in Maven Central or make the release 2.3.1-b180717.0505 available there.
Thank you very much for the support in advance.
best Regards,
Reza
The text was updated successfully, but these errors were encountered:
thanks for this idea, but this stating repo from maven.java.net is not part of our offical list of maven-repos, where our company wide nexus can get jars from and therefore we can not get access to this jar (For security reasons we are only allowed to access jars from the company nexus). Therefore we can only access those jars, which are officially hosted at mvnrepository.com or search.maven.org. Also i doubt that our company nexus admins will add this staging repo.
Is there any alternative? What is the process to get jars from staging to mvnrepository.com?
Best regards,,
Hello,
there was a fix for the problem
"Fix XJC ant task to work without fork. "
created with this commit:
dad8495#diff-9e91db6a172b85bd4a5588d9aa151e85
We checked the released versions of jaxb and this bugfix can be found starting from the
release 2.3.1-b180717.0505, but this release has never made it to Maven Central or Maven Repo.
We tried to get 2.4.x running, but we get a lot of dependency issues and compaitiblity problems there, therefore the most simple solution would be, if someone could create another 2.3.x release and make it official in Maven Central or make the release 2.3.1-b180717.0505 available there.
Thank you very much for the support in advance.
best Regards,
Reza
The text was updated successfully, but these errors were encountered: