I've been trying, along with a couple of co-workers, to import OpenWebBeans into an eclipse environment and run the tests. I've encountered the mentioned issue:

[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-jetty-plugin' does not exist or no valid version could be found

when running:

mvn jetty:run -Pjetty

after having checked out the latest svn trunk and run:

mvn clean install
mvn clean package -Pjetty

Is it possible you have a local copy of maven-jetty-plugin?

We'd love to start helping with OpenWebBeans development, but we could really use some help getting a working environment set up and figuring out what we can do to help.

- Are all current work items in jira OWB? Are there some we can help with?
- What is the procedure to set up an environment to run the tests and do 
development
using eclipse? (i.e. what libs/levels need to be installed, are there project files we can import to generate a standard dev env, etc) - What are the current plans for handling the separation of JSR-330 and update the open web beans code to accommodate the changes? - Will we be making OWB dependency injection pluggable so folks can pick whatever implementation they want or will we be linking it in directly (regardless of whether we write or obtain the code)?

If you can help us get started, we'd love to help.

Paul J. Reder


On 08/16/2009 04:58 PM, Gurkan Erdogdu wrote:

PS: I had problems starting the guess sample with mvn clean package -Pjetty jetty 
run. Need to fix a few things in maven-scm now, and will look at it 
on>>thuesday. gn8!

I have separated guess/ project into three different modules

guess -->  for guess sample, removing ejb and jms parts

ejb-sample -->  using OpenEJB in Tomcat. Have to configure Tomcat with OpenEJB 
firstly. Then deploy it into Tomcat. It does not work on any other containers like 
Jetty.

jms-sample -->  jms injections. Have to deploy it into full blown Java EE server 
supporting JMS provider. JMS sample currently using "ConnectionFactory" as JMS 
Connection Factory JNDI. You can also change this with respect to application server JMS 
JNDI name policy via openwebbeans.properties

I run mvn clean package -Pjetty and mvn jetty:run -Pjetty. It works for me.

Please ensure that, you check in all recent changes from the svn, and

mvn clean install from root folder.

Thanks;

--Gurkan

----- Original Message ----
From: Gurkan Erdogdu<[email protected]>
To: [email protected]
Sent: Sunday, August 16, 2009 10:18:13 PM
Subject: Preparing for Release M3

Hi guys;

I want to release M3 in this week to include EJB functionality and couple of bug
fixes. Also adding more documentation.

WDYT?

Thanks;

--Gurkan




--
Paul J. Reder
-----------------------------------------------------------
"The strength of the Constitution lies entirely in the determination of each
citizen to defend it.  Only if every single citizen feels duty bound to do
his share in this defense are the constitutional rights secure."
-- Albert Einstein

Reply via email to