-
1. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
sboscarine Jul 28, 2010 2:02 PM (in response to wangliyu)Hello Wang,
I'm a community volunteer on the archetypes project. Thank you so much for pointing this out. I've apologize for missing the Servlet API. That definitely needs to be in there. It will go in the next release, which will be available very soon. We have some exciting additions for the Java EE archetype (JBossAS/Glassfish) coming out with that release as well.
Thank you for also for pointing out the EL 2.0 addition. I'll test it out. If it works as expected, I'll put it in the next release as well. If not, I'll post back here to discuss.
Once the new archetype is ready (hopefully in a few days), I will update this thread.
Comments like this are greatly helpful. We will get a new release out quickly and hopefully it will be put to good use by you and others.
Thanks Again!
-
2. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
wangliyu Jul 28, 2010 2:48 PM (in response to wangliyu)I'm also trying to use Gradle in my proj, I'm using Maven and trying to like it and always failed, I looked at Gradle, it seems a lot better than Maven (except the mvn archetype:generate part), I'm wondering if you could include a build.gradle in archetype, that will be better.
-
3. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
sboscarine Jul 28, 2010 4:37 PM (in response to wangliyu)
Wang Liyu wrote on Jul 28, 2010 14:48:
I'm also trying to use Gradle in my proj, I'm using Maven and trying to like it and always failed, I looked at Gradle, it seems a lot better than Maven (except the mvn archetype:generate part), I'm wondering if you could include a build.gradle in archetype, that will be better.Hello Wang,
If there is demand, it can be done. However, I would first ask why. What does Gradle bring to the table? I am not familiar with Gradle and would be interested to learn what I am missing. If we can seed a discussion as to the pros and cons of Gradle, we could definitely get some movement on integrating it.
Thank you,
Steven -
4. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
mstruk.strukelj.parsek.net Aug 17, 2010 11:40 AM (in response to wangliyu)Here's one interesting take on Gradle: http://community.jboss.org/wiki/Gradlewhy
-
5. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
wangliyu Aug 20, 2010 2:08 PM (in response to wangliyu)Hi, can you add arquillian test case in the archetypes?
-
6. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
sboscarine Aug 20, 2010 2:47 PM (in response to wangliyu)Hello Wang,
We have had Arquillian Test cases in trunk for awhile now. Right now we're being held up by some missing dependencies in Nexus for the Arquillian JBoss libraries.The newest version is supports glassfish and Arquillian. The glassfish version is working great. The JBoss AS 6.0.0.M4 Arquillian tests are what's preventing us from doing a full release.
We're exciting about the new release and can't wait to get it in your hands...hopefully very soon.
Thanks!
Steven -
7. Re: Weld Maven artifact Tomcat bug and replace the EL2.1 with JBoss EL 2.0.0GA
wangliyu Aug 23, 2010 8:46 AM (in response to wangliyu)I have tried to add JBossAS6M4 remote test case into my project and found it can't talk to the Server, It first missing jboss ejb3.1 from the maven repo and I managed to get that work and it reported failed arquillianBeforeSuite (org.jboss.arquillian.impl.event.FiredEventException: org.jboss.arquillian.spi.LifecycleException: Could not connect to container), it seems it can't talk to the JBossAS6M4 for some reason.
I found that the Arquillian document is not accurate, and there is a big API change in the arquillian alpha3 --- the ShrinkWrap.create() parameters order changed, this is bad.
anyway, I'll check out the latest version from the trunk and see if that helps. Thanks a lot.