[jbosstools-issues] [JBoss JIRA] (JBDS-2296) Add m2eclipse-buildhelper to installer
[
https://issues.jboss.org/browse/JBDS-2296?page=com.atlassian.jira.plugin....
]
Nick Boldt updated JBDS-2296:
-----------------------------
Attachment: JBDS2296.patch.txt
Added to installer in trunk and beta1 branch ([^JBDS2296.patch.txt]):
{code}
./features/org.sonatype.m2e.buildhelper.feature_0.15.0.201207090124
./plugins/org.sonatype.m2e.buildhelper_0.15.0.201207090124.jar
{code}
Note that I'm not pulling the one-minute-newer N build 0.15.0.201207090125 when I have
a perfectly good mirror of the 0124 one already. Figure it can't be much better one
min later, can it? :D
Add m2eclipse-buildhelper to installer
--------------------------------------
Key: JBDS-2296
URL: https://issues.jboss.org/browse/JBDS-2296
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Build, installer
Affects Versions: 6.0.0.Alpha2
Reporter: Fred Bricon
Assignee: Max Rydahl Andersen
Labels: respin-a
Fix For: 6.0.0.Beta1
Attachments: JBDS2296.patch.txt
m2eclipse-buildhelper is required to use mavenized seam projects which declare additional
source directories :
{noformat}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.7</version>
<executions>
<execution>
<id>add-source</id>
<phase>generate-sources</phase>
<goals>
<goal>add-source</goal>
</goals>
<configuration>
<sources><source>${basedir}/src/hot</source></sources>
</configuration>
</execution>
</executions>
</plugin>
{noformat}
If the m2eclipse-buildhelper plugin is missing, you'll get an error marker :
{quote}Plugin execution not covered by lifecycle configuration:
org.codehaus.mojo:build-helper-maven-plugin:1.7:add-source (execution: add-source, phase:
generate-sources)
{quote}
m2eclipse-buildhelper is available from
http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira