On Mon, Sep 28, 2009 at 10:58 PM, Daniel Kulp wrote:
> That said, you DO need to tell it where your workspace is. You can use the
> -D flag on the command line if you want. For me, I added a activeProfile to
> my settings.xml:
>
>
> extra
>
>
> extra
>
On 2009-09-28, at 6:28 AM, Daniel Kulp wrote:
On Sun September 27 2009 5:37:24 pm Jason van Zyl wrote:
On 2009-09-27, at 2:08 PM, Roland Asmann wrote:
Again, the way we work DOES have real workspace resolution. The
maven-eclipse-plugin makes the projects in the reactor reference
each
other
On Sun September 27 2009 5:37:24 pm Jason van Zyl wrote:
> On 2009-09-27, at 2:08 PM, Roland Asmann wrote:
> > Again, the way we work DOES have real workspace resolution. The
> > maven-eclipse-plugin makes the projects in the reactor reference each
> > other PER DEFAULT, and any other projects in t
> On Mon, Sep 28, 2009 at 7:07 AM, Jason van Zyl
> wrote:
>>
>> I just ran it on a project and that's not what it did. I'm not talking
>> only about multi-module projects but other projects you may refer to.
>> I'm often working on several related projects where I need to work with
>> them all at
On Mon, Sep 28, 2009 at 7:07 AM, Jason van Zyl wrote:
>
> I just ran it on a project and that's not what it did. I'm not talking only
> about multi-module projects but other projects you may refer to. I'm often
> working on several related projects where I need to work with them all at the
> sa
On 2009-09-27, at 2:08 PM, Roland Asmann wrote:
On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will
force
a build of project a... but all the jar files will be installed
into
a
>
> On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
>
>>>
>>> On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
>>>
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local m
On 2009-09-27, at 1:40 PM, Roland Asmann wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository (~/.m2/rep
>
> On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
>
>> if you're using the m2eclipse plugin, building project b will force
>> a build of project a... but all the jar files will be installed into
>> and resolved from your local maven repository (~/.m2/repository),
>> not the target directory.
>
On 2009-09-27, at 8:30 AM, Nayan Hajratwala wrote:
On Sep 27, 2009, at 11:26 AM, Jason van Zyl wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will
force a build of project a... but all the jar files will be
installed in
On Sep 27, 2009, at 11:26 AM, Jason van Zyl wrote:
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed
into and resolved from your local maven repository (~/.m
On 2009-09-27, at 6:59 AM, Nayan Hajratwala wrote:
if you're using the m2eclipse plugin, building project b will force
a build of project a... but all the jar files will be installed into
and resolved from your local maven repository (~/.m2/repository),
not the target directory.
The JA
if you're using the m2eclipse plugin, building project b will force a
build of project a... but all the jar files will be installed into and
resolved from your local maven repository (~/.m2/repository), not the
target directory.
Not sure why you would want the jar files in your target direc
I have configured Multiple project in my eclipse workspace and each project
has its own POM.XML . I have worked with the dependencies with single
eclipse project with multiple modules in that single project and it works
fine when build with Maven but when working with Different projects is there
an
14 matches
Mail list logo
