[JBoss JIRA] (JBIDE-15295) EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15295?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15295:
-------------------------------------
This is caused by the EAP zipped repo missing maven metadata about available versions
> EAP 6.1 maven repo not recognized for use with Java EE Web Project wizard
> -------------------------------------------------------------------------
>
> Key: JBIDE-15295
> URL: https://issues.jboss.org/browse/JBIDE-15295
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples
> Affects Versions: 4.1.0.Final
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 4.1.1.CR1
>
> Attachments: Maven_EAP61.png, Maven_warning.png, settings.xml
>
>
> For the Java EE Web Project wizard, the EAP 6.1 maven repo is not recognized as being a JBoss Enterprise Maven repository.
> The project states that it can be used with EAP 6 so I would assume this to include EAP 6.0 and 6.1.
> Attached are:
> * my settings.xml file, with profiles generated by JBDS 'Configure Maven Repositories'
> * screenshot of added EAP 6.1 maven repo
> * Screenshot of enterprise maven repo warning in Java EE Web Project wizard
--
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, 5 months
[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-13869:
------------------------------------
Hi [~mickael_istria], How is this suppose to work? Our favorite use case would be to: cd to integration-test folder and execute: {code} mvn clean verify -Prun-on-installed-application -Dtycho.surefire.runtimePath=/home/psrna/jbdevstudio-7.1.0.Beta1/studio/ {code}
Then I would expect that tycho installs our integration tests to the tycho.surefire.runtimePath and run them. So basically I should see JBDS screen/UI when running the tests. Right? But I didn't see anything similar ..
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13869
> URL: https://issues.jboss.org/browse/JBIDE-13869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test.
> 2) use something else than surefire to run the already built testsuites.
--
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, 5 months
[JBoss JIRA] (JBIDE-15796) Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15796?page=com.atlassian.jira.plugi... ]
Koen Aers resolved JBIDE-15796.
-------------------------------
Resolution: Rejected
> Deployment error: No servlet class has been specified for servlet javax.ws.rs.core.Application
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15796
> URL: https://issues.jboss.org/browse/JBIDE-15796
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.1.Beta1
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.1.1.CR1
>
> Attachments: forge-html5.server.log
>
>
> Deployment with error: No servlet class has been specified for servlet javax.ws.rs.core.Application.
> Prepare app in forge console:
> 1) new-project --named testp --type war
> 2) setup persistence (HIBERNATE, JBOSS_AS7)
> 3) scaffold-x setup --scaffoldType angularjs --overwrite
> 4) entity --named Customer
> 5) field string --named name
> Scaffold HTML5:
> * scaffold-x from Customer.java
> Build and deploy on the server.
> See server.log attached for more description.
> I assume this should work out of the box right?
--
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, 5 months