[
https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15374:
------------------------------------
To verify:
{code}
jbosstools-target-platforms$ git add remote -p mickaelistria
jbosstools-target-platforms$ git fetch mickaelistria JBIDE-15374
{code}
then these steps to locally resolve both TPs:
https://github.com/jbosstools/jbosstools-target-platforms/tree/4.40.x#upd...
Result:
{code}
[INFO] JBDS Target Platforms ............................. SUCCESS [0.507s]
[INFO] JBDS Multiple (Composite) Target Platform ......... SUCCESS [31:00.642s]
[INFO] JBDS Unified (Aggregate) Target Platform .......... SUCCESS [1.313s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
{code}
However, [~dgolovin] found this:
{code}
[ERROR] Validation found errors in 1 .target files:
Could not resolve content of jbdevstudio-unified.target
Could not find "org.eclipse.m2e.feature.feature.group/1.5.0.20131002-0330" in
the repositories of the current location
{code}
Suspect the problem is that building the unified.target requires the
*-DtargetRepositoryUrl* commandline flag in order to resolve it against your local disk
(as the updated TP is not yet live in
http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/ ):
{code}
mvn install
-DtargetRepositoryUrl=file://path/to/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/
{code}
Create target platform from Luna M2 dependencies
------------------------------------------------
Key: JBIDE-15374
URL:
https://issues.jboss.org/browse/JBIDE-15374
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: target-platform
Affects Versions: 4.2.0.Alpha1
Reporter: Nick Boldt
Assignee: Mickael Istria
Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned
4.40.x.
Luna schedule:
http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule
--
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