August 2011 - jboss-user - Jboss List Archives

[Beginner's Corner] - persistence unit Exception while publishing (Jboss AS7 and OpenJPA)

by Ido Barash

Ido Barash [http://community.jboss.org/people/ibarash] created the discussion "persistence unit Exception while publishing (Jboss AS7 and OpenJPA)" To view the discussion, visit: http://community.jboss.org/message/619155#619155 -------------------------------------------------------------- Hello, I am new to JBoss, and I just installed the new AS7. I am using Java 1.6, and OpenJPA 2.1 I managed to define my data-source, connected it with my jndi, everything looks fine. When I try to publish, I get the following exeption: 16:27:32,333 ERROR org.jboss.msc.service.fail org.jboss.msc.service.fail (MSC service thread 1-6) MSC00001: Failed to start service jboss.deployment.unit."advisor-server.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."advisor-server.war".INSTALL: Failed to process phase INSTALL of deployment "advisor-server.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) http://community.jboss.org/message/619155#619155#619155/:1.6.0_24 persistence unit Exception while publishing (Jboss AS7 and OpenJPA) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) http://community.jboss.org/message/619155#619155#619155/:1.6.0_24 persistence unit Exception while publishing (Jboss AS7 and OpenJPA) at java.lang.Thread.run(Thread.java:662) http://community.jboss.org/message/619155#619155#619155/:1.6.0_24 persistence unit Exception while publishing (Jboss AS7 and OpenJPA) Caused by: java.lang.NullPointerException at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addProviderProperties(PersistenceUnitDeploymentProcessor.java:346) at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.addPuService(PersistenceUnitDeploymentProcessor.java:253) at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.handleWarDeployment(PersistenceUnitDeploymentProcessor.java:164) at org.jboss.as.jpa.processor.PersistenceUnitDeploymentProcessor.deploy(PersistenceUnitDeploymentProcessor.java:94) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) I put openjpa-all-2.1.0.jar in standalone\lib folder. my persistence.xml (located at the META-INF): Can you please help me? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619155#619155] Start a new discussion in Beginner's Corner at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

1
1
0 / 0

[IronJacamar] - Validator problems

by Martin Phillips

Martin Phillips [http://community.jboss.org/people/mphillip] created the discussion "Validator problems" To view the discussion, visit: http://community.jboss.org/message/619017#619017 -------------------------------------------------------------- Hi guys, I've been having a go at running the validator using the standalone ironjackamar and have run into a bit of a problem (on both windows and linux). Firstly, the JEE classes are not in the classpath for the validator: C:\jboss.ironjackamar\ironjacamar-1.0.0.Final\doc\validator>java -classpath ..\..\lib\ironjacamar-validator-cli.jar;..\. .\lib\ironjacamar-common-spi.jar;..\..\lib\jboss-logging.jar;..\..\lib\jboss-common-core.jar;..\..\lib\ironjacamar-spec- api.jar;..\..\lib\papaki-core.jar;..\..\lib\javassist.jar;..\..\lib\ironjacamar-common-impl.jar;..\..\lib\ironjacamar-co mmon-impl-papaki.jar;..\..\lib\ironjacamar-common-api.jar;..\..\lib\ironjacamar-validator.jar org.jboss.jca.validator.cl i.Main c:\test\MQRA\7.0.1-noclasspath\wmq.jmsra.rar Exception in thread "main" java.lang.NoClassDefFoundError: javax/jms/JMSException at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:247) at org.jboss.jca.validator.Validation.createResourceAdapter(Validation.java:256) at org.jboss.jca.validator.Validation.validate(Validation.java:155) at org.jboss.jca.validator.cli.Main.main(Main.java:92) Caused by: java.lang.ClassNotFoundException: javax.jms.JMSException at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) ... 5 more I added them in using the JEE jar I used to create the RA and then ran into the following exception: C:\jboss.ironjackamar\ironjacamar-1.0.0.Final\doc\validator>java -classpath ..\..\lib\ironjacamar-validator-cli.jar;..\. .\lib\ironjacamar-common-spi.jar;..\..\lib\jboss-logging.jar;..\..\lib\jboss-common-core.jar;..\..\lib\ironjacamar-spec- api.jar;..\..\lib\papaki-core.jar;..\..\lib\javassist.jar;..\..\lib\ironjacamar-common-impl.jar;..\..\lib\ironjacamar-co mmon-impl-papaki.jar;..\..\lib\ironjacamar-common-api.jar;..\..\lib\ironjacamar-validator.jar;C:\k000\src\com.ibm.mq.con nector\src\3rdparty\j2ee.jar org.jboss.jca.validator.cli.Main c:\test\MQRA\7.0.1-noclasspath\wmq.jmsra.rar java.io.IOException: . can't be created at org.jboss.jca.validator.Validation.validate(Validation.java:171) at org.jboss.jca.validator.cli.Main.main(Main.java:92) Validation unknown On linux I was running as root, so there should be no file permission issues. Any thoughts? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619017#619017] Start a new discussion in IronJacamar at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

2
3
0 / 0

[JBoss Cache] - Re: is this a good use for jboss cache

by Venkatesh Balaji

Venkatesh Balaji [http://community.jboss.org/people/venquet] created the discussion "Re: is this a good use for jboss cache" To view the discussion, visit: http://community.jboss.org/message/619104#619104 -------------------------------------------------------------- Hi Robert, Just for an update, we have implemented this and working perfectly for last one year! Rgds Balaji -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619104#619104] Start a new discussion in JBoss Cache at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

1
0
0 / 0

[jBPM] - Re: In memory TaskClient without Mina or JMS

by Franklin Antony

Franklin Antony [http://community.jboss.org/people/frankee787] created the discussion "Re: In memory TaskClient without Mina or JMS" To view the discussion, visit: http://community.jboss.org/message/619069#619069 -------------------------------------------------------------- Dear Daniele, In the patched jar there is a class called *DefaultEscalatedDeadlineHandler* After the *deadline.setEscalated(true);* Should it include *deadline.setEscalated(true);* Some how the boolean value is not getting persisted in the table. I can see *SELECT* queries such as follows trying to get the Deadline and Potentials owners, but nothing with *INSERTS/UPDATES* Hibernate: select reassignme0_.Escalation_Reassignments_Id as Escalation2_1_, reassignme0_.id as id1_, reassignme0_.id as id10_0_ from Reassignment reassignme0_ where reassignme0_.Escalation_Reassignments_Id=? Hibernate: select potentialo0_.task_id as task1_1_, potentialo0_.entity_id as entity2_1_, organizati1_.id as id6_0_, organizati1_.DTYPE as DTYPE6_0_ from Reassignment_potentialOwners potentialo0_ left outer join OrganizationalEntity organizati1_ on potentialo0_.entity_id=organizati1_.id where potentialo0_.task_id=? Hibernate: select task0_.id as id11_3_, task0_.allowedToDelegate as allowedT2_11_3_, task0_.taskInitiator_id as taskIni23_11_3_, task0_.priority as priority11_3_, task0_.activationTime as activati4_11_3_, task0_.actualOwner_id as actualO24_11_3_, task0_.createdBy_id as createdBy25_11_3_, task0_.createdOn as createdOn11_3_, task0_.documentAccessType as document6_11_3_, task0_.documentContentId as document7_11_3_, task0_.documentType as document8_11_3_, task0_.expirationTime as expirati9_11_3_, task0_.faultAccessType as faultAc10_11_3_, task0_.faultContentId as faultCo11_11_3_, task0_.faultName as faultName11_3_, task0_.faultType as faultType11_3_, task0_.outputAccessType as outputA14_11_3_, task0_.outputContentId as outputC15_11_3_, task0_.outputType as outputType11_3_, task0_.parentId as parentId11_3_, task0_.previousStatus as previou18_11_3_, task0_.processInstanceId as process19_11_3_, task0_.skipable as skipable11_3_, task0_.status as status11_3_, task0_.workItemId as workItemId11_3_, user1_.id as id6_0_, user2_.id as id6_1_, user3_.id as id6_2_ from Task task0_ left outer join OrganizationalEntity user1_ on task0_.taskInitiator_id=user1_.id left outer join OrganizationalEntity user2_ on task0_.actualOwner_id=user2_.id left outer join OrganizationalEntity user3_ on task0_.createdBy_id=user3_.id where task0_.id=? Hibernate: select deadline0_.id as id4_0_, deadline0_.deadline_date as deadline2_4_0_, deadline0_.escalated as escalated4_0_ from Deadline deadline0_ where deadline0_.id=? Any hints or ideas on this problem Regards, Franklin * * -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619069#619069] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

1
0
0 / 0

[JNDI and Naming] - Re: JBoss As 7 problem with jndi port

by Paulo Feal

Paulo Feal [http://community.jboss.org/people/paulinux] created the discussion "Re: JBoss As 7 problem with jndi port" To view the discussion, visit: http://community.jboss.org/message/619047#619047 -------------------------------------------------------------- Este es el *boot.log* al arrancar Jboss as 7: 12:14:11,696 INFO [org.jboss.modules] JBoss Modules version 1.0.1.GA 12:14:12,067 INFO [org.jboss.msc] JBoss MSC version 1.0.0.GA 12:14:12,125 INFO [org.jboss.as] JBoss AS 7.0.0.Final "Lightning" starting 12:14:12,127 DEBUG [org.jboss.as.config] Configured system properties: file.encoding = UTF-8 file.encoding.pkg = sun.io file.separator = / java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment java.awt.printerjob = sun.print.PSPrinterJob java.class.path = /opt/jboss-as-7.0.0.Final/jboss-modules.jar java.class.version = 50.0 java.endorsed.dirs = /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/endorsed java.ext.dirs = /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/ext:/usr/java/packages/lib/ext java.home = /usr/lib/jvm/java-6-sun-1.6.0.20/jre java.io.tmpdir = /tmp java.library.path = /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/amd64/server:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/amd64:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name = Java(TM) SE Runtime Environment java.runtime.version = 1.6.0_20-b02 java.specification.name = Java Platform API Specification java.specification.vendor = Sun Microsystems Inc. java.specification.version = 1.6 java.util.logging.manager = org.jboss.logmanager.LogManager java.vendor = Sun Microsystems Inc. java.vendor.url = http://java.sun.com/ http://java.sun.com/ java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi http://java.sun.com/cgi-bin/bugreport.cgi java.version = 1.6.0_20 java.vm.info = mixed mode java.vm.name = Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name = Java Virtual Machine Specification java.vm.specification.vendor = Sun Microsystems Inc. java.vm.specification.version = 1.0 java.vm.vendor = Sun Microsystems Inc. java.vm.version = 16.3-b01 javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory javax.xml.validation.SchemaFactory: http://www.w3.org/2001/XMLSchema http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory javax.xml.xpath.XPathFactory: http://java.sun.com/jaxp/xpath/dom http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory jboss.home.dir = /opt/jboss-as-7.0.0.Final jboss.host.name = pfeal jboss.modules.dir = /opt/jboss-as-7.0.0.Final/modules jboss.node.name = pfeal jboss.qualified.host.name = pfeal jboss.server.base.dir = /opt/jboss-as-7.0.0.Final/standalone jboss.server.config.dir = /opt/jboss-as-7.0.0.Final/standalone/configuration jboss.server.data.dir = /opt/jboss-as-7.0.0.Final/standalone/data jboss.server.deploy.dir = /opt/jboss-as-7.0.0.Final/standalone/data/content jboss.server.log.dir = /opt/jboss-as-7.0.0.Final/standalone/log jboss.server.name = pfeal jboss.server.temp.dir = /opt/jboss-as-7.0.0.Final/standalone/tmp line.separator = logging.configuration = file:/opt/jboss-as-7.0.0.Final/standalone/configuration/logging.properties module.path = /opt/jboss-as-7.0.0.Final/modules org.jboss.boot.log.file = /opt/jboss-as-7.0.0.Final/standalone/log/boot.log org.jboss.resolver.warning = true org.xml.sax.driver = __redirected.__XMLReaderFactory os.arch = amd64 os.name = Linux os.version = 2.6.32-33-generic path.separator = : sun.arch.data.model = 64 sun.boot.class.path = /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/resources.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/rt.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/jsse.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/jce.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/charsets.jar:/usr/lib/jvm/java-6-sun-1.6.0.20/jre/classes sun.boot.library.path = /usr/lib/jvm/java-6-sun-1.6.0.20/jre/lib/amd64 sun.cpu.endian = little sun.cpu.isalist = sun.desktop = gnome sun.io.unicode.encoding = UnicodeLittle sun.java.launcher = SUN_STANDARD sun.jnu.encoding = UTF-8 sun.management.compiler = HotSpot 64-Bit Server Compiler sun.os.patch.level = unknown sun.rmi.dgc.client.gcInterval = 3600000 sun.rmi.dgc.server.gcInterval = 3600000 user.country = ES user.dir = /opt/jboss-as-7.0.0.Final/bin user.home = /home/pfeal user.language = es user.name = pfeal user.timezone = Europe/Madrid 12:14:13,274 INFO [org.jboss.as] creating http management service using network interface (management) port (9990) securePort (-1) 12:14:13,287 INFO [org.jboss.as.logging] Removing bootstrap log handlers Any idea? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/619047#619047] Start a new discussion in JNDI and Naming at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

1
0
0 / 0

[JBoss Microcontainer] - Non-daemon threads running when using Deploymentmanager in JBoss 6

by Bernd Zeitler

Bernd Zeitler [http://community.jboss.org/people/Frito] created the discussion "Non-daemon threads running when using Deploymentmanager in JBoss 6" To view the discussion, visit: http://community.jboss.org/message/618834#618834 -------------------------------------------------------------- I used the deployment manager to realize deployment/undeployment with ANT. This example code worked fine with JBoss 5 but has problems with JBoss 6: final Context ctx = new InitialContext(); final DeploymentManager dm = (DeploymentManager) ctx.lookup("DeploymentManager"); dm.distribute("thejar", new URL("file:./testdist/hello.jar"), true).run(); dm.prepare("thejar").run(); dm.start("thejar"); dm.stop("thejar").run(); dm.remove("thejar"); In real life, the deployment progress is evaluated and deployment status is checked after every call to the deployment manager ;) Deployment and undeployment still work as expected, but this code now leaves two non-daemon threads running. Both are threads from jboss remoting, a worker thread and an accecptor thread. Did I miss something? Regards, Bernd -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/618834#618834] Start a new discussion in JBoss Microcontainer at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

2
2
0 / 0

[jBPM] - JBPM - Process Image - API

by Robson Watt

Robson Watt [http://community.jboss.org/people/robstor] created the discussion "JBPM - Process Image - API" To view the discussion, visit: http://community.jboss.org/message/618925#618925 -------------------------------------------------------------- Hi all.. I need recovery, using the jbpm api, the process image (jpg) and the gpd.xml.. Someone know how I could do it? Context: I need show in a web application where is a specific task.. If this task has errors paint it in red (for example) Thank you for your help.. Best Regards. Robson -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/618925#618925] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 4 months

2
1
0 / 0

[Snowdrop] - JBoss 6 + Snowdrop2 + Red5

by Bruno Santos

Bruno Santos [http://community.jboss.org/people/bmsantos] created the discussion "JBoss 6 + Snowdrop2 + Red5" To view the discussion, visit: http://community.jboss.org/message/605008#605008 -------------------------------------------------------------- Greetings! I'm trying to make Red5 (1.0 RC1) Spring WAR run under JBoss 6 AS. For that I'm using the latest Snowdrop2 Spring Deployer (2.0.0-M1-SP1). One of the errors that I got was that ther org.jboss.virtual.VFS file was not found in the classpath. JBoss 6 AS includes the jboss-vfs.jar that includes the or.jboss.vfs.VFS class in it. Is there a work around for this issue? Thanks -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/605008#605008] Start a new discussion in Snowdrop at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 5 months

4
20
0 / 0

[JBoss Tools] - SEAM BIRT Integration Scripted DS report works when embedded, but not when designType=run or frameset

by pretorga

pretorga [http://community.jboss.org/people/pretorga] created the discussion "SEAM BIRT Integration Scripted DS report works when embedded, but not when designType=run or frameset" To view the discussion, visit: http://community.jboss.org/message/618671#618671 -------------------------------------------------------------- Hi I have a BIRT report that uses a Scripted DataSource in a SEAM web application. When I embed my report like this: <ui:define name="body"> <rich:panel> <b:birt designType="embed" designName="/report/register_entries.rptdesign" embeddable="true"> <b:param name="reportTitle" value="Register Entries" /> </b:birt> </rich:panel> </ui:define> ... the report runs fine. Report.initialize() as well as open() and fetch() methods are called. When I try to use the frameset viewer, or try to use designType=run to create pdf/xls like this: <b:birt xmlns:ui=" http://java.sun.com/jsf/facelets http://java.sun.com/jsf/facelets" xmlns:s=" http://jboss.com/products/seam/taglib http://jboss.com/products/seam/taglib" xmlns:b=" http://jboss.com/products/seam/birt http://jboss.com/products/seam/birt" designType="frameset" designName="/report/register_entries.rptdesign" title="Register Entries Frameset Report"> </b:birt> and <b:birt xmlns:ui=" http://java.sun.com/jsf/facelets http://java.sun.com/jsf/facelets" xmlns:s=" http://jboss.com/products/seam/taglib http://jboss.com/products/seam/taglib" xmlns:b=" http://jboss.com/products/seam/birt http://jboss.com/products/seam/birt" designType="run" format="pdf" designName="/report/register_entries.rptdesign" title="Register Entries PDF Report"/> I get my data from a SEAM component in the open() of the Scripted DataSet as follows: var reportDataProvider = Packages.org.jboss.seam.Component.getInstance("reportDataProvider", true)' When using designType frameset or run, reportDataProvider is null. I'm not entirely sure why. My problem seems to be the inverse of this http://community.jboss.org/message/326971#326971 http://community.jboss.org/message/326971#326971 Any ideas? -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/618671#618671] Start a new discussion in JBoss Tools at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&cont...]

13 years, 5 months

2
2
0 / 0

[JBoss Tools] - m2e(clipse)-wtp 0.13.1 : Back to the m2e marketplace

by Fred Bricon

Fred Bricon [http://community.jboss.org/people/fbricon] modified the blog post: "m2e(clipse)-wtp 0.13.1 : Back to the m2e marketplace" To view the blog post, visit: http://community.jboss.org/community/tools/blog/2011/08/01/m2eclipse-wtp-... -------------------------------------------------------------- As I mentioned in the previous blog post ( http://community.jboss.org/en/tools/blog/2011/06/23/m2eclipse-wtp-0130-ne... http://community.jboss.org/en/tools/blog/2011/06/23/m2eclipse-wtp-0130-ne...), m2e-wtp had to be pulled out of the m2e marketplace, as it forced its installation for all non-WTP systems. In order to fix this issue, the code responsible for generating the MANIFEST.MF for all projects had to be integrated into the mavenarchiver feature. That means m2e-wtp 0.13.1 now requires the installation of mavenarchiver from the m2e-extras update site. It will be discovered automatically from the new m2e-wtp update site, hosted by Red Hat, so it will be completely transparent for new users. However, please note that the mavenarchiver feature replaces the pomproperties one, so the *pomproperties must be uninstalled before upgrading m2e-wtp*. Thus, the preferred ways to install m2e-wtp remain : 1) Import existing Java EE projects into the workspace; You'll be proposed to install the m2e-wtp plugin : http://community.jboss.org/servlet/JiveServlet/showImage/38-4023-16816/m2... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4023-1681... click on Finish and the installation will proceed. Your projects will be imported but the workspace will have to be restarted. 2) Go to Window > Preferences > Maven > Discovery and click on "Open catalog". Select m2e-wtp and proceed with the installation. http://community.jboss.org/servlet/JiveServlet/showImage/38-4023-16814/m2... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4023-1681... 3) Old school installation : Use this JBoss / Red Hat update site : http://dev.eclipse.org/mhonarc/lists/m2e-users/msg00938.html http://download.jboss.org/jbosstools/updates/m2eclipse-wtp/ While reviewing the installation details, you can see that mavenarchiver 0.14.0 will be found and installed automatically (provided there is not a more recent version already installed) http://community.jboss.org/servlet/JiveServlet/showImage/38-4023-16815/m2... http://community.jboss.org/servlet/JiveServlet/downloadImage/38-4023-1681... Other that the changes necessary to reinstate m2e-wtp to the m2e marketplace, There is only one other bugfix in 0.13.1, which fixes deployment of war archives overlays in Windows ( https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&versi... https://issues.sonatype.org/secure/ReleaseNote.jspa?projectId=10310&versi...). *UPDATE (03/08/2011) :* m2e-wtp is now also available from the http://marketplace.eclipse.org/content/maven-integration-eclipse-wtp Eclipse Marketplace. However, it seems some people are unable to install it directly. Please note that m2e-wtp requires m2e 1.0. So, if it's not installed already, Eclipse must be able to find it in the available update sites. m2e can be installed from either http://download.eclipse.org/releases/indigo http://download.eclipse.org/releases/indigo (for Indigo) or http://download.eclipse.org/technology/m2e/releases/ http://download.eclipse.org/technology/m2e/releases/ (for Helios and Indigo). The change in m2e's namespace (org.maven.ide -> org.eclipse.m2e) between m2e 0.12.x and 1.0 renders updates impossible from m2e-wtp 0.12.x to 0.13.x. Thus you have no choice but to uninstall m2e < 1.0 and m2e-wtp < 0.13 before proceeding with m2e-wtp 0.13.x's installation. (I hope I'm clear enough :-)) Enjoy, Fred. https://twitter.com/#%21/fbricon https://twitter.com/#!/fbricon -------------------------------------------------------------- Comment by going to Community [http://community.jboss.org/community/tools/blog/2011/08/01/m2eclipse-wtp-...]

13 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-user August 2011