[jbosstools-issues] [JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency
Nick Boldt (JIRA)
issues at jboss.org
Tue Mar 24 11:05:19 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053002#comment-13053002 ]
Nick Boldt commented on JBIDE-18772:
------------------------------------
{quote} This approach makes that we'll slowly prefer avoiding JOB_NAME and other Jenkins property in favor of properties that are inside the pom directly.{quote}
How would the jbosstools-server_master job know where to publish, then, if not using JOB_NAME? What property would you use?
Maybe $\{project.artifactId}_$\{jbosstools_site_stream} = server.all_master ?
Or $\{project.artifactId}_$\{project.parent.version} = server.all_4.2.3.Final-SNAPSHOT ?
If we push a call to rsync.sh into the parent pom for all projects that use the parent pom, we might want to wrap that with a profile so that local builds don't attempt to deploy. Or so that other projects that use the parent pom (like jbosstools-discovery) don't try to deploy accidentally. Does that make sense?
> 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: Feature Request
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.Alpha2
>
>
> 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.11#6341)
More information about the jbosstools-issues
mailing list