[JBoss JIRA] Commented: (JBDS-221) eclipse update manager for JBDS
by Nick Boldt (JIRA)
[ https://jira.jboss.org/jira/browse/JBDS-221?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBDS-221:
---------------------------------
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=269536 to discuss the option of warning people about the installation of unsigned jars (much the same way people are warned to accept a CA for signed jars).
As to the pwnage status, that's no longer a problem. 'Scuse my flippancy. :)
Signed jars mean different things to different providers (@ Eclipse, "contents are as described" vs. @ Red Hat, "contents are as described and were built following a strictly regimented process to ensure quality"), so for the moment, JBDS won't be doing signed jars, which means we can move forward with provisioning an https-auth'd update site for 2.0.1. For now, https will be a sufficient mechanism for ensuring what you see is what you get.
(We do build with a regimented, reproduceable process, but it's not yet aligned with one that will allow for signing... for now, anyway. More to come on that front in future.)
> eclipse update manager for JBDS
> -------------------------------
>
> Key: JBDS-221
> URL: https://jira.jboss.org/jira/browse/JBDS-221
> Project: Developer Studio
> Issue Type: Sub-task
> Components: Build
> Affects Versions: LATER
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 2.0.1, 2.1.0
>
> Attachments: tasktop-signup-1.png, tasktop-signup-2.png, tasktop-signup-3.png
>
>
> requires update manager to support password protected content.
> Need to verify that the info in the following thread is correct: http://dev.eclipse.org/newslists/news.eclipse.tools/msg49329.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Commented: (JBDS-221) eclipse update manager for JBDS
by Nick Boldt (JIRA)
[ https://jira.jboss.org/jira/browse/JBDS-221?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBDS-221:
---------------------------------
> This ticket contains two different requests which are handled by 2
> different team. I cannot split or clone this ticket.
As requested, I split the ticket into
[redhat.com #1001109] please install rpm-sign on Hudson slaves soavmg2, soavmg3, soavmg6
and
[redhat.com #1001114] please set up kerberos on Hudson slaves soavmg2, soavmg3, soavmg6
... then with perfect comedic timing, I was told:
> Hi Nick - We'll be handling the ticket, so there's no point in splitting
> it up. I'm merging back into #1000278.
Meanwhile, I've also been told that hudson isn't secure enough, so we're pwned atm:
> For signing, we need to use systems that are secured. At a minimum this
> means access only by those that will be doing the signing, corp kerberos
> authentication and strictly limited root access. As you know, the build
> systems aren't up to those standards so we'll need to find an alternative.
> eclipse update manager for JBDS
> -------------------------------
>
> Key: JBDS-221
> URL: https://jira.jboss.org/jira/browse/JBDS-221
> Project: Developer Studio
> Issue Type: Sub-task
> Components: Build
> Affects Versions: LATER
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 2.0.1, 2.1.0
>
> Attachments: tasktop-signup-1.png, tasktop-signup-2.png, tasktop-signup-3.png
>
>
> requires update manager to support password protected content.
> Need to verify that the info in the following thread is correct: http://dev.eclipse.org/newslists/news.eclipse.tools/msg49329.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBIDE-3986) Incorrect creation Smooks configuration file XML-to-Java
by Aliaksey Nis (JIRA)
Incorrect creation Smooks configuration file XML-to-Java
---------------------------------------------------------
Key: JBIDE-3986
URL: https://jira.jboss.org/jira/browse/JBIDE-3986
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: smooks
Affects Versions: 3.0.0.GA
Environment: WindowsXP SP2
JBoss Tools
Version: 3.0.0.GA
Build id: JBossTools-ALL-win32-3.0.0.GA-R200903040656-H10
JRE 1.5_08
Reporter: Aliaksey Nis
EXECUTE: Create Seam 2fp war project.
EXECUTE: Select it in Package Explorer, Right click. New > Other > Smooks Configuration file.
EXECUTE: Select name and this project, press next. Select XML-to-Java, press Finish.
FAILURE: Configuration file created incorrectly. In Source tab i see error - "can't load xml file". In Graph and Configuration tabs all buttons and links disabled(but not shown with gray color to mark them as disabled). So nothing can be clicked in newly created configuration file.
P.S. If created Java-to-Java file - all works.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years
[JBoss JIRA] Created: (JBIDE-3932) Seam runtime isn't checked as default if it is added using New Project Wizard or Project -> Preferences -> Seam Settings
by Anton Klimkovich (JIRA)
Seam runtime isn't checked as default if it is added using New Project Wizard or Project -> Preferences -> Seam Settings
-------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-3932
URL: https://jira.jboss.org/jira/browse/JBIDE-3932
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Seam
Affects Versions: 3.0.0.GA
Reporter: Anton Klimkovich
Priority: Minor
1.
EXECUTE: New -> Seam Web Project
EXECUTE: Press Add button on Seam Facet wizard
EXECUTE: Add seam 2.1.1GA runtime for example
EXECUTE: Open Preferences - > JBoss Tools -> Web -> Seam
FAILURE: Seam 2.1.1 runtime isn't checked as default
2.
EXECUTE: Create Seam 2.1 web project
EXECUTE: Open Preferences - > JBoss Tools -> Web -> Seam
EXECUTE: Delete Seam 2.1 runtime
EXECUTE: Select seam 2.1 project
EXECUTE: Preferences -> Seam Settings
EXECUTE: Press Add button and add seam 2.1.1GA runtime
EXECUTE: Open Preferences - > JBoss Tools -> Web -> Seam
FAILURE: Seam 2.1.1 runtime isn't checked as default
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years