[jbosstools-issues] [JBoss JIRA] (JBIDE-21142) could JBDS Discovery build depend on JDBS root pom?

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-21142:
------------------------------------

Looks like this is technically possible but for two concerns:

a) dependency chain

If we do this, we'll have this chain of dependency:

jbosstools-discovery/jbdevstudio/pom.xml depends on jbdevstudio-product/pom.xml depends on jbosstools-build/parent/pom.xml

This is technically doable but means we have a fully-open jbosstools-* project depending on a private repo jbdevstudio-* project. Good news here is that the Jenkins job can support this.

b) nexus artifacts

If we do this, we'll have to publish the jbdevstudio-product/pom.xml into Nexus so that the jbosstools-discovery/jbdevstudio/pom.xml can resolve it

----

So, since we need to publish a second nexus artifact anyway, I'm inclined to prefer that we simply add a *second parent pom into jbosstools-build* for this purpose.

But...

* since "this purpose" is simply to remove the number "10.0" from the jbosstools parent pom, in order to suggest that we don't directly associate (and release) JBT 4.4.x with JBDS 10.x, and
* since we DO co-release those (and have for 7+ years in a row with no indication we'll stop doing so any time soon)...

I'm inclined to just leave the *devstudioReleaseVersion = 10.0* in the JBT 4.4 parent pom, and close this as rejected on the grounds that it's process overhead and more crap to maintain, simply to avoid having a JBDS-related version number from appearing in the JBT parent pom.

Side note: if we used a symlink on the devstudio.redhat.com site to link to a "/neon/" folder from the actual /10.0/ folder, or simply used /neon/ as the path segment in the JBDS update site URLs, we could forgo the need for this variable entirely. But that idea was killed some time ago [1].

[1] https://issues.jboss.org/browse/JBIDE-20993

> could JBDS Discovery build depend on JDBS root pom?
> ---------------------------------------------------
>
>                 Key: JBIDE-21142
>                 URL: https://issues.jboss.org/browse/JBIDE-21142
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.4.0.Alpha1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> {quote}
> creation of a JBDS/discovery parent pom?
> https://github.com/jbosstools/jbosstools-build/commit/5ce5c5aa9c6febd562de584b7c05a8e80f6b0a27#diff-04dc5d029560773ac79faaf3da0fbb22R17
> and https://github.com/jbosstools/jbosstools-discovery/pull/279
> try this: jbds disco depends on jbds prod root pom?{quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)