Resource references across different projects are not supported by
design. This is definitely a feature.
Resource references across different modules of the same project are not
supported because of eclipse workspace limitations -- there is no easy
way to properly support incremental build. If so
On 09/25/2012 12:45 PM, Igor Fedorenko wrote:
Resource references across different projects are not supported by
design. This is definitely a feature.
Resource references across different modules of the same project are not
supported because of eclipse workspace limitations -- there is no easy
w
Hello,
first let me thanks the m2e* team for the great job. I work on a rather large
project organized as follow:
-EAR
-EJB A1
-EJB A2
-WAR A3
-EJB C1
-EJB C2
-WAR C3
-EJB C1
-EJB C2
-WAR C3
Developers usually only work on one or two projects. Say EJB A2 and WAR A3. The
other dependencies
Import of nested projects is not a problem, m2e had this for ages. The
problem is proper representation of multi-module maven projects in
eclipse workspace, where each module is really a sub-directory of the
same project with different configuration.
--
Regards,
Igor
On 12-09-25 8:00 AM, Rafał K
m2e-wtp doesn't do any deployment by itself. This is the server adapter
responsibility to unpack archives during deployment. I *think*, you should
ask on https://forums.oracle.com/forums/forum.jspa?forumID=578 or whatever
place you can find support for the glassfish server adapter (let me know if
That url is configurable if you specify (in eclipse.ini):
-Dm2e.discovery.url=/some/url/
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=337912.
/Anders
On Mon, Sep 24, 2012 at 2:26 AM, Benson Margulies wrote:
> On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl wrote:
>> I automated everything
Thanks for the quick answer. I will ask the glassfish plugin team but just to
be sure that I am clear. The problem occurs as soon as one of the projects is
closed.
I assume that the default policy in that case is to use the jar instead of a
directory. Are you aware of such a rule?
Steve
Thanks
Platform: debian testing ("wheezy"),
eclipse 3.8.0,
m2e 0.12.1.20110112-1712 (installed from
http://m2eclipse.sonatype.org/sites/m2e )
The natural thing for maven projects in a workspace, would be to have a
parent POM in the workspace itself.
Is there a way to create and main
> -Original Message-
> From: m2e-users-boun...@eclipse.org [mailto:m2e-users-
> boun...@eclipse.org] On Behalf Of Steinar Bang
> Sent: Tuesday, September 25, 2012 3:28 PM
> To: m2e-users@eclipse.org
> Subject: [m2e-users] Creating and editing a parent POM in the workspace
> directory?
>
>
Typical workspace filesystem directory structure looks like
workspace/
parentA/
moduleA1/
pom.xml
moudleA1/
pom.xml
pom.xml
parentB/
...
During project import m2e will logically (!) flatten nested directory
structure and create workspace projec
Hi,
I have updated all the entries in the catalog that I have access to, and the
build job for the staged version of the catalog is passing:
http://ci.tesla.io:8080/job/m2eclipse-discovery-catalog-stage/36/console
Users who want to try the updated version of the catalog can do so by adding
-D
It would be nice if http://repository.tesla.io:8081 could be moved to port
80 so that those of use behind a corporate proxy can connect to it more
easily.
Thanks,
Mike
On Tue, Sep 25, 2012 at 5:42 PM, Jason van Zyl wrote:
> Hi,
>
> I have updated all the entries in the catalog that I have acces
12 matches
Mail list logo
