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

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-18772:
----------------------------------------

Using the following piece of pom file, we can simply have p2 repo deployed with "mvn deploy"
{code:xml}
	<build>
		<plugins>
			<plugin>
				<groupId>org.codehaus.mojo</groupId>
				<artifactId>exec-maven-plugin</artifactId>
				<version>1.3.2</version>
				<executions>
					<execution>
						<goals>
							<goal>exec</goal>
						</goals>
						<phase>deploy</phase>
						<configuration>
							<executable>rsync</executable>
							<arguments>
								<arg>-aPrz</arg>
								<arg>--rsh=ssh</arg>
								<arg>--protocol=28</arg>
								<arg>${project.build.directory}/repository</arg>
								<arg>tools at filemgmt.jboss.org:jbosstools/updates/mars/snapshots/builds/${JOB_NAME}/${BUILD_ID}-B${BUILD_NUMBER}/all/repo/</arg>
							</arguments>  
						</configuration>
					</execution>
				</executions>
			</plugin>
		</plugins>
	</build>
{code}

So we can replace directly invocation of rsync.sh in scripts by a "mvn deploy -f site/pom.xml"
[~nickboldt] WDYT?

> 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)