[JBoss JIRA] (JBIDE-13404) Support for Deltaspike 0.3 (0.4)
by Jaroslav Jankovič (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13404?page=com.atlassian.jira.plugi... ]
Jaroslav Jankovič updated JBIDE-13404:
--------------------------------------
Summary: Support for Deltaspike 0.3 (0.4) (was: Support for Deltaspike 0.4)
Description: At this moment, deltaspike tooling supports deltaspike release version 0.2 incubation. In 0.3 a change in secure module was made (declaration of SecurityExtension in META-INF/services/javax.enterprise.inject.spi.Extension) and tooling doesn't support it yet. This should be fixed (was: At this moment, deltaspike tooling supports deltaspike 0.3. However, the current version of deltaspike is 0.4. This should be supported as well.)
> Support for Deltaspike 0.3 (0.4)
> --------------------------------
>
> Key: JBIDE-13404
> URL: https://issues.jboss.org/browse/JBIDE-13404
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: CDI extensions
> Affects Versions: 4.0.0.Final
> Reporter: Jaroslav Jankovič
> Assignee: Viacheslav Kabanovich
> Fix For: 4.1.0.Alpha1
>
>
> At this moment, deltaspike tooling supports deltaspike release version 0.2 incubation. In 0.3 a change in secure module was made (declaration of SecurityExtension in META-INF/services/javax.enterprise.inject.spi.Extension) and tooling doesn't support it yet. This should be fixed
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12974 at 1/23/13 2:08 AM:
-------------------------------------------------------------
Sorry, Nick, I was on vacation last week.
Great job, thanks!
I have a couple of comments.
1. Where is org.jboss.tools.ui.bot.ext and org.jboss.tools.ui.bot.ext.test? The former was the number one reason we wanted this site :)
2. Yes, we're aware of the failures. I don't think we can have simple maven builds work everywhere in the near future. But perhaps we could at least change the tests so by default only a 100%-working subset will be run. I'll comment on the other JIRA.
3. Why deprecate coretests? That is not the same thing as integrationtests, right? coretests contain unit tests for all the components and I thought that's something we want to continue doing. Also, coretests update site is still set up in the parent pom by default, right?
-3.- 4. Could we have a mechanism in the parent pom to enable the integrationtests update site? Or maybe we could just add it to our root pom? Having it in parent pom seems cleaner. (But not on by default.)
Tomorrow I will try to use it using repo definition in my setting.xml locally.
was (Author: mmalina):
Sorry, Nick, I was on vacation last week.
Great job, thanks!
I have a couple of comments.
1. Where is org.jboss.tools.ui.bot.ext and org.jboss.tools.ui.bot.ext.test? The former was the number one reason we wanted this site :)
2. Yes, we're aware of the failures. I don't think we can have simple maven builds work everywhere in the near future. But perhaps we could at least change the tests so by default only a 100%-working subset will be run. I'll comment on the other JIRA.
3. Why deprecate coretests? That is not the same thing as integrationtests, right? coretests contain unit tests for all the components and I thought that's something we want to continue doing. Also, coretests update site is still set up in the parent pom by default, right?
3. Could we have a mechanism in the parent pom to enable the integrationtests update site? Or maybe we could just add it to our root pom? Having it in parent pom seems cleaner. (But not on by default.)
Tomorrow I will try to use it using repo definition in my setting.xml locally.
> add missing IUs to coretests and soatests sites
> -----------------------------------------------
>
> Key: JBIDE-12974
> URL: https://issues.jboss.org/browse/JBIDE-12974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.1.0.Alpha1
>
>
> The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content.
> [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Are there any other missing IUs you need on those sites?
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 1/23/13 12:42 AM:
--------------------------------------------------------------
New proposal from Nick, +1'd by Max:
{quote}
G:A:V
org.jboss.tools.targetplatforms : jbosstoolstarget-unified : 4.20.5.Final-SNAPSHOT
therefore these URLs would be produced:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget-uni...
{quote}
Build #12 is blue:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
Results here:
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2...
http://www.qa.jboss.com/binaries/RHDS/targetplatforms/jbdevstudiotarget/4...
(and similar URLs 4.21.3 and 4.30.0, too)
Nexus entries:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
(and similar URLs 4.21.3 and 4.30.0, too)
was (Author: nickboldt):
New proposal from Nick, +1'd by Max:
{quote}
G:A:V
org.jboss.tools.targetplatforms : jbosstoolstarget-unified : 4.20.5.Final-SNAPSHOT
therefore these URLs would be produced:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget-uni...
{quote}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-13361) Update version of GWT archetype in JBT 3 / JBDS 5 Central
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13361?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-13361.
-----------------------------------
Resolution: Done
You have to add Redhat Maven Repository (http://maven.repository.redhat.com/techpreview/all/).
That can be done using File>New>Other>JBoss Tools>Configure Maven Repositories, Quick Fix or by editing the settings.xml file.
> Update version of GWT archetype in JBT 3 / JBDS 5 Central
> ---------------------------------------------------------
>
> Key: JBIDE-13361
> URL: https://issues.jboss.org/browse/JBIDE-13361
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, maven
> Affects Versions: 3.3.2
> Environment: JBDS 5.0.2.CR2 H238
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 3.3.2
>
>
> I started testing JBDS 5.0.2 and found out I cannot run mvn package on the GWT project from JBoss Central.
> I thought it was using the same mechanism as JBDS 6, but apparently not. And the archetype version is set to org.jboss.errai.archetypes:jboss-errai-kitchensink-archetype:2.0.0.Final while the current version in JBDs 6 is 2.1.1.Final. Can we update it?
> The 2.0.0.Final gives this error when trying to run Maven Build... clean package:
> {code}
> [INFO] [ERROR] Errors in '/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated/org/jboss/tools/gwt/kitchensink/client/shared/_MemberValidatorImpl.java'
> [INFO] [ERROR] Line 430: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Line 452: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Line 477: The method validate(GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, V, ConstraintValidator<A,? super V>, ConstraintDescriptorImpl<A>, Class<?>[]) in the type AbstractGwtSpecificValidator<Member> is not applicable for the arguments (GwtValidationContext<T>, Set<ConstraintViolation<T>>, Member, String, SizeValidatorForMap, ConstraintDescriptorImpl<Size>, Class<?>[])
> [INFO] [ERROR] Cannot proceed due to previous errors
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 33.994s
> [INFO] Finished at: Wed Jan 09 15:11:42 CET 2013
> [INFO] Final Memory: 27M/205M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.codehaus.mojo:gwt-maven-plugin:2.4.0:compile (default) on project gwt-kitchensink: Command [[
> [ERROR] /bin/sh -c /Library/Java/JavaVirtualMachines/jdk1.7.0_07.jdk/Contents/Home/jre/bin/java -Xmx512m -classpath /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/java:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/resources:/Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/classes:/Users/rasp/.m2/repository/javax/enterprise/cdi-api/1.0-SP4/cdi-api-1.0-SP4.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/interceptor/jboss-interceptors-api_1.1_spec/1.0.1.Final/jboss-interceptors-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/javax/inject/javax.inject/1/javax.inject-1.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/transaction/jboss-transaction-api_1.1_spec/1.0.1.Final/jboss-transaction-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/annotation/jboss-annotations-api_1.1_spec/1.0.1.Final/jboss-annotations-api_1.1_spec-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ws/rs/jboss-jaxrs-api_1.1_spec/1.0.0.Final/jboss-jaxrs-api_1.1_spec-1.0.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.1.Final/hibernate-jpa-2.0-api-1.0.1.Final.jar:/Users/rasp/.m2/repository/org/jboss/spec/javax/ejb/jboss-ejb-api_3.1_spec/1.0.2.Final/jboss-ejb-api_3.1_spec-1.0.2.Final.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-validator/4.2.0.Final/hibernate-validator-4.2.0.Final-sources.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-bus/2.0.0.Final/errai-bus-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-common/2.0.0.Final/errai-common-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/reflections/reflections/2.0.0.Final/reflections-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/guava/guava/10.0.1/guava-10.0.1.jar:/Users/rasp/.m2/repository/com/google/code/findbugs/jsr305/1.3.9/jsr305-1.3.9.jar:/Users/rasp/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar:/Users/rasp/.m2/repository/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-marshalling/2.0.0.Final/errai-marshalling-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/inject/guice/3.0/guice-3.0.jar:/Users/rasp/.m2/repository/aopalliance/aopalliance/1.0/aopalliance-1.0.jar:/Users/rasp/.m2/repository/org/mvel/mvel2/2.1.Beta8/mvel2-2.1.Beta8.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-api/1.6.1/slf4j-api-1.6.1.jar:/Users/rasp/.m2/repository/org/slf4j/slf4j-log4j12/1.6.1/slf4j-log4j12-1.6.1.jar:/Users/rasp/.m2/repository/log4j/log4j/1.2.16/log4j-1.2.16.jar:/Users/rasp/.m2/repository/org/javassist/javassist/3.15.0-GA/javassist-3.15.0-GA.jar:/Users/rasp/.m2/repository/org/jboss/errai/io/netty/netty/4.0.0.Alpha1.errai.r1/netty-4.0.0.Alpha1.errai.r1.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-ioc/2.0.0.Final/errai-ioc-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-codegen/2.0.0.Final/errai-codegen-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-tools/2.0.0.Final/errai-tools-2.0.0.Final.jar:/Users/rasp/.m2/repository/hsqldb/hsqldb/1.8.0.7/hsqldb-1.8.0.7.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-cdi-client/2.0.0.Final/errai-cdi-client-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-javax-enterprise/2.0.0.Final/errai-javax-enterprise-2.0.0.Final.jar:/Users/rasp/.m2/repository/org/jboss/errai/errai-weld-integration/2.0.0.Final/errai-weld-integration-2.0.0.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar:/Users/rasp/.m2/repository/org/hibernate/hibernate-jpamodelgen/1.1.1.Final/hibernate-jpamodelgen-1.1.1.Final.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-user/2.4.0/gwt-user-2.4.0.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA.jar:/Users/rasp/.m2/repository/javax/validation/validation-api/1.0.0.GA/validation-api-1.0.0.GA-sources.jar:/Users/rasp/.m2/repository/com/google/gwt/gwt-dev/2.4.0/gwt-dev-2.4.0.jar com.google.gwt.dev.Compiler -gen /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/target/.generated -logLevel INFO -style OBF -war /Users/rasp/jbossqa/JBDS/5.0.2/workspace-eap-238/gwt-kitchensink/src/main/webapp -localWorkers 4 org.jboss.tools.gwt.kitchensink.KitchenSink
> [ERROR] ]] failed with status 1
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I tried doing this in JBDS 6 with the newer version and it worked for me. Then I removed my whole local maven repo and tried again in JBDS 5.0.2 and now it works. Something is wrong here - the idea of maven is that it should always get the right dependencies, no?
--
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
13 years, 2 months
[JBoss JIRA] (JBIDE-12974) add missing IUs to coretests and soatests sites
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12974?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-12974:
---------------------------------------
Sorry, Nick, I was on vacation last week.
Great job, thanks!
I have a couple of comments.
1. Where is org.jboss.tools.ui.bot.ext and org.jboss.tools.ui.bot.ext.test? The former was the number one reason we wanted this site :)
2. Yes, we're aware of the failures. I don't think we can have simple maven builds work everywhere in the near future. But perhaps we could at least change the tests so by default only a 100%-working subset will be run. I'll comment on the other JIRA.
3. Why deprecate coretests? That is not the same thing as integrationtests, right? coretests contain unit tests for all the components and I thought that's something we want to continue doing. Also, coretests update site is still set up in the parent pom by default, right?
3. Could we have a mechanism in the parent pom to enable the integrationtests update site? Or maybe we could just add it to our root pom? Having it in parent pom seems cleaner. (But not on by default.)
Tomorrow I will try to use it using repo definition in my setting.xml locally.
> add missing IUs to coretests and soatests sites
> -----------------------------------------------
>
> Key: JBIDE-12974
> URL: https://issues.jboss.org/browse/JBIDE-12974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing, updatesite
> Affects Versions: 4.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.1.0.Alpha1
>
>
> The coretests [3] and soatests [4] sites are missing requirements/dependencies such as org.jboss.tools.ui.bot.ext. For JBDS 6.1 / 7.0, that missing dep can be added if you open a JIRA and specify what needs to be added. I might have to create a new feature to wrap the missing content.
> [3] http://download.jboss.org/jbosstools/updates/nightly/coretests/trunk/
> [4] http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk/
> Are there any other missing IUs you need on those sites?
--
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
13 years, 2 months