[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4703:
-------------------------------------
[~nickboldt][~jeffmaury] I have tried it with Jeff's project, it works as expected. But when I try ITests, project is not rebuilt, [~odockal] have experienced same behavior.
> Auto build is not working for maven project
> -------------------------------------------
>
> Key: JBDS-4703
> URL: https://issues.jboss.org/browse/JBDS-4703
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 12.0.0.AM1
> Environment: F27, F28, Win10
> Red Hat JBoss Developer Studio
> Version: 12.0.0.AM1
> Build id: AM1-v20180508-1631-B2428
> Build date: 20180508-1631
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: test.zip
>
>
> Auto build is not working.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-26016) javax.websocket is missing from default classpath entries of WildFly 12 Runtime
by Marco Del Percio (JIRA)
Marco Del Percio created JBIDE-26016:
----------------------------------------
Summary: javax.websocket is missing from default classpath entries of WildFly 12 Runtime
Key: JBIDE-26016
URL: https://issues.jboss.org/browse/JBIDE-26016
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.5.3.Final
Environment: Windows 7, Eclipse Oxygen.3a Release (4.7.3a), WildFly 12.0.0. Final
Reporter: Marco Del Percio
Priority: Minor
Attachments: javax.websocket.missing.png
When creating a new server instance based on WildFly 12 Runtime, the default classpath entries of such runtime do not include javax.websocket.
The workaround is to manually amend the default classpath entries for that runtime and add the missing module.
javax.websocket has always been there by default until WildFly 11 Runtime, I don't see why it shouldn't be there with WildFly 12 Runtime
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBDS-4703) Auto build is not working for maven project
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBDS-4703?page=com.atlassian.jira.plugin.... ]
Josef Kopriva commented on JBDS-4703:
-------------------------------------
[~nickboldt] - I think there was no error message in log, I will retest it tomorrow
- JDK 1.8 171, devstudio 12.0.0.AM1 B2428
- tycho was installed
> Auto build is not working for maven project
> -------------------------------------------
>
> Key: JBDS-4703
> URL: https://issues.jboss.org/browse/JBDS-4703
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: maven
> Affects Versions: 12.0.0.AM1
> Environment: F27, F28, Win10
> Red Hat JBoss Developer Studio
> Version: 12.0.0.AM1
> Build id: AM1-v20180508-1631-B2428
> Build date: 20180508-1631
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 12.0.0.GA
>
> Attachments: test.zip
>
>
> Auto build is not working.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months
[JBoss JIRA] (JBIDE-26015) write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-26015:
----------------------------------
Summary: write doc about using ccipush/pull scripts to manage Jenkins jobs on CCI
Key: JBIDE-26015
URL: https://issues.jboss.org/browse/JBIDE-26015
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, devdoc
Reporter: Nick Boldt
* get and build maven tool
* configure keystore
* jenkins crumbs
* set up bash scripts
* pull jobs (one by one or batch modes)
* edit jobs / save changes to github repo
* push jobs back to server (one by one or batch push mode)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 5 months