You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tomee.apache.org by "Matthew Broadhead (JIRA)" <ji...@apache.org> on 2016/02/28 10:18:26 UTC

[jira] [Commented] (TOMEE-1720) tomee as a maven dependency

    [ https://issues.apache.org/jira/browse/TOMEE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170979#comment-15170979 ] 

Matthew Broadhead commented on TOMEE-1720:
------------------------------------------

i changed it to
{code:xml}
<dependency>
	<groupId>org.apache.openejb</groupId>
	<artifactId>tomee-plume-webapp</artifactId>
	<version>1.7.3</version>
	<type>pom</type>
	<scope>provided</scope>
</dependency>
{code}

but i get error
{noformat}
The type javax.el.ELException cannot be resolved. It is indirectly referenced from required .class files
{noformat}

> tomee as a maven dependency
> ---------------------------
>
>                 Key: TOMEE-1720
>                 URL: https://issues.apache.org/jira/browse/TOMEE-1720
>             Project: TomEE
>          Issue Type: Bug
>          Components: TomEE Core Server
>    Affects Versions: 1.7.3
>            Reporter: Matthew Broadhead
>
> Currently my projects in eclipse have the TomEE server runtime include on the build path.  this works fine but it is not very portable and upgrading requires changing the build path for every project rather than changing the version number in the pom.xml.
> Is it possible to include TomEE using Maven?  I tried adding 
> {code:xml}
> <dependency>
> 	<groupId>org.apache.openejb</groupId>
> 	<artifactId>tomee-plume-webapp</artifactId>
> 	<version>1.7.3</version>
> </dependency>
> {code}
> but it gives "Missing artifact org.apache.openejb:tomee-plume-webapp:jar:1.7.3"
> I have tried the tomee-maven-plugin but I prefer to be able to stop and start the server from eclipse and also the debugger is easier to set up.  Also eclipse starts all the projects together and integrates them.  (I suppose if tomee-maven-plugin is capable of all this I could try it again)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)