[jbosstools-issues] [JBoss JIRA] (JBTIS-318) Generate source bundles for IS component features.

Paul Leacu (JIRA) issues at jboss.org
Mon Sep 8 14:09:01 EDT 2014


    [ https://issues.jboss.org/browse/JBTIS-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13000045#comment-13000045 ] 

Paul Leacu commented on JBTIS-318:
----------------------------------

Hey [~KrisVerlaenen] - I noticed that jBPM3 is actually generating the source bundles correctly.  I think what I need is something like this for each feature pom.xml:

         <build>
                 <plugins>
                         <plugin>
                                 <groupId>org.eclipse.tycho.extras</groupId>
                                 <artifactId>tycho-source-feature-plugin</artifactId>
                         </plugin>
                         <plugin>
                                 <groupId>org.eclipse.tycho</groupId>
                                 <artifactId>tycho-p2-plugin</artifactId>
                         </plugin>
                 </plugins>
         </build>

   wdyt?

> Generate source bundles for IS component features.
> --------------------------------------------------
>
>                 Key: JBTIS-318
>                 URL: https://issues.jboss.org/browse/JBTIS-318
>             Project: JBoss Tools Integration Stack
>          Issue Type: Sub-task
>          Components: drools/ jBPM
>    Affects Versions: 4.2.0.Alpha1, 8.0.0.Alpha1
>            Reporter: Paul Leacu
>            Assignee: Kris Verlaenen
>
> jBPM/ Drools must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS.
> Courtesy [~nickboldt]:
> How to make maven/tycho build source bundles and features:
> In the upstream projects:
> http://wiki.eclipse.org/Minerva#Source
> Then in the aggregator for JBTIS/JBSIS update site:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L248-L262
> As a result, users can install sources from within JBDS rather than
> needing a separate source zip with .java files. Way more useful, if
> you're a java developer using JBDS/Eclipse.
> If you also want to produce a zip of *actual source files* as pulled
> from github, I have a script for that, too.
> See:
> 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources
> Produces a zip of the contents of the JBDS product build, so people can
> build it offline. Does NOT include upstream sources.
> Result:
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_master/all/devstudio.product_master-SNAPSHOT-src.zip
> (2.4M)
> 2.
> https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/publish.sh#L464-L500
> Produces a zip of upstream sources based on upstream project zips. This
> is the old approach, since pulling a previously-built zip doesn't 100%
> guarantee you're getting the correct version AND it requires that the
> upstream project produce a source zip.
> -OR-
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L123-L164
> Fetches sources directly from github based on the source-reference in
> the specified plugins' manifest.mf files, then collates those sources
> into a single zip.
> Results:
> http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/all/jbosstools-build-sites.aggregate.site_master-SNAPSHOT-src.zip
> (35M)
> Ref:
> (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide.
> (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct?
> (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it.
> (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that
> (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience.
> (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles
> (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources
> (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized"
> (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/category.xml#L248-L250 (cc: pleacu )
> Components that generate source bundles:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/jbpm/4.5.200.Final/
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/esb/1.5.303.Final/
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/bpel/1.2.101.Final/
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/modeshape/3.6.0.Final/
> Some that don't:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/fuse-tooling/7.2.0/all/repo/
> http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/switchyard/2.0.0/
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/teiiddesigner/8.5.0.Final/



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list