[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

Max Rydahl Andersen (JIRA) issues at jboss.org
Fri Apr 24 03:23:52 EDT 2015


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

Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------

im not wrong ;)

just because the current parent pom has all these shared variables does not automatically mean it should be munged in together with deployment setup.

The shared parameters could stay in the "root" parent pom, but another specific parent could be made to handle the project type specific deployment. 

I'm not saying this is what we should go do blindly, just saying there are ways to better split the different concerns to avoid conflict/unnecessary churn.


btw. I thought the suggestion was to just use mvn deploy - not that everything would use the same mojo. i.e. my expectations would have been that the pom of the "non-module" projects would override what the parent says about deploy and configure it properly for them using whatever scripts etc. we need for them ?
 

> Include publish.sh in parent pom as versioned maven dependency
> --------------------------------------------------------------
>
>                 Key: JBIDE-18772
>                 URL: https://issues.jboss.org/browse/JBIDE-18772
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Mickael Istria
>            Priority: Critical
>             Fix For: 4.3.0.Beta1
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible 
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jbosstools-issues mailing list