Re: [orbit-dev] Add Jaxen and JDom zu Orbit

[Gunnar Wagenknecht <gunnar@xxxxxxxxxxxxxxx>]

Dirk,

Can you publish the modified artifacts (jar and sources) to repo.eclipse.org? AFAIK Roland wrote a Jenkins job that could help with this.

-Gunnar


-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx, http://guw.io/


> On Nov 13, 2019, at 14:40, Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx> wrote:
> 
> Hi,
> 
> Is there anybody who could help me with this? 
> 
> Greez, 
> Dirk 
> 
> Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx> schrieb am Fr., 8. Nov. 2019, 11:33:
> Hi,
> 
> jaxen is merged. Thanks for the support! :-)
> 
> Now I would like to add also JDOM2. Two topics that need to be clarified:
> 
> 1. Could someone please create the ATO CQ?
> 2. Is it possible to add a custom src jar? As stated in the CQ there is a license issue with the sources. It was addressed to the project and they accepted and fixed it. But there is no newer release. In APP4MC the sources where modified locally (only a javadoc issue), so I could use that one instead of the one provided in Maven. Any suggestion on how this can be accomplished?
> 
> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11158 
> 
> Greez,
> Dirk 
> 
> On Wed, Oct 30, 2019 at 5:20 PM Dirk Fauth <dirk.fauth@xxxxxxxxxxxxxx> wrote:
> Thanks for the pointer. It worked now. I have created a ticket and pushed a path to Gerrit:  https://git.eclipse.org/r/#/c/151800/
> 
> Hope things are correct this way.
> 
> Next step is the creation of the jdom recipe. But I need to find a way to exchange the sources because of a small issue reported by the IP team.
> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=11158 
> 
> The APP4MC team solved this by locally modifying the sources. The issue was also reported to the JDOM team and they accepted the patch. But since then there was no release.
> 
> Any hint on how to handle this?
> 
> Greez,
> Dirk 
> 
> On Tue, Oct 29, 2019 at 3:02 PM Roland Grunberg <rgrunber@xxxxxxxxxx> wrote:
> > I am trying to create the recipe for jaxen 1.1.6. But it fails with an exception because the web page that is referenced as Bundle-License in the manifest does not exist anymore. Overriding that value in the osgi.bnd does not help as it only affects the result.
> 
> I think it's actually due to
> https://repo1.maven.org/maven2/jaxen/jaxen/1.1.6/jaxen-1.1.6.pom ,
> which is where ebr-maven-plugin checks to read the license. It looks like
> the project transitioned to github hence the older webpage being down.
> You should be able to override this by adding -Dlicense="New BSD" to
> the create-recipe mojo invocation. See
> https://github.com/eclipse/ebr/blob/master/releng/maven-plugins/ebr-maven-plugin/src/main/java/org/eclipse/ebr/maven/CreateRecipeMojo.java#L123
> for more info on what kind of things can be set.
> 
> In the worst case, I think the recipe generation succeeded for everything
> but the about file so even if the above doesn't work, you can always look
> at other about files and go from there. There's also a template at
> https://github.com/eclipse/ebr/blob/master/releng/maven-plugins/ebr-maven-plugin/src/main/resources/recipe-about.html
> 
> Cheers,
> Roland Grunberg
> 
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/orbit-dev
> _______________________________________________
> orbit-dev mailing list
> orbit-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/orbit-dev