[JBoss JIRA] Created: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
5:05 p.m.
Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, Requirements
Affects Versions: 5.0.0.M1
Reporter: Nick Boldt
Assignee: Fred Bricon
From Max:
We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Fred Bricon commented on JBDS-1635:
-----------------------------------
Seeing how fast m2e-core API is changing, I'm +1 to wait for their release of M7
before doing anything serious.
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, Requirements
Affects Versions: 5.0.0.M1
Reporter: Nick Boldt
Assignee: Fred Bricon
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:24 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Max Rydahl Andersen updated JBDS-1635:
--------------------------------------
Fix Version/s: 5.0.0.M2
Priority: Critical (was: Major)
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Fred Bricon
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:05 a.m.
New subject: [JBoss JIRA] Updated: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Fred Bricon updated JBDS-1635:
------------------------------
Component/s: maven
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Fred Bricon
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Fred Bricon edited comment on JBDS-1635 at 6/10/11 2:29 PM:
------------------------------------------------------------
I updated http://svn.jboss.org/repos/devstudio/trunk/product/extras/site/site.xml and
http://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbd...
Reassigning to you Nick just in case there's anything left to do wrt the build. Close
if everything's fine
was (Author: fbricon):
I updated http://svn.jboss.org/repos/devstudio/trunk/product/extras/site/site.xml and
http://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbd...
Reassigning in case to you Nick just in case there's anything left to do wrt the
build. Close if everything's fine
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
New subject: [JBoss JIRA] Assigned: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Fred Bricon reassigned JBDS-1635:
---------------------------------
Assignee: Nick Boldt (was: Fred Bricon)
I updated http://svn.jboss.org/repos/devstudio/trunk/product/extras/site/site.xml and
http://svn.jboss.org/repos/devstudio/trunk/product/features/com.jboss.jbd...
Reassigning in case to you Nick just in case there's anything left to do wrt the
build. Close if everything's fine
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:08 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1635:
----------------------------------
Looks like the JBDS target platform is missing some requirements, which I've added:
{core} <unit
id="org.eclipse.m2e.feature.feature.group"
version="1.0.0.201106052308"/>
<unit
id="org.maven.ide.eclipse.wtp.feature.feature.group"
version="0.13.0.201106020304"/>
<unit id="ch.qos.logback.classic"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.core"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110"/>
<unit id="org.slf4j.api"
version="1.6.1.v20100831-0715"/>
<unit id="com.ning.async-http-client"
version="1.6.3.201106052308"/>
<unit id="org.jboss.netty"
version="3.2.4.Final-201106052308"/>{core}
Also adding them to product/features/com.jboss.jbds.m2e.feature/feature.xml:
{core} <import plugin="ch.qos.logback.classic"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.core"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="org.slf4j.api"
version="1.6.1.v20100831-0715" match="compatible"/>
<import plugin="com.ning.async-http-client"
version="1.6.3.201106052308" match="compatible"/>
<import plugin="org.jboss.netty"
version="3.2.4.Final-201106052308" match="compatible"/>{core}
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1635 at 6/10/11 11:09 PM:
------------------------------------------------------------
Looks like the JBDS target platform is missing some requirements, which I've added:
{code} <unit
id="org.eclipse.m2e.feature.feature.group"
version="1.0.0.201106052308"/>
<unit
id="org.maven.ide.eclipse.wtp.feature.feature.group"
version="0.13.0.201106020304"/>
<unit id="ch.qos.logback.classic"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.core"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110"/>
<unit id="org.slf4j.api"
version="1.6.1.v20100831-0715"/>
<unit id="com.ning.async-http-client"
version="1.6.3.201106052308"/>
<unit id="org.jboss.netty"
version="3.2.4.Final-201106052308"/>{code}
Also adding them to product/features/com.jboss.jbds.m2e.feature/feature.xml:
{code} <import plugin="ch.qos.logback.classic"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.core"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="org.slf4j.api"
version="1.6.1.v20100831-0715" match="compatible"/>
<import plugin="com.ning.async-http-client"
version="1.6.3.201106052308" match="compatible"/>
<import plugin="org.jboss.netty"
version="3.2.4.Final-201106052308" match="compatible"/>{code}
was (Author: nickboldt):
Looks like the JBDS target platform is missing some requirements, which I've
added:
{core} <unit
id="org.eclipse.m2e.feature.feature.group"
version="1.0.0.201106052308"/>
<unit
id="org.maven.ide.eclipse.wtp.feature.feature.group"
version="0.13.0.201106020304"/>
<unit id="ch.qos.logback.classic"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.core"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110"/>
<unit id="org.slf4j.api"
version="1.6.1.v20100831-0715"/>
<unit id="com.ning.async-http-client"
version="1.6.3.201106052308"/>
<unit id="org.jboss.netty"
version="3.2.4.Final-201106052308"/>{core}
Also adding them to product/features/com.jboss.jbds.m2e.feature/feature.xml:
{core} <import plugin="ch.qos.logback.classic"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.core"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="org.slf4j.api"
version="1.6.1.v20100831-0715" match="compatible"/>
<import plugin="com.ning.async-http-client"
version="1.6.3.201106052308" match="compatible"/>
<import plugin="org.jboss.netty"
version="3.2.4.Final-201106052308" match="compatible"/>{core}
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Nick Boldt edited comment on JBDS-1635 at 6/10/11 11:10 PM:
------------------------------------------------------------
Looks like the JBDS target platform is missing some requirements...
{code}Missing requirement: Maven Integration for Eclipse Refactoring 1.0.0.201106052308
(org.eclipse.m2e.refactoring 1.0.0.201106052308) requires 'bundle org.slf4j.api
1.6.1' but it could not be found{code}
...which I've added:
{code} <unit
id="org.eclipse.m2e.feature.feature.group"
version="1.0.0.201106052308"/>
<unit
id="org.maven.ide.eclipse.wtp.feature.feature.group"
version="0.13.0.201106020304"/>
<unit id="ch.qos.logback.classic"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.core"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110"/>
<unit id="org.slf4j.api"
version="1.6.1.v20100831-0715"/>
<unit id="com.ning.async-http-client"
version="1.6.3.201106052308"/>
<unit id="org.jboss.netty"
version="3.2.4.Final-201106052308"/>{code}
Also adding them to product/features/com.jboss.jbds.m2e.feature/feature.xml:
{code} <import plugin="ch.qos.logback.classic"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.core"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="org.slf4j.api"
version="1.6.1.v20100831-0715" match="compatible"/>
<import plugin="com.ning.async-http-client"
version="1.6.3.201106052308" match="compatible"/>
<import plugin="org.jboss.netty"
version="3.2.4.Final-201106052308" match="compatible"/>{code}
was (Author: nickboldt):
Looks like the JBDS target platform is missing some requirements, which I've
added:
{code} <unit
id="org.eclipse.m2e.feature.feature.group"
version="1.0.0.201106052308"/>
<unit
id="org.maven.ide.eclipse.wtp.feature.feature.group"
version="0.13.0.201106020304"/>
<unit id="ch.qos.logback.classic"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.core"
version="0.9.27.v20110224-1110"/>
<unit id="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110"/>
<unit id="org.slf4j.api"
version="1.6.1.v20100831-0715"/>
<unit id="com.ning.async-http-client"
version="1.6.3.201106052308"/>
<unit id="org.jboss.netty"
version="3.2.4.Final-201106052308"/>{code}
Also adding them to product/features/com.jboss.jbds.m2e.feature/feature.xml:
{code} <import plugin="ch.qos.logback.classic"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.core"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="ch.qos.logback.slf4j"
version="0.9.27.v20110224-1110" match="compatible"/>
<import plugin="org.slf4j.api"
version="1.6.1.v20100831-0715" match="compatible"/>
<import plugin="com.ning.async-http-client"
version="1.6.3.201106052308" match="compatible"/>
<import plugin="org.jboss.netty"
version="3.2.4.Final-201106052308" match="compatible"/>{code}
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:09 p.m.
New subject: [JBoss JIRA] Commented: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBDS-1635:
----------------------------------
Actually, works better as included plugins than imported (required) plugins.
Also had to add these:
{code}
<plugin id="org.eclipse.equinox.p2.discovery.compatibility"
version="1.0.1.v20110502-1955" match="compatible"
download-size="0" install-size="0"/>
<plugin id="org.eclipse.equinox.p2.discovery"
version="1.0.100.v20110502-1955" match="compatible"
download-size="0" install-size="0"/>
<plugin id="org.eclipse.equinox.p2.ui.discovery"
version="1.0.0.v20110502-1955" match="compatible"
download-size="0" install-size="0"/>
<plugin id="org.eclipse.net4j.jms.api"
version="3.0.0.v20110516-1727" match="compatible"
download-size="0" install-size="0"/>
{code}
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 p.m.
New subject: [JBoss JIRA] Resolved: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Nick Boldt resolved JBDS-1635.
------------------------------
Release Notes Text: m2e 1.0 and m2e-wtp 0.13 are now on the JBDS 5 Extras site, along
with the org.jboss.tools.maven.* features from JBoss Tools
Resolution: Done
Closing.
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:36 a.m.
New subject: [JBoss JIRA] Commented: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Fred Bricon commented on JBDS-1635:
-----------------------------------
Thanks Nick, I don't know how I could miss these. I guess it was really time to go on
weekend.
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:27 a.m.
New subject: [JBoss JIRA] Closed: (JBDS-1635) Include JBoss Maven Integration in JBDS Extras site (along with m2eclipse 0.13) ?
[
https://issues.jboss.org/browse/JBDS-1635?page=com.atlassian.jira.plugin....
]
Libor Zoubek closed JBDS-1635.
------------------------------
Include JBoss Maven Integration in JBDS Extras site (along with
m2eclipse 0.13) ?
---------------------------------------------------------------------------------
Key: JBDS-1635
URL: https://issues.jboss.org/browse/JBDS-1635
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: Build, maven, Requirements
Affects Versions: 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Critical
Fix For: 5.0.0.M2
From Max:
> We're not planning on supporting JBoss Maven Integration
(org.jboss.tools.maven.*) before there is stable api from m2e.
> But I guess it could be put on the Extras site as a 3rd party "selected"
plugin.
> The maven stuff can't just be put into JBDS 4.x sites without
some work. So its a +1 for JBDS 5 once Snjezana/Fred are ok with it.
From Sneja:
+1
Awaiting feedback from Fred.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4809
days inactive
4944
days old
jbosstools-issues@lists.jboss.org
12 comments
4 participants
participants (4)
-
Fred Bricon (JIRA) -
Libor Zoubek (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)