[
https://issues.jboss.org/browse/JBIDE-8989?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-8989:
------------------------------------
Nick, we still need to publish the update site somewhere, as part of that build. That
means either define a -Dm2e.site-compressed value for the build (current value is
http://repository.sonatype.org/service/local/repositories/forge-sites/con...
but we can't publish there), or setup the post-build publish step in hudson. Either
way, I don't know what to put in there
The published update site needs to be made public.
Setup m2eclipse-wtp build jobs on JBoss infrastructure
------------------------------------------------------
Key: JBIDE-8989
URL:
https://issues.jboss.org/browse/JBIDE-8989
Project: Tools (JBoss Tools)
Issue Type: Task
Components: maven, UpStream
Affects Versions: 3.3.x
Reporter: Fred Bricon
Assignee: Fred Bricon
Priority: Blocker
Labels: build, m2eclipse, maven
Fix For: 3.3.x
The current JBT/maven 3.3.x builds fail due to an incompatibility between m2e-core and
m2eclipse-wtp.
The Sonatype Hudson grid, used to build m2eclipse-wtp, is down, for good.
Seems the best way to build m2eclipse-wtp is to do it on our own infrastructure.
Ideally we'd need to create 2 new Hudson jobs on the JBoss grid, building
https://github.com/sonatype/m2eclipse-wtp.git
and basically running
{noformat} mvn clean deploy -Dtarget.platform=m2e-wtp-e36 -Ppublish-site{noformat} and
{noformat} mvn clean deploy -Dtarget.platform=m2e-wtp-e37{noformat}
We'll need to set the appropriate parameters for site publishing (see
https://github.com/sonatype/m2eclipse-wtp/blob/master/org.maven.ide.eclip...)
as well as things like -Xmx512m and the path to a private local repo, if needed.
Please contact me you need more informations.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira