[JBoss JIRA] (JBIDE-15374) Create target platform from Luna M2 dependencies
by Nick Boldt (JIRA)
[ 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
12 years, 6 months
[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15606:
------------------------------------
PR pushed to master; similar PR pushed to 4.1.x branch so if we need to use this again we can. I would prefer to not have to but it's nice to have a backup approach.
Using combination of new job + jbosstools-promote job, we now have published all the _410 CI builds to here:
http://download.jboss.org/jbosstools/updates/stable/kepler/core/
* birt 1.5.0,
* hibernate 3.7.0,
* portlet 1.5.0,
* project-examples 1.5.1 (JBT 4.1.0.1 patch site, includes only the changed feature not the whole jbosstools-central site)
> build tool to regenerate component update sites from published JBT aggregate
> ----------------------------------------------------------------------------
>
> Key: JBIDE-15606
> URL: https://issues.jboss.org/browse/JBIDE-15606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Beta1
>
>
> When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so.
> We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects.
> This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15606:
------------------------------------
[~maxandersen] I would like to mark this JIRA resolved. Do you have any more clarifying questions to ask before I resolve & close this?
> build tool to regenerate component update sites from published JBT aggregate
> ----------------------------------------------------------------------------
>
> Key: JBIDE-15606
> URL: https://issues.jboss.org/browse/JBIDE-15606
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.1.Beta1
>
>
> When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so.
> We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects.
> This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15620:
----------------------------------------
Converted to a Sub-Task of JBIDE-13228
> Wrong CDI warnings
> ------------------
>
> Key: JBIDE-15620
> URL: https://issues.jboss.org/browse/JBIDE-15620
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Affects Versions: 4.1.1.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x
>
> Attachments: wrong-cdi-warnings.png
>
>
> I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes:
> * HttpSession
> * HttpServletRequest
> But the CDI 1.1 spec allows them to be injected (and my web app works fine).
> I'll attach a stacktrace to illustrate the wrong warnings
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15620:
-----------------------------------
Parent: JBIDE-13228
Issue Type: Sub-task (was: Bug)
> Wrong CDI warnings
> ------------------
>
> Key: JBIDE-15620
> URL: https://issues.jboss.org/browse/JBIDE-15620
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Affects Versions: 4.1.1.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x
>
> Attachments: wrong-cdi-warnings.png
>
>
> I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes:
> * HttpSession
> * HttpServletRequest
> But the CDI 1.1 spec allows them to be injected (and my web app works fine).
> I'll attach a stacktrace to illustrate the wrong warnings
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-15620 at 10/7/13 2:10 PM:
------------------------------------------------------------------------
This is new in CDI 1.1. The section '3.8 Additional built-in beans' in CDI 1.1 spec differs from '3.6. Additional built-in beans' in CDI 1.0 spec in the following
1. javax.security.Principal instead of java.security.Principal (can it be a typo?)
2. Added built-in beans to be provided by servlet container:
javax.servlet.http.HttpServletRequest
javax.servlet.http.HttpSession
javax.servlet.ServletContext
3. Omitted built-in beans (replaced by 1.2.7 Relationship to Bean Validation)
javax.validation.ValidationFactory
javax.validation.Validator
I suggest changing this issue from Bug to Task linked to JBIDE-13228.
was (Author: scabanovich):
This is new in CDI 1.1. The section '3.8 Additional built-in beans' in CDI 1.1 spec differs from '3.6. Additional built-in beans' in CDI 1.1 spec in the following
1. javax.security.Principal instead of java.security.Principal (can it be a typo?)
2. Added built-in beans to be provided by servlet container:
javax.servlet.http.HttpServletRequest
javax.servlet.http.HttpSession
javax.servlet.ServletContext
3. Omitted built-in beans (replaced by 1.2.7 Relationship to Bean Validation)
javax.validation.ValidationFactory
javax.validation.Validator
I suggest changing this issue from Bug to Task linked to JBIDE-13228.
> Wrong CDI warnings
> ------------------
>
> Key: JBIDE-15620
> URL: https://issues.jboss.org/browse/JBIDE-15620
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x
>
> Attachments: wrong-cdi-warnings.png
>
>
> I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes:
> * HttpSession
> * HttpServletRequest
> But the CDI 1.1 spec allows them to be injected (and my web app works fine).
> I'll attach a stacktrace to illustrate the wrong warnings
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15620) Wrong CDI warnings
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-15620:
-----------------------------------------------
This is new in CDI 1.1. The section '3.8 Additional built-in beans' in CDI 1.1 spec differs from '3.6. Additional built-in beans' in CDI 1.1 spec in the following
1. javax.security.Principal instead of java.security.Principal (can it be a typo?)
2. Added built-in beans to be provided by servlet container:
javax.servlet.http.HttpServletRequest
javax.servlet.http.HttpSession
javax.servlet.ServletContext
3. Omitted built-in beans (replaced by 1.2.7 Relationship to Bean Validation)
javax.validation.ValidationFactory
javax.validation.Validator
I suggest changing this issue from Bug to Task linked to JBIDE-13228.
> Wrong CDI warnings
> ------------------
>
> Key: JBIDE-15620
> URL: https://issues.jboss.org/browse/JBIDE-15620
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.1.Alpha1
> Reporter: Juergen Zimmermann
> Assignee: Viacheslav Kabanovich
> Fix For: 4.2.x
>
> Attachments: wrong-cdi-warnings.png
>
>
> I moved to WildFly (and therefore to Weld 2.0.CR1 resp CDI 1.1). I'm getting warnings about wrong dependency injection of these classes:
> * HttpSession
> * HttpServletRequest
> But the CDI 1.1 spec allows them to be injected (and my web app works fine).
> I'll attach a stacktrace to illustrate the wrong warnings
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15614) Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15614:
---------------------------------------
{quote}
actually - might be Rob's additional fix removed that warning.
{quote}
Right. There isn't a warning when using the EAP 6.1+ runtime.
> Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate
> ------------------------------------------------------------------------
>
> Key: JBIDE-15614
> URL: https://issues.jboss.org/browse/JBIDE-15614
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: runtime-detection, server
> Affects Versions: 4.1.0.Final
> Environment: JBDS 7.0.0.GA
> Reporter: Martin Malina
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1
>
>
> 1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
> 2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
> Let me know if you want subtasks for these two.
--
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
12 years, 6 months
