[JBoss JIRA] (JBIDE-15621) Runtime isn't detected when adding it right after it was deleted
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15621?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-15621:
------------------------------------
Attachment: runtime 01 - select folder.png
runtime 02 - add.png
runtime 03 - remove.png
runtime 04 - select folder again.png
runtime 05 - problem.png
runtime 06 - workaround 01 - deselect.png
runtime 07 - workaround 02 - select.png
> Runtime isn't detected when adding it right after it was deleted
> ----------------------------------------------------------------
>
> Key: JBIDE-15621
> URL: https://issues.jboss.org/browse/JBIDE-15621
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.0.1.Final
> Reporter: Radoslav Rábara
> Attachments: runtime 01 - select folder.png, runtime 02 - add.png, runtime 03 - remove.png, runtime 04 - select folder again.png, runtime 05 - problem.png, runtime 06 - workaround 01 - deselect.png, runtime 07 - workaround 02 - select.png
>
>
> JBoss Runtime Detection doesn't detect a runtime, when the runtime is removed and then added.
> Workaround exists.
--
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-15198) Move away from sonatype aether to eclipse aether
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15198?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15198:
---------------------------------------
{quote}
p.s. is arquillian the only place aether is used ?
{quote}
No, it isn't. A similar code is used in the JBoss Maven integration - JBoss Maven quickfixes. Maybe, there are some other places, too.
I will check the PR asap.
> Move away from sonatype aether to eclipse aether
> ------------------------------------------------
>
> Key: JBIDE-15198
> URL: https://issues.jboss.org/browse/JBIDE-15198
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven, project-examples, testing-tools
> Affects Versions: 4.1.0.CR1
> Reporter: Fred Bricon
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> With Maven 3.1.0, Sonatype Aether has been replaced with Eclipse Aether. m2e 1.5.0 will soon do the same. Currently, I've found that at least the following plugins have a dependency to the Sonatype version :
> - org.jboss.tools.arquillian.core
> - org.jboss.tools.maven.project.examples
> - org.jboss.tools.maven.ui
> Ideally the next m2e version won't embed the jars directly (but this is not guaranteed). Aether is available from this p2 repo : http://download.eclipse.org/aether/aether-core/milestones
--
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 Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15606:
---------------------------------------------
btw. with https://issues.jboss.org/browse/ORG-1647 working again we might be able to drop most if not all of this custom publish.sh stuff and just rely on nexus.
Worth checking out IMO.
> 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 Juergen Zimmermann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15620?page=com.atlassian.jira.plugi... ]
Juergen Zimmermann updated JBIDE-15620:
---------------------------------------
Attachment: wrong-cdi-warnings.png
> 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
> 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